• 💀 Happy Halloween! 💀 It's time to vote for the best terrain! Check out the entries to Hive's HD Terrain Contest #2 - Vampire Folklore.❗️Poll closes on November 14, 2023. 🔗Click here to cast your vote!
  • 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 HD Level Design Contest #1 is OPEN! Contestants must create a maze with at least one entry point, and at least one exit point. The map should be made in HD mode, and should not be openable in SD. Only custom models from Hive's HD model and texture sections are allowed. The only exceptions are DNC models and omnilights. This is mainly a visual and design oriented contest, not technical. The UI and video walkthrough rules are there to give everyone an equal shot at victory by standardizing how viewers see the terrain. 🔗Click here to enter!

Locust acting weird (glitchy movement)

Not open for further replies.
I add locust to the unit in my projectile system, and set movement type to float, because the map is going to have different height levels and occasional fight near the bay, so it looks and works nice coupled with the parabolic function, but the problem is that when I spawn projectiles, they move my hero a bit, because they seem to obstruct the pathing, although all projectiles have locust, disabled pathing, and collision size of 0. There's no point in posting the script as the script is obviously not the problem, as this happens even if I simply create the projectile on top of the unit, or even near it. Locust and crow form are added in object data, the only solution I've seen so far is setting movement type to fly, which fucks up height calculations of parabola function, and those are not just eyecandy here, since I actually use different missile heights in gameplay. Any clues?
Oh and I recommend using the following functions to move the hero
  • Custom script: call SetUnitX( udg_Unit, GetLocationX(udg_Point) )
  • Custom script: call SetUnitY( udg_Unit, GetLocationY(udg_Point) )
This way the hero is forced to the location and it doesn't lose it's current order/action, which will happen with the regular GUI instant move function.
Anitarf@Wc3c said:
The only situations I know of where locust doesn't work as it normally does is in combinations with chaos morphing or hiding units. The [thread=81742]WC3 Ability Guide[/thread] explains this in more detail. I have used one of the exceptions listed there in my [thread=104322]Glacial Wall[/thread] spell. Try copying and using the [thread=101150]xe dummy unit[/thread] instead of your unit to confirm that the problem is with the unit and not your triggers.
Anitarf solved this problem, I thought it was not script related but apparently it is.
Not open for further replies.