Wow... a real error message

[1stlancer]

Okay, these 'dummy' units are killing me. I've got it all set up. I made a custom unit to be the dummy for this move. When I use the ability, it sets off a trigger that goes like this:

Event: Unit casts ability

Condition: Ability is equal to Osmosis

Action: Create first dummy, teach it starfire, and tell it to cast starfire. Create second dummy, teach it earthquake, and tell it to cast earthquake.

All good so far. My hero's channeling, my two dummies are channeling, and with the modifications I've made it makes for one well-blended AoE drain spell + daze. Here's where the problem comes in. I need to get rid of them.

Event: Unit stops casting ability, Unit finishes casting ability (need both in case the player interrupts the hero's channeling)

Condition: Ability is equal to Osmosis

Action: Remove all units in group (units of type(dummy)) from the game.

Seems like it should work, but when I interrupt the spell, the game crashes. That's right, it CRASHES. It said that it was referencing a memory cell of all 0's (0x00000000... or whatever) so it makes me think I might be telling it to look for something that's not there, like a null pointer or something. If anyone has ideas or has run into a similar problem, please do tell.

 

[Darg]

does it crash if you comment out the remove all units action?

 

[1stlancer]

I removed the remove all units action to see what it would do, and replaced it with a text message, so I could be sure that I had the events/conditions right. Funny thing happened.

I could interrupt the spell and I'd get my text message, all well and good. I could then control my hero, and (after removing the locust ability from my dummies) I could move my first dummy. But the second I either left the game after creating the dummies or gave the second dummy any command whatsoever, my game crashed, cue error message.

So I've sort of figured it out. I know where the problem is, I just don't know why it's happening. What I did was separate the dummies into their own independent triggers and handled them that way. Works just fine. I'll just lay low and hope no weird bug pop up again. : /