- Sep 17, 2018
- 4,451
- 5,665
My bad for asking you. I didn't know that the dev was like that. My earliest save actually had the same bug, and the one before that was hours of work behind. I'll just restart the game from scratch...again, lol. Sorry though
If it can be fixed, the fix is already in my mod. Feel free to try it outNo need for apologies. It's the dev I have issues with, not really your request. You might try asking srksrk-68 if he'll produce a fix since he's still actively producing a mod for the game.
A little background: The game represents the characters as state machines, and they change states when triggered by triggers that occur while proceeding the story. The game has rollback disabled by default for a reason because those state transitions cannot normally be rolled back. When a saved game is loaded, the sequence of all triggers that occured so far is re-played on all state machines so that, in theory, the current state is reached.
When such a trigger chain is broken, it may be that a trigger is being applied to a state maching that has the wrong state, so that the target state will not be reached and it stays in the current state. As a result, all following triggers run void as well because they assume a further progressed state already.
The mod fixes that in a way that whenever a trigger cannot be applied to a state machine, it does a depth search on all triggers and states to find a path from the current state to the target state of the current trigger, and applies all those triggers before. That way, the current trigger can be applied and the state can correctly progress.
That will work in most cases, except when it is so broken that a certain search depth is reached, in which case it will stop searching to prevent deadlocks. However, I never encountered such a case.