-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
"/test" command is not registered. #1504
Comments
Correct. I've purposefully excluded that command from being registered because it's been annoying trying to get it to work without it instantly kicking the player that has permission to use it. It's pretty low on my priority list but I'll keep this issue open in case I end up revisiting it. |
The For future reference please either create a new issue tracker if you find a command that isn't registered or add a comment with new information. (I don't get a notification when you edit the title or issue description). |
Alright, I'll keep that in mind. I've updated the title/description as well since "/resetchunks" is no longer available. |
Spark link
https://spark.lucko.me/D62uie0Ye0
Expected behavior
When the "register-minecraft-debug-commands" setting is set to "true", this should register all of the hidden debugging commands.
Observed/Actual behavior
The "/test" command is not registered when "register-minecraft-debug-commands" is set to "true". The other debugging commands are registered, however.
Steps/models to reproduce
In the Purpur configuration, set "register-minecraft-debug-commands" to "true". When you attempt to run "/test", the server will behave as if it doesn't exist due to it not being registered. The rest of the debugging commands (such as "/raid", "/warden_spawn_tracker", and "/serverpack") will be registered, however.
Purpur version
Current: git-Purpur-2309 (MC: 1.21.1)
Previous: git-Purpur-2308 (MC: 1.21.1)
Agreements
Other
No response
The text was updated successfully, but these errors were encountered: