Server Setup:
- Proxy: Velocity
- Backend: Purpur 1.21.11 (Single backend server)
- Geyser / Floodgate
The Bug:
The proxy extension enters an infinite self-feeding merge loop (backend #0 vs #0), throwing constant Duplicate bedrock_identifier warnings. During this loop, it creates massive amounts of _bedrock_merge_scratch_* directories inside the work/merged/ folder. These scratch folders are never cleaned up, which rapidly fills the entire proxy disk space and crashes the proxy container.
Inbox Status:
The work/inbox/clanes/ folder is clean and correct (only contains Bedrock.zip and mappings.json, no duplicate backend folders). The issue is entirely within the merge process.
Workaround:
We had to remove the RSPM jar from Velocity, delete the bloated work/merged/ folder to reclaim space, and place the backend's Bedrock.zip directly into Geyser's packs/ folder manually.
Server Setup:
The Bug:
The proxy extension enters an infinite self-feeding merge loop (
backend #0 vs #0), throwing constantDuplicate bedrock_identifierwarnings. During this loop, it creates massive amounts of_bedrock_merge_scratch_*directories inside thework/merged/folder. These scratch folders are never cleaned up, which rapidly fills the entire proxy disk space and crashes the proxy container.Inbox Status:
The
work/inbox/clanes/folder is clean and correct (only containsBedrock.zipandmappings.json, no duplicate backend folders). The issue is entirely within the merge process.Workaround:
We had to remove the RSPM jar from Velocity, delete the bloated
work/merged/folder to reclaim space, and place the backend'sBedrock.zipdirectly into Geyser'spacks/folder manually.