Skip to content
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

Open
3 of 4 tasks
Mickey42302 opened this issue Mar 30, 2024 · 3 comments
Open
3 of 4 tasks

"/test" command is not registered. #1504

Mickey42302 opened this issue Mar 30, 2024 · 3 comments

Comments

@Mickey42302
Copy link

Mickey42302 commented Mar 30, 2024

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

  • I am running the latest version of Purpur available from https://purpurmc.org/downloads.
  • I have searched for and ensured there isn't already an open issue regarding this.
  • I ticked all the boxes without actually reading them
  • My version of Minecraft is supported by Purpur.

Other

No response

@granny
Copy link
Member

granny commented Apr 8, 2024

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.

@Mickey42302 Mickey42302 changed the title "/test" command is not registered. "/test" and "/resetchunks" commands are not registered. Sep 22, 2024
@granny
Copy link
Member

granny commented Sep 27, 2024

The resetchunks command no longer exists since the release of version 1.21 [1.21-pre1] (it existed from 1.18 [21w37a] to 1.20.6).

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).

@Mickey42302 Mickey42302 changed the title "/test" and "/resetchunks" commands are not registered. "/test" command is not registered. Sep 27, 2024
@Mickey42302
Copy link
Author

The resetchunks command no longer exists since the release of version 1.21 [1.21-pre1] (it existed from 1.18 [21w37a] to 1.20.6).

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants