🏆 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!
It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!
Did it, wont work... ehm. Any other sugestion how to make unit unselectable ?
BTW i gave you +rep coz i saw you trying to help me, on few post already.
Ehm... seems like this works:
-------- Unhide Dummy --------
For each (Integer A) from 1 to 100, do (Actions)
Loop - Actions
Unit - Unhide Titan1_store_Hiden[(Integer A)]
Unit - Remove Locust from Titan1_store_Hiden[(Integer A)]
Unit - Add Locust to Titan1_store_Hiden[(Integer A)]
Unit - For Titan1_store_Hiden[(Integer A)] set ability state to Permanent for ability Locust
He is talking about the Locust ability not Lotus.
Also i think that you could try storing it into a variable and after unhide add the locust ability to it(maybe even create a spellbook with locust(never tried it) and adding it to the unit).
Y lol, lotus is position of body xD, sry about that, yes you can, you have to add loctus(rofl forgot the name again) and then you haveto make it permanent, but still, wc3 bug is that unit with loc... ability is selectable after you hide and unhide it.
If there is no way to remove it, why not to replace units?
Just replace unit with the unit of the same type / hp / mp, and the new unit won't have locust ability.
The other way is hiding it, removing it, and unhiding it? The only difference between that and replacing the unit as a whole is that you have to drag-select an "unlocusted" unit instead of simply clicking it (oh, and you only see its HP bar by pressing the alt-key). In general, that's not a big problem.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.