SC2Mapster

Heya I'm trying to make it so that when you click a unit it will tint colour and then when you click it again it goes back to normal. I tried adding the following to the actor events:
UnitClick.Wall_Dirt
=> IsStatus Clicked 1
     Set TintColor 96,255,43

UnitClick.Wall_Dirt
=> IsStatus Clicked 2
     ClearTintColor

ActorCreation
     StatusSet Clicked 1

UnitClick.Wall_Dirt
=> IsStatus Clicked 1
     StatusSet Clicked 2

UnitClick.Wall_Dirt
=> IsStatus Clicked 2
     StatusSet Clicked 1

It seems however it causes to trigger the IsStatus Clicked 2 events aswell when you click it once.

Quote from DrSuperEvil:
Tried adding the At Caster term as well?
----

Nope, Where should it be added (I'm new to the data editor)?

@DrSuperEvil:

So I guess I'll have to make the tinting an effect/behaviour?

Quote from DrSuperEvil:
No. Just add the At Caster term so that it checks the status is 0/1 at the caster (clicked) unit and not any other of your units of the same type.
----

Well the term at (caster) doesn't exist in the UnitClick.

@DrSuperEvil: Go

Ye, your problem is the way the engine decides to run actor events, I didn't figure out wether you have some form of control over the ordering or if the engine decides it all at run time. I imagine your current event flow chart looks a bit like this:

Click Unit-> Clicked == 1? -> Set Tint -> Set Clicked == 2 -> Clicked == 2? -> Set Tint -> Set Clicked = 1

I had a similar issue with some things I was testing recently. I have a map file somewhere where I corrected the problem, will take a look to see if I can't find it and post the solution.

@Kalekin:

Thanks!

@DrSuperEvil:

Yeah I know but it doesn't seem to be there, I know it is at the Marauder however when I try to add the Term it's not there.

the at - term only appears for events, where it can be used.

@Kueken531:

Strange that it doesn't show up on unitclick then, that's an event afterall

Exactly, but its an event, which does not support a caster or anything like this, thats why the at is irrelevant, thus cannot be used.

If you use for example an effect - event, you can use at again, because an effect has a caster, a target etc.

gonna bump it as I'm still having the problem.

Quote from DrSuperEvil: Go

Then do like a marauder since that works and have the click use a status increment and when status = 2 it sets status = 0

this.

Instead of

UnitClick.Wall_Dirt
-> IsStatus Clicked 1
StatusSet Clicked 2

UnitClick.Wall_Dirt
-> IsStatus Clicked 2
StatusSet Clicked 1

Try

UnitClick.Wall_Dirt
StatusIncrement Clicked

UnitClick.Wall_Dirt
-> IsStatus Clicked 3
StatusSet Clicked 1

for your way, it seems to trigger both events sequentially, so it sets the status before checking the 2nd event. With the increment, this should be irrelevant.

@Kueken531:

Alright, it worked when I set

UnitClick.Wall_Dirt
StatusIncrement Clicked

UnitClick.Wall_Dirt
IsStatus 5
StatusSet 1

UnitClick.Wall_Dirt
IsStatus 3
ClearTint

What it did (I think) was that it counts both pressing and releasing as a click for some reason.
Thanks for the help DrSuperEvil and Kueken!

Quote from syltman: Go

What it did (I think) was that it counts both pressing and releasing as a click for some reason.

Makes sense, too bad you cannot select a sub-event (like UnitClick.Wall_Dirt.click or UnitClick.Wall_Dirt.release)