CancelledPacketHandleException: null

[andrewkm]

Paper 1.19.4 Build 484
CrazyCrates compiled against 2417a0e

Just witnessed a user do the following:

[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast lost connection: Kicked for spamming
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine

All within the same second.
When questioned, he stated he had the command on a macro while in a minecart.

Immediately after the console literally blew up as such:
https://pastebin.com/raw/eqDEDhyJ

This spam continued for a good 3-5 minutes before it finally stopped.

[TrueDarkLord]

Paper 1.19.4 Build 484 CrazyCrates compiled against 2417a0e

Just witnessed a user do the following:

[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast lost connection: Kicked for spamming
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine
[21:54:49] [Server thread/INFO]: TescosToast issued server command: /cc open starmachine

All within the same second. When questioned, he stated he had the command on a macro while in a minecart.

Immediately after the console literally blew up as such: https://pastebin.com/raw/eqDEDhyJ

This spam continued for a good 3-5 minutes before it finally stopped.

Use external plugins or base server features to limit packets, and to make it even better, limit the overall command and messages that can be sent in a specified amount of time.

[andrewkm]

We already limit packets and commands, I've been attempting to reproduce with macros of my own and cannot, I have no idea how they managed to do this.

They mentioned they saw the "crate already open" message, perhaps something glitched out and ran them all at once.

None the less if a fix isn't planned for this we can fork and figure it out.

[ryderbelserion]

well, better late than never

[ryderbelserion]

I'll add a cooldown option for commands, would that be enough?

[andrewkm]

Sure that would be nice :)
I closed it as I was just going over all my authored github issues to clean them up a bit, and haven't had this happen again since the report so figured it was fixed.