Rain of [X] System, Version 1.1a

[Moderator]

16:18, 29th Apr 2010
The_Reborn_Devil:

The triggering looks good and this system is very useful for GUI users.


Status: Approved
Rating: Recommended

 

[Rmx]

I saw the spell it is an impressive system but >>

1 : It leaks the Target point of ability being cast when you index it, you don't remove the location.

2 : Make the unit fall from more height they seem like moving on the ground, if you look at it artisticaly

This is it for now ^^

Edit : Forgot to rate ... 4/5 ... keep the good work and +reP **)

 

[lolreported]

I saw the spell it is an impressive system but >>

1 : It leaks the Target point of ability being cast when you index it, you don't remove the location.

2 : Make the unit fall from more height they seem like moving on the ground, if you look at it artisticaly

This is it for now ^^

Edit : Forgot to rate ... 4/5 ... keep the good work and +reP **)

Oh, didn't see that leak, anyway. I've uploaded a new version 1.1a and in that update the leak is removed I also added an option that make you able to adjust the starting height of the shards

Thx for the help! +rep

 

[Reaper2008]

Didn't look at it much, but.... indexing?

That will not be in compliance with new rules, but I don't mind. 5/5, as it's easy to edit. Not really efficient (GUI), but no problem.

 

[lolreported]

Didn't look at it much, but.... indexing?

That will not be in compliance with new rules, but I don't mind. 5/5, as it's easy to edit. Not really efficient (GUI), but no problem.

Huh? New rules, I must have missed that. So, aren't you allowed to use the indexing system anymore?

Edit: Thx for the rating btw +rep

 

[Rmx]

That will not be in compliance with new rules,

Recycled indexing is Allowed .. but if it isn't then REJECTED ..

Also about the spell Good job

 

[Reaper2008]

I think it'll be accepted if the indexes are correctly recycled.

 

[calex3]

So paladon's indexing array system is allowed?

 

[Asgard_Ragna]

So paladon's indexing array system is allowed?

When it uses the dynamic index recycling or other recycling it is, yes.

 

[Rmx]

So paladon's indexing array system is allowed?

Ofcourse but it should be recycled in the last ... not indexed to infinity

 

[Roflcoptor]

Well I think from what the rules tell it wouldn't be allowed, but i guess it would hardly even reach 8190.

Still you can easily recycle indexes.

Now you might wanna ask:
Hey why is the "basic" System so bad?

Well let's assume you have a DoT system and use it with spells, which have like 1min duration. Now everyone spams DoT's and the system keeps on counting higher and higher, but never resets, because before all DoT's end there are new ones cast, so it might crash the 8xxx limit sometime (still not very probable but it might).

Using recycling, you would have to have 8190 instances RUNNING to reach the limit.

Recycling works like this (assuming we have 4 spells running; the numbers symbolize their index)

1 2 3 4 ---All 4 spells run, now spell 3 ends
1 2   4 ----Now spell 4 is set in the free space (so all "4" variables have to be set to "3" variables
1 2 4  ---Now spell 2 ends/ same procedure
1    4
1 4 --Now spell 4 ends no recycle
1 ---now spell 1 ends finish turn off loop and so on

EDIT: I was inspired by Dynasti's struct tutorial

 

[MortAr]

Good at all, but it is damaging both enemies and allies?
And, what if I want to make the fire test spell with a damage-per-second?
Something like, 50 initial damage (when the fire ball hits the ground)
and a 10 damage/second when it hits an enemy unit?
Try adding something like this, it should be good.

 

[Deuterium]

Indexing is still allowed... do I have to go around saying it?

CRAPPY INDEXING isn't allowed... there's a difference.

And thus, this would get approved, instant recycling is not a must.

 

[Rmx]

Yes you could recycle normaly just like Paladon sys, or my older spells ^^

 

[Roflcoptor]

Still it's better to recycle them properly, if they last longer, or get used very often, just to reduce loop count

 

[Kingz]

I wrote a tutorial about how to recycle things and the extended version of paladons indexing with it, so you guys can check it out
It uses quite efficent recycling though is increased the variables number a bit(i think 3).

 

[darkreapers]

woah nice system cant wait to try it out!

 

[lolreported]

Good at all, but it is damaging both enemies and allies?
And, what if I want to make the fire test spell with a damage-per-second?
Something like, 50 initial damage (when the fire ball hits the ground)
and a 10 damage/second when it hits an enemy unit?
Try adding something like this, it should be good.

You can set two options if it will damage enemies and/or enemies and allies or structures. Yes, I may add a dps option like that

 

[Itachi009]

if you use indexes, you can find out the first free index place with an easy snip of code or with a little gui trigger, you can find a tutorial here in thehive or on wc3campaigns how to do that, the system itself would be uberuseful if it would be vJass
4/5

 

[supertoinkz]

When is the Channel option coming? D:
I need it!

 

[lolreported]

Channeling option? Ehm, I don't know if I will add that option, maybe if I got time

 

[supertoinkz]

Too bad :C.

 

[FRENGERS]

Really love this @.@
5/5 +rept

 

[Recom]

Awesome stuff!

EDIT:

I found two bugs in the version 1.1a I downloaded here:

1. in the RoX Loop, where the array gets reduced, the following condition of the if-statement is causing a bug. Both arrays are checked in an "and-condition". This will cause the trigger to never stop.

code

• If (All Conditions are True) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • RoX_NumberOfWaves[RoX_Index[3]] Less than or equal to 0
  • Then - Actions
    • Custom script: call RemoveLocation(udg_RoX_TargetPoint[udg_RoX_Index[3]])
    • Set RoX_Index[2] = (RoX_Index[2] - 1)
    • Set RoX_Off[RoX_Index[3]] = False
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • RoX_Index[2] Less than or equal to 0
        • RoX_Index[1] Less than or equal to 0
      • Then - Actions
        • Set RoX_Index[1] = 0
        • Trigger - Turn off RoX Loop <gen>
      • Else - Actions
  • Else - Actions

To fix this, there must be only checked for RoX_Index[2].

• If - Conditions
  • RoX_Index[2] Less than or equal to 0

2. in the RoX Loop, before the spell gets killed, the "RoX_Off" bool is set to "False".

code

• If (All Conditions are True) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • RoX_NumberOfWaves[RoX_Index[3]] Less than or equal to 0
  • Then - Actions
    • Custom script: call RemoveLocation(udg_RoX_TargetPoint[udg_RoX_Index[3]])
    • Set RoX_Index[2] = (RoX_Index[2] - 1)
    • Set RoX_Off[RoX_Index[3]] = False
  • Else - Actions

But it has to be "True".

• Set RoX_Off[RoX_Index[3]] = True

Otherwise the "finished" or "dead" spells will continue running, causing an "override" of variables.

 

[Domyno]

cant find Dummy. mdx
can you give me a link?

 

[KitsuneTailsPrower]

Great system, but there's an issue where magic immune units still take damage even when "magic immunes resist damage" is set to true in gameplay constants.