[General] Making a unit untargetable

[ilian53]

How can i make something untargetable neither by spell or the mouse? When you hover the mouse over it you shouldn't be able to see the force controlling it or anything. Unselectable and being able to click through it. Is it possible?

 

[Chucky]

make it invulnerable if you want to be unattackable by all players and give it the locust ability.

 

[Maker]

• Untitled Trigger 013
  • Events
    • Player - Player 1 (Red) skips a cinematic sequence
  • Conditions
  • Actions
    • Set u = Footman 0030 <gen>
    • Custom script: call UnitAddAbility(udg_u, 'Aloc')
    • Custom script: call UnitRemoveAbility(udg_u, 'Aloc')

 

[ilian53]

I don't understand why would adding the locust ability be able to make it unselectable or anything. Could you please explain? (I will try it though)

 

[Chucky]

do you know the crypt lord's ability locust swarm ? they float around biting enemies but you can't select them with the mouse. Only the computer can move them around because he issues orders directly not by mouse.

 

[ilian53]

Yes i know that. I didn't find the buff/ability id Aloc though, is it the buff that the locusts have? Or something like that?

 

[Chucky]

I don't think it has any buf...Just go into object editor, give a unit the locust ability, place the unit in the map then test. You'll see that it works.

 

[The_Silent]

Is a ability called Locust, just add it to the unit in it'll become unelectable

 

[Dr Super Good]

I don't understand why would adding the locust ability be able to make it unselectable or anything. Could you please explain? (I will try it though)

Its one of those facts with WC3. The locust passive ability just does make the units unselectable and untargetable.

Yes we can explain why the locust ability was programmed with those hard coded properties (for the locusts of the locust swarm ability used by the crypt lord hero) but why the locust passive has these properties and not some other arbitrary passive was a development choice by blizzard that we can not explain.

This is where SC2 data is far more logical than WC3.

 

[Chucky]

Its one of those facts with WC3. The locust passive ability just does make the units unselectable and untargetable.

Yes we can explain why the locust ability was programmed with those hard coded properties (for the locusts of the locust swarm ability used by the crypt lord hero) but why the locust passive has these properties and not some other arbitrary passive was a development choice by blizzard that we can not explain.

This is where SC2 data is far more logical than WC3.

Please explain in detail the more advanced features of the Starcraft 2 editor as I do not own SC2.

 

[Dr Super Good]

All the data in SC2 is made by extending primitive types. As such you need more data to get something done in SC2 but it is a lot more flexible.

Want a unit with a slow attack and no damage? In WC3 you need atleast 1 damage dealt while in SC2 you can just skip a damage effect from his weapon effect chain.
You can also do nice visual effects such as getting a roach to jump onto the back on an ultralisk to make a roach rider (stupid idea but should be completly possible).

 

[ilian53]

The starcraft editor is really complex. When i opened it for the first time i was like "wtf, how am i supposed to do anything?" and i am still unable to create a custom unit...

I heard blizzard created the SC2 editor first and then created the game itself using it and nothing custom even the UI itself is modifiable. Everything can be made in SC2 (without diablo, because triggers are lacking 1 critical thing that diablo has, the moving of the character when the mouse is pressed).