GUI Knockback 2.5D v4.2.5.0

[Edy]

Amazing stuff, will be using it cheers
+rep

 

[Oljin]

works perfect, good job!

 

[Edy]

Is there any way to exclude a unit that is being knocked back to bumb (scatter) othe units, allies and enemies alike. I'm using this system quite often it would be of great help.

 

[Pyrogasm]

Is there any way to exclude a unit that is being knocked back to bumb (scatter) othe units, allies and enemies alike. I'm using this system quite often it would be of great help.

Read the system documentation, please:

-------- Knockback2DCollision --------
-------- You can specify the collision radius of units to be adjacently knocked back if you want --------
-------- A value of 0 will require the units' collision sizes to overlap to knock back --------
-------- A value greater than 0 will allow that much space between the units to still permit the knockback --------
-------- A value less than 0 will disable collision checking altogether. --------

 

[lishi1608]

Hi Bribe, this is awesome lib. But why doesn't your code interrupt spell? When I set unit position it stops my order. I look into your code at a glance, finding you are setting position too. What's the magic?

 

[Uncle]

Hi Bribe, this is awesome lib. But why doesn't your code interrupt spell? When I set unit position it stops my order. I look into your code at a glance, finding you are setting position too. What's the magic?

Move unit instantly issues a stop command where as this doesn't:

• Custom script: call SetUnitX (udg_Unit, GetLocationX(udg_Point))
• Custom script: call SetUnitY (udg_Unit, GetLocationY(udg_Point))

Edit: Just realized you said you're already doing that. Dunno, set unit position doesn't interrupt for me.

 

[Bribe]

Hi Bribe, this is awesome lib. But why doesn't your code interrupt spell? When I set unit position it stops my order. I look into your code at a glance, finding you are setting position too. What's the magic?

I don't use SetUnitPosition except for with the dummy unit. As Uncle already said, the system uses SetUnitX/Y which are light operations that don't issue a Stop order.

 

[pOke]

Hi Bribe,

I am trying to replicate your destructable search and destroy method for spells that will destroy trees as units moves along a path.

However, I don't follow where I would set or decide this portion of the code:

Spoiler

• If (All Conditions are True) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • Knockback2DKillTrees Equal to True
  • Then - Actions
    • -------- Square the radius so we don't have to use SquareRoot when comparing distance. --------
    • Set K2DDestRadius[UDex] = (Knockback2DDestRadius x Knockback2DDestRadius)
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Knockback2DDestRadius x 2.00) Greater than K2DMaxDestRadius
      • Then - Actions
        • -------- Update the size of the enumerating rect to compensate for the desired extra radius. --------
        • Set K2DMaxDestRadius = (Knockback2DDestRadius x 2.00)
        • Custom script: call SetRect(udg_K2DRegion, 0.00, 0.00, udg_K2DMaxDestRadius, udg_K2DMaxDestRadius)
      • Else - Actions
    • Set Knockback2DDestRadius = Knockback2DDefaultDestRadius
  • Else - Actions

Spoiler

library TreeSearch initializer init

        globals
      
        private rect TREE_REGION = GetWorldBounds()
        private real maxX = GetRectMaxX(TREE_REGION)
        private real maxY = GetRectMaxY(TREE_REGION)
        private real minX = GetRectMinX(TREE_REGION)
        private real minY = GetRectMinY(TREE_REGION)
      
        private real defaultDestRadius = 128.
        private real maxDestRadius = defaultDestRadius * 2.
        private string treeOrDebris = "attack"
        private unit debrisKiller
        private real tX
        private real tY
        private real tRadius
      
        endglobals
      
private function KillTree takes nothing returns nothing
    local real x
    local real y
    local destructable d = GetEnumDestructable()
    if GetWidgetLife(d) > .405 and IssueTargetOrder(debrisKiller, treeOrDebris, d) then
        set x = GetWidgetX(d) - tX
        set y = GetWidgetY(d) - tY
        if x*x + y*y <= tRadius then
            call KillDestructable(d)
        endif
    endif
  
    set d = null
endfunction

function TreeSearch takes real x, real y, real radius returns nothing
    call MoveRectTo(TREE_REGION, x, y)
    call SetUnitX(debrisKiller, x)
    call SetUnitY(debrisKiller, y)
    set tX = x
    set tY = y
    if radius == 0. then
        set radius = defaultDestRadius
    endif
    set tRadius = radius
    call EnumDestructablesInRect(TREE_REGION, null, function KillTree)
endfunction

private function init takes nothing returns nothing
    set debrisKiller = CreateUnit(Player(PLAYER_NEUTRAL_PASSIVE), 'ugho', 0,0, 270.)
    call UnitAddAbility(debrisKiller, 'Aloc')
    call ShowUnit(debrisKiller, false)
    call PauseUnit(debrisKiller, true)
    call SetRect(TREE_REGION, 0., 0., maxDestRadius, maxDestRadius)

endfunction


endlibrary

 

[Bribe]

You need to square tRadius (set tRadius = radius*radius). Otherwise, the rest looks the same as I have it.

 

[pOke]

Thank you! Really appreciate the effort you put into your code comments and your responsiveness.

Spoiler: updated

library TreeSearch initializer init

        globals
      
        private rect TREE_REGION
        private real maxX
        private real maxY
        private real minX
        private real minY
      
        private real defaultDestRadius = 128.
        private real maxDestRadius = defaultDestRadius * 2.
        private string treeOrDebris = "attack"
        private unit debrisKiller
        private real tX
        private real tY
        private real tRadius
      
        endglobals
      
