Velocity not syncing datapack registries correctly, affecting modded fabric platforms
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
In the example of Supplementaries, players are kicked when using items that call to a specific api. I've reported this to the developers, and they're stating that velocity isn't handling the sync of datapack registries correctly.
Here's the client crash that's happening:
https://gist.github.com/purejosh/c6da9ecba61745eb4ccf69737ea2fc25
Please let me know what other info you may need. Might be easier to start an open conversation with the dev of Supplementaries, MehVahdJukaar.
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
Start by reviewing the linked client crash report and the Supplementaries example, then reproduce the kick on a modded Fabric platform. Trace how Velocity synchronizes datapack registries and compare the result with the registry expected by the affected API. Done means the reported item interaction no longer kicks clients and registry synchronization is verified.
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