Rework: Commands

[Wolf2323]

The command syntax grew historically and does not fit the users current needs.
This rework should clarify & unify command syntax across the plugin. Additionally, new commands should make new administrative options possible.
Explanation: Arguments in <> are mandatory, [] is optional, CAPS are keywords.
Contributing changes and new commands: Join the discussion by commenting.

Unmodified Commands

• /q condition
• /q item
• /q give
• /q config
• /q delete
• /q rename
• /q vector
• /q version
• /q update
• /q reload
• /q backup
• /q create
• /q debug
• /questlang
• /compass
• /cancelquest

Modified Commands

• /q purge
  • Add a argument for a specific quest package
  • New format: q purge <EVERYONE|name> <tags|points|objectives|journal|backpack|EVERYTHING> [ALL_PROFILES]
  • Add a confirm dialog (with authentification?)
  • Different permissions for purging the own profile vs. different profiles vs. all profiles
• /backpack
  • Add a player Argument to open a Player backpack
  • Refering: Command for backpack of a player #385
• /q objective
  • Add Syntaxt to allow the remove of all objectives from one package
  • Refering: Better Tag managment #864
• /q tag
  • Add Syntaxt to allow the remove of all tags from one package
  • Refering: Better Tag managment #864
• /q point
  • Add Syntaxt to allow the remove of all points from one package
  • Refering: Better Tag managment #864
• /q globaltag
  • Add Syntaxt to allow the remove of all globaltags from one package
  • Refering: Better Tag managment #864
• /q globalpoint
  • Add Syntaxt to allow the remove of all globalpoints from one package
  • Refering: Better Tag managment #864
• /q journal
  • Add Syntaxt to allow the remove of all journal entries from one package
  • Refering: Better Tag managment #864
• /q event
  • Add a silance flag to the command
  • Refering: Silence console output with a "silent" flag in /q command #620
• Add a new subcommand that returns the value of the given point variable. The same could also be usefull for objectives / conditions (progress / true|false). Could also be solved through command "inline variables".
  • Refering: Point, Condition, Objective, etc Parsing (List Alternative) #1387
• /journal
  • a way to open a journal directly with a sub command

Removed Commands

New Commands

• /q search
  • Seach for Tags, Objectives, Points in the database for all Players
  • Refering: Add a Search Command #900

Conceptual Problems

Some command senders (commandblocks) cannot accept a command response message async. These repsponses must be scheduled to run on the next tick.

[MonzterDev]

/q purge <Objective/Tag/Points> <player>
You can choose either a specific Player or if Player isn’t defined it’ll apply to everyone, which can remove specific or all Objectives, Tags, or Points

[SaltyAimbOtter]

Added to the list. Thanks for the contribution 😀

[Wolf2323]

Also purge per quest package should be added here

[seyfahni]

Small addition to /q reload: Titanium mentioned that we should add journal entries and items to the post-reload statistics too. With the new instruction system (that would maybe also allow adding new types) it might be better to let things add themselves to something like a statistics collector that then dynamically print all the stats out. This might also be reusable for BStats.

[MonzterDev]

A command which you can execute an uncreated event, but you create the event in the command
For example /q eventTest MonzterSlayer command q point add items.Test 100
It’s a way of basically executing an event to test if it works.

[seyfahni]

For all the commands that output long lists (tags, objectives etc.):

• Add filtering / search
• Add pagination