Dummy Units

What's the trigger to make a dummy unit, and how do you make it do things? I need one that will inflict steady fire damage over a period of like 10 seconds.

The trigger to make dummy units is the same as the one used to make normal units. Just be sure to have it create your premade dummy unit. To have it do damage, just do something like

Unit - Cause (unit) to damage tempUnit, dealing 500.00 damage of attack type Spells and damage type Normal

I know the damage half of it. So I need to make a custom unit? How do I make the unit invisible (100%) so Nobdoy can see it at all? Or do I just try and find a secluded area and have it spawn there and cuase the damage?

They both work relatively well. The invisible ability would be the same one that a Shade uses.

If you create the unit and immidately destroy it after dealing damage though, there's no reason to go to any of these lengths - no one will see it since WC3 doesn't update the screen in the middle of a trigger.

Hum... your dummy unit should have no model and the Locust ability...
Start with that.

Without a model though, you get an error in WE which can be annoying. Look at the Caster System and they have a dummy model there you can use. Give it the ability Locust to make it unselectable and make sure you check "Hide in Minimap".

I'm gonna go with a less complicated system here. Make unit, damage, and destory. Simple. I may give it the shade ability and put it under player Neutral Hostile, and obviously hide from minimap. But I need it to do damage over 10 seconds, so I'll just do it like that. Make it live for 10 seconds, attack cooldown= 1sec. I think that'll work for what I;'m trying to do. We'll see. I'll keep you posted.

Erm, the dummymodel.mdx from Caster System has no model, its 1x1 pixle and thats transparent.

There is no model in the caster dummy whatsoever, just bone names.

I know. I'm just saying the error message you get otherwise with:

Unable to load file ____.mdx

is kinda annoying. But yea, it makes no difference.

Ok, I don't think I need a dummy unit after all, sry guys :( I decided to just use an action loop that loops 5 times. The action is inflict 25 damage. But how do I make it so that the trigger loops at certain times? (like every 3 seconds or somthing)

EDIT: wait, nevermind. I;ll just put a polled wait in for 3 seconds after the damage action.

NEVER NEVER NEVER NEVER NEVER NEVER NEVER....

use a wait inside of a loop. It will be WAY off. Waits are only good for things you want to occur maybe once where accuracy isn't as big of an issue. Instead, use timers. I don't know how to use them in GUI but if you search for them, I bet you could use them. Its pretty easy in Jass though...

Can't you use JASS to change transparency/alpha or is that only for text?

Waits aren't that off. A wait of 3 seconds would be fairly accurate (about to do a test).

Using them inside a GUI loop though, REMEMBER that the loop integer is a global, so if you have two using the same integer....it will go haywire.

EDIT: PolledWait is roughly .35 longer each time than it was meant to be, for a 3 second interval (though most likely this is not proportional to the time period). Depends on how much accuracy you mean.

*gasp* OK... that crashes and burns my idea *sob* What do you mean by timers? I used a Game-Time wait, is that bad? Rather, could I use an If, Then, else, multi action loop? "If targeted unit is alive", "then continue loop", "else end loop" or something along those lines?
@captaingriffen wait, what do you mean no more than 1 wait on an integer? (you mean 2 waits in one integer loop will throw it off?) It doesn't need to be 110% accurate. It's just damage over time. nothing big. Ok, I set the Polled Wait time to 2.65 seconds. Does that make up for the extra .35 seconds?

As I said, using them as single-shot is fine. While in a loop, their "offness" is really exacerbated since obviously, it keeps doing it over and over.

What he was saying was thet Loop Integer A and Loop Integer B are global variables. So, when you run this again, the loop Integer A from one run may interact with the loop Integer A in the second run during the wait (because they are the same), which will obviously screw things up.