[Trigger] Silent Strike (offset problems)

[thegreatninjaman]

i am working on a spell that silences enemy hero then teleports him to that hero. for some reason it keeps teleporting the hero to center of map instead of behind him.

• Silent Kill
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to Silent Strike (silence. Shadow Ninja)
  • Actions
    • Wait 0.75 seconds
    • Set SilentKillTempPoint1 = (Position of (Target unit of ability being cast))
    • Unit - Move (Casting unit) instantly to (SilentKillTempPoint1 offset by 75.00 towards (Angle from (Position of (Casting unit)) to SilentKillTempPoint1) degrees), facing SilentKillTempPoint1
    • Unit - Cause (Casting unit) to damage (Target unit of ability being cast), dealing (75.00 x (Real((Level of Silent Strike (silence. Shadow Ninja) for (Casting unit))))) damage of attack type Spells and damage type Normal
    • Custom script: call RemoveLocation( udg_SilentKillTempPoint1 )

any help would be appreciated

 

[Pharaoh_]

It's because of the wait. Store every value needed in a variable before proceeding with the actions.
Use Triggering unit instead of Casting unit.

 

[thegreatninjaman]

thank you

 

[defskull]

However, Waits works well with (Triggering unit), only that function works well.

 

[Maker]

However, Waits works well with (Triggering unit), only that function works well.

There are other unit event responses that work after a wait

 

[Bribe]

The best way is definitely an indexing system anyway. Most people need to store a lot more than just the (Triggering unit) or (Triggering player).

Are there other common functions that are MUI with a wait?

 

[mckill2009]

why dont you make it all in custom scipts and use local variables?

• Custom script: local unit caster = GetTriggerUnit()
• Custom script: local unit target = GetSpellTargetUnit()
• Custom script: local location loc1 = GetUnitLoc(target)
• Custom script: local location loc2 = PolarProjectionBJ(loc1, 75.00, GetUnitFacing(target))
• Custom script: local real damage = 75. * I2R(GetUnitAbilityLevel(caster, 'ABILITYCODEHERE'))
• Wait 0.75 seconds
• Custom script: call SetUnitPositionLoc(caster, loc2)
• Custom script: call UnitDamageTarget(caster, target, damage, false, false, ATTACK_TYPE_MAGIC, DAMAGE_TYPE_NORMAL, null)
• Custom script: call RemoveLocation(loc1)
• Custom script: call RemoveLocation(loc2)
• Custom script: set caster = null
• Custom script: set target = null
• Custom script: set loc1 = null
• Custom script: set loc2 = null

 

[Bribe]

Because the learning curve on that is too steep for most GUI users. It's better to help people learn to help themselves, and putting the "solution" in custom script is going to confuse and/or turn off most people.

 

[Ceday]

The best way is definitely an indexing system anyway. Most people need to store a lot more than just the (Triggering unit) or (Triggering player).

Are there other common functions that are MUI with a wait?

Lots of event responses except GetSpellTargetUnit and GetSpellTargetX/Y/Point

I am lying, I just tested this with Killing unit, dying unit, attacking unit long ago and they are working fine

 

[Justify]

Lots of event responses except GetSpellTargetUnit and GetSpellTargetX/Y/Point

I am lying, I just tested this with Killing unit, dying unit, attacking unit long ago and they are working fine

They (should) work because they don't exist. They are only wrapper functions for triggering unit.

 

[Kanadaj]

why dont you make it all in custom scipts and use local variables?

• Custom script: local unit caster = GetTriggerUnit()
• Custom script: local unit target = GetSpellTargetUnit()
• Custom script: local location loc1 = GetUnitLoc(target)
• Custom script: local location loc2 = PolarProjectionBJ(loc1, 75.00, GetUnitFacing(target))
• Custom script: local real damage = 75. * I2R(GetUnitAbilityLevel(caster, 'ABILITYCODEHERE'))
• Wait 0.75 seconds
• Custom script: call SetUnitPositionLoc(caster, loc2)
• Custom script: call UnitDamageTarget(caster, target, damage, false, false, ATTACK_TYPE_MAGIC, DAMAGE_TYPE_NORMAL, null)
• Custom script: call RemoveLocation(loc1)
• Custom script: call RemoveLocation(loc2)
• Custom script: set caster = null
• Custom script: set target = null
• Custom script: set loc1 = null
• Custom script: set loc2 = null

LOL DUDE it's just a JASS scipt captured in the fiery cage of GUI ^^
Oh and I'm not sure, but for me sometimes the "Starts the effect of an ability" functions doesn't give back the target correctly... (or was it the "finishes casting an ability"?)

 

[Maker]

They (should) work because they don't exist. They are only wrapper functions for triggering unit.

Dying unit is a wrapper, but killing and attacking are not.

 

[mckill2009]

Because the learning curve on that is too steep for most GUI users. It's better to help people learn to help themselves, and putting the "solution" in custom script is going to confuse and/or turn off most people.

I regret that I'm stuck with GUI for a very long time in the past that's why
I'm encouraging people to learn jass immediately after learning the basics of GUI ...

LOL DUDE it's just a JASS scipt captured in the fiery cage of GUI ^^
Oh and I'm not sure, but for me sometimes the "Starts the effect of an ability" functions doesn't give back the target correctly... (or was it the "finishes casting an ability"?)

local variables can make a simple spell MUI in a non-complicated way ...

Starts the effect works just fine but it's the starts the effect for the caster
or triggering unit, not the target so it will cast almost instant which is not
good if you want to delay the effect, to avoid this you may use timers for
the delay...

 

[Justify]

Dying unit is a wrapper, but killing and attacking are not.

True, wrong response. Attacked unit is the wrapper