Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug][Dungeon Reset] "Duping" on Resets #18

Open
illutian opened this issue Sep 14, 2022 · 0 comments
Open

[Bug][Dungeon Reset] "Duping" on Resets #18

illutian opened this issue Sep 14, 2022 · 0 comments

Comments

@illutian
Copy link

Mod Version: 5.4.1605
Game Version: 0.210.6

Note: This was also reported on the Nexus Mod page by a Rakorath. But the actions they performed differ from mine. But resulted in the same outcome; dupes.

I noticed that the locations are not "destroyed" by the mod before regenerating them. This is causing item duplication; the items are 'clipped' into each other.

I tested this out with a Draugr Village (MeadowVillage in the mod settings). What I did was killed all the mobs in a couple of buildings that were "sealed" (mobs could not get out). I destroyed one entire building and a part of another.

I did a dungeonreset command and noticed that the mobs that were in the sealed buildings respawned, the mobs still alive appear to have been left alone, the totally destroyed building was restored (albeit with 'full health' structure pieces), and the partially destroyed building was duped.
...as in the parts I destroyed were restored (again with full health structures) but, also, the pieces that weren't destroyed had new pieces created inside them (you could see the clipping and the Work Hammer on Repair would flip between the two pieces on hover over).

This was following running a dungeon that I had a second run-through. I noticed I was "E-ing" the yellow mushrooms twice..every single time. Then I came upon a Surtling Core, "E-ed" it; looted. But then saw the core still in one of those stands. "E-ed" again and got a second one.
...That's what prompted the above test.

I've also noticed the dungeon layout isn't randomized, even though the code appears to call for the "Destroy"-ing of the area. Not sure if this is intended or part of the bug, so I'll include it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant