[Tutorial] Projectile-Based Triggered Spell System

[Moderator]

12th Dec 2015
IcemanBo: Too long as NeedsFix. Rejected.

Projectile-Based Triggered Spell System | Reviewed by Maker | 31st Aug 2013

NEEDS FIX

Get rid of the A unit dies trigger, make the dummy not decay instead Get rid of the non MUI examples You leak events, adding one for every unit and not clearing them There is no way to tell which instance made the hit ========================================== Periodically checking for a buff is not a good method for this kind of a system. ========================================== I recommend using a configuration trigger where you set values for damage, the ability, dummy unit type and so on Check GH_MUI_INDEX only when you deindex

[tr]

 

[deathismyfriend]

never use integer A/B they are less efficient and slower than making ur own variable.

this is bad. For each (Integer B) from (Integer A) to MD_MUI_INDEX, do (Actions)
integer A may not be 1.

u never de-index so this spell is not MUI.

The top 2 spells are not MUI because they have a time period b4 they are used were the variables can be changed. u never index or de-index.

anything u use twice or more should be stored into a variable. example: last created unit / picked unit / level of ability

using skip remaining actions in a loop trigger is a very bad idea.

check out my tutorial things a guier should know. the chapter how to index will show u how to properly index / de-index spells to make them fully MUI

 

[GabbyM]

never use integer A/B they are less efficient and slower than making ur own variable.

this is bad. For each (Integer B) from (Integer A) to MD_MUI_INDEX, do (Actions)
integer A may not be 1.

u never de-index so this spell is not MUI.

The top 2 spells are not MUI because they have a time period b4 they are used were the variables can be changed. u never index or de-index.

anything u use twice or more should be stored into a variable. example: last created unit / picked unit / level of ability

check out my tutorial things a guier should know. the chapter how to index will show u how to properly index / de-index spells to make them fully MUI

I used it so many times, with 250 Unit projectile speed, and they all worked out perfectly. I had five out of the times, and they all worked perfectly, so i declared it MUI.

Yeah, i'll just fix that Integer A, give me a few mins.

I never said that the top two was MUI, that is why they do not have that "(MUI)"

Yeah, it's more of a concept. But otherwise, the execution still varies; so people may or may not do what i did, and may or may not do what i did.

But just to appease you, i'll try and fix all of these flaws you're pointing out.

 

[deathismyfriend]

after another quick look yes ur last spell is MUI but it is very inefficient. u should use the new method which is found in my tutorial. this will not be approved with this de-indexing method.

the first 2 triggers r not MUI.

integer A/ B should be removed they are both bad to use.

 

[UndeadImmortal]

I used it so many times, with 250 Unit projectile speed, and they all worked out perfectly. I had five out of the times, and they all worked perfectly, so i declared it MUI.

MUI means Multi-unit Instanceable. Try putting 2 same heroes then order the first hero to cast the ability to a target, then immedietly order the second hero to cast the same ability to the same target, you'll find the bug.

Also a documentation to the 3 triggers won't hurt

 

[deathismyfriend]

the third one is MUI but it does so by reducing every instance of the spell by reducing its index one by one which is very inefficient.

the other 2 arent MUI like u and i stated

 

[GabbyM]

after another quick look yes ur last spell is MUI but it is very inefficient. u should use the new method which is found in my tutorial. this will not be approved with this de-indexing method.

the first 2 triggers r not MUI.

integer A/ B should be removed they are both bad to use.

I told you, i'm still fixing it.

this is bad. For each (Integer B) from (Integer A) to MD_MUI_INDEX, do (Actions)
integer A may not be 1.

Yeah, i meant it that way.

Because the Integer B starts at where is the current loop of A to bring down all the other existing indexed values above, to make room on the top.

Yes, i am aware that Indexing IS inefficient, but that is all i got for the moment. I'm currently trying Hashtables, and i'm just familiarizing myself, that is why i'm not using it on submitted spells yet.

Also, i have fixed that Integer A-B loops, it should be fine right now.

the third one is MUI but it does so by reducing every instance of the spell by reducing its index one by one which is very inefficient.

the other 2 arent MUI like u and i stated

I didn't said that they were MUI. That is why they do not have that "(MUI)" on the codes.

 

[deathismyfriend]

i cant see the spell so can u update the triggers on the page.

also look at my tutorial u dont need hashtables. hashtables are slower than indexed arrays which is the method i show u how to use in my tutorial things a guier should know. its in the chapter how to index.

 

[GabbyM]

i cant see the spell so can u update the triggers on the page.

also look at my tutorial u dont need hashtables. hashtables are slower than indexed arrays which is the method i show u how to use in my tutorial things a guier should know. its in the chapter how to index.

http://www.hiveworkshop.com/forums/...9/things-gui-user-should-know-233242/#Section 2 Ch 12

Are you sure about that tutorial? because i remember doing the very same thing you did; just with different variable names, and i also took account the possibility of a trigger ending in between indexes;

Say Index-1 is not finished, and index-3 is not finished, but index-2 is already finished. So what i did, is to push down the Index-3 to the position of index-2, once Index-2 is completed and the units above index are not. It's kind of like pulling a book in a middle of a stack of books, what i did is made the book on top of Index-2 to take it's place, and so on and so forth on the preceding indexes.

 

[deathismyfriend]

That is my tutorial. It is up to date and the indexing is exactly what I use for all my spells. If somethig doesn't work when u try it ask questions. It's easy to mess something up when learning something new.

 

[GabbyM]

That is my tutorial. It is up to date and the indexing is exactly what I use for all my spells. If somethig doesn't work when u try it ask questions. It's easy to mess something up when learning something new.

I get it now, what you are doing is registering the last index to the voided index to avoid using the for-integer-loop action. That's kinda ingenious.

Yeah, give me a few minutes to apply the changes.

 

[deathismyfriend]

I get it now, what you are doing is registering the last index to the voided index to avoid using the for-integer-loop action. That's kinda ingenious.

Yeah, give me a few minutes to apply the changes.

Yup that's exactly how it works. Note that I didn make that eat its just the way I learned.

 

[GabbyM]

Yup that's exactly how it works. Note that I didn make that eat its just the way I learned.

Point well taken, can i have a 5?

It's updated, and ready to go. I hope that this system gets attention.

 

[doomhammer99]

FLARE GUN and ICE BLAST are Both not MUI

but nice spell tho' ^^. Keep up. +rep

 

[GabbyM]

FLARE GUN and ICE BLAST are Both not MUI

but nice spell tho' ^^. Keep up. +rep

Didn't i just said that? I specified it NOT to be mui, to show how the system should work.

 

[Lord_Demon_X]

I don't understand why you're using these lines:

• Or - Any (Conditions) are true
  • Conditions
    • (MDTarget[Temp_Integer_A] is dead) Egal to* TRUE
    • (MDTarget[Temp_Integer_A] has buff Mystic Dagger Validation (Pause)) Egal to TRUE

Just check with an And if the target is alive and has the buff.

• If (All Conditions are True) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • (MDTarget[Temp_Integer_A] is dead) Egal to* FALSE
    • (MDTarget[Temp_Integer_A] has buff Mystic Dagger Validation (Pause)) Egal to* TRUE
  • Then - Actions
  • Else - Actions

You call it as a tutorial, so why you don't submit it in the tutorials section ?

And btw you're missing a configuration triggers for the following things:
-Special effects models
-Damages
-Ability
-Buff
-Damage type
-"Attack type"
-Position of the effect attached to the target

Oh and one more thing: You don't need to order the caster doing his attack animation because he'll do it when he will attacks.

 

[GabbyM]

I don't understand why you're using these lines:

• Or - Any (Conditions) are true
  • Conditions
    • (MDTarget[Temp_Integer_A] is dead) Egal to* TRUE
    • (MDTarget[Temp_Integer_A] has buff Mystic Dagger Validation (Pause)) Egal to TRUE

Just check with an And if the target is alive and has the buff.

• If (All Conditions are True) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • (MDTarget[Temp_Integer_A] is dead) Egal to* FALSE
    • (MDTarget[Temp_Integer_A] has buff Mystic Dagger Validation (Pause)) Egal to* TRUE
  • Then - Actions
  • Else - Actions

You call it as a tutorial, so why you don't submit it in the tutorials section ?

And btw you're missing a configuration triggers for the following things:
-Special effects models
-Damages
-Ability
-Buff
-Damage type
-"Attack type"
-Position of the effect attached to the target

Oh and one more thing: You don't need to order the caster doing his attack animation because he'll do it when he will attacks.

- Special Effect Models: Handled at the Object Editor
- Damages: It is specified in the initiatory trigger to configure damage.
- Buff: Validating buff is handled at the Object Editor
- Damage Type: As always, it is by your choice. As a triggerer, it's basic to be aware of how the Unit - Damage Target functions. If you intend to make your own without knowledge of how to configure the Unit - Damage Target function, then you will certainly fail. As a prerequisite with this tutorial is to actually know your way around the triggers.
- Attack Type: Ditto
- Position of the effect attached to the target: Can be handled by Object Editor or the trigger editor. But this case, i specified that Special effect for the target unit (Hydralisk Impact) and the position of the trigger-unit (Blink <Special>)

Yes, i have to order the unit to attack, because it is a modified "Blink Strike", as well as you may never know if there are other units the target may decide to attack even if she was assigned on another unit. It is ordered to attack, not to appease the animation, but to actually order the unit to attack the target than running rampant after.

Really, have you taken account that a unit may not receive the buff when they die while still the projectile is in flight? It checks whether the unit is dead or has the buff to trigger the ability. If it was triggered, and the target is dead then it does nothing, if it is still alive but triggered, it will do what it is supposed to do. If you leave a trigger running like that, it will eventually slow the game.

With your current suggestion, it will automatically trigger the moment you sent the projectile flying instead of when it hits because the target is already alive, thus it finishes the condition.

I know how little you look at the new guys, but i'm telling you i know what i'am doing.

And i placed it here, because even if it is a tutorial, it is still a spell-pack/template/system. Thus it has a place in this section. I also want to see if it has gained much attention than just being commented at.

 

[deathismyfriend]

