Fade System v1.3

[Moderator]

18:49, 14th Sep 2012
Magtheridon96:

Approved.
This is a useful, robust system.
Good job.

 

[gorillabull]

triggers:

show

[trigger=initialization]Initialization
Events
Map initialization
Conditions
Actions
Visibility - Create an initially Enabled visibility modifier for Player 1 (Red) emitting Visibility across (Entire map)
Player - Make Player 1 (Red) treat Player 2 (Blue) as an Ally with shared vision
Player - Make Player 2 (Blue) treat Player 1 (Red) as an Ally with shared vision
Trigger - Run AI1 <gen> (ignoring conditions)
[/trigger]
[trigger=AI1]AI1
Events
Conditions
Actions
Wait (Random real number between 0.00 and 1.00) seconds
Set TempPoint = (Random point in (Entire map))
Unit - Order Anti-Mage 0002 <gen> to Night Elf Warden - Blink TempPoint
Custom script: call RemoveLocation (udg_TempPoint)
Wait (Random real number between 0.00 and 1.00) seconds
Unit - Order Anti-Mage 0002 <gen> to Human Mountain King - Thunder Clap
Trigger - Run (This trigger) (ignoring conditions)
[/trigger]
[trigger=FadeInt]FadeInit
Events
Map initialization
Conditions
Actions
-------- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --------
-------- Add this to your map initialization --------
-------- It simply initializes the hashtable for the system --------
-------- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --------
Hashtable - Create a hashtable
Set FadeSystemHash = (Last created hashtable)
[/trigger]
[trigger=MainLoop]MainLoop
Events
Time - Every 0.05 seconds of game time
Conditions
Actions
-------- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --------
-------- This is the main loop. It's pretty basic as long as you know hashtables. --------
-------- There's no need to change anything here except the timer (if you wanna make it tick faster maybe) --------
-------- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --------
Unit Group - Pick every unit in FadeSystemGroup and do (Actions)
Loop - Actions
Set TempBool = (Load (Key (Picked unit)) of (Key FadeIn) from FadeSystemHash)
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
If - Conditions
TempBool Equal to True
Then - Actions
Hashtable - Save ((Load (Key (Picked unit)) of (Key FadeStart) from FadeSystemHash) + (Load (Key (Picked unit)) of (Key FadeSpeed) from (Last created hashtable))) as (Key (Picked unit)) of (Key FadeStart) in FadeSystemHash
Else - Actions
Hashtable - Save ((Load (Key (Picked unit)) of (Key FadeStart) from FadeSystemHash) - (Load (Key (Picked unit)) of (Key FadeSpeed) from (Last created hashtable))) as (Key (Picked unit)) of (Key FadeStart) in FadeSystemHash
Animation - Change (Picked unit)'s vertex coloring to (100.00%, 100.00%, 100.00%) with (Load (Key (Picked unit)) of (Key FadeStart) from FadeSystemHash)% transparency
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
If - Conditions
((TempBool Equal to True) and ((Load (Key (Picked unit)) of (Key FadeStart) from FadeSystemHash) Greater than or equal to (Load (Key (Picked unit)) of (Key FadeEnd) from FadeSystemHash))) or ((TempBool Equal to False) and ((Load (Key (Picked unit)) of (Key FadeStart) from FadeSystemHash) Less than or equal to (Load (Key (Picked unit)) of (Key FadeEnd) from FadeSystemHash)))
Then - Actions
Unit Group - Remove (Picked unit) from FadeSystemGroup
Hashtable - Clear all child hashtables of child (Key (Picked unit)) in FadeSystemHash
Else - Actions
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
If - Conditions
(Number of units in FadeSystemGroup) Equal to 0
Then - Actions
Trigger - Turn off (This trigger)
Else - Actions
[/trigger]

 

[FRENGERS]

Deal with it 5/5 + REPT

 

[crehym]

@gorillabull. Hey dude thanks, did you really typed that? That's what I exactly need, except the first 2 since they are map stuffs.

@FRENGERS Thanks!

 

[MortAr]

Fade... system? You call this, system?
I mean, you really think this is an actual system?!!?

 

[crehym]

Yes.

What makes it not?

 

[defskull]

Cool system, 9000/5, why not.
Can't imagine how useful this to... users, lol.

 

[WindowsVistaSucks]

A little... Simple don't you think?

 

[crehym]

^I hope I have made it dynamic enough though while being short, simple and fully MUI.
@defs Hey thanks~

 

[defskull]

^I hope I have made it dynamic enough though while being short, simple and fully MUI.

Sometimes we don't take the term 'being short' or 'simple' literally, but nice for your first try, good job.

 

[maddeem]

Yo seriously? This will remove tints on units!

 

[Tank-Commander]

Waits are inconcistent, use timers or MUI generated waits

 

[crehym]

Yo seriously? This will remove tints on units!

Yea. Completely forgot aobut that. It's updated and now supports tinted units. An example is also present.
There is no way, though, to get the tint from the trigger editor so you have to manually save tinted units' tints in any way (hashtables etc) you want so you can reference them from the trigger editor.

Waits are inconcistent, use timers or MUI generated waits

I only used waits for the AI. Kindly check the map and triggers first.

 

[defskull]

Please release another resource (System preferably), I would like to see more from you.

 

[MortAr]

Maybe a system that hides units!

 

[defskull]

Maybe a system that hides/reveals units!

Why do you use VertexColoring if you can just Hide the unit using the ShowUnit function ?

Also, by pressing ALT bar, you can still see the "faded" unit, lol.
Not unless you disable the HP Bar of a unit.
And not to forget, dots on the minimap.