private function KillTree takes nothing returns nothing
    local real x
    local real y
    local destructable d = GetEnumDestructable()
    if GetWidgetLife(d) > .405 and IssueTargetOrder(debrisKiller, treeOrDebris, d) then
        set x = GetWidgetX(d) - tX
        set y = GetWidgetY(d) - tY
        if x*x + y*y <= tRadius then
            call KillDestructable(d)
        endif
    endif
  
    set d = null
endfunction

function TreeSearch takes real x, real y, real radius returns nothing
    call SetUnitX(debrisKiller, x)
    call SetUnitY(debrisKiller, y)
    call PauseUnit(debrisKiller, false)
    set tX = x
    set tY = y
    if radius == 0. then
        call SetRect(TREE_REGION, 0., 0., maxDestRadius, maxDestRadius)
        set radius = defaultDestRadius
    else
        call SetRect(TREE_REGION, 0., 0., radius*2, radius*2)
    endif
  
    set tRadius = radius*radius
    call MoveRectTo(TREE_REGION, x, y)
    call EnumDestructablesInRect(TREE_REGION, null, function KillTree)
    call PauseUnit(debrisKiller, true)
endfunction

private function init takes nothing returns nothing
    set TREE_REGION = GetWorldBounds()
    set maxX = GetRectMaxX(TREE_REGION)
    set maxY = GetRectMaxY(TREE_REGION)
    set minX = GetRectMinX(TREE_REGION)
    set minY = GetRectMinY(TREE_REGION)
  
    set debrisKiller = CreateUnit(Player(PLAYER_NEUTRAL_PASSIVE), 'ugho', 0,0, 270.)
    call UnitAddAbility(debrisKiller, 'Aloc')
    call ShowUnit(debrisKiller, false)
    call PauseUnit(debrisKiller, true)
    call SetRect(TREE_REGION, 0., 0., maxDestRadius, maxDestRadius)

endfunction


endlibrary

 

[Bribe]

Knockback2DSimple is your problem. Delete that line as it makes the system ignore pathing checks.

 

[emil23]

View attachment 332262View attachment 332263

View attachment 332264View attachment 332265
@Bribe hey with thw help of the uncle i am using greater bash ability it has most of things from ur system but there is problem. Some units get pulled into air and lands at same spot without direction to push them more



Look for frodo at photo for him its fine he lands away. Do you know how to fix this bug.i realised that for units with 15 colizion it always works but for units with 20 they get only pulled up and land at same spot. On map i copied it from everything works fine and theres no such bug.

 

[Edy]

View attachment 332262View attachment 332263

View attachment 332264View attachment 332265
@Bribe hey with thw help of the uncle i am using greater bash ability it has most of things from ur system but there is problem. Some units get pulled into air and lands at same spot without direction to push them more



Look for frodo at photo for him its fine he lands away. Do you know how to fix this bug.i realised that for units with 15 colizion it always works but for units with 20 they get only pulled up and land at same spot. On map i copied it from everything works fine and theres no such bug.

Had a simmilar issue.
Depends if they're pre-placed or spawned.
On spawned enemies it works perfectly, I think it's a problem with the Unit Indexer..IDK wait for Bribe - maybe you need to register all preplaced units somehow.

 

[emil23]

Had a simmilar issue.
Depends if they're pre-placed or spawned.
On spawned enemies it works perfectly, I think it's a problem with the Unit Indexer..IDK wait for Bribe - maybe you need to register all preplaced units somehow.

They are placed

 

[Bribe]

I think the problem here is the line in the Knockback 2D Destroy trigger "Animation - Change Knockback2DUnit flying height to (Default flying height of Knockback2DUnit) at 0.00"

That line should instead be: "Animation - Change UDexUnits[UDex] flying height to (Default flying height of UDexUnits[UDex]) at 0.00"

I've attached an updated map. Please let me know if it fixes the problem.

 

[emil23]

I solved it before u responded after changing Robust pathning to 0 it works fine

 

[Bribe]

I solved it before u responded after changing Robust pathning to 0 it works fine

Yeah but that shouldn't have an impact.

 

[emil23]

Yeah but that shouldn't have an impact.

well it works fine only at testing zone in single player.but at multiplayer in normal game when heroes fight together sometimes they get slided on ground only. so should i change that line? btw this is map im using. can u take a look at it and tell me if problem is in my map? because i dont use all of ur triggers only some.

 

[emil23]

Message from uncle



You should tell Bribe that Uncle edited his Knockback 2D system in order to implement some stuff that you wanted and that I already fixed the problem with Knockback 2D Destroy. Tell him that I replaced the flying height effect that he was using before with a new one that has a parabola effect so the unit's height changes smoothly over the course of the knockback duration. Explain that it works perfectly fine in the Knockback v.7 Demo map that I created for you even with Robust Pathing set to 0/1/2. However, for some reason the system has problems when we import it into your LotR map and for whatever reason setting the Robust Pathing to 0 helped fix some of those problems. Note that we tried using his original system in your LotR map but it had the same problems.





My problem is currently when i m testing this knockback on single player on single units it works fine. Its supossed to make unit fly in some height then land unit away with direction. But when 9 Heroes fight together i noticed that theres a bug. Units are often slided throught ground only. Without hright to go up into air.idk really what causes it. Maybe it happens when heroes are too close to eachother? I sent u a map im using.it has ur system but bit edited. I can send u the lotr map where this system has issues. My robous pathning is 0.

