Frost Wrath v1.1a

[Moderator]

11:21, 4th Jan 2010
TriggerHappy:

As maker said hashtables would be way slower than reading from a global, so for your constant values just use a global. Otherwise this spell is approvable.

 

[-Berz-]

Ah, screenshot... fixing

 

[krisserz]

^^ the contest had just finished, and the spell is already here xP
But it is nice.
(Psst, you done something wrong with your bb code in description (

) ;p)

 

[-Berz-]

Well, I'll update my submission a few times (still better than just saying "mah 60th spel, hop u lyek it and gief gief rep")

 

[krisserz]

Well, I'll update my submission a few times (still better than just saying "mah 60th spel, hop u lyek it and gief gief rep")

Nah, it`s "gief gief REP, REP, REP!!!! and CREDITS!!!"

The coding is ok, the rest is ok, overal is ok, generally is ok, looks ok. So 4/5 ;p

 

[-Berz-]

Nobody else lyekz mah zpel :/

 

[krisserz]

But ur zpellpack is uberproimbaowningkillingspree. Taht is 1337 ;] Tis one is 1337 2!

Unfortunately this haven`t made you win your competition. But it is eye-candy!
Calex`s spell was eye-candy too... ;p

 

[calex3]

I like it.... It is useful for my map I'm making .....
(I am making map where you ahve hero with 20 hp and with "lucky" spells which deal 2-5 damage....Like meat hook so i neeed small and crazy cool things like this one )
And eyecandy is not bad at all we all love your spell

 

[Maker]

I'd separate these from the casting trigger, and create an initilization trigger for the constant values. Though the performance gain is very small, it's still there

You save/load FW_KB_Speed to hashtable though it's a global constant, it does not get modified. It would be slightly faster to just use the variable instead of loading it from hashtable.

The hotkey is wrong.

I like the spell overall, well done.

 

[-Berz-]

Fixed the hothey (learn was actually correct )
Well I wont stick those values to init trigger since someone could get confused when importing. Speed is saved/loaded because if someone would desire to increase/decrease KB speed per level (so it would no longer be a constant).

Thanks for your comment, and for a few pointers

 

[Foxiu]

Hi BerZ
I have a problem...
First trigger is saving FW_KB_Distance as 110/180 but second load it as 0
and when it's 0 then knockback and slow don't work
can u help me with that?

 

[-Berz-]

What do you mean it's 0? It's related to picked unit and when it reaches 0 it stops as mentioned. please be more specific what's the problem.

 

[Foxiu]

I know what you mean but... it's saves KB_Distance for enemies at AoE and turn on second trigger... when second trigger starts it's do nothing because at first KB_Distance = 0 but it should be 180 or 110
i can't explain it

 

[-Berz-]

So you're saying you set the distance to 0?

 

[Foxiu]

nooo... it's automaticly setting to 0 ;/ maybe save and load hashtables don't work corectly... it's saves as 180/110 and load as 0... it's must by hashtables bug

 

[-Berz-]

Aha, I understand now. It doesn't bug to me though.

Try to set only one variable ignore/delete that 110 variable and arrange the actions so it will work on all units the same(Knockback distance), and let's see what happens.

 

[Foxiu]

I did like you said but that still didn't work so i tried a lot of things and nothing ;/
I'm bored
Is there a simple way to do knockback without hashtables?
A simple without cuting tree
For example: every 0.03s move unit to point, change point

 

[-Berz-]

You only need knockback? Check for Paladon's knockaback system that contains knockback on single target, aoe, and aoe around the caster. Yes there are other methods that don't require hashtables.

If you need single target knockback, then check my Simple Spell pack spell; beast attack.

 

[Ravernomus]

I guess non has seen what happens if the spell is cast on unwalkable terrain. If one casts that spell on terrain where units can not pass then the effect appears somewhere else, but near. I guess it is not such a problematic bug, since the units in initial AoE are affected and not those where effect spawns. It is just to mention, not to criticize

 

[Maker]

• You should separate the hashtable creation from the Initialization trigger. Create own initialization trigger for the spell
• You should set constants in this init trigger, not during every cast
• You only need 3 location variables for the ability, not 5
• You could use this block in the cast trigger
  • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
    • If - Conditions
      • FW_KnockBack_On Equal to True
      • (Number of units in FW_Damage_Group) Greater than 0
    • Then - Actions
      • Trigger - Turn on Frost Wrath KB <gen>
    • Else - Actions
• Use proper tree detection method -> link
  ^There might be some ability that destroys only trees...
• In the beginning of the looping trigger you load values that you might not need, if the flow goes to the else
• You have RemoveLocations twice in the looping trigger, only have them once
• Remove invulnerability ability from the dummies, the have Locust which makes them invulnerable
• You could set the dummy's Art - Animation - Cast point to 0 so it casts abilities instantly, and not with a 0.3 second delay
• Art - Death Time could be lowered from 3.04 seconds so the dummies are removed earlier