Server.properties bug - non-admin players get kicked for spam when sending a single message
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
Setting either 'chat-spam-threshold-seconds' or 'command-spam-threshold-seconds' in server.properties to 0 prevents players from being kicked for spam when sending chat messages/typing commands.
Observed/Actual behavior
On Paper servers, setting these properties to 0 makes it so you can't send any chat messages/commands at all without being kicked from the server for spam.
On vanilla, however, setting these properties simply makes it so players no longer get kicked for spam, as intended.
Steps/models to reproduce
Create a new Paper 26.2 server and set both 'chat-spam-threshold-seconds' and 'command-spam-threshold-seconds' to 0
Start the server
Without being opped, send a single message or type a single command and see what happens.
Plugin and Datapack List
No plugins or datapacks apart from the built-in ones: [vanilla (built-in)], [file/bukkit (world)], [paper (built-in)]
Paper version
[16:13:54 INFO]: Checking version, please wait...
[16:13:54 INFO]: This server is running Paper version 26.2-84-main@26e81c4 (2026-07-26T18:11:33Z) (Implementing API version 26.2.build.84-stable)
You are running the latest version
Other
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce on a Paper 26.2 server using both server.properties thresholds set to 0, then send one chat message and one command as a non-opped player. Compare the behavior with vanilla and trace the server's spam-check handling for these settings. Done means each single message or command is accepted without a spam kick, matching vanilla behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100