Also the thing u were talking about is fixed alreday. Colision of my units is 15 18 and 20

 

[emil23]

Yeah but that shouldn't have an impact.

I have second problem i am using ur system and the uncle remade it a bit. it works fine on cave trolls on my map. but i added it for sauron the last boss on map. knockback sometimes just only stuns, sometimes work with height only and sometimes just direction. and sometimes knocks normally. and after few minuts of fighting sauron game total freezes everything stops and i have to press alt+f4 to exit game. all i would like to know is how to fix this issue. there isnt much difference beetwen cave trolsl and sauron, so i got no idea why its broken on sauron. cave trolls and both sauron are on map all the time, they both have 48 pathning. sauron has few custom spells with other coding too but no one of these spells enables knockback triggers i think, it used to do so but i fixed it.

 

[Khaletsky]

Hello Bribe, hello everyone. Maybe I miss something but how can I change this system to ignore obstacles completely? It seems like even when unit is flying or amphibious it still hits the walls (water) and bounces off it, even though normally unit would pass it completely ignoring it. Seems like your system checks collision even if it doesn't exist sadly.

 

[Bribe]

Hello Bribe, hello everyone. Maybe I miss something but how can I change this system to ignore obstacles completely? It seems like even when unit is flying or amphibious it still hits the walls (water) and bounces off it, even though normally unit would pass it completely ignoring it. Seems like your system checks collision even if it doesn't exist sadly.

Non-destructable obstacles are indistinguishable from an impasse without some very immense overhead to do some calculating like "is point reachable by unit". That's simple to just determine by looking at it with your eyes, but the code is messy AF.

 

[Khaletsky]

Non-destructable obstacles are indistinguishable from an impasse without some very immense overhead to do some calculating like "is point reachable by unit". That's simple to just determine by looking at it with your eyes, but the code is messy AF.

I'm just bad at this, is there a way to add some condition to make your system ignore pathing for some units/passive abilities/etc? If there is pls tell me how can I change it without breaking whole system.

 

[Bribe]

I'm just bad at this, is there a way to add some condition to make your system ignore pathing for some units/passive abilities/etc? If there is pls tell me how can I change it without breaking whole system.

Each knockback instance can be defined with its own pathing configuration. So a missile-type unit could use this system, hypothetically, using the Simple pathing option.

 

[Veronnis]

@Bribe So, Ironically after some time I've made most of the systems listed under your signature in GUI only to just find out that you had already made them all. Anyway I'm now familiar with them so I might as well finish the knockback one haha. I'm less familiar with Jass but I understand it is the only way to move a unit without "stunning" it. As you know the jass-based movement will send a unit flying through walls and anything else.

Looking at your System here:

Spoiler: System

function K2DItemCheckXY takes real x, real y returns boolean
call SetItemPosition(udg_K2DItem, x, y)
return GetWidgetX(udg_K2DItem) == x and GetWidgetY(udg_K2DItem) == y
endfunction
function K2DItemCheckAxis takes real x, real y returns boolean
local real x2 = x*udg_K2DRadius[udg_UDex]
local real y2 = y*udg_K2DRadius[udg_UDex]
set x = udg_K2DX + x2
set y = udg_K2DY + y2
if K2DItemCheckXY(x, y) and not IsTerrainPathable(x, y, PATHING_TYPE_WALKABILITY) then
set x = udg_K2DX - x2
set y = udg_K2DY - y2
return K2DItemCheckXY(x, y) and not IsTerrainPathable(x, y, PATHING_TYPE_WALKABILITY)
endif
return false
endfunction

Could you tell me:
1. What the item is for and why it would fail without it?
2. Why my GUI trigger does not appear to be functioning? (Listed point is the origin of a tree)

• (Terrain pathing at (Point(-1306.00, -1700.00)) of type Walkability is off) Equal to True

^Does not consider that point unwalkable when paired in if/then/else.

Thanks, much appreciated!

 

[Uncle]

@Veronnis
1. When you try to move an Item to somewhere unwalkable like Water it will automatically move to the next closest possible location on the map. This can be used to determine pathing.

Example: You move an Item to the 0,0 coordinates on the map. After moving it you then check the Items X,Y coordinates. If the Item's X,Y coordinates are different than 0,0 then we know that you tried to move the item to an unwalkable point and that the Item was moved somewhere nearby. That's the basic idea of what he's doing but he does it in a slightly more complex way by moving the Item to different positions around the knocked back units. If the Item isn't where it's supposed to be then we know it hit something Unpathable.

2. I think Terrain Pathing checks for Cliffs/Doodads/Water/Boundary/etc... but not Destructibles.

 

[Veronnis]

@Uncle
Oh okay, I was already using the same method with the item here but, not being very familiar with Jass I had misread his code to be functioning without the item (Point based-only) and yet the item was included anyway. Now with that clarified it sounds like it moves the item (to check for pathing), then offsets a new point based on a variable collision size and moves the end destination to that new point (to accommodate for valid placement after collision size is considered). Is that correct?

 

[Uncle]

@Uncle
Oh okay, I was already using the same method with the item here but, not being very familiar with Jass I had misread his code to be functioning without the item (Point based-only) and yet the item was included anyway. Now with that clarified it sounds like it moves the item (to check for pathing), then offsets a new point based on a variable collision size and moves the end destination to that new point (to accommodate for valid placement after collision size is considered). Is that correct?

