PaperMC / PaperMC/Velocity

Disable Redirect on Server Disconnect Config Option

Open
#1,410 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: feature
Dominant language
Java
Stars
2.3k
Forks
959
Avg merge
5d 10h
Merged PRs (30d)
2

Description

Requested Feature

The try section is for both initial connections to the server and also if a player gets kicked, this request is to make it so that the try section is just for initial connections, and all backend server disconnects do not redirect the player. When players get kicked from any server, they should be kicked from the proxy as well under this configurable option.

Why is this needed?

Queue systems are currently buggy and the implementation is weird on Velocity. The backend server disconnects will simply boot the players into the queue server, resulting in a reconnect loop that cannot be broken. An option to not redirect players after initial connection to the proxy will solve this.

Alternative Solutions

I've tried contacting plugin developers and getting something made on the plugin-side. This was not possible or successful.

Additional Information

No response

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 tracing how the proxy handles initial connections and backend server disconnects, focusing on the existing try-section behavior. Define a configuration option that preserves initial connection attempts but prevents redirects after backend disconnects, and verify that affected players are disconnected from the proxy instead. No specific files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
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.