This system could be useful for making spells with "fade" effect.

 

[crehym]

This system could be useful for making spells with "fade" effect.

Yes. Exactly!

Anyways I can't think of other "unique" systems so might just make a couple of spells. Soooon

 

[doomhammer99]

THumbs UP! 1000/5

 

[Adiktuz]

Why do you use VertexColoring if you can just Hide the unit using the ShowUnit function ?

I think that's exactly what he was trying to say... make a system which uses ShowUnit... XD...


anyway this is really useful stuff...

 

[maddeem]

This thread is either full of sarcasm or do people really like this....?

WAIIIT SERIOUSLY?!
I just looked at the triggers. This is the definition of redundant and retarded.
Your using Last Created Hashtable... Really?
You spam functions like Picked Unit, Triggering Unit... ugh
This "system" is ludacris.

 

[defskull]

Just wait for Magtheridon to say on behalf of me.

 

[Magtheridon96]

I don't understand what all the fuss is about :l

Simple systems are not bad.

But there's a catch:
If you choose to submit a simple system, it must be perfect.
More complex systems sometimes get away with a couple of things.

 

[baassee]

me is perfect

 

[defskull]

There you go, Mag has said on behalf of me.

 

[crehym]

Your using Last Created Hashtable... Really

Must have missed that. Look, I was using the hashtable variable in the others so definitely that wasn't intended. Anyway fixed.

Regarding the other thing you said (and what Magtheridon said), I really have no idea. I thought that's actually faster that storing the picked/triggering unit to a variable or other ways. Sorry I really don't get what you are trying to say.

I can read and understand JASS but I can't/don't use it.

 

[Adiktuz]

Variable look-up executes faster than function calls so its better to save things [like triggering unit etc] first into a variable if ur gonna use them multiple times...

 

[Magtheridon96]

@crehym:

Explanation

• bla bla bla (Picked unit) bla bla bla
• bla bla bla (Picked unit) bla bla bla
• bla bla bla (Picked unit) bla bla bla
• bla bla bla (Picked unit) bla bla bla
• bla bla bla (Picked unit) bla bla bla

->

• Set TempUnit = (Picked unit)
• bla bla bla TempUnit bla bla bla
• bla bla bla TempUnit bla bla bla
• bla bla bla TempUnit bla bla bla
• bla bla bla TempUnit bla bla bla
• bla bla bla TempUnit bla bla bla

The second trigger is faster.
(Picked unit) calls a function to determine the picked unit.
It's not very efficient to keep redetermining the picked unit, obviously; It's better to store that unit into a variable so we can use the value directly without having to redetermine him in every action.

Not important:

Spoiler

(Of course, at the level of C++, it's just returning a value and doing nothing else, but function calls are slow, while variable lookups are way faster, and because optimizers have the ability to change variable names, they will be even faster in a finished-map. (The shorter the variable names, the faster the system)
Native function names can't be changed.

 

[defskull]

Also Mag, you should state another technique when to actually use a variable.
Like,

• Set U = (Triggering unit)
• Unit - Kill U

Should be,

• Unit - Kill (Triggering unit)

 

[crehym]

Oh.

I thought that calling those functions were actually faster because I've read others saying use TriggeringUnit instead of others (now I know against "CastingUnit","AttackingUnit" etc). I also thought that saving up by not using variables save space etc plus you can't actually reference a variable from a hashtable. It doesn't really also show how much "faster" or "better" it became or it can become.

Updated anyway. Change handles and you now use variables to set up the settings.

Thanks for the lessons too

 

[baassee]

Non-arrayed variables are fine. However, arrayed variables... just bad behaviour using those for simple tasks.

 

[baassee]

Sorry for the double post but I have a legit reason to do it.

-You should fix things in the main loop trigger. You set the key, yet you aren't using it.

And now my nice thread about MUI ticks in. Even mag should notice that if I add a unit twice, it will break.

 

[crehym]

Sorry for the double post but I have a legit reason to do it.

-You should fix things in the main loop trigger. You set the key, yet you aren't using it.

And now my nice thread about MUI ticks in. Even mag should notice that if I add a unit twice, it will break.

Actually I was using the key already, though I missed one line because I was rushing with the updates.
Fixed.

If you add a unit twice, it will simply override the previous settings. I didn't made it stack on a single unit because imagine if you added a fade in and a fade out effect, it will make the unit flicker which is ugly. It wasn't suppose to stack on a single unit but it is fully MUI.

 

[Adiktuz]

I agree that overwriting previous fades on the same unit will be much better than making it stack... Unless you're trying to make a Christmas light...

 

[baassee]

What if I have spell that fades units in and another one for the other way around.

 

[Adiktuz]

no matter how you look at it, if you cast them at the same unit it will be christmas lights...

 

[crehym]

What if I have spell that fades units in and another one for the other way around.

Like what Adiktuz said.

Also, I didn't intend it to stack on a single unit.
I could've then saved a dummy as a handle for every instance of fading for it to be fully SUMI (like how you described it in your thread), but then again, it will look ugly and flicker esp if it is opposing fades.

So a second fade will override the first one.


Though it will be best to have options for both. I'm too lazeh though to do that atm.

 

[baassee]

Maybe you should have a real variable that sets the current alpha of the unit so it wont hack like it does now...

 

[crehym]

^ What?

Anyway updated.
-renamed triggers.
-added this line

• Animation - Change FSUnit's vertex coloring to (FSRed%, FSGreen%, FSBlue%) with FSStart% transparency

so there is no need to set the initial opacity in your spell.

 

[FRENGERS]

Huraay it's cool now @.@

 

[Rasamayu]

Great System i love it, ty