To be honest I don't entirely understand what he's doing I just know the gist of it. Anyway, I'm off to bed, hopefully the man himself can break it down.

 

[Bribe]

@Uncle
Oh okay, I was already using the same method with the item here but, not being very familiar with Jass I had misread his code to be functioning without the item (Point based-only) and yet the item was included anyway. Now with that clarified it sounds like it moves the item (to check for pathing), then offsets a new point based on a variable collision size and moves the end destination to that new point (to accommodate for valid placement after collision size is considered). Is that correct?

That sounds about right. But let me explain just to make sure.

In order for a unit to get from 0,0 to 0, 100, it needs to slide. Let's say in ten steps for simplicity. So in one pass, I check if 0,10 is safe using an item. But I'll also check if there is enough "padding" around 0,10 so that's why I use "robustness" in case of large collision sizes.

Then I do the same for 0,20/30, etc. Until either the point is unsafe or the destination is reached.

But with bouncing enabled, the destination can change geometrically.

 

[Veronnis]

@Bribe , sweet thanks for confirming that. I presume the item is used for the check because it does not trigger "unit enters region". Im on my phone right now or I'd just look at your code, but when you move the unit do you move it to x and y simultaneously or separately? If done separately I presume said unit might accidentally enter a region before it is moved to the other axis. Does that happen if assigned in 2 separate commands?

 

[Bribe]

@Bribe , sweet thanks for confirming that. I presume the item is used for the check because it does not trigger "unit enters region". Im on my phone right now or I'd just look at your code, but when you move the unit do you move it to x and y simultaneously or separately? If done separately I presume said unit might accidentally enter a region before it is moved to the other axis. Does that happen if assigned in 2 separate commands?

I've not tested if "enters region" might trigger twice if the angle severe enough to trigger two separate regions at once, but given the general fluidity of motion and micro steps of the coordinates this is inconsequential.

 

[Veronnis]

Doing my own test it looks like units do trigger entered regions during the movement that may have been avoided had the movement been to a point instead of an x and then a y coordinate, but as you said because of the smallness of the distance travelled it is rare this is of noteworthy effect.

 

[DoomBlade]

Hello Bribe. Is there a way to prevent the adjacent knockback?

 

[Uncle]

Hello Bribe. Is there a way to prevent the adjacent knockback?

• Set Knockback2DDefaultBounce = True

^I think you change that to False in the Knockback 2D Config trigger.

Otherwise, post your trigger.

 

[DoomBlade]

• Set Knockback2DDefaultBounce = True

^I think you change that to False in the Knockback 2D Config trigger.

Otherwise, post your trigger.

Unfortunately, it wasn't that. But I found it. Im stupid.

• Set VariableSet Knockback2DCollision = -1.00

This needed to be negative value, it was even explained in this map triggers.

 

[Planetary]

This is an awesome KB system. I ran the JASS source through a Lua converter and Lua-fied the GUI. Almost have it working.

Something got tweaked with calculations, so working through that still. It randomly works from very specific angles.

If someone else also desires a Lua variant but better understands its syntax and any conversion woes, feel free to have a gander (attached).

 

[Uncle]

It'd be great if Bribe came out with a Lua version.
@Planetary
Note that you can throw away the Unit Indexer entirely since you can plug units directly into your Tables:

function LuaIndex()
    KnockbackTable = {}
    local unit = CreateUnit(Player(0), FourCC("Hpal"), 0, 0, 270) --Create a Paladin at x: 0, y: 0, for Player 1
    table.insert(KnockbackTable , unit)
end

function LuaLoop()
    for k,v in pairs(KnockbackTable) do
        print(k,v) -- prints the Table Key (1, 2, 3) and the Table Value (Our Units)
        --Move the unit, etc...
        local x = 100
        local y = 100
        SetUnitPosition(v, x, y) -- v = our Paladin (units)
    end
end

 

[Bribe]

I had a Lua version of this, but when U uninstalled Reforged it got nuked.

 

[Uncle]

That's a damn shame... I'm guessing you're not too interested in doing it all over again, at least not for a while.

 

[Bribe]

That's a damn shame... I'm guessing you're not too interested in doing it all over again, at least not for a while.

Yeah to be honest I built this resource because GUI didn't have a good enough Knockback system at the time. The math wasn't even mine to begin with. I ended up changing a few things in the math to make it configurable and to check for outbound angles, but I don't know enough about velocity to do a proper movement arc without yet again copying someone else's math.

 

[Ugabunda]

Hi Bribe, can I use this system if I use Unit Event instead of your Unit Indexer?

I'd prefer to use yours, but I have some JASS spells which depend on Unit Indexer - and without it I would get errors...

 

[Bribe]

Hi Bribe, can I use this system if I use Unit Event instead of your Unit Indexer?

I'd prefer to use yours, but I have some JASS spells which depend on Unit Indexer - and without it I would get errors...

You can use GUI Unit Event instead of Unit Indexer with this.

 

[Ugabunda]

Ahh so stupid - I just realized that GUI Unit Event is also a system from you! Ok thanks a lot!

 

[Plebbetry]

Hi, i'm not sure if this is the place to ask and i'm new to WorldEdit, but is there some form of tutorial on how to use this? I'd like to learn how to use this and trigger a knockback without the use of the damage engine. I have tried fiddling around triggers for a while now, but i am unable to get it to work.

 

