Meteorsystem [Gui,Mui] v1.0

[Moderator]

14:21, 3rd Apr 2009
Eccho:

Squiggy, the effects and idea was lulzy indeed, but in a positive way Nothing wrong here. However I have a few things to say about your code, which is, frankly, it's almost lacking. Also, the spell technique you are using is complex. However it is approved and useful. But take a look at my reply in the thread and fix a few things.

 

[f0rsAk3n]

Awe>...some!!!!!!!!!!!!!!

 

[Malcous]

Squiggy , very useful system 100/5 +rep love it

 

[Jack_Sparrow93]

This is just great!

 

[Kingz]

I think this more looks like a spell than a system...
I don't like using of too many abilites/buffs/units in any custom spell/system and yours has a lot of them...
Still it's funny but you could have used a dummy.mdx model and attach it to 1 unit, then instead of using bunch of dummy units you could simply attach difrent models to one dummy...
Nice for lulz, i worked on a lulz spellpack recently but got bored...

 

[Squiggy]

http://www.hiveworkshop.com/forums/spells/?id=vvl75z
eh?

 

[Kingz]

Just try what i said instead of using MS_unit use MS_string which will use difrent strings instead of units, then instead of 10 units make one, give it the imported dummy.mdx model and simply attach random models to it...
This will reduce the number of units so it makes the system more user friendly...

 

[calex3]

only i dont like falling units it.. sux to see turtle falling down from sky......you are so tuf with animals..and are we all having same avatar some russian.....

 

[Cihparg]

O.O Lemme see

Is one within the lol?

 

[Dynasti]

Spell Evaluation

Info

This review was done by Dynasti. If you got a question about this review then please leave me a visitor message

Triggering/Scripting - 3/5

A lot of it was good Squiggy, good to see you making progress in your overall WE skill.

The triggering is nice but could have been better. Example:

• spelltrig2
  • Events
    • Time - Every (Random real number between 0.30 and 0.80) seconds of game time
  • Conditions
  • Actions
    • -------- ... --------

This time event will only be random one time, then it will repeat. My advice, use a timer.

And I think you could have done this more advanced instead of a death event with a timed drop. If you had used a Z movement instead it would look more realistic and good.( This means also if you do it this way you can remove those dummy abilities like TC and WS )​

Visual Effects - 0/5

-​

Documentation - 4/5

Documentation is very good at some points, noobs would actually learn much from this . But I have to say that it could have been better at some places, like explanation of the dummy abilities and such.​

Idea - 0/5

-​

Rating

7/10 Useful

Nice system Squiggy but I would have expected more from you. Keep it up mate
+rep and thumbs up for approval!

 

[Rmx]

WOW nice review Dynasti *** ME LIKE ***

Squiggy i love ur spell it's Crazy and very good........

5/5

 

[dimitri231]

u suck, just used changed the spell Animal Rei

 

[Eccho]

Squiggy, these are the things you should take a look at.

• Special Effect - Create a special effect attached to the chest of (Last created unit) using Abilities\Spells\Human\Polymorph\PolyMorphTarget.mdl
• Set MS_temp_eff = (Last created special effect)
• Custom script: call DestroyEffect(udg_MS_temp_eff)

I wonder why you do this. It might be very minor, but it would be much faster to destroy the last created spell effect instead (there is an action). You do this twice, once in the spelltrig2 and once in the spelltrig3

Spelltrig3 does also leak a point.

I personally would remove all units having a doodad model. They does not look good at all when dying.

Edit: It is pointless to have a timer event with a random interval set. This is just determined at the start of everytime you initialize the map. And Dynasti has mentioned it too.

 

[Squiggy]

Squiggy, these are the things you should take a look at.

• Special Effect - Create a special effect attached to the chest of (Last created unit) using Abilities\Spells\Human\Polymorph\PolyMorphTarget.mdl
• Set MS_temp_eff = (Last created special effect)
• Custom script: call DestroyEffect(udg_MS_temp_eff)

I wonder why you do this. It might be very minor, but it would be much faster to destroy the last created spell effect instead (there is an action). You do this twice, once in the spelltrig2 and once in the spelltrig3

Spelltrig3 does also leak a point.

I personally would remove all units having a doodad model. They does not look good at all when dying.

Edit: It is pointless to have a timer event with a random interval set. This is just determined at the start of everytime you initialize the map. And Dynasti has mentioned it too.

Urr yeah.. I was told that destroying it instantly leaks
Gotta change this back to normal

 

[Eccho]

Hm, I dont know who told you, but it seems very unlogical that it should leak.

This is how the functions looks like:

function AddSpecialEffectLocBJ takes location where, string modelName returns effect
    set bj_lastCreatedEffect = AddSpecialEffectLoc(modelName, where)
    return bj_lastCreatedEffect
endfunction

function AddSpecialEffectTargetUnitBJ takes string attachPointName, widget targetWidget, string modelName returns effect
    set bj_lastCreatedEffect = AddSpecialEffectTarget(modelName, targetWidget, attachPointName)
    return bj_lastCreatedEffect
endfunction

function DestroyEffectBJ takes effect whichEffect returns nothing
    call DestroyEffect(whichEffect)
endfunction

 

[Mage_Goo]

Squiggy, for the spelltrig3, that trigger when Meteor unit dies, you can make it more simple in condition.
Like, give the Meteor Unit an ability, then add this condition:

• Conditions
  • (Level of Dummy Ability for (Triggering unit)) Not equal to 0

 

[Dimetrixdemon]

Hehe