Crashes clients with fabric mods that use ConfigurationTasks
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
Hello. I know that Velocity is still improving its stability with Fabric modded servers, so I wanted to report another bug.
There's a mod called MightyMail, which sends a config packet to clients on login, however these packets are unable to traverse through the proxy. This causes mods like MM to crash when the items are used, as the config packet didn't make it to the client.
The developer for MM said that Velocity would need to support custom ConfigurationTasks, which is a vanilla feature. Does a plugin exist that allows this to work? Or, as a developer that might be more familiar with how Velocity works, is support for ConfigurationTasks possible?
I really want to help make Velocity the absolute best proxy, so anything I can do to help, I will.
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 report names MightyMail, Fabric modded servers, and vanilla ConfigurationTasks but no files or tests. Start by reproducing the login configuration-packet path with MightyMail, then trace how Velocity handles these tasks; done means the custom configuration packet reaches the client without the mod crash.
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
- 30/100