No, why?manstiebetter
Events
Unit - A unit comes within range of PlayerUnits[1]
Conditions
(Unit-type of (Triggering unit)) Equal to (==) Jumper
Actions
Animation - Change PlayerUnits[1] flying height to 350.00 at 500.00
Wait 0.90 seconds
Animation - Change PlayerUnits[1] flying height to 5.00 at 500.00
Wait 0.05 seconds
Animation - Change PlayerUnits[1] flying height to 0.00 at 500.00
Actions - Pick Every Unit of Jumper in Playable Map Area and Add Event to Jumper1 A unit comes within range of Picked Unit(s)
Events
Conditions
(Unit-type of (Triggering unit)) Equal to (==) (Unit-type of PlayerUnits[1])
Actions
Animation - Change PlayerUnits[1] flying height to 350.00 at 500.00
Wait 0.90 seconds
Animation - Change PlayerUnits[1] flying height to 5.00 at 500.00
Wait 0.05 seconds
Animation - Change PlayerUnits[1] flying height to 0.00 at 500.00
Why 500? Do you even understand what that field is for?manstieAnimation - Change PlayerUnits[1] flying height to 350.00 at 500.00
Exactly. Excellent thinking!samtre1)it might be your PlayerUnits[1] equals to No Unit
Stupid, stupid stupid!samtre3)maybe you could change your Jumpers collision size to about 0.01?lol or 10 or so, the unit's collision size collides with ground units, so maybe you need to change the collision size a bit.
samtre(Unit-type of (Triggering unit)) Equal to (==) (Unit-type of PlayerUnits[1])
Wrong. Arrays are only initialized after event registration is complete. You told the trigger at event init to watch units coming close to null. PlayerUnit[1] was null when the game started. It only gets assigned to a value on map init, which happens after event init.manstiePlayerUnit[1] is = a unit.
Yes, if the event is registered for the jumper.manstieDoes Triggering Unit work for the unit that "the jumper came within range to"?
You messed it up yourself. By the way there has been nothing in patches for a long while that could break maps like yours. All recent patches have done nothing with the editor. 1.24 is the first editor patch in years. And it's change only affects the return bug.manstieIt was working before... (I haven't upgraded to 1.24 yet though)
samtre
(Unit-type of (Triggering unit)) Equal to (==) (Unit-type of PlayerUnits[1])
Does Triggering Unit work for the unit that "the jumper came within range to"?
Boosters
-- Events
-- Conditions
- ((Triggering unit) is A Hero) Equal to True
- Player_Boosting[(Player number of (Owner of (Triggering unit)))] Equal to False
- (Unit-type of (Triggering unit)) Equal to Ice Skater
-- Actions
- Set Player_Boosting[(Player number of (Owner of (Triggering unit)))] = True
- Special Effect - Destroy Player_Special_Effect[(Player number of (Owner of (Triggering unit)))]
- Special Effect - Create a special effect attached to the origin of (Triggering unit) using Abilities\Spells\Orc\EtherealForm\SpiritWalkerChange.mdl
- Set Player_Special_Effect[(Player number of (Owner of (Triggering unit)))] = (Last created special effect)
- Unit - Set (Triggering unit) movement speed to 522.00
- For each (Integer A) from 1 to 200, do (Actions)
- - Loop - Actions
- - - Wait 0.01 seconds
- - - Unit - Move (Triggering unit) instantly to ((Position of (Triggering unit)) offset by 10.00 towards (Facing of (Triggering unit)) degrees)
- Wait 1.00 seconds
- Set Player_Boosting[(Player number of (Owner of (Triggering unit)))] = False
Return to 3ICE's Sliding System for RoC
Users browsing this forum: No registered users and 1 guest