Thylacine Studios - Forum

The Vicious Wolpertinger Paradox Crash  (Read 549 times)

Offline Zack

  • Administrator
  • *****
  • Posts: 3386
    • View Profile
Re: The Vicious Wolpertinger Paradox Crash
Reply #2 May 27, 2016, 02:04:03 PM
This should be fixed in 0.0.3 - if you don't have that version already, please restart Steam.
Designer and Programmer of Siralim and The Negative. Follow us on: Facebook | Twitter | YouTube

Offline SirFinbar

  • *
  • Posts: 17
    • View Profile
The Vicious Wolpertinger Paradox Crash
Reply #1 May 27, 2016, 02:02:46 PM
1) Is your issue a bug, or is it a crash?
Crash.

2) If it's a crash, please copy and paste the full error message below, or post a screenshot of it. Otherwise, leave this field blank.

___________________________________________
############################################################################################
FATAL ERROR in
action number 1
of  Step Event0
for object obj_battlecontroller:

Variable obj_battlecontroller.cid(100055, -2147483648) not set before reading it.
at gml_Script_inv_ItemForbidden
############################################################################################
--------------------------------------------------------------------------------------------
stack frame is
gml_Script_inv_ItemForbidden (line 0)
gml_Script_scr_GetRandomCreatureByClass
gml_Script_bc_CreatureCast
gml_Script_bc_CreatureCastRandomSpell
gml_Script_bc_OnAttack
gml_Script_bc_CreatureAttack
gml_Script_bc_Turn
gml_Object_obj_battlecontroller_Step_0


3) Please describe in as much detail as possible how to reproduce the bug or crash.
Was just directing an attack from my Vicious Wolpertinger to the enemy Vicious Wolpertinger.

4) What operating system are you playing the game on? Windows, Mac OS, Android, iOS, or Playstation? If it's Playstation, please also state your region (NA or EU).
Windows 10

5) What game version are you playing? You can find the version number on the title screen in the lower left corner.
Latest

6) Any other details to help us solve the problem, such as what you were doing when the bug/crash occurred, or any hints on how we can reproduce it.
Nope. Perhaps when two sorcery on hit creatures attack one another?