MUI question

[Chewii]

In many MUI spells i see people storing stuff in "unnecessary" variables.
Like so

• Set Damage[index] = 400

and use it for something like

• Unit - Cause Unit to damage Unit2, dealing Damage[index] damage of attack type Spells and damage type Unknown

Why not just do like this?

• Unit - Cause Unit to damage Unit2, dealing 400 damage of attack type Spells and damage type Unknown

and skip the whole variable? because it wont make the spell less MUI right?

 

[MortAr]

Faster to configurate.
Also, if its a MUI spells, it allows every instance to have a different value, not always use a constant one.

 

[Chewii]

But if the value is supposed to be the same every instance then it must be declared as MUI without the variable?

 

[MortAr]

It is MUI as long as it works for multiple units at the same time.
Variables such as this one will not make "un-MUI".

 

[Nichilus]

If the damage is constant then I think yes.
Storing the value first is better if the damage is different per cast (like it takes part of caster's attribute as bonus, etc.). It's way better to store it if your ability is AoE-based (in other words, it's better if you were about to loop a group of targets)

 

[Xonok]

One common practice in programming is like this "If you use something more than once, then put it in a variable".
There is also a similar saying about functions.

 

[deathismyfriend]

Changing a variable tht u only have to click once to set it is better than clicking 4 or 5 times for same effect

 

[Xonok]

Changing a variable tht u only have to click once to set it is better than clicking 4 or 5 times for same effect

Exactly. There's also one more reason, if the engine is well-written. Variables are faster to read than running through a set of functions to get those variables. (Eww, GetTriggeringUnit)

 

[deathismyfriend]

Lol ya plus it's easier to edit the variables.