[General] Why exactly do terrain functions run so badly?

[Tal'Rarity]

Like why the leaks and d/c's as well were we never given the access needed to fix these? Not to mention it doesn't even re-set destructible heights.

 

[deathismyfriend]

Depends what exactly you mean ?
When changing a terrain tile to another it runs perfectly fine. It is however very costly so it can cause the op-limit to be hit.

 

[Tal'Rarity]

Sorry, I meant the height-changing of terrain such as crater.

 

[deathismyfriend]

I believe that is because it is an effect. The area around the terrain effect is never updated so it looks bad. I don't think this will be fixed. You may be able to manipulate it on your own though and cause the terrain deformation and update the surrounding object to the new terrain height. But be careful as those are costly and can easily hit the op-limit if a big area is done at once.

 

[Dr Super Good]

Like why the leaks and d/c's as well were we never given the access needed to fix these?

It causes an out of sync error because the results of the deformation are not deterministic and meant to be used purely cosmetically. Especially when used with GetLocationZ the result returned could be different for each player depending on their visual settings and build of WC3 and easily result in an oos error.

We cannot fix it as WC3 is a closed source game owned by Blizzard so we lack the facilities to fix it. The solution would be to make deformations deterministic using very strict rules and possibly even ignoring the game settings (who plays below max anyway?).

It is not just trigger deformations that are a problem, it also applies to shockwave and war stomp.