packet-limiter action DROP is ignored for book editing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
When packet-limiter is set to DROP, the player should stay connected even if they edit books rapidly.
Observed/Actual behavior
The player is immediately kicked with the message "Book edited too quickly!" despite the DROP configuration.
Steps/models to reproduce
- Set 'packet-limiter.all-packets.action' to DROP in paper-global.yml.
- Remove all plugins.
- Connect via localhost.
- Open a Book and Quill, write text, and click 'Done' very quickly multiple times.
Plugin and Datapack List
None (Tested on a clean vanilla environment).
Paper version
1.21.11 (Build #106)
Other
I confirmed this issue persists even on a local connection with no network interference.
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
Start by reproducing the rapid Book and Quill edits with packet-limiter.all-packets.action set to DROP in paper-global.yml on a clean server. Trace how the book-edit packet is handled and how the "Book edited too quickly!" kick bypasses the configured action; done means the player stays connected under the reported steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100