1. Community
  2. Plugin Support
  3. Raid Tracker
Kicked: Packet Flooding: Client CommandFixed
Plugin Page
Posted 6 years ago
Last updated 6 years ago
#1
Hello,

Been recieiving this when non-auth level users are using /x.

(Kicked: Packet Flooding: Client Command)

Any idea how I fix that?

Posted 6 years ago
Last updated 6 years ago
#2
No idea what could be causing this. Rename the command in the config to avoid players from using the command for now.

Settings > Explosions Command > x
Posted 6 years ago
Last updated 6 years ago
#3
In response to nivex ():
No idea what could be causing this. Rename the command in the config to avoid players from using the...
I'd assume ddraw trying to be ran on non-admin clients?
Posted 6 years ago
Last updated 6 years ago
#4
In response to Wulf ():
I'd assume ddraw trying to be ran on non-admin clients?
He's using the admin command, which requires an authLevel to use the command. 

 if (player.net.connection.authLevel < _authLevel && !_authorized.Contains(player.UserIDString)) { player.ChatMessage(msg("Not Allowed", player.UserIDString)); return; }​

So, I'm not sure how this would cause packet flooding. Unless it's ChatMessage? In any event, I've changed player.ChatMessage to Player.Message as a potential workaround.
Posted 6 years ago
Last updated 6 years ago
#5
In response to nivex ():
He's using the admin command, which requires an authLevel to use the command. 

if (play...
Pretty sure both methods send the same way, using the chat.add client command.
Posted 6 years ago
Last updated 6 years ago
#6
Your latest patch has fixed this issue. For clarification, I was trying to allow users without authlevel & added to the config/permissions to use the command.
Locked automatically