3D Pathing v2.0

[Moderator]

12th Dec 2015
IcemanBo: Too long as NeedsFix. Rejected.

Units bug at edges of platforms, the go up and down very rapidly making them blink
Units can also get stuck on edges of platforms
I used a flying unit and it somehow lost its selection circle
Maybe flying units don't need to fall
You might not want to pick structures
I think you should use a group you don't destroy, add/remove units to/from it

Old reviews

Instead of picking every unit in the map, you should do a group managing system. No you're picking structures and dead units also.

Use a group you never destroy, add units that enter the map/ are bough/revived etc. there. Remove dead units.

The Crow Form adding shouldn't be done in the looping trigger. As far as I can see, this shouldn't be done in the looping trigger as it goes to the then only once:

• (Load 0 of TempInteger from Pathing) Equal to 0

And like Bribe said, make the two hashtable values normal variables.
I also recommend Unit Indexer instead of a hashtable due to arrays being faster.

Efficiency should be improved.

Bribe, 12th Aug 2011

• Hashtable - Save 30 as 0 of 0 in Pathing
• -------- *Gravity Level* Note that if you make it 0 units will be suspended in air. --------
• Hashtable - Save 8 as 0 of 1 in Pathing

These two should be normal variables, not hashtable values.

Custom script: set udg_TempUnit = GetEnumUnit()
Set TempInteger = (Key (Picked unit))

The custom script is still unnecessary and still you reference (Picked unit) even though you had it set to a variable right above it. Reference the variable - don't call the function again.

Because you reference every single unit in the map every 0.03 seconds, I strongly advise using arrays with GUI Unit Indexer instead of hashtables, because hashtables are way slower than arrays.

 

[Noobsmoke]

Very nice worked and very usefull thanks for sharing 5/5. I got 1 question btw, why this system isn't intended to be used more then 100 units ? i mean ... why 100 ? (just curious )

 

[maddeem]

If you have about 100 units or more it lags xD (haven't actually tested this theory, just a guess)
+rep for first comment =p

 

[xxxMAX_007xxx]

If you stand on second platform in the bot of the map and jump from it to the left your unit will slide forever

this applies to all platforms with low height

 

[mnib]

/\ This
happend to me both on bottom ramp as for uper ramp

 

[maddeem]

really? i must have uploaded the 0 gravity map... ill test this now
Fixed, lol the error was so small took me like an hour to find xD
~Updated~

 

[makai]

my foot man sliding... btw, it's annoying when you order your unit to move behind the cliff and the cliff make your unit stop...

 

[maddeem]

I was going to have it so that you can go under terrain. Then it would have been 3D pathing. Saddly you can't make a unit's height go to a negative value through triggers. Really disappointing >=(
I have a few new fixes n such anyway though. I'll post them in a second.
~Updated~

 

[Magtheridon96]

>.>
._.
-.-
o.o


Ok.. Now that I'm over that, time to actually post something serious.

In your Main Trigger, don't use (Picked Unit) after you already did:

• Custom script: set udg_TempUnit = GetEnumUnit()

Use that variable instead.

Also, instead of adding and removing the crow form ability, do this:

• Custom script: if UnitAddAbility(udg_TempUnit,'Arav') then
• Custom script: call UnitRemoveAbility(udg_TempUnit,'Arav')
• Custom script: endif

This is much safer (A unit that already has the ability would be f***ed if you add and remove the ability.


Btw, this was done along time ago in vJass by Nestharus
He called it CliffBound.
Then he wrote SlopeSpeed, but unfortunately, they're sorta graveyarded

One last thing, always remember this:
Never repeat stuff like (Picked Unit)...
Set them inside variables and then use said variables instead of calling the function again and again and again

 

[maddeem]

Orly? Already been done? Ehh. Anyway do you know how to set a unit's height to a negative value ingame?

 

[Magtheridon96]

Orly? Already been done?

Dont worry about that, they were graveyarded

Here's a tip, setting the unit's fly height to 0 moves the unit to the ground. If you want to allow units to move underground, the tunnel (Underground tunnel that is) should have it's base as part of the terrain and the cieling should be a doodad ^^

 

[.VTZ.]

u can fit it into a Grand Chase map like, with some jump (ground to plataforms)?

 

[maddeem]

Sorry guys, I didn't realize I wasn't posting the right version like 5 times xD
Anyway, I've updated a few things.

"u can fit it into a Grand Chase map like, with some jump (ground to plataforms)?"
You can put in a jump spell. Heck, might add that myself =p

~Updated~

 

[.VTZ.]

but non jass spells make units "move" for each second? or it detect units height, without any chance to face a invisible wall lol?

k. ill try

 

[D1000]

Units always make little stops while running down the ramp at the bottom of the map
Also a soldier which fell down in the edge of two overlaying blocks got stuck (see pic)

Otherwise it seems to be a great system, 5* (To lazy to look at the triggers in the moment)

 

[maddeem]

Fixed all bugs. Also added jumping =)
~Updated~

 

[.VTZ.]

yeah thanks for the jump spell.
but it do not going to work, wc3 plataforms just cant be walkable Under it :x
for mine map idea

 

[maddeem]

~Updated to a moderator's request~

"Because you reference every single unit in the map every 0.03 seconds, I strongly advise using arrays with GUI Unit Indexer instead of hashtables, because hashtables are way slower than arrays. "

First off, I'd like you to prove that hashtables are slower then using arrays with your GUI Unit Indexer.
Second, I laughed when you basically advertised your spell in my system.
And it is absolutely essential that I pick every unit every .03 seconds.
I see nothing wrong with using custom script, as this is my system I will do to it what I see fit.

 

[ZeroNoWing]

will you add damaging to this system?
I mean... When unit lands from high cliff it get damage/

 

[maddeem]

will you add damaging to this system?
I mean... When unit lands from high cliff it get damage/

I originally had it that way but i figured no one would really need this. I can add it back soon =p

 

[ZeroNoWing]

okay thanks ))

 

