the idea of the standard is nice, but this is community set like it was in bukkit. its up to the developers how they wanna make their plugins, and we enjoy our freedom over such. the standard shouldn’t be enforced, rather it should only be a reference as to how they should make their plugin should they choose to follow it.
and those extra commands like /wg instead of /worldguard are a built-in feature, they’re references to the same command. aliases are nice. they can also be overridden.
Why limited? It’s only a Standard defined by the community, maybe backed by a java library that creates files like the help and permission config.
It just recommends you to do it that way, it does not force you
The title is unrepresentative of the purpose of a standard, the purpose is to allow consistency not to limit anything. Consistency would allow better cross plugin compatibility. Even with a standard one would not be limited on any of the mentioned accounts, command names, permission nodes and file names would still be limitless. They would just be ether more explicit or fuzzy, depending on the intended result on a per-instance basis.
