Changing animation when acquiring an item

[HelloFlighty]

• Carrying
  • Events
    • Unit - A unit Acquires an item
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to Peasant
  • Actions
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • ((Item carried by (Triggering unit) in slot 1) Equal to No item) and ((Item carried by (Triggering unit) in slot 2) Equal to No item)
      • Then - Actions
        • Animation - Add the gold animation tag to (Triggering unit)
      • Else - Actions

I can't seem to get this to work, I want the gold animation tag to be added to any peasant that acquires and item, so it actually looks like he is carrying something.

 

[Jampion]

If there is no item in slot 1, it will be picked up and will be in slot 1, so there will always be an item in slot 1.
The item is already picked up, when the event fires.

 

[HelloFlighty]

If there is no item in slot 1, it will be picked up and will be in slot 1, so there will always be an item in slot 1.
The item is already picked up, when the event fires.

how can I make a system that adds the gold tag when the unit has 1 or more items in his inventory and remove the gold tag when there are No items in his inventory?

 

[Jampion]

If he just picked up the first item, it will be in slot 1, so

unit acquires an item
item being manipulated = item in slot of triggering unit and "hero has no other items"

I think you could also just use the event without conditions (except the peasant condition), because whenever the unit acquires an item it will have >= 1 items
It would add the tag, if the unit already has it, but I don't think that's bad.

 

[Kaijyuu]

There's no harm in adding it if already has it, from what I remember. So just always add it when a peasant picks up an item.

As for removing it, just check every time a peasant uses or loses an item if all its slots are empty.

EDIt: Ninja~

 

[HelloFlighty]

There's no harm in adding it if already has it, from what I remember. So just always add it when a peasant picks up an item.

As for removing it, just check every time a peasant uses or loses an item if all its slots are empty.

EDIt: Ninja~

What trigger checks if all a units slots are empty? i can't seem to find one

UPDATE: Nvm i found it, thanks guys

EDIT: so i got this and it doesn't change the units animation.

• Not Carrying
  • Events
    • Unit - A unit Loses an item
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to Peasant
  • Actions
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Number of items carried by (Triggering unit)) Equal to 0
      • Then - Actions
        • Animation - Remove the gold animation tag to (Triggering unit)
      • Else - Actions

RE-EDIT: Solved it with this

• Not Carrying
  • Events
    • Unit - A unit Loses an item
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to Peasant
  • Actions
    • Set TempUnit = (Triggering unit)
    • Countdown Timer - Start Drop_Timer as a One-shot timer that will expire in 0.00 seconds

• Timer End
  • Events
    • Time - Drop_Timer expires
  • Conditions
  • Actions
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Number of items carried by TempUnit) Equal to 0
      • Then - Actions
        • Animation - Remove the gold animation tag to TempUnit
      • Else - Actions

Apparently Warcraft 3 doesn't recognise the event "Loses an item" quick enough because it needs a delay for some reason

 

[Kaijyuu]

A 0 second wait will suffice and not require any global variables. "Triggering unit" is one of the few event response variables preserved over waits, so it's safe to use after one.

 

[HelloFlighty]

A 0 second wait will suffice and not require any global variables. "Triggering unit" is one of the few event response variables preserved over waits, so it's safe to use after one.

i know i could use the Wait action but i've had bad experiences with that action before and i've been told by some pretty experienced editors Not to use it and to use timers instead because "wait" stuffs up triggers in some cases and is unreliable

 

[Kaijyuu]

Long waits tend to be inaccurate, and using an enormous number of them will lag your map in ways timers won't. 0 second waits won't be a problem pretty much ever.

 

[Jampion]

A problem with wait is for example, that 0 seconds wait is not 0 seconds, but more like 0.1 seconds. This effect is even worse on multiplayer maps.
Wait Command, Good or Bad?