GUI AutoFly v1.0.0.1

[Moderator]

Vengeancekael
Date: 2012/Aug/29 12:55:27

Comment: [Approved]
Done what Bribe suggested.

Staff Contact - Rules

 

[Tank-Commander]

I'm prehaps even lost for words on how rediculously simple this is

 

[Magtheridon96]

Yes you are.

 

[Tank-Commander]

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

 

[Magtheridon96]

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 ^_^

 

[Vengeancekael]

Oh my god. This is so simple even I could approve it xD

 

[Adiktuz]

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

 

[Magtheridon96]

And then you saw the triggers

 

[WindowsVistaSucks]

I'm prehaps even lost for words on how rediculously simple this is

Image

 

[Bribe]

You can join them on one line:

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.

 

[Kingz]

The comments are actually longer than the code itself.

Anyhow... i for sure will never remember to use this xD

 

[David]

Wow, xD Its too simple Even I can do this >.> Anyway how are u dawg ?

 

[baassee]

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

 

[Bribe]

'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.

 

[Magtheridon96]

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:

 

[Almia]

Its has a funny effect too which makes the footprints fly!

 

[Bribe]

Doesn't GetBooleanAnd have to evaluate both expressions first while passing them to the function?

Yeah I guess not everyone uses JNGP or the optimizer so I guess this don't work

Though you could do:

call GetBooleanAnd(UnitAddAbility(udg_UDexUnits[udg_UDex], 'Amrf') and UnitRemoveAbility(udg_UDexUnits[udg_UDex], 'Amrf'), true)

 

[Magtheridon96]

Ah, brilliant idea Bribe ^_^
Heck, I can even avoid the function call and do this:

if (UnitAddAbility(u, 'Amrf') and UnitRemoveAbility(u, 'Amrf')) then
endif

edit
Updated.

 

[defskull]

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.

 

[Adiktuz]

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...

 

[Magtheridon96]

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.

 

[defskull]

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.

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.

 

[Adiktuz]

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...

 

[rulerofiron99]

Simple enough that we don't need to credit you if used in maps? ;p

 

[Magtheridon96]

I don't ask for credit, but it would be nice if you credited Nestharus and azlier for the original scripts.

 

[doomhammer99]

Nice! But not very helpful.

 

[defskull]

Nice! But not very helpful.

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).

 

[KnnO]

Another resource by you :3
And a new download button .. I missed alot

 

[BlackEnvyX]

This system is... awesome!

+ Rep

 

[Magtheridon96]

It's not that awesome

 

[Almia]

I agree

 

[Spacebuns]

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.

 

[Bribe]

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.

The 1.00 event fires for everything. And that's only in Unit Event where I use the 0.5 event.