Rework plugin messaging handling and API
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
The current plugin messaging handling logic is less than ideally structured. It is part a hack to make Forge happy, part meant to keep the Minecraft client happy, and part embellishment. This is one of my least favorite parts of the Velocity code base by far. While progress was made in Velocity 1.1.0 to clean it up it is still not where I'd like it.
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
No files, tests, or entry points are named. Start by mapping the existing plugin messaging handling in the Velocity codebase and its separate Forge and Minecraft client responsibilities; document the intended API boundary and verify compatibility with both consumers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100