[Uncle]

Hi, i'm not sure if this is the place to ask and i'm new to WorldEdit, but is there some form of tutorial on how to use this? I'd like to learn how to use this and trigger a knockback without the use of the damage engine. I have tried fiddling around triggers for a while now, but i am unable to get it to work.

I recommend copying these actions from the "On Damage" trigger in Bribe's test map and pasting them into a new trigger. This new trigger can then be referenced whenever you want to issue a Knockback.

• Actions
  • -------- There are four required variables when issuing a knockback --------
  • -------- --------
  • -------- 1. Knockback2DAngle -------- this is the direction angle the unit is knocked back (in degrees) --------
  • -------- 2. Knockback2DTime -------- this is how long the unit will be knocked back (in seconds) --------
  • -------- 3. Knockback2DDistance -------- this is how far the unit will be knocked back --------
  • -------- 4. Knockback2DUnit -------- this is the unit being knocked back --------
  • -------- --------
  • -------- When all four variables are set, you can run the Knockback 2D trigger, ignoring conditions --------
  • -------- --------
  • Set VariableSet CenterPoint = (Position of DamageEventSource)
  • Set VariableSet TargetPoint = (Position of DamageEventTarget)
  • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
  • Custom script: call RemoveLocation(udg_CenterPoint)
  • Custom script: call RemoveLocation(udg_TargetPoint)
  • Set VariableSet Knockback2DTime = 0.90
  • Set VariableSet Knockback2DDistance = 500.00
  • Set VariableSet Knockback2DUnit = DamageEventTarget
  • -------- --------
  • -------- When all variables are set, run the Knockback 2D trigger, checking conditions if you want to be safe --------
  • -------- --------
  • Trigger - Run Knockback 2D <gen> (checking conditions)

^These are the important Actions for issuing a Knockback.

So now whenever you want to issue a Knockback, you copy and paste these Actions from the trigger I told you to create, and adjust the variables accordingly:

1) Set CenterPoint to be the position of the Source of the Knockback. So you want to change DamageEventSource to be equal to your Source Unit.
2) Set TargetPoint to be the position of the Target of the Knockback. So you want to change DamageEventTarget to be equal to your Target Unit.
3) Set Knockback2DTime to be how long you want the Knockback to last.
4) Set Knockback2DDistance to be how far you want the Knockback to travel.
5) Set Knockback2DUnit = The Target of the Knockback.

The final step is to run the Knockback trigger:

• Trigger - Run Knockback 2D <gen> (checking conditions)

This tells the system to create a Knockback based on your designated settings.

Here's an example using Storm Bolt:

• Storm Bolt Example
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to Storm Bolt
  • Actions
    • Set VariableSet CenterPoint = (Position of (Casting unit))
    • Set VariableSet TargetPoint = (Position of (Target unit of ability being cast))
    • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
    • Custom script: call RemoveLocation(udg_CenterPoint)
    • Custom script: call RemoveLocation(udg_TargetPoint)
    • Set VariableSet Knockback2DTime = 2.00
    • Set VariableSet Knockback2DDistance = 1000.00
    • Set VariableSet Knockback2DUnit = (Target unit of ability being cast)
    • Trigger - Run Knockback 2D <gen> (checking conditions)

Note that there are quite a few other Variables that you can set when issuing a Knockback, here's just a few:

• Set VariableSet Knockback2DKillTrees = True
• Set VariableSet Knockback2DPause = True
• Set VariableSet Knockback2DBounces = True

If you don't set these yourself then the System will automatically use their Default values. The Default values can be found in "Knockback 2D Config". You can adjust these to your liking.

 

[Plebbetry]

I recommend copying these actions from the "On Damage" trigger in Bribe's test map and pasting them into a new trigger. This new trigger can then be referenced whenever you want to issue a Knockback.

• Actions
  • -------- There are four required variables when issuing a knockback --------
  • -------- --------
  • -------- 1. Knockback2DAngle -------- this is the direction angle the unit is knocked back (in degrees) --------
  • -------- 2. Knockback2DTime -------- this is how long the unit will be knocked back (in seconds) --------
  • -------- 3. Knockback2DDistance -------- this is how far the unit will be knocked back --------
  • -------- 4. Knockback2DUnit -------- this is the unit being knocked back --------
  • -------- --------
  • -------- When all four variables are set, you can run the Knockback 2D trigger, ignoring conditions --------
  • -------- --------
  • Set VariableSet CenterPoint = (Position of DamageEventSource)
  • Set VariableSet TargetPoint = (Position of DamageEventTarget)
  • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
  • Custom script: call RemoveLocation(udg_CenterPoint)
  • Custom script: call RemoveLocation(udg_TargetPoint)
  • Set VariableSet Knockback2DTime = 0.90
  • Set VariableSet Knockback2DDistance = 500.00
  • Set VariableSet Knockback2DUnit = DamageEventTarget
  • -------- --------
  • -------- When all variables are set, run the Knockback 2D trigger, checking conditions if you want to be safe --------
  • -------- --------
  • Trigger - Run Knockback 2D <gen> (checking conditions)

^These are the important Actions for issuing a Knockback.

So now whenever you want to issue a Knockback, you copy and paste these Actions from the trigger I told you to create, and adjust the variables accordingly:

1) Set CenterPoint to be the position of the Source of the Knockback. So you want to change DamageEventSource to be equal to your Source Unit.
2) Set TargetPoint to be the position of the Target of the Knockback. So you want to change DamageEventTarget to be equal to your Target Unit.
3) Set Knockback2DTime to be how long you want the Knockback to last.
4) Set Knockback2DDistance to be how far you want the Knockback to travel.
5) Set Knockback2DUnit = The Target of the Knockback.

The final step is to run the Knockback trigger:

• Trigger - Run Knockback 2D <gen> (checking conditions)

This tells the system to create a Knockback based on your designated settings.

Here's an example using Storm Bolt:

• Storm Bolt Example
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to Storm Bolt
  • Actions
    • Set VariableSet CenterPoint = (Position of (Casting unit))
    • Set VariableSet TargetPoint = (Position of (Target unit of ability being cast))
    • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
    • Custom script: call RemoveLocation(udg_CenterPoint)
    • Custom script: call RemoveLocation(udg_TargetPoint)
    • Set VariableSet Knockback2DTime = 2.00
    • Set VariableSet Knockback2DDistance = 1000.00
    • Set VariableSet Knockback2DUnit = (Target unit of ability being cast)
    • Trigger - Run Knockback 2D <gen> (checking conditions)

Note that there are quite a few other Variables that you can set when issuing a Knockback, here's just a few:

• Set VariableSet Knockback2DKillTrees = True
• Set VariableSet Knockback2DPause = True
• Set VariableSet Knockback2DBounces = True

If you don't set these yourself then the System will automatically use their Default values. The Default values can be found in "Knockback 2D Config". You can adjust these to your liking.

Aaaah, now i understand, thanks a lot my man.
Also, will (Position of (Target unit of ability being cast)) work for abilities like War Stomp and Thunder Clap?

 

[Uncle]

Aaaah, now i understand, thanks a lot my man.
Also, will (Position of (Target unit of ability being cast)) work for abilities like War Stomp and Thunder Clap?

Nope, there is no Target unit of ability being cast for those abilities. You need to use a Pick Every Unit function:

Spoiler: Trigger

• AoE Knockback
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to War Stomp
  • Actions
    • -------- Area of Effect = 250/300/350 (War Stomp levels 1 to 3) --------
    • Set VariableSet AreaOfEffect = (200.00 + (50.00 x (Real((Level of (Ability being cast) for (Triggering unit))))))
    • -------- --------
    • -------- For efficiency sake we can alter the setup of these variables. Instead of creating CenterPoint over and over again, simply create it once at the start. --------
    • -------- Then remove it once after the Pick Every Unit function. --------
    • Set VariableSet CenterPoint = (Position of (Triggering unit))
    • Custom script: set bj_wantDestroyGroup = true
    • Unit Group - Pick every unit in (Units within AreaOfEffect of CenterPoint.) and do (Actions)
      • Loop - Actions
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • ((Picked unit) belongs to an enemy of (Triggering player).) Equal to True
            • ((Picked unit) is A flying unit) Equal to False
            • ((Picked unit) is Magic Immune) Equal to False
            • ((Picked unit) is Mechanical) Equal to False
            • ((Picked unit) is invulnerable) Equal to False
            • ((Picked unit) is A structure) Equal to False
            • ((Picked unit) is dead) Equal to False
          • Then - Actions
            • Set VariableSet TargetPoint = (Position of (Picked unit))
            • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
            • Custom script: call RemoveLocation(udg_TargetPoint)
            • Set VariableSet Knockback2DTime = 0.90
            • Set VariableSet Knockback2DDistance = 500.00
            • Set VariableSet Knockback2DUnit = (Picked unit)
            • Trigger - Run Knockback 2D <gen> (checking conditions)
          • Else - Actions
    • Custom script: call RemoveLocation(udg_CenterPoint)

Note that I altered it slightly for efficiency. I set CenterPoint before the Pick Every Unit function and remove it afterwards. This is done because it's unnecessary to create/remove CenterPoint over and over again since it's position never changes.

Not to overwhelm you, but there is a minor issue with the above trigger. The Pick every unit within range function doesn't work exactly the same as how Area of Effect abilities work. For Area of Effect abilities like War Stomp, the collision size of the enemy unit is taken into consideration when checking if it's in range. Pick every unit within range does not take the collision size into consideration, resulting in inconsistencies between the two. Because of this a unit may be stunned by War Stomp but not get knocked back if it's near the edge of the abilities AoE. The solution is just two extra lines of code as well as a minor adjustment of an existing line:

Spoiler: Improved Trigger

