dr3ams / Roguelike-Adventures-and-Dungeons-2

Roguelike Adventures and Dungeons 2
https://www.curseforge.com/minecraft/modpacks/roguelike-adventures-and-dungeons-2
Other
57 stars 17 forks source link

[Bug]: Lootr Chests sometimes stop spawning loot #193

Open Kyruh opened 1 year ago

Kyruh commented 1 year ago

General Info

Your launcher

Curseforge

Modpack version

1.0a

Describe your issue

While exploring the many dungeons I've noticed the chests from lootr sometimes don't spawn any loot. They'll be gold indicating I haven't opened it yet, so then I do and it's completely empty. Chest turns silver and can't get any loot. Usually a restart of the client will fix it temporarily but the issue always comes back and I keep missing out on loot. Once the chest turns silver, I miss out on the loot forever. Restarting it doesn't make the loot that was supposed to spawn, spawn. This happens mostly with the tiny 3 dungeon that have a mob spawner in each room. (Underground typically in caves)

While making a new world in creative singleplayer, opening chest after chest I can't repeat the issue. It only seems to happen in my singleplayer survival world. I can't reproduce the issue at will but it happens repeatedly in my singleplayer survival world.

Steps to reproduce the issue

  1. Find a lootr chest 2. Open the chest (chance it won't have any loot at all and then continues to do that with every future chest)

That's really all there is to it, most of the time I find loot, but then they stop and every future chest I find is empty until I restart.

Additional Information

I don't have any screenshots and I don't know if the log would help here. I haven't been exploring because of the issue and I'm scared of future chests not having loot. I'll be putting the log here anyways.

rad latest log.zip

VanyaBaou commented 1 year ago

It sounds like you're referring to the dungeon that is something like 4-5 half-sphere rooms, which typically have 2-3 chests per room, and 1 vanilla spawner per room. If that is the case, I can confirm it is an issue specifically with one of the two loot tables used for the chests. This should be the relevant problematic loot table: image

If you encounter this in other structures, we would need to know either the specific structure or the loot table registry name There should be a command to get block info with some sub-command from the ct command (something like /ct blockinfo)

Kyruh commented 1 year ago

I will do this once I get home from work today thank you