| 01-11-2004, 04:39 AM | #1 |
is there any way to make a unit unselectable? i selected the knight as my custom unit, changed the model to something thats not visible, but i dont want the person to be able to know its there by clicking on it. |
| 01-11-2004, 04:46 AM | #2 |
Using a "Unit - Add Ability" trigger to give it the Locust (Aloc) ability makes an unit unselectable. |
| 01-11-2004, 05:04 AM | #3 |
that did NOT work. |
| 01-11-2004, 06:02 AM | #4 |
Yes it does. Give it the unit ability "Locust". It will make it unselectable. I wonder what happens when you change selection size to 0 also... |
| 01-11-2004, 06:19 AM | #5 |
Selection size to zero doesn't do much...that's the size of the little green circle. (unless there's something new in 1.4) |
| 01-11-2004, 06:36 AM | #6 |
whoops, my bad, im a moron, lol, thx u 2 :) |
| 01-11-2004, 11:41 AM | #7 |
Locust makes a unit unslectable. It also makes it untargetable, invisible on minimap and turns off collision for and against the unit. This is fine for caster type units in custom spell creation and a few other uses. If all you want is a unselectable unit without all of the other things you have to do several things. First create a chaos ability that transforms a unit into the unit you want. It must create a new unit type not just transform a footman into a footman. Remove the chaos research requirement for your new ability. Then add your chaos and locust to the unit. This should all be done in the object editor not with triggers. The new unit is now unselectable only. There are a few disadvantages to this. First you have to have a chaos ability for each unit. Second if your unit is hidden it will lose the unselectablity. Since locust cannot be added via triggers you cant just reset the unselctablity. You would have to create a new unit. |
| 01-11-2004, 02:34 PM | #8 | |
Quote:
This statement isnt entirely accurate. If you use UMSWE you can use enter the Aloc ability string instead of using the GUI. That way you can add the ability. |
| 01-11-2004, 05:36 PM | #9 |
If you go to Spawned Effects and use the model 'bugger'... it's unselectable and invisible... |
| 01-14-2004, 10:15 AM | #10 |
th15: Didnt know UMSWE had that. We dont use it. We also dont have to redo our trigger systems every time a new patch comes out. :Heh: OT: There are a few models that can do that as well as the hide ability. Didnt know what bugger did tho. Never messed with it. |
| 01-16-2004, 12:15 PM | #11 |
you can simply add the spell to a unit via custom script like UnitAddAbilityBJ("Aloc", udg_unit) (not sure whether the function is correct or not, you can go get it by converting a test trigger with the function in GUI into custom text) |
