quoted instructions about betonquest HOT 1 CLOSED

I believe the Tokenizer API proposed in #2762 should not just split on whitespaces and around quotes, but also collect more information for a particular instruction. Similar to what #2749 did, preprocess optional arguments. The issue with that PR was that without a set of requirements, it would take any key-value argument as valid. (Ex. minecraft=diamond)

Invalid instruction item minecraft:diamond
Valid instruction item 'minecraft:diamond'

To handle this and reduce the repeated use of key-value string patterns or their raw instruction, I propose passing those requirements to the parser during initialization. Another API would be used to predefine its structure.

The requirements could include

• # of required arguments, or unlimited (for notify and variable events)
• valid keys for optional arguments
• set of predefined flags

Proposal for setting flags

login events:welcome_message --flags:global,persistence
login events:welcome_message --f:global,persistence

This change would make it easier to parse and to enforce a particular order
<identifier> <required arguments>... <optional arguments> <flags>

It would also mean using a different syntax for handling run events, as it does not work with nested conditions.

Another solution to this would be quoting each nested instruction.
run 'tag add beton' 'give emerald:5 condition:nested_condition' conditions:main_condition

from betonquest.