Same shipreck different loot
Open
kqrrot2227 messagesstarted Jun 25, 2026, 11:42 PM
kqrrot2227 messagesstarted Jun 25, 2026, 11:42 PMgameplay
kqrrot222OP3 months agoDon't have evidence as me and Vylence weren't recording, but me, @Vylence and @happygolucky were playing in a blackout lobby. Me and Vylence commed that we got 4 iron from the chest, and happy said we were crazy and he got 12. After the game we recreated the seed, and the loot table for me and vylence was what happy got, but it was definitely only 4 when we were in the lobby.
Not sure of a vanilla minecraft mechanic that can do this? We tried diff chunk gen, but dont think that has an impact on chest loot anyway. Would be really annoying if this happened in a comp game and not a lobby.
(logs as well but dont think they provide anything useful) https://mclo.gs/1jYMg4Q + specific bit of logs from game start to after shipwreck looted.
Not sure of a vanilla minecraft mechanic that can do this? We tried diff chunk gen, but dont think that has an impact on chest loot anyway. Would be really annoying if this happened in a comp game and not a lobby.
(logs as well but dont think they provide anything useful) https://mclo.gs/1jYMg4Q + specific bit of logs from game start to after shipwreck looted.
3788 lines | 2 errors
1
Background PinguApp3 months ago(edited)
purple_carrot
2 Issues Found:
You likely have too much RAM allocated, which can cause lag spikes.
You should allocate 3400-5600 MB by going to Settings > Java in Prism. You're using an outdated Prism Launcher version. To update, simply press the Update button in Prism.Page 1/1 • Prism 26.1.1 Draftout log
kqrrot222OP3 months ago
Diff wood type shipwreck as well (could check the original world)
kqrrot222OP3 months ago
https://discord.com/channels/1493030345048719483/1513756802196705290 So identical to this mb for not looking hard enough
kqrrot222OP3 months ago
And evidence of different loot tables as i didnt loot food chest or map chest
kqrrot222OP3 months ago
6384860572011009202 seed
Fox4 🦊2 months ago
I'm gonna presume this was fixed by the new chunk generation