While developing and playtesting a scripted event from 7.0, I came upon the discovery that out-of-party forced after turn actions can cause full game crashes under certain circumstances. I can't get to all of them right away, but I will be removing all of these types of interactions from the game code rather than try to repair them. This situation is most common with the discoverable character Ares, but also occurs in some instances with others. A standalone fix cannot be deployed at this time, and this will be addressed with 7.0. In the meantime, to avoid this crash, its best to let Ares either deliver the final blow, or deliver the final blow with anyone except the character who would attack last or end of turn damage over time effects. Ex: In a party of 4 characters, the fastest 3 attackers are safe, while the final attacker and the DoT proc are both unsafe.
This also caused a considerable hiccup in developing one of the major scripted events in Obscurite which now needs to be completely rewritten. We'll talk about in the postmortem in January what exactly was there before it was removed, as opposed to what will actually launch with 7.0.
How You Can Help
- If you discover any full game crashes with yellow code appearing on the side, please let me know where exactly in the game world this happened so I can lock down which troop it is. The game might seem small, but there are over 2000 Troop pages and ~10% of them have multiple pages. It would take a considerable amount of time (that I don't have) to comb through every one preventatively. I have already marked two specific Ares battles, plus two after-turn Alex and Ruby battles for permanent change.
- This also applies to any game crash, not just battles. Please report them ASAP so I can address them all together this month.
Thank you for your time on this matter
//hardytier