Config should not be in the cast triggers.

If this is a tutorial it should be in the tutorial section not spell section.

Also I don't look down on new ppl lol. Everyone had to start off somewere. Technically I'm new as I haven't been doing this for over a yr yet. Also I only did GUI for about 2 months.

New has nothing to do with anything when I look at triggers. I simply look at then to help others improve.

 

[Maker]

• Don't post any non MUI examples
• Subtract 1 from Temp_Integer_A when deindexing
• Don't check if the group is empty 33 times per second
• Units can lose the buff in that 0.03 second interval. There is a possibility that some instances never get deindexed

 

[GabbyM]

• Don't post any non MUI examples
• Subtract 1 from Temp_Integer_A when deindexing
• Don't check if the group is empty 33 times per second
• Units can lose the buff in that 0.03 second interval. There is a possibility that some instances never get deindexed

- Shouldn't they know at least, how the system works in basic?
- Why? it is zeroed every time the for-int-loop is used. I think you mean MD_MUI_INDEX, and i already did that.
- Actually, i took account that if they died right before the projectile impacts. But of course, i guess i have to update my spell if they happen to be Magic Immune...
- I only did that 0.03 because a lot of people are telling me that you should never use 0.01. But that is my concern as well, but a lot of people believe that it will cause lag, even if it doesn't have anything to manipulate within the observable map. I have the reason to believe that 0.01 actions/s is safe if it is just for calculation.

Config should not be in the cast triggers.

If this is a tutorial it should be in the tutorial section not spell section.

Also I don't look down on new ppl lol. Everyone had to start off somewere. Technically I'm new as I haven't been doing this for over a yr yet. Also I only did GUI for about 2 months.

New has nothing to do with anything when I look at triggers. I simply look at then to help others improve.

Yeah, even if this is a tutorial. It is still a spell pack, system, and a template. So it should be judged as one.

Wasn't referring to you that time.

 

[Maker]

- Shouldn't they know at least, how the system works in basic?
- Why? it is zeroed every time the for-int-loop is used. I think you mean MD_MUI_INDEX, and i already did that.
- Actually, i took account that if they died right before the projectile impacts. But of course, i guess i have to update my spell if they happen to be Magic Immune...
- I only did that 0.03 because a lot of people are telling me that you should never use 0.01. But that is my concern as well, but a lot of people believe that it will cause lag, even if it doesn't have anything to manipulate within the observable map. I have the reason to believe that 0.01 actions/s is safe if it is just for calculation.

-Might as well make it MUI. This is the spell database, not a tutorial forum.
-The instance that is moved from last position to current doesn't get looped
-It is not about dying. Spells can remove the buff, but the unit is alive. The unit remains to be looped.
-Only do the check when you deindex

 

[GabbyM]

-Might as well make it MUI. This is the spell database, not a tutorial forum.
-The instance that is moved from last position to current doesn't get looped
-It is not about dying. Spells can remove the buff, but the unit is alive. The unit remains to be looped.
-Only do the check when you deindex

You people really crave MUI don't you? I just don't have the patience for another MUI. Besides, the resource is the System, not the spells because they are just for demonstration. The full examination should be focused entirely at the Mystic Dagger.

Fine, i'll get that -1 Temp_Int_A for you.

Yes, i am aware of having the buffs removed by something like Purge, but with a 0.03 Window, it's highly unlikely. And of course, you can just add a Motion Buffer; meaning there is a definite time the projectile is valid. And if they exceeded a definite amount of flight-time or distance, then the impact will be already invalid.

Just give me a few mins, i'll add that -Temp_Int_A and that motion-buffer system.

Update:

Just did, and fixed the Multi-Unit Instance-ability, i actually forgot to create indexes for the caster. V1.2 Build 2 Is live.

 

[Maker]

I would rather use a damage detection system, when a unit takes damage, check if it has the buff. That should work and it is accurate.

 

[GabbyM]

I would rather use a damage detection system, when a unit takes damage, check if it has the buff. That should work and it is accurate.

I don't know, i heard that the damage comes first before the buff... And if the buff doesn't apply, it could go on forever without a loop.

Let me check that.

UPDATE:

I tried that "Unit - Takes Damage" event, and it doesn't work every time. I tried a lot. Maybe you can branch out.

 

[Magtheridon96]

What Maker is suggesting is the usage of a Damage Detection system like this one for the damage event.

Damage detection is the kind of thing that requires a whole system :/

 

[GabbyM]

What Maker is suggesting is the usage of a Damage Detection system like this one for the damage event.

Damage detection is the kind of thing that requires a whole system :/

The entire problem is that, you need something unique for the system to find, that they can validate.

With the damage detection, it is just bad because it doesn't distinguish between normal attacks and ability attacks. That is why the system uses specialized buff to work with.

 

[Magtheridon96]

With the damage detection, it is just bad because it doesn't distinguish between normal attacks and ability attacks. That is why the system uses specialized buff to work with.

Then use this one.

 

[GabbyM]

Then use this one.

Couldn't make it work either.

 

[Magtheridon96]

Guess it's time to summon Satan then.

Maker, grab the candles, I'll get the goat. This is going to be a long night.