What changed
2 fixes0 additions0 changes0 removals
fixedA bug report from a player highlighted something which has been in the game since the start, but only very very rarely hits. The bug is that if you move an NPC while you're in combat, the game can crash. This is something I've tested many times before and found working fine, but when I tried to reproduce it myself after reading the bug report, it hit the first time! And then proceeded to not hit again all the other times I tried to reproduce it afterwards. Turns out it's a very specific timing issue that hits if you move an NPC while in combat less than 250 milliseconds before the next round is processed. 250 milliseconds is the default interval the game waits after seeing the most recent file system change before processing it, to make sure it handles batches of changes properly. Because the game would be waiting for this interval before processing the change, when the next round of combat was resolved it was trying to use the old file paths of the NPC, resulting in a crash! So there you go.
fixedFix for game logic processing updates while file system change processor is waiting for batches of updates, resulting in the game using out of date file system information.
Directory Dungeon - File Explorer Dungeon Crawler changes
fixedA bug report from a player highlighted something which has been in the game since the start, but only very very rarely hits. The bug is that if you move an NPC while you're in combat, the game can crash. This is something I've tested many times before and found working fine, but when I tried to reproduce it myself after reading the bug report, it hit the first time! And then proceeded to not hit again all the other times I tried to reproduce it afterwards. Turns out it's a very specific timing issue that hits if you move an NPC while in combat less than 250 milliseconds before the next round is processed. 250 milliseconds is the default interval the game waits after seeing the most recent file system change before processing it, to make sure it handles batches of changes properly. Because the game would be waiting for this interval before processing the change, when the next round of combat was resolved it was trying to use the old file paths of the NPC, resulting in a crash! So there you go.
fixedFix for game logic processing updates while file system change processor is waiting for batches of updates, resulting in the game using out of date file system information.
Quick update before InterfaceX26 starts tomorrow.
A bug report from a player highlighted something which has been in the game since the start, but only very very rarely hits. The bug is that if you move an NPC while you're in combat, the game can crash. This is something I've tested many times before and found working fine, but when I tried to reproduce it myself after reading the bug report, it hit the first time! And then proceeded to not hit again all the other times I tried to reproduce it afterwards. Turns out it's a very specific timing issue that hits if you move an NPC while in combat less than 250 milliseconds before the next round is processed. 250 milliseconds is the default interval the game waits after seeing the most recent file system change before processing it, to make sure it handles batches of changes properly. Because the game would be waiting for this interval before processing the change, when the next round of combat was resolved it was trying to use the old file paths of the NPC, resulting in a crash! So there you go.
Simple fix is to not process any game logic updates while waiting for batches file system changes :)
v1.18 Changelog
