On my vanilla server, I have a trigger that is executed when players click on some text in the chat, and it's often needed to be clicked repeatedly. But when players click it enough times, they get automatically kicked. It's really annoying, and nobody on my server likes it.
The disconnect.spam kick should be prevented when using click events, or a line should be added to the server properties file to disable disconnect.spam or set it to chat only.
Comments 8
@unknown:
disconnect.spam
@unknown:
On my vanilla server.....click on some text in the chat
No plugins, completly vanilla.
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
Is this still an issue in 1.11.2? If so, please provide detailed steps on how to reproduce this issue.
This is still an issue in 1.21.7.
This affects sign, book, and chat click events, but the quickest way to test this is using dialogs.
Steps to reproduce: Start a multiplayer server, deop yourself, and run this command from the console:
/dialog show @p { "type": "minecraft:multi_action", "pause":false, "after_action": "none", "actions": [{ "label": "Click here!", "action": { "type": "run_command", "command": "trigger dummy add 1" }} ], "title":"MC-101859"}
After that, either click the button repeatedly, or tab-select it and hold down the spacebar. After a certain number of uses, the player is kicked for spamming.
This only happens if the player does not have operator permissions, happens regardless of whether or not the command is successful, and happens regardless of whether or not command feedback is enabled - which means the player can be kicked for spamming the chat without even sending anything visible to chat. And there is no setting to disable this.
Given that the original creator of this ticket seems not to have migrated their account to the new bug tracker, I would be willing to take over maintaining this report once it is re-opened.
What plugin are you using that keeps making everything crash?