What is this condition that causes you to utterly shatter any piece of code you come in contact with?
First Blizzard, now Mojang. You really are ruthless, you know that?
Initializing strings locally is not a bright idea.
if GetLocalPlayer() == GetOwningPlayer(GetTriggerUnit()) then
call DisplayTextToPlayer(GetLocalPlayer(),0,0,"You gain "+I2S(somevalue) +gold")
endif
Perhaps...
call DisplayTextToPlayer(GetOwningPlayer(GetTriggerUnit()),0,0,"You...
Which is odd because I received that exact message today. So either we have the exact same virus, or Blizzard did something. I lean toward the latter.
And not only that, a quick Google reveals that a multitude of users are experiencing this issue.
And behold, Google yields the answer. Wolfram...
I wonder what happens if you put the implant into a cockroach.
Maybe we will hear about their plans for world domination? Or at least the domination of the box of cereal in my cupboard?
Zombies do have a habit of blocking out the sun for some reason, yes.
A good call SetDayNightModels("", "") will make everything perfectly black without a light source nearby, if that is what you mean by darker.
Otherwise you will need a different day/night model.
Oh, I have encountered bugs which this has fixed. Removed units counting as alive for 0 seconds (while not really 0 seconds) has caused me some annoyance. If you have not, well then. There is nothing I can do about that. The death event is unfortunate.
If you feel this belongs in the mausoleum...
The common.ai UnitAlive native shares one flaw with the rest of the IsUnitAlive methods. This flaw is that removed units are not recognised as dead immediately after removal. This incredibly short script takes care of that for you.
Yes, it makes RemoveUnit slightly slower. But what sort of...