PaperMC / PaperMC/Paper

Possible issue with PluginMessages to clients

Open
#8,668 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Expected behavior

When joining the server, if the port that the simple voice uses is open, the simple voice will connect to the client in 100% of cases (if mod installed)

Observed/Actual behavior

When you use paper, voice chat will ALMOST (occasionally, randomly) not work:

  • From time to time (as if randomly) when joining the server, the plugin will not be able to authorize the player. According to my observation, this most often happens at the first login to the server.
  • If you do the steps below.
Steps/models to reproduce

This plugin will not be able to authorize the player (and voice chat will almost not work) if you do the following:

  1. Create a new paper server.
  2. Install simple voice
  3. Log in to the server
  4. Fly around the world (away from spawn) for about a minute
  5. Get down, break some blocks
  6. Log out of the server
  7. Stop it right away
  8. Start again
  9. Log in 5-6 seconds after server start
  10. You will see the problem.
Plugin and Datapack List

Datapacks: 0
Plugins (1): voicechat (simple voice)

Paper version

paper 1.19.2-307

Other

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

No Paper files, tests, or code entry points are named. Start by reproducing the restart-and-reconnect sequence on Paper 1.19.2 and compare it with Spigot, then review the linked Simple Voice Chat investigation and Discord discussion. The issue is resolved when the authorization failure is explained and a verified fix or regression test covers the scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.