-
Notifications
You must be signed in to change notification settings - Fork 3
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
Crash in most recent experimental version #5
Comments
Hey! This is a known issue on experimental. There are breaking changes between stable and experimental on the gamesave system, which causes FloodgateMod to crash when the game saves if there are existing link between floodgates and streamgauges. I will fix this when experimental hits stable. Unfortunately that also means that in experimental only the drought/schedule settings will work. Sorry for the inconvinience! |
I realized after looking through the closed issues that this was a known issue, I think it would be best to leave it open so that others like myself don't think this is a new issue. |
Good call, leaving open until current experimental hits stable |
https://github.com/R-T-B/Timberborn-SimpleFloodgateTriggers/releases/tag/1.0.3 For those who want, working build for experimental. No plans to takeover or anything, this is an interim thing just until next stable. Source is at same repo. |
Mods used:
BepInExPack, TimberAPI, Simple Floodgate Triggers, Tiny Warehouse, More Platforms, Ladder
Recreation of the bug:
Playing without setting any triggers will not yield a crash. Setting a floodgate to trigger based on water level marker causes my game to crash within a few in-game days. Not entirely sure, but it also only crashed during a drought, this may be due to when I set the trigger or part of the bug.
Additional Information:
Possibly related, the floodgate I tried to set up does not affect adjacent floodgates regardless of whether sync was turned on. I tried turning sync off to see if it would no longer crash, this did not help. Also, I did not try any other trigger settings, as this is the one trigger I desire, although the bug may also be present with other trigger options
The text was updated successfully, but these errors were encountered: