First, so what's new?
- Fixed some bad text (wrong name for Zenji family)
- Fixed a bug in the final battle when a certain character's HP hit 0 on the nose
- Fixed THE BUG where very rarely interacting with something (NPC, chest, object) would make the game soft lock
At long last! Man, since release there was that aforementioned bug. For anyone interested, here was the flow when you went to interact with something:
- Approach thing
- Hit confirm
- There's a ray cast (not visible to the player)
- If the ray detects an interactable...
- Set global.interacting to true (this is a flag that blocks player input other than for interacting purposes... also at some point I put in a guard here, so at some point it'll switch to off if there's no text box detected)
- Set some properties on the thing you're interacting with (lock them in place, update flags if relevant)
- Pop open the text box
- Conclude interacting
- Set global.interacting to false upon completion of interacting
So I was watching a video of Multiplayer Dungeon playing PSRO (link), and noticed when completing a quest, it bypassed the actual quest completion dialogue. This got me to think about/dig into the process listed above. So I opened up like 20 apps and 30 browser tabs, which made my game lag super bad. In Godot's debug box, I saw *something* broke down in steps 6 or 7. The flag got updated, but no text box ever popped up. So on the one hand, I'm still not 100% sure what caused the bug (definitely lag-induced), but I did think of a solution. Rather than setting global.interacting to true immediately upon attempted initiation of interacting (and if that flag stays on, no walking/menu inputs are registered), I pushed off global.interacting and updating of quest flags to as the text box opens. So if the text box fails to open, the only indication that anything went wrong is you'll hit confirm near to something and there's just no response.
Long story short, not a 100% fix, but I pushed 5 and 6 above to be after 7. Treats the main symptoms at least.