• AoE Knockback Improved
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to War Stomp
  • Actions
    • -------- Area of Effect = 250/300/350 (War Stomp levels 1 to 3) --------
    • Set VariableSet AreaOfEffect = (200.00 + (50.00 x (Real((Level of (Ability being cast) for (Triggering unit))))))
    • -------- --------
    • -------- For efficiency sake we can alter the setup of these variables. Instead of creating CenterPoint over and over again, simply create it once at the start. --------
    • -------- Then remove it once after the Pick Every Unit function. --------
    • Set VariableSet CenterPoint = (Position of (Triggering unit))
    • Custom script: set bj_wantDestroyGroup = true
    • Unit Group - Pick every unit in (Units within (AreaOfEffect + 300.00) of CenterPoint.) and do (Actions)
      • Loop - Actions
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • ((Picked unit) belongs to an enemy of (Triggering player).) Equal to True
            • ((Picked unit) is A flying unit) Equal to False
            • ((Picked unit) is Magic Immune) Equal to False
            • ((Picked unit) is Mechanical) Equal to False
            • ((Picked unit) is invulnerable) Equal to False
            • ((Picked unit) is A structure) Equal to False
            • ((Picked unit) is dead) Equal to False
          • Then - Actions
            • Custom script: if IsUnitInRange(GetEnumUnit(), GetTriggerUnit(), udg_AreaOfEffect) then
            • Set VariableSet TargetPoint = (Position of (Picked unit))
            • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
            • Custom script: call RemoveLocation(udg_TargetPoint)
            • Set VariableSet Knockback2DTime = 0.90
            • Set VariableSet Knockback2DDistance = 500.00
            • Set VariableSet Knockback2DUnit = (Picked unit)
            • Trigger - Run Knockback 2D <gen> (checking conditions)
            • Custom script: endif
          • Else - Actions
    • Custom script: call RemoveLocation(udg_CenterPoint)

So I changed (Units within AreaOfEffect) to (Units within (AreaOfEffect + 300.00)). This should guarantee that all nearby units, regardless of collision size, are taken into consideration.

Then once a unit is picked we run this line of code:

• Custom script: if IsUnitInRange(GetEnumUnit(), GetTriggerUnit(), udg_AreaOfEffect) then

And at the bottom we close it off with this:

• Custom script: endif

Think of this as an extra Condition. It checks if the Picked unit (GetEnumUnit) is within AreaOfEffect range of the Triggering unit (GetTriggerUnit). The reason I use this is because it takes into consideration Collision Size, meaning it will work exactly the same as War Stomp and other AoE abilities.

So using War Stomp level 1 as an example:
-AreaOfEffect is set to 250.00.
-I pick every unit within 250.00 + 300.00 (550.00) AoE of the Caster regardless of their collision sizes.
-I then run the IsUnitInRange function which DOES take into consideration collision sizes, using the original AreaOfEffect (250.00) for the comparison.
-If the unit is indeed "InRange" then I knock it back.

This fixes the issue I described above with collision sizes and calculating AoE.

 

[Plebbetry]

Nope, there is no Target unit of ability being cast for those abilities. You need to use a Pick Every Unit function:

Spoiler: Trigger

• AoE Knockback
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to War Stomp
  • Actions
    • -------- Area of Effect = 250/300/350 (War Stomp levels 1 to 3) --------
    • Set VariableSet AreaOfEffect = (200.00 + (50.00 x (Real((Level of (Ability being cast) for (Triggering unit))))))
    • -------- --------
    • -------- For efficiency sake we can alter the setup of these variables. Instead of creating CenterPoint over and over again, simply create it once at the start. --------
    • -------- Then remove it once after the Pick Every Unit function. --------
    • Set VariableSet CenterPoint = (Position of (Triggering unit))
    • Custom script: set bj_wantDestroyGroup = true
    • Unit Group - Pick every unit in (Units within AreaOfEffect of CenterPoint.) and do (Actions)
      • Loop - Actions
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • ((Picked unit) belongs to an enemy of (Triggering player).) Equal to True
            • ((Picked unit) is A flying unit) Equal to False
            • ((Picked unit) is Magic Immune) Equal to False
            • ((Picked unit) is Mechanical) Equal to False
            • ((Picked unit) is invulnerable) Equal to False
            • ((Picked unit) is A structure) Equal to False
            • ((Picked unit) is dead) Equal to False
          • Then - Actions
            • Set VariableSet TargetPoint = (Position of (Picked unit))
            • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
            • Custom script: call RemoveLocation(udg_TargetPoint)
            • Set VariableSet Knockback2DTime = 0.90
            • Set VariableSet Knockback2DDistance = 500.00
            • Set VariableSet Knockback2DUnit = (Picked unit)
            • Trigger - Run Knockback 2D <gen> (checking conditions)
          • Else - Actions
    • Custom script: call RemoveLocation(udg_CenterPoint)

Note that I altered it slightly for efficiency. I set CenterPoint before the Pick Every Unit function and remove it afterwards. This is done because it's unnecessary to create/remove CenterPoint over and over again since it's position never changes.

Not to overwhelm you, but there is a minor issue with the above trigger. The Pick every unit within range function doesn't work exactly the same as how Area of Effect abilities work. For Area of Effect abilities like War Stomp, the collision size of the enemy unit is taken into consideration when checking if it's in range. Pick every unit within range does not take the collision size into consideration, resulting in inconsistencies between the two. Because of this a unit may be stunned by War Stomp but not get knocked back if it's near the edge of the abilities AoE. The solution is just two extra lines of code as well as a minor adjustment of an existing line:

Spoiler: Improved Trigger

• AoE Knockback Improved
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to War Stomp
  • Actions
    • -------- Area of Effect = 250/300/350 (War Stomp levels 1 to 3) --------
    • Set VariableSet AreaOfEffect = (200.00 + (50.00 x (Real((Level of (Ability being cast) for (Triggering unit))))))
    • -------- --------
    • -------- For efficiency sake we can alter the setup of these variables. Instead of creating CenterPoint over and over again, simply create it once at the start. --------
    • -------- Then remove it once after the Pick Every Unit function. --------
    • Set VariableSet CenterPoint = (Position of (Triggering unit))
    • Custom script: set bj_wantDestroyGroup = true
    • Unit Group - Pick every unit in (Units within (AreaOfEffect + 300.00) of CenterPoint.) and do (Actions)
      • Loop - Actions
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • ((Picked unit) belongs to an enemy of (Triggering player).) Equal to True
            • ((Picked unit) is A flying unit) Equal to False
            • ((Picked unit) is Magic Immune) Equal to False
            • ((Picked unit) is Mechanical) Equal to False
            • ((Picked unit) is invulnerable) Equal to False
            • ((Picked unit) is A structure) Equal to False
            • ((Picked unit) is dead) Equal to False
          • Then - Actions
            • Custom script: if IsUnitInRange(GetEnumUnit(), GetTriggerUnit(), udg_AreaOfEffect) then
            • Set VariableSet TargetPoint = (Position of (Picked unit))
            • Set VariableSet Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
            • Custom script: call RemoveLocation(udg_TargetPoint)
            • Set VariableSet Knockback2DTime = 0.90
            • Set VariableSet Knockback2DDistance = 500.00
            • Set VariableSet Knockback2DUnit = (Picked unit)
            • Trigger - Run Knockback 2D <gen> (checking conditions)
            • Custom script: endif
          • Else - Actions
    • Custom script: call RemoveLocation(udg_CenterPoint)

So I changed (Units within AreaOfEffect) to (Units within (AreaOfEffect + 300.00)). This should guarantee that all units, regardless of collision size, are taken into consideration.

Then once a unit is picked we run this line of code:

• Custom script: if IsUnitInRange(GetEnumUnit(), GetTriggerUnit(), udg_AreaOfEffect) then

And at the bottom we close it off with this:

• Custom script: endif

Think of this as an extra Condition. It checks if the Picked unit (GetEnumUnit) is within AreaOfEffect range of the Triggering unit (GetTriggerUnit). The reason I use this is because it takes into consideration Collision Size, meaning it will work exactly the same as War Stomp and other AoE abilities.

So using War Stomp level 1 as an example:
-AreaOfEffect is set to 250.00.
-I pick every unit within 250.00 + 300.00 (550.00) AoE of the Caster regardless of their collision sizes. -I then run the IsUnitInRange function which DOES take into consideration collision sizes, using the original AoE (250.00) for the comparison.
-If the unit is indeed "InRange" then I knock it back

This fixes the issue I described above with collision sizes and calculating AoE.

I can't seem to open your test map, it's giving me a "-Level info data missing or invalid", but that's no problem i'll try to recreate it manually.
I'd like to know how to make the "AreaOfEffect" variable and if the "= true" part of the first custom script in the improved trigger is part of the text that has to be written in or needs to be checked in a comparison menu thingy (don't know how it's called)

 

[Uncle]

I can't seem to open your test map, it's giving me a "-Level info data missing or invalid", but that's no problem i'll try to recreate it manually.
I'd like to know how to make the "AreaOfEffect" variable and if the "= true" part of the first custom script in the improved trigger is part of the text that has to be written in or needs to be checked in a comparison menu thingy (don't know how it's called)

Yeah, I use the latest version of Warcraft 3 so you won't be able to open it unless you're up to date.

AreaOfEffect is a Real variable.

The most common variables you'll use: Integer = whole number, Real = number with a decimal, Boolean = True/False, String = "some text", and many more.

And Custom script is always written by the user. Understand that Custom script is the actual code that Warcraft 3 uses. For example, here's a Unit variable being set in GUI (the standard trigger editor):

• Set Variable SomeUnit = (Triggering unit)

And this is what that Action looks like when converted to code or "custom script".

set udg_SomeUnit = GetTriggerUnit()

You can see that the code looks fairly similar to the GUI example above it.

And to further explain GUI:
GUI stands for Graphical User Interface, which is what the Trigger Editor is. It's a simplified version of coding that has an easy to use interface (buttons, graphics, search for text, etc) to make coding easier.

So when you use Custom script you're skipping the pretty GUI shell that surrounds the code and going right to the source. It can be confusing sometimes because you'll notice that the naming conventions will change between GUI and code (Custom script). For example, a Point variable in GUI is actually called a Location in code. It's not that confusing though because their names both convey the same idea, which is a reference to some position in the game.

 

[Plebbetry]

Yeah, I use the latest version of Warcraft 3 so you won't be able to open it unless you're up to date.

AreaOfEffect is a Real variable.

The most common variables you'll use: Integer = whole number, Real = number with a decimal, Boolean = True/False, String = "some text", and many more.

And Custom script is always written by the user. Understand that Custom script is the actual code that Warcraft 3 uses. For example, here's a Unit variable being set in GUI (the standard trigger editor):

• Set Variable SomeUnit = (Triggering unit)

And this is what that Action looks like when converted to code or "custom script".

set udg_SomeUnit = GetTriggerUnit()

You can see that the code looks fairly similar to the GUI example above it.

And to further explain GUI:
GUI stands for Graphical User Interface, which is what the Trigger Editor is. It's a simplified version of coding that has an easy to use interface (buttons, graphics, search for text, etc) to make coding easier.

So when you use Custom script you're skipping the pretty GUI shell that surrounds the code and going right to the source. It can be confusing sometimes because you'll notice that the naming conventions will change between GUI and code (Custom script). For example, a Point variable in GUI is actually called a Location in code. It's not that confusing though because their names both convey the same idea, which is a reference to some position in the game.

I see, the trigger works perfectly.
Thank you for taking the time to explain all these things to me.