-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Errors with mods loaded in a different world #47932
Comments
this also happens with other mods - I have a world with quite some mods and then two for testing stuff where I only have one or so mods; I didn't look terribly deep into the json errors I got but from what I can tell, having aftershock, dinomod or sweet cataclysm in a different world and not in yours also affects your current world at least to some degree |
Harvest lists (and possibly other things) need something like #33312 |
Harvest data from the previously loaded world was not reset, leading to a bunch of errors from unrelated mods in a different world. Add a harvest_list::reset() method to clear the previously loaded harvest list, and call it from unload_data(). Fix CleverRaven#47932
I've had it happen the other way around as well: |
I can reproduce this in 0.E-3, but not in experimental 0.E-9956. It looks like this one was probably fixed last year by #40047. |
Harvest data from the previously loaded world was not reset, leading to a bunch of errors from unrelated mods in a different world. Add a harvest_list::reset() method to clear the previously loaded harvest list, and call it from unload_data(). Fix CleverRaven#47932
Describe the bug
When starting a new game in a new world, the mods in other worlds may cause error messages.
Here is one such message:
Others include:
Steps To Reproduce
Expected behavior
Mods added to world (A) should have no effect on world (B).
Screenshots
Versions and configuration
Dark Days Ahead [dda],
Disable NPC Needs [no_npc_food],
Bionic Professions [package_bionic_professions],
Magiclysm [magiclysm]
]
Additional context
Found when investigating #47924
The text was updated successfully, but these errors were encountered: