There is, that’s why I made this plugin. I honestly doubt the team should ever fix it, personally I’m a fan of the underline, and not a fan of the petty arguments it was causing. So I decided Why don’t we have both
I will also take requests for features that might otherwise be missed or considered not core to Sponge, so at this stage while it might just be a formatting fix, I plan to add features + templates once the next version of the Text API hits.
If the plugins are using CommandSpec (the easy way to create commands) they just need to add .permissions(“example.command”) to their CommandSpec.builder().arguments(…).build() builder chain.
If they implement CommandCallable themselves, they need to implement testPermission themselves.
If the plugin does this correctly, and it’s still not working, either it’s a bug in sponge, or the player really does have permission for the command (maybe they are opped and the permissions implementation gives them the permission?)
Hm, I wonder if there is something I could do to help with this… Got any ideas? Blacklisting commands from forge mods from appearing or mis-behaving plugins is exactly the sort of feature I’d consider if you have any rough ideas on how it should work.
Make it so it breaks down the first help page into plugin categories. Then when you click the plugin it will give you the commands for just that plugin!
How do I jump to any page? For example, something like /help -p 10. There is /page command, but it’s useless without internal UUID.
Edit: I figured it out. It’s “/page page 10” for viewing page 10. (Though UUID was non-optional parameter… I dunno what’s up with that)
How do I get help for child commands? Like /help mycmd add, or /help mycmd admin purge.
For example, for this command tree: mycmd ├add ├change │├name │└coords └remove
“/help mycmd change” should display grandchild commands “name” and “coords”, and “/help mycmd change name” should display description.
Also, is it possible to display all aliases for given command?
