Author Topic: Fatal error if a custom enemy created on a platform  (Read 236 times)

Alley

  • The Blue Leader
  • Level 14: Grooper
  • *
  • Posts: 496
  • Deals with art in PC and acting and drawing
    • View Profile
    • Team Alju5
Fatal error if a custom enemy created on a platform
« on: December 01, 2018, 10:32:44 PM »
If a moving platform is in touch with a custom enemy before it will be visible then a fatal error ends the game. This error is similar to the other errors I have reported about built-in object touching custom one in a first step of creation...

Code: [Select]
___________________________________________
############################################################################################
FATAL ERROR in
action number 1
of  Step Eventobj_platform
for object obj_custom_enemy:

Variable obj_custom_enemy.type(100497, -2147483648) not set before reading it.
at gml_Object_obj_custom_enemy_Collision_c0f37d60_b4d1_468d_8da0_aa659a2ced1d
############################################################################################
--------------------------------------------------------------------------------------------
stack frame is
gml_Object_obj_custom_enemy_Collision_c0f37d60_b4d1_468d_8da0_aa659a2ced1d (line -1)
Alley (T_Alj5)

Christian Game Maker

  • Currently developing Project ASM (The Adventures Of Super Mike) And manager of platformbuilderfansite.weebly.com!
  • Level 21: Magmus
  • *
  • Posts: 1949
  • The way of the Cross leads home.
    • View Profile
    • The Adventures of Super Mike Website (ASM)
Re: Fatal error if a custom enemy created on a platform
« Reply #1 on: December 01, 2018, 10:59:12 PM »
Hmm... Interesting.
Christian Game Maker: 3:16 Numbers Of Hope

TingThing

  • Admin and Developer
  • Level 15: Spreker
  • *
  • Posts: 526
  • Creator and Developer of Platform Builder
    • View Profile
    • Platform Builder Home
Re: Fatal error if a custom enemy created on a platform
« Reply #2 on: December 08, 2018, 04:32:11 PM »
Just for the record, the latest version should have this fixed now. I didn't include that in the updates because I wasn't certain if it was completely fixed, but I'm pretty sure it is.