Knockback Unit

[WraithSeeker]

You need JNGP aka JassNewGenPack or any vJASS complier.

 

[Silvenon]

lol, i'm glad this function didn't have any major bugs, i was kinda expecting that someone will report something already, i guess i'm just lucky (with a lot of previous help from you guys)

i MAY try to modify it a bit, look at your posts etc, but i didn't do jass for a long time now, i have to get into track again

 

[Yixx]

I also have one thing to mention here
It is actually the same efficiency thing as with your Jump System,
You create a unit for every Destructable you kill (you check for it to be a tree),,
Just do as you did with the Jump sys there, a global unit, and move it
(Dont forget to order it to stop again,,)

EDIT:
I have seen this before, and it is kinda strange to me:

set Total = Total + 1
set Ar[Total - 1] = dat

Just flip those two, and remove the -1 from the (now) second line,,
I though you already knew that =P

 

[Silvenon]

I also have one thing to mention here
It is actually the same efficiency thing as with your Jump System,
You create a unit for every Destructable you kill (you check for it to be a tree),,
Just do as you did with the Jump sys there, a global unit, and move it
(Dont forget to order it to stop again,,)

EDIT:
I have seen this before, and it is kinda strange to me:

set Total = Total + 1
set Ar[Total - 1] = dat

Just flip those two, and remove the -1 from the (now) second line,,
I though you already knew that =P

Thanks for the help, but I don't feel like editing this anymore. There are much better knockback systems on wc3c or thehelper. The jump function, however, isn't so common.

Yeah, someone already pointed out that calculation thing, but I didn't fix it because I think there was something wrong with that, however, I can't remember what. Also, it's not really a problem.

 

[InfinateAnswers]

the GUI part that says Set Target = Target unit of casting can it be changed to All units in x range?

 

[Silvenon]

Don't freakin use this. There are much better systems.

 

[D4RK_G4ND4LF]

you are creating a new rect every time you check for trees
you are creating a new unit every time you check if that dest is a tree
SetUnitX/Y will knock units into environment and make them stuck there
(better use some item to check pathing there first)
IsTerrainPathable is crap because it does not detect trees since they are placed after blizzard ran its crappy path mapping stuff or something

GetLocationZ has the ability to desync.

if you use it wrong
e.g. if you are using thunder clap (don't know if it was this special effect but might be) the terrain will not be deformed with special graphic setting and therefore GetLocationZ will return a different value
but you should not use terrain deforming special effects any way since they can cause lag in multi player maps with mass doodads and players and units in certain cases
however GetLocationZ is obsolete for path checking since there is some item trick
(i wrote a tutorial about it
(not really finished yet bout it soon will be)

 

[Prince.Zero]

Don't freakin use this. There are much better systems.

I already used this when i started jass
it was my candle of guidence
i forgot to give you rep
GJ

i also removed some redundant calls now because well.. i have an AOS.

 

[Bribe]

Moved back to Submissions until some things are fixed, namely getting rid of "onDestroy", TreeFilter should use a better check (a static unit that always exists, plenty of good options out there), needs pathing check...

 

[Bribe]

Execute called by trigger evaluations, twice the workload so it fails.

No pathing checks so it fails.

Using unsafe pausing and unpausing of units so it fails.

Using dynamic units for tree checking is epic fail.

Using a dynamic rect instead of SetRect or MoveUnitTo is bad.

Graveyarded.