-
Notifications
You must be signed in to change notification settings - Fork 568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GM commands randomly ordered #213
Comments
I think alphabetical order is best, since it would follow the structure of the page |
depends on the commands though, but alphabetical would solve most of the issues I guess (unless there is a stupid command like the old "morph/demorph") |
Alphabetical order will be by far the easiest to maintain. I think we should put everything in alphabetical order by default and make as few exceptions as possible. I think morph/demorph or similar dox/undox would be useful to group though. |
I'm currently working on alphabetizing commands. As I'm going through this, I'm realizing that commands would be more discoverable if they were grouped by some sort of category. For example, I was using the |
* Alphabetize GM Commands * Place main commands before subcommands (eg. .teleport comes before .teleport name) * Order commands starting with `un` as if they did not have the `un` prefix. * This places them next to their opposite command * For example, possess will be next to unpossess, and both will be in the `p` section (eg. 1. player learn, 2. possess, 3. unpossess, 4. quest) * Place `showarea` and `hidearea` commands next to each other, in the `s` section
now they have been alphabetized! but if someone ever wants to work on grouping them by logical order, it's gonna be a not so easy job! |
Reorganize the commands by LOGIC (or alphabetical order)
example: .cheat commands are randomly inserted, hard to browse
http://www.azerothcore.org/wiki/GM-Commands
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: