Bug #144: Quest version usage/admin test mode
| ID | #144 |
|---|---|
| Submitter | Apollo |
| Product | EOSERV |
| Severity | Feature Request |
| Status | CLOSED, WONTFIX |
| Submitted | 1st Oct 2012 |
| Updated | 1st Oct 2012 |
12 years, 13 weeks ago
It would be nice to make use of quest version numbers to update only quests where the version is altered (in case of someone working on multiple quests, only versions changes are updated with request). Also, adding an "admin" or "test" flag to the main state to grant admin only access could benefit a server to allow live testing without the need of a second server solely for testing quests.
Comments
12 years, 13 weeks ago
IsAdmin() could probably serve other purposes as well, like warps to special maps, item spawns (admin clothes for non-item spawners), or whatever administrative task you deem useful enough to have a GUI.
12 years, 13 weeks ago
Admin-only testing can be achieved with a StatGreater("admin", 0) rule check, and resetting the quest if they don't meet the requirements.
A version change was going to be used to mark serious breaking changes to a quest, where all current questers would be forced to restart (though probably leaving people who had finished it alone). That would allow quest state names to be safely reused if the entire quest was redone from start to finish, without worrying about if any of the state names matched (i.e. ''quest 4, version 1, state '''DoStuff''''' would differ from ''quest 4, version 2, state '''DoStuff''''').
Requiring the version to be changed whenever you wanted to reload a quest (even to fix a simple typo) is just a huge hassle for no real gain, where marking progress on a quest with the version number has some kind of tangible benefit.
Updated Status to CLOSED, WONTFIX
Add Comment
Please don't post unless you have something relevant to the bug to say.
Do not comment to say "thanks" or "fix this please".
Please log in to add comments. EOSERV Bug Tracker > Bug #144: Quest version usage/admin test mode