Moderator
M
Moderator
Vengeancekael
Date: 2012/Aug/29 12:55:27
Comment: [Approved]
Done what Bribe suggested.
Staff Contact - Rules
Date: 2012/Aug/29 12:55:27
Comment: [Approved]
Done what Bribe suggested.
Staff Contact - Rules
-
Are you planning to upload your awesome spell or system to Hive? Please review the rules here.
-
🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
-
It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!
GUI AutoFly v1.0.0.1
- Author(s)
- Magtheridon96
- Tags
- System, GUI / Triggers
- Size
- 21.04 KB
- Rating
- Downloads
- 397
- Created
- Aug 23, 2012
- Updated
- Aug 29, 2012
- Resources
- 1
- State
Approved
This bundle is marked as recommended. It works and satisfies the submission rules.
This system is so simple, uploading it should count as trolling, but it actually is quite useful.
With this simple system, you would never need to add crow form and remove it ever again.
All ground units would be able to 'fly'.
It's also more efficient this way since you can omit 2 function calls per spell cast (for spells involving 3D movement).
This system is based on Nestharus' AutoFly (UnitIndexer version).
This system requires GUI UnitIndexer by Bribe.
Keywords:
fly, autofly, nestharus, bribe, unit, indexer, unit indexer, dynamic, hanky, item, recipe, naruto, spell, system.
With this simple system, you would never need to add crow form and remove it ever again.
All ground units would be able to 'fly'.
It's also more efficient this way since you can omit 2 function calls per spell cast (for spells involving 3D movement).
-
GUI AutoFly
-
Events
-
Game - UnitIndexEvent becomes Equal to 1.00
-
-
Conditions
-
Actions
-
-------- ----------------- --------
-
-------- This trigger will run whenever a unit is indexed. --------
-
-------- This means that it runs whenever a new unit enters the map. --------
-
-------- ----------------- --------
-
-------- First, I'm adding the crow form ability to the indexed unit. --------
-
-------- The reason we're using it inside an if block is because the "UnitAddAbility" function returns a boolean. --------
-
-------- This boolean represents the successfulness of the ability adding. We need this here, because if a unit --------
-
-------- already had a crow form ability, it couldn't be added. The reason we're also using UnitRemoveAbility --------
-
-------- in the same line is because JASS has a short-circuiting feature. If one of the expressions in an 'and' --------
-
-------- expression returns false, then it stops. --------
-
-------- ----------------- --------
-
-------- We do not want to call UnitRemoveAbility for a unit that failed to have the ability added. --------
-
-------- Without this form of protection, units that already had the crow form ability would have it --------
-
-------- removed completely. --------
-
-------- ----------------- --------
-
Custom script: if UnitAddAbility(udg_UDexUnits[udg_UDex], 'Amrf') and UnitRemoveAbility(udg_UDexUnits[udg_UDex], 'Amrf') then
-
Custom script: endif
-
-
This system requires GUI UnitIndexer by Bribe.
- Bribe - GUI UnitIndexer
- Nestharus - AutoFly (vJASS UnitIndexer version)
- Azlier - AutoFly (vJASS AIDS version)
If you're going to rate this, I demand it be no more than a "Useful - 3". Something as simple as this doesn't deserve anything higher than that.
Keywords:
fly, autofly, nestharus, bribe, unit, indexer, unit indexer, dynamic, hanky, item, recipe, naruto, spell, system.
Contents
Reviews
- Joined
- May 26, 2009
- Messages
- 1,829
I'm prehaps even lost for words on how rediculously simple this is
- Joined
- Dec 12, 2008
- Messages
- 7,379
Yes you are.
- Joined
- May 26, 2009
- Messages
- 1,829
Though I would say anybody who'd need to make units able to fly for their spell to work would probably just do it themselves long before looking on the site for a system to help them do it XD
- Joined
- Dec 12, 2008
- Messages
- 7,379
Well, yeah, that's true.
That's why this system is only for people making maps
If they've started the map a long time ago, they can shorten their triggers by removing the Add/Remove Crow form lines, and just put this into their maps. Maps are assumed to have unit indexers in them already because they're very standard and common.
If they're starting one, they'd use this if they were sane and had tons of Z-movement spells ^_^
That's why this system is only for people making maps
If they've started the map a long time ago, they can shorten their triggers by removing the Add/Remove Crow form lines, and just put this into their maps. Maps are assumed to have unit indexers in them already because they're very standard and common.
If they're starting one, they'd use this if they were sane and had tons of Z-movement spells ^_^
- Joined
- Aug 11, 2009
- Messages
- 6,528
Oh my god. This is so simple even I could approve it xD
- Joined
- Oct 16, 2008
- Messages
- 10,450
After not being able to browse the spells section for months, this is what I saw on top... And I was like, "hey they should approve this already"... XD
- Joined
- Dec 12, 2008
- Messages
- 7,379
And then you saw the triggers
- Joined
- Jul 21, 2010
- Messages
- 923
Last edited by a moderator:
Code Moderator
- Joined
- Sep 26, 2009
- Messages
- 9,464
You can join them on one line:
Having fewer lines in GUI helps the trigger to load more quickly when viewing it, and also easier to copy & paste in case the user wants to consolidate a bunch of triggers with the same event. And with GetBooleanAnd instead of "local boolean b" the user can copy & paste it wherever without a syntax error.
JASS:
call GetBooleanAnd(UnitAddAbility(udg_UDexUnits[udg_UDex], 'Amrf'), UnitRemoveAbility(udg_UDexUnits[udg_UDex], 'Amrf'))Having fewer lines in GUI helps the trigger to load more quickly when viewing it, and also easier to copy & paste in case the user wants to consolidate a bunch of triggers with the same event. And with GetBooleanAnd instead of "local boolean b" the user can copy & paste it wherever without a syntax error.
- Joined
- Jun 5, 2008
- Messages
- 2,572
The comments are actually longer than the code itself.
Anyhow... i for sure will never remember to use this xD
Anyhow... i for sure will never remember to use this xD
- Joined
- Jan 21, 2012
- Messages
- 1,982
Wow, xD Its too simple Even I can do this >.> Anyway how are u dawg ?
Even I can do this >.> Anyway how are u dawg ?
- Joined
- Nov 14, 2008
- Messages
- 3,256
I always wondered about these AutoFlies - we have both 'Amrf' and 'Arav'. What will happen if the unit has 'Arav' already; double flying :O ^^
Anyway simple and neat - this system have looked the same for too long - new API pls
Anyway simple and neat - this system have looked the same for too long - new API pls
Code Moderator
- Joined
- Sep 26, 2009
- Messages
- 9,464
'Arav' works the same way but 'Amrf' is not an ability found on regular-units (unlike Arav which belongs to DotT).
I believe using Amrf instead of Arav is leftover from the time before we used "if UnitAddAbility", so we would remove the ability no matter if that function returned true or not. I could be wrong. Berb(anog) might know more on this.
I believe using Amrf instead of Arav is leftover from the time before we used "if UnitAddAbility", so we would remove the ability no matter if that function returned true or not. I could be wrong. Berb(anog) might know more on this.
- Joined
- Dec 12, 2008
- Messages
- 7,379
Doesn't GetBooleanAnd have to evaluate both expressions first while passing them to the function? =o
This way, a unit that already has 'Amrf' somehow will lose the ability D:
This way, a unit that already has 'Amrf' somehow will lose the ability D:
- Joined
- Apr 24, 2012
- Messages
- 5,113
Its has a funny effect too which makes the footprints fly!
Code Moderator
- Joined
- Sep 26, 2009
- Messages
- 9,464
Yeah I guess not everyone uses JNGP or the optimizer so I guess this don't work
Though you could do:
JASS:
call GetBooleanAnd(UnitAddAbility(udg_UDexUnits[udg_UDex], 'Amrf') and UnitRemoveAbility(udg_UDexUnits[udg_UDex], 'Amrf'), true)- Joined
- Dec 12, 2008
- Messages
- 7,379
Ah, brilliant idea Bribe ^_^
Heck, I can even avoid the function call and do this:
edit
Updated.
Heck, I can even avoid the function call and do this:
JASS:
if (UnitAddAbility(u, 'Amrf') and UnitRemoveAbility(u, 'Amrf')) then
endifedit
Updated.
Last edited:
- Joined
- Mar 27, 2008
- Messages
- 8,035
If you can make them "fly" (LITERALLY), this will be an awesome system.
Currently you're just changing its height so it will make the unit look like it is "flying" but it's not, it's just visual.
You still can't cross cliffs/waters/etc.
I wish you could do this, this would be awesome
I tried to do this, but end up creating 2 different units per unit-type, that's not efficient would it ?
Same as Maker's Melee/Range Switch system, it requires you to create 2 unit per unit-type, quite non-user-friendly if you ask me.
Currently you're just changing its height so it will make the unit look like it is "flying" but it's not, it's just visual.
You still can't cross cliffs/waters/etc.
I wish you could do this, this would be awesome
I tried to do this, but end up creating 2 different units per unit-type, that's not efficient would it ?
Same as Maker's Melee/Range Switch system, it requires you to create 2 unit per unit-type, quite non-user-friendly if you ask me.
- Joined
- Oct 16, 2008
- Messages
- 10,450
That is the limitation of the wc3 engine itself for you...
of course you can create a custom pathing system but it would be much efficient and easier to just have two units...
of course you can create a custom pathing system but it would be much efficient and easier to just have two units...
- Joined
- Dec 12, 2008
- Messages
- 7,379
That's not what this system is for, the only purpose it holds is giving units the Amrf ability so you can modify unit Z.
It's simple and modular.
It's simple and modular.
- Joined
- Mar 27, 2008
- Messages
- 8,035
But making the unit "fly" visually is highly related to the unit, actually "fly" (pass cliffs/water/etc) instead just visually.
Just saying the potential of this system.
- Joined
- Oct 16, 2008
- Messages
- 10,450
the thing is, the most efficient way to do it in wc3 is by having two units... which is not always good especially in maps where data is specific to each unit...
and users can always make everything pathable then just create customized pathing systems...
and users can always make everything pathable then just create customized pathing systems...
- Joined
- Jul 10, 2006
- Messages
- 3,315
Simple enough that we don't need to credit you if used in maps? ;p
- Joined
- Dec 12, 2008
- Messages
- 7,379
I don't ask for credit, but it would be nice if you credited Nestharus and azlier for the original scripts.
- Joined
- Dec 5, 2011
- Messages
- 368
Nice! But not very helpful.
- Joined
- Mar 27, 2008
- Messages
- 8,035
It is helpful for me, since it does not allow you to keep calling the same check over and over again (example: trigger that makes unit fly).
- Joined
- Sep 18, 2011
- Messages
- 195
Another resource by you :3
And a new download button .. I missed alot
And a new download button .. I missed alot
- Joined
- Mar 27, 2008
- Messages
- 1,003
This system is... awesome!
+ Rep
+ Rep
- Joined
- Dec 12, 2008
- Messages
- 7,379
It's not that awesome
- Joined
- Apr 24, 2012
- Messages
- 5,113
I agree
- Joined
- Apr 20, 2010
- Messages
- 797
I think you should add the Event line "UnitIndexEvent equal to 0.5" to make summoned units also able to change their Z, since in Bribe's Unit indexing system UnitIndexEvent = 0.5 is used to detect a unit being summoned.
Code Moderator
- Joined
- Sep 26, 2009
- Messages
- 9,464
The 1.00 event fires for everything. And that's only in Unit Event where I use the 0.5 event.
