Mine Bomb

[DarkslayerK9]

How do i do this: Ok i hve this Engineer unit and i want to add a ability to it that can put down mines then be able to detonate them when they want to causing damage to anyone in area. Plz help!

 

[Elvendan]

Use land mine ability to place mines.
Add ability "explode" to that engineer.
Make a trigger which damages the area when mine dies.
Make a trigger to kill mines when "explode" ability activated.

 

[DarkslayerK9]

How do i make the Trigger?

 

[Berb]

With the Trigger Editor.

 

[DarkslayerK9]

No i meant how do u make trigger for this: your hero use ability to put down a land mine then use other ability called "detonate" to set it off

thats my question on the trigger. How do u do that?

 

[Elvendan]

You need three triggers. Like these:

• Events
  • Unit - A unit Starts the effect of an ability
• Conditions
  • (Ability being cast) Equal to Land mine
• Actions
  • Unit - Add Detonate to (Casting unit)

• Events
  • Unit - A unit Starts the effect of an ability
• Conditions
  • (Ability being cast) Equal to Detonate
• Actions
  • Unit Group - Pick every unit in (Units of type Mine) and do (Actions)
    • Loop - Actions
      • Unit - Explode (Picked unit)

• Events
  • Unit - A unit Dies
• Conditions
  • (Unit-type of (Dying unit)) Equal to Mine
• Actions
  • Unit - Cause (Dying unit) to damage circular area after 0.00 seconds of radius 550.00 at (Position of (Dying unit)), dealing 300.00 damage of attack type Chaos and damage type Demolition

 

[Berb]

In Warcraft III, everything is event-driven. Whether you've got a piece of code that is executed at initialization or when a unit dies, an item is bought, etc, there are events that dictate when specified actions are executed. If you've got a spell, there is an event that lets you execute code upon that spell being cast (or put into effect).

Once you've decided which events you need to keep track of (make triggers for) you can think about adding conditions to those events. For example, if you want to detect when any ability is cast then you can use the event Unit starts the effect of an ability. If you only want to detect a specific ability then you would need to specify which ability in the Conditions section.

Everything in the pretty GUI is fairly well labeled, and there are descriptions on many of the dialogs that provide information on what specific "actions" do. If you do not understand what they mean, then you can post here with your questions - but I do implore you to read through the drop-down dialogs carefully as many of your questions can be answered by simply reading the GUI.

 

[Drunken_Jackal]

Use Triggering Unit instead of dying unit. And also use Triggering Unit instead of Casting Unit. The ability should be based off Thunder Clap.
Attached test map. The only problem is that you can still learn the plant bomb.

 

[Elvendan]

Use Triggering Unit instead of dying unit.

Could you please explain exactly why "Triggering unit" is better than "Dying unit"?
I always thought it's better not to use Triggering unit everywhere except such cases when there's no specific event-respond unit. Because "Triggering unit is too general and may not work properly sometimes. Maybe I'm just dumb, explain me where am I wrong?

 

[Berb]

Whenever you've got the opportunity to use Triggering unit, use it. It is the fastest response native for obtaining that specific unit, to the best of my knowledge. If so, then yes, you would be wrong.

 

[defskull]

Could you please explain exactly why "Triggering unit" is better than "Dying unit"?
I always thought it's better not to use Triggering unit everywhere except such cases when there's no specific event-respond unit. Because "Triggering unit is too general and may not work properly sometimes. Maybe I'm just dumb, explain me where am I wrong?

(Triggering unit) is on the first item on the list, and below it will follow like (Dying unit) and so on
So, using (Triggering unit) will be more efficient

 

[Berb]

Though it isn't more efficient simply because it is closer to the top of the drop-down dialog. To my knowledge, the position of an action in the drop-down box has no significance in determining the efficiency of the action.

 

[Elvendan]

it is closer to the top of the drop-down dialog

Are you kidding me? (Triggering Unit) is in the bottom of that dialog, nearly the last string in it. So why do I have to use it?
Some time ago I overused (triggering unit) in my triggers and it caused a bunch of really weird bugs which I was unable to fix. So I searched around the internet and eventually found an advice to use exact response to the event. I replaced all of my (triggering units) to such and it started to work. Since then I'm trying never to use (triggering unit) and never had such unfixable bugs.
Now you're saying I'm wrong and I'm trying to understand why. Again, to that drop-down dialog. As you can see it is in the very bottom of the list:

 

[Drunken_Jackal]

You definitely dont get it.
Example, you wanna add an ability to a unit, you use the unit ability action. And it shows this line automatically:

• Add Ability to (Triggering Unit)

And lets say the event is when a unit enters a region.
So triggering unit would also refer to the unit entering the region.
And when you choose the ability action, it automatically says triggering unit.
Heres a link to prove my point:
http://www.hiveworkshop.com/forums/...quick-tutorial-common-triggering-tips-190802/
Scroll down to conclusion.

 

[defskull]

@Elvendan
You want to compare between GUI efficiency and JASS efficiency ?
You made my day :')
GUI will show you (Triggering unit) is on the most bottom in the list BUT not in JASS

@Link
In case you missed this out, Elvendan:

Decrease your menu-scrolling time
Not only is (Triggering unit) <<faster>> than (Casting unit) or (Dying unit) in terms of execution time, it's actually faster to click because it is always the first option on the menu tree. Just use (Triggering unit) and, of course, set it to a variable if you use it more than 2-3 times.

Now that that's been mentioned, how about (Owner of (Triggering unit))? Ever notice that (Triggering player) is the first item on the menu-tree? That's because it's able to be used in more cases than you could imagine.

Every event which is selectable as "Any unit ---" is, in JASS, a "playerunitevent". This means that it has two triggering components, a unit, and a player.

Long story short, every "Any unit event" can use (Triggering player) instead of (Owner of (Triggering unit)) and get the same results.

This will cut down on your menu-scrolling time as well as game execution time, so it's faster in every sense of the word.

You can thank PurgeAndFire for showing me the (Triggering player) trick.

 

[Elvendan]

Yeah, yeah, I already +repped Blindman for being patient with such noob as me. Now I get it. I never learned Jass so that was an expected mistake.
Thank you too, defskull, but please don't make fun of me

 

[defskull]

Was trying to explain, here take some rep !