Resourcepack issues while connecting to two backends in a row
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 960
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
If we connect to two backend servers that both have their own resourcepack, switching from the first server to a second one, the second backend will have issues loading the resourcepack, it won't even prompt the user, it will just get stuck without doing anything
however connecting to the second backend directly without connecting to the first one enables the pack to load, keep in mind that both servers have their own different packs
Proxy --> Backend1 (pack loads) --> Backend2 (pack won't load)
Proxy --> Backend2 (pack loads)
I have confirmed this situation only happens while under a velocity proxy.
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
Reproduce the reported sequence through a Velocity proxy: connect to Backend1 with its resource pack, then switch to Backend2 with a different pack, and compare it with connecting to Backend2 directly. Trace the resource-pack handling during backend switching; done means the second backend prompts for and loads its pack instead of becoming stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100