The perfect one step solution for creating Ice/Sliding Mazes in both Reign of Chaos and The Frozen Throne. It is the only decent system around and it even works in RoC, is lagfree, perfectly optimized, fast and reliable. The included TerrainKill feature frees you from the tedious task of creating a thousand kill-regions.

manstieI swear it's impossible to make a unit unable to turn on a certain ice. Impossible!The Hive Workshop can't help me out with it How did swmpmoele do it!?

You have a contradiction there. "I swear it's impossible to make a unit unable to turn on a certain ice." and "How did swmpmoele do it!?" now if swmpmoele was able to do it, then it is definitely possible to do.

But yes, War3 has it's limitations.

My guess is, swmpmoele (whoever he is...) used an old, laggy sliding system, which works with locations instead of coordinates. The lag the system generates prevents the player from clicking fast enough.

If only you could link to a map in particular so I can deprotect it and tell you the solution... I'm still not a mind reader you know.

Well, 3ICEI have found the solution! (I can't believe that you didn't know how to fix it, although you probably did... it's one of those things about you wanting me to do it myself, right?)And that solution is easily added onto your sliding system!

All I did was add an if/then/else to the bottom of the Slide trigger just before: set u=null

I thought in one of the triggers, it said: "Disable this trigger to turn off Steering."

Wouldn't it be better if you just make ALL the ice un-steerable? I didn't try editing any of the triggers, but if 3Ice's system's steering is based on the unit's turn speed, I might have found a solution, in GUI, that is....

If it is, mine would be like this:If a certain unit is on a certain ice, turn rate change to 0.01, or 0.00, haven't tried it in triggers as I have only did in unit editor...zzzDisabling the turning when leaving the terrain, or you could set a Region, when you leave it resets your turning speed, and enters changes to 0.00 or 0.01

If I'm wrong, then I'm sorry on interrupting in your arguments... I'm just trying to help.....

What's so bad about them? I'm just converting some GUI to JASS then adding it to your sliding system. Of course I don't know how to write Jass BJ = Blow Job Functions

I think it is how fast the unit turns around?But at when its at 0 it still turns..?I think an example would be Custom Hero Line Wars, I noticed that the pack horse takes a huge time to turn around and sometimes walks around in a circle to try and turn 180 degrees.

samtreI thought in one of the triggers, it said: "Disable this trigger to turn off Steering."

At the first post:

ManstieIf you mass click in a different direction while on the unable-to-steer ice, it can kind of turn a bit (I noticed this on polar escape as well). Is there a way to fix it?

3ICE also followed point out to us that even when sliding the units still have the ability to move around.

3ICE, take a look at this; the turn rates from 0.5 to 3 look almost exactly the same, but 0 is different.

From this, everyone can see that if we removed those two letters B and J, our code would run faster. Most BJs just call a native with the same parameters. BJ functions are useless and should not be used. (Some people use CustomDefeatBJ and similar functions, because they don't understand how they work. Some BJs span a hundred lines. Not many has patience to read them all so they accept the crippled speed at which they run.) And I agree with you, this name choice really sucks.

manstieI think an example would be Custom Hero Line Wars, I noticed that the pack horse takes a huge time to turn around and sometimes walks around in a circle to try and turn 180 degrees.

Pack horse's turn rate is 0.01, a value which is not allowed in the world editor by default. Catapults move like this too.

manstie3ICE, take a look at this; the turn rates from 0.5 to 3 look almost exactly the same, but 0 is different.

Interesting. Will edit this post after testing is done.

EDIT:Why did you leave in one empty trigger? Renaming the peasants to their corresponding turn rates was a clever idea.But 0.0 actually has 0.1! Always double check everything to avoid such errors.Could have used more between 0.1 and 0.3, probably a 0.25 too.I hope everyone realizes that this is percentage-based, so 0.1 is 10%, 0.5 is 50% and 3.0 is 300%.You should have imported my sliding system so we could test how this all affects sliding.There is still much change going on between 0.5 and 0.9 though.The {0.01 ; 0.99} interval is important. {0} remains untested and the purpose of {1;3} is not yet understood.

That's silly, why make 2 different types of jass (talking to blizzard) when one is them jass, and the other is more efficient...Off Topic Question: How do you make an error message? (e.g. "That unit is already at full Health")

Yay! You called GUI silly. (Even if you don't yet realize it.) That means I successfully converted you into a JASSer. Because you already see the bloat that GUI is, it will be hard for you to use it ever again.

And to explain that above statement: The BJ functions were made as a 'layer' of JASS for GUI to access. I can think on many valid reasons why Blizzard decided to create the BJ functions. Whenever we talk about BJ functions in JASS, we mean the functions that are used by GUI. (Well, most of the time anyway.)

And the other question: Error messages are silly, just display it as normal text. (Or if you must do useless things instead of focusing on improving your map... Vexorian's SimError is first result on google.)