[Bribe]

First off, I'd like you to prove that hashtables are slower then using arrays with your GUI Unit Indexer.

Arrays are 4-6 times faster than hashtables, sometimes even faster.

Second, I laughed when you basically advertised your spell in my system.

If it wasn't mine I would still recommend it because it's a much better solution to what you have here.

And it is absolutely essential that I pick every unit every .03 seconds.

Nothing wrong with that. Only if you do this you need to put a huge, huge emphasis on efficiency to make sure your script can handle even tough performance scenarios.

Keep in mind that you might have a way way faster computer than a lot of other people.
So what runs no problem for you may totally lag other computers.

 

[maddeem]

Arrays are 4-6 times faster than hashtables, sometimes even faster.



If it wasn't mine I would still recommend it because it's a much better solution to what you have here.


Nothing wrong with that. Only if you do this you need to put a huge, huge emphasis on efficiency to make sure your script can handle even tough performance scenarios.

Keep in mind that you might have a way way faster computer than a lot of other people.
So what runs no problem for you may totally lag other computers.

No one will use this anyway lol
this is was more of a test to see if something like this was even possible. Anyway I don't feel like updating this anymore.

 

[Exavier00]

Please continue it... i've been searching for this a long time... dont stop... i need it for my map

 

[maddeem]

Oh? Got any ideas on how to improve it. And since you need it... I might convert this to use indexing! (will be faster)

 

[Exavier00]

yes...
+please fix the part when a unit tries to get into higher ground..(it makes them blink, stop, and return them to their previous position)...
+can you make a pathing that could stack one another? example. when you're at the ground (i.e base level) you try to walk to high ground (higher pathing) you'll end up walking underneath the pathing, but if you're at higher ground or at least your height (pathing) is higher than where you want to go it allows you to get to that height (pathing). "maybe you can add fly to those units which enters that path? and remove them if the go to base ground or decrease and increase their height depending on the pathing"... also gravity is cool!

 

[maddeem]

"+please fix the part when a unit tries to get into higher ground..(it makes them blink, stop, and return them to their previous position)... "
That is the whole point of this system lol
As for the second part. It is impossible. Why? Tis much to hard to explain.

 

[Justicebringer]

Well done dude!