|
Post by anon on Oct 11, 2017 12:34:34 GMT -8
___________________________________________
############################################################################################
FATAL ERROR in
action number 1
of Alarm Event for alarm 7
for object obj_dungeon:
Unable to find any instance for object index '100174' name '<undefined>'
at gml_Script_scr_convo_status
############################################################################################
--------------------------------------------------------------------------------------------
stack frame is
gml_Script_scr_convo_status (line 0)
gml_Object_obj_dungeon_Alarm_7
|
|
|
Post by DukeFluffy on Oct 11, 2017 15:06:23 GMT -8
This managed to sneak past me. If I am able to recreate the crash I'll release a hotfix.
Thank you for the report.
Edit: Found, fixed, etc. There were two issues- first, the player might go to the Kompound (without Kobold Knight), which would most likely result in a crash when it tried to call 'conversation flags' from his object without him existing. That's simpler to fix, and was the result of the code overhaul. The second issue was that an enemy mob might spawn in the first room right on top of the player, just as Kobold Knight was beginning a conversation. Because most objects are disabled during battles, the conversation would try to access those same variables and also crash. I was able to fix both by adding in exceptions to the first issue and making mobs in the first room of the Kompound start at least 400 pixels away from the player. I'll no doubt change that to apply to all dungeons at some point in the near future.
|
|