PaperMC / PaperMC/Paper

Chat Validation Error while using Velocity and Version 1.20.4

Open
#10,800 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs triage type: bug version: 1.20.4
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

Players to chat and then run commands without being kicked.

Observed/Actual behavior

Players typing in chat, then run a command and it fails to validate message acknowledgements, resulting in kicking them from the server. Even lowered from Purpur (a fork of paper) down to paper, and velocity to a lower version before 1.20.6 support. Issues still persist.
PaperServer
VelocityServer

Steps/models to reproduce

Use Velocity and Paper Version 1.20.4 to type in chat at least twice, then run a command like gamemode spectator.

Plugin and Datapack List

Started with a lot of plugins, eventually moved all of them away to try to fix the issue. Result was same issue.

Paper version

Paper:
[00:17:34 INFO]: Checking version, please wait...
[00:17:35 INFO]: This server is running Paper version git-Paper-496 (MC: 1.20.4) (Implementing API version 1.20.4-R0.1-SNAPSHOT) (Git: 7ac24a1 on ver/1.20.4)
You are running the latest version
Previous version: git-Purpur-2176 (MC: 1.20.4)

Velocity:
[00:06:52 INFO]: Booting up Velocity 3.3.0-SNAPSHOT (git-be678840-b378)

Other

I have been trying to work on this issue for 3 full days. I usually use Purpur due to my server using features like 6 row enderchests. I dropped it down to Paper to see if this issue kept happening. This issue could be on either Paper or Velocity's side. It only happens on version 1.20.4. I switched from Bungeecord forwarding to modern, changed all the server configs, even deleted them all and moved plugins away, and the issue stayed. I joined from local IP and domain both to test.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with Paper 1.20.4 and Velocity 3.3.0-SNAPSHOT, using the stated chat-then-gamemode sequence. Review the validation and kick output from both servers, then determine whether the behavior remains with plugins removed and whether it belongs to Paper or Velocity. Done means chat and commands work without message-acknowledgement kicks.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.