Backend transport independence
Open
Nobody has claimed this yet.
type: feature
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
Velocity should provide transport-independence. This will allow two important use-cases:
- Other, possibly more efficient encodings of the Minecraft protocol (or even tunneled implementations like Minecraft over WebSocket).
- Velocity-internal servers (limbo servers could be implemented as a Velocity plugin).
It is not a goal for Velocity to support frontend transport independence at this time.
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
The issue names no files, tests, or entry points. Start by mapping Velocity’s backend transport and server-connection code, then determine how protocol encoding and internal servers would be separated from the current transport. Done would mean supporting alternate or tunneled backend transports without requiring frontend transport independence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100