GUI Knockback 2.5D v4.2.5.0

[Losam]

Bribe, I could mention one example where I can use your system?

 

[Opaque]

Hmm I can't get this system working for my triggers... I know I imported the system correctly, because when I copied your OnDamage trigger into my map, all my units knockbacked properly. But when I tried to use knockback in my triggers, it doesn't work. Is it something wrong with my trigger?

• Shockwave
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to Shockwave
  • Actions
    • Set ShockwavePt = (Position of (Triggering unit))
    • Set ShockwavePt2 = (Target point of ability being cast)
    • Unit - Create 1 Shockwave Dummy for (Triggering player) at ShockwavePt facing ShockwavePt2
    • Unit - Set level of Shockwave Damage (Units) for (Last created unit) to (Level of (Ability being cast) for (Triggering unit))
    • Unit - Add a (5.00 + (Real((Level of (Ability being cast) for (Triggering unit))))) second Generic expiration timer to (Last created unit)
    • Set Knockback2DAngle = (Angle from ShockwavePt to ShockwavePt2)
    • Custom script: call RemoveLocation (udg_ShockwavePt)
    • Custom script: call RemoveLocation (udg_ShockwavePt2)
    • Set Knockback2DTime = (5.00 + (Real((Level of (Ability being cast) for (Triggering unit)))))
    • Set Knockback2DDistance = ((Real((Level of (Ability being cast) for (Triggering unit)))) x (2250.00 + (125.00 x (Real((Level of (Ability being cast) for (Triggering unit)))))))
    • Set Knockback2DUnit = (Last created unit)
    • Trigger - Run Knockback 2D <gen> (ignoring conditions)

 

[Berb]

D0100 is Hexadecimal.

Actually xD0100 is hexadecimal. D0100 is just some random characters.

 

[Bribe]

@Opaque, try putting a game message in the trigger, if the game message doesn't show, then the ability being cast is the problem. By "not working" is it not doing a single thing at all? Have you copied the object editor ability from the map and made sure its levels are set to Peasant/Knight/Infernal/Centaur like I have in my map?

@Berb, only a computer needs 0x to understand that what you're giving it is hex, in fact if you use a programming calculator it doesn't print the results with an 0x prefix, it just prints the D0100.

 

[Opaque]

The ability works fine, because it executes all the functions as it should, except for the knockback part. But I'm sure I implemented your system properly, because when I copied your OnDamage trigger, the knockback worked fine.

 

[Losam]

Bribe, I wanted to SING your system with units of the group (example: Suppose a unit uses a spell, so the spell takes one unit of the group and throws them away) as I do?

 

[Bribe]

I dunno what you are asking. I think something is getting lost in translation here.

 

[Solu9]

I am unsure how to get this system to work with an ability. It works fine when the hero can knockback on every hit. But I would like the knockback only to occur when an ability is used.

Can someone post a mini tutorial how to do so?

 

[neku99]

so uh I apparently... I cant get this to work. I've done the installation just as you said. I did notice that when I cast my spell (basically pushes target unit back) It shows the SFX on the unit but it doesn't get knocked back. Any help? I've been on this for about an hour now :/

 

[Orthane]

Hello, I am requesting to the owner of this system for permission to improve system to allows new configerations for customizing features for users of this knockback.

New True/Falses:
1> Allow_Freewill_Knockback
2> Allow_Rebound
3> Allow_KillTree
4> Allow_UnitBumping
5> Allow_IgnorePathing

The System was not user friendly and always forced people to use all effects of the knockback, not just what they wanted so I decided to modify that issue.

1. True/False option for a singular unit in the knockback index that allows a unit to attack, move around and cast spells while being knocked back
2. True/False option for a singular unit in the knockback index that allows you to control what units are allowed to rebound off of un-pathable locations
3. True/False option on if you want to destroy trees when knocked into them (including if you rebound off of them)
4. True/False option for a singular unit in the knockback index that allows control over if a unit causes a chain reaction bumper car effect with the knockback system towards units.
5. True/False if that singular unit is allowed to knockback over cliffs and un-pathables.

 

[jonbon29]

So this is the knockback system, pretty cool.

 

[ZiBitheWand3r3r]

Excellent system, much better then previous one I used before.
I especially like feature that knockbaced unit can knockback another unit that is on his way. That feature "cleans" area around knockback-source as it should be.

 

[Bribe]

Ok, new update after several years.

ToolorDie needed a way for units to be knocked over water if they have amphibious pathing. The system uses a custom inferno to check pathing, which always returns false over deep water. I made a configurable boolean Knockback2DPause which is effective for the WHOLE map and cannot be toggled true or false as long as there are any active knockbacks. To be safe, I recommend leaving it as false unless you need that unique capability that ToolorDie requires.

I do not have a way to allow the unit to bounce while the pause method is used, but I will add one in a future update if it is requested.

I updated the default timeout to run at 60fps instead of 30, but you can change it back if you want.

Units that are knocked back will now have their prop window locked, so the effect is much smoother than it used to be.

Knockback2D 1.2.0.0 is now live.

EDIT: In the next 24 hours I will release version 2.0.0.0 which will use an item to check pathing in addition to the inferno, this way units don't run into buildings any more. I will also update it to give the user control over whether the knockback will bounce, and add an event if it doesn't so the user can decide if they want on-impact effects (like Poppy hitting units into a wall in LoL). I will also give a pseudo-3d effect that if the user wants to enable they can. It will only affect the flying height, not the pathing, so the unit will still bounce/stop when it hits a wall.

 

[Bribe]

Ok, it took a bit longer than I had originally planned, but I have now released version 2.0!

Everything can now be customized per-knockback, so if you have one knockback that needs the unit to be stunned, and another that needs it to not interrupt channeling spells, now you have it.

A unit can now be paused and still bounce off of walls.

If a unit hits a wall and is not supposed to bounce, that unit will still be "stunned" for the duration of the knockback.

A unit can have its flying height set to a value that will peak in the middle of the knockback. Pretty simple, but makes this officially 2.5D (not 3D since I am not checking for 3D pathing).

You can now determine whether or not the knockback should kill trees or just simply stop when it hits them.

You also can now set a trigger to run when the unit hits an impassible object. The trigger will fire multiple times if a knockback bounces multiple times before expiring. If the trigger is disabled, this event will not fire, meaning if you only wanted it to run for one bounce you can take advantage of this.

I am proud to present this to the community! Again, please report any bugs. I have tested it pretty heavily, but nothing is for certain.

 

[ZiBitheWand3r3r]

Well, I found previous version of your knockback very usefull.
There are already implemented in my map mini-stuns (for some knockback based spells), also I use disable unit movement (call SetUnitPropWindow(u, 0.00)), and pausing all units (for arena battles). So Im afraid to not interfere with all new abilitites in 2.5Dver.
Dont get me wrong but it would be usefull to get, as you said:

Keep it simple

simple knockback system with this feature when knockbaced unit will knockback other units on his path. Something like minimalistic version but fast and smooth.
You mb remember I wrote in other post that I found infinite stunned paladin, and inferno. I though because of bug in my map, but today I tested and it is wrong fields in Object editor in your K2DPathAbil. It's Data-Duration: 0.00
When Stats-CastingTime:3600.00 expires then spell is finished and we have on map infinite stunned paladin for example. Solution is set Data-Duration: for 3.00
so if it happends, summoned unit will exists 2sec (cause of Data-ImpactDelay: 1.00)

So maybe you consider to upload this minimalistic version (previous one with fixed OE fields). I got previous ver on my PC, but maybe other users wants;]

 

[Bribe]

The object editor data did not change, so there's nothing to be reverted as far as that goes.

The PauseUnit feature is unnecessary, same with the SetUnitPropWindow, so you can disable those function calls if you don't want them. Don't use the PauseUnit option, anyway, as I only made that for Toolordie so he can get the feature he needed in his specific map.

Why would a unit have its movement disabled with SetUnitPropWindow in your map, if I may ask? There are other ways to disable a unit, for example an infinite-duration Channel ability.

 

[ZiBitheWand3r3r]

There's spell "Nibiru" where I use SetUnitPropWindow(u, 0)
Victims around are moved in 0,03sec loop to the center point. Units can't move, teleport or cast spells. After few seconds when dmg is applied I call EnableUnitMovement (it is SetUnitPropWindow(u, GetUnitDefaultPropWindow(u) * bj_DEGTORAD)).
Anyway I have your previous version, and modified OE field I wrote. Will make tests today but for now theres no reason for me to switch to new 2.5 ver.

 

[Bribe]

If you want the unit to not move, attack or cast spells, just add a high-duration channel ability to it and order it to cast it.

https://www.hiveworkshop.com/forums/jass-resources-412/snippet-suspendunit-266681/

And about the error you were talking about with permastun summons, you already found out that your entire map was bugged because of a cached order ID and not this system. It is impossible for this system to let the dummy caster actually drop an inferno, because even if you let an hour pass without a knockback, the caster is paused.

 

[ToolorDie]

He did it. I'll be gosh darned, Mr. Bribe did it.

Relied on his original system for a combat system I had in mind, I had the idea to further the excitement by making it possible to fight over water (had spare animations on models) and I asked Bribe to do it. He tried a few possibilities he could think of to incorporate fighting over water, we thought it couldn't be done, yet here it is ladies and gentlemen.

This is Crouching Briber Hidden Dragon!!

 

[Legal_Ease]

I am unsure how to get this system to work with an ability. It works fine when the hero can knockback on every hit. But I would like the knockback only to occur when an ability is used.

Can someone post a mini tutorial how to do so?

I am not super smart, but I can usually figure this stuff out. But, this time, I can't. I'm getting some ideas and I may figure it out eventually, but it would be nice if someone could just explain this. What do I do to set the event that causes the knockback. I get that it is on all damage, but how to I adjust that to be only spell damage or only damage from specific spells. I don't want every spell to knock back. I'm sorry for being such a noob, but I really like this system and I want to use it. Also, how do I turn normal damage back on? BTW, this is awesome stuff Bribe!

 

[Bribe]

The OnDamage trigger is just an example. You only need KnockBack 2D trigger for this to work.

To make it work with a specific spell, you would use the event "a unit starts the effect of an ability" and check if the ability being cast is the same as your ability. The Knockback2D unit is the target of the ability being cast, and the distance, angle and time are up to you.

 

[Legal_Ease]

The OnDamage trigger is just an example. You only need KnockBack 2D trigger for this to work.

To make it work with a specific spell, you would use the event "a unit starts the effect of an ability" and check if the ability being cast is the same as your ability. The Knockback2D unit is the target of the ability being cast, and the distance, angle and time are up to you.

Wow, thanks for the fast response. I like the detect damage system too though. For example, I might like to make a flame strike that knocks units back if they enter the flame after it is already going, or I might want to have it knock a unit back with a projectile.

Also, to be clear for future members, to activate the knockback, you would put your spell in an event at the top of the "OnDamage" trigger, like so:

(New) OnDamage

• On Damage
  • Events
    • Unit - A Unit Starts the Effect of an Ability
  • Conditions
    • (Ability Being Cast) Equal to MyNewAbility
  • Actions
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • Then - 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 CenterPoint = (Position of DamageEventSource)
        • Set TargetPoint = (Position of DamageEventTarget)
        • Set Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
        • Custom script: call RemoveLocation(udg_CenterPoint)
        • Custom script: call RemoveLocation(udg_TargetPoint)
        • Set Knockback2DTime = 0.90
        • Set Knockback2DDistance = 150.00
        • Set Knockback2DUnit = DamageEventTarget
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • (Owner of DamageEventSource) Not equal to (Owner of DamageEventTarget)
          • Then - Actions
            • -------- --------
            • -------- There are new (2015 September), optional variables to consider when issuing a knockback --------
            • -------- If they are not set, their default states assigned in the Knockback 2D main trigger will be used --------
            • -------- --------
            • -------- Knockback2DBounces -------- if the unit will bounce off of walls or remain stunned there. --------
            • -------- Knockback2DKillTrees -------- If you want surrounding trees to die, this is for you --------
            • -------- Knockback2DHeight -------- How high you want the unit to go during the knockback --------
            • -------- Knockback2DOnImpact -------- this trigger is run when the unit hits a wall. --------
            • -------- -------- If it is bouncing, it can hit multiple walls and fire this trigger multiple times --------
            • -------- -------- The trigger will not run if it is off, so you can use this if you only want it to run on the first bounce --------
            • -------- Knockback2DPause -------- features more precise pathing if true, but interrupts channeling spells. --------
            • -------- Knockback2DSource -------- If you need to store this unit to deal damage on-impact or within the timer loop --------
            • -------- --------
            • Set Knockback2DBounces = False
            • Set Knockback2DHeight = 100.00
            • Set Knockback2DKillTrees = True
            • Set Knockback2DOnImpact = On Impact <gen>
            • Set Knockback2DPause = True
            • Set Knockback2DSource = DamageEventSource
          • Else - Actions
        • -------- --------
        • -------- When all variables are set, run the Knockback 2D trigger, ignoring conditions --------
        • -------- --------
        • Trigger - Run Knockback 2D <gen> (ignoring conditions)
      • Else - Actions
    • Set DamageEventAmount = 0.00

Do I have that correct?

 

[Bribe]

The DamageEventX and IsDamageSpell stuff works only from actual damage trigger. With the event you have, you want to use stuff like "target point of ability being cast", "casting unit" and "target unit of ability being cast"

 

[Legal_Ease]

The DamageEventX and IsDamageSpell stuff works only from actual damage trigger. With the event you have, you want to use stuff like "target point of ability being cast", "casting unit" and "target unit of ability being cast"

Thank you again. I want to make sure I have this right.
For war stomp, do I do it, like this?

Set CenterPoint = (Target of ability being cast) Set TargetPoint = (Target point of ability being cast)

Also, how do I get the damage detection system to work with it? So, for example, an event like:

Events Unit - A unit is damaged

and a condition:

conditions Source of damage equal to (udg_Custom_Ability)

I have tried to make spells based on shockwave, but it is difficult to make the knockback move forward, spreading the units apart in a cone. The damage system would allow much more precision with much less effort.

I was able to make it work with a spell based on Storm Bolt like this:

trigger

• Then - Actions
  • Set CenterPoint = (Position of (Casting unit)) *
  • Set TargetPoint = (Position of (Target unit of ability being cast)) *
  • Set Knockback2DAngle = (Angle from CenterPoint to TargetPoint)
  • Custom script: call RemoveLocation(udg_CenterPoint)
  • Custom script: call RemoveLocation(udg_TargetPoint)
  • Set Knockback2DTime = 0.50
  • Set Knockback2DDistance = 300.00
  • Set Knockback2DUnit = (Target unit of ability being cast) *

*indicates the changes to make a spell targeting a unit to run the system.

 

[Bribe]

I have updated the map to add a few things

1) Gravity can now be specified per-knockback
2) The On Impact trigger in the map now taunts the knocked back unit to attack the knockback source in order to get it attacking again ASAP.
3) Since I had so many requests for a unit to be knocked back when hit by shockwave, I've added that to the map as well. When the ability effect starts, I set a boolean to let the On Damage trigger know that spell damage is coming from shockwave. When it stops, I set that boolean back to false.

 

[Almia]

woah!

i'm deleting my knockback 2d

 

[Arad MNK]

Knockback 2.5D

XD

Anyway I'm using this ;D


Just an idea that you can dynamically change the Effect in-game, not in the Initialization. I can do some small changes so I Can do that, but it makes my knockback effect change when my unit was already knockbacked, so maybe having these options:

Changing the Knockback effect In-game so that the Previous effect would still stay with the already knockbacked units;
Changing an Effect WHILE a Unit is being knockbacked.

I know, this may require some Indexing, but it seems doable


Either ways, 5/5!

 

[Bribe]

Cool; I always considered the effects optional add-ons but I will give it a way to cuatomize it per knockback in the next update. Good suggestion!

edit: I have now added the suggestion! Use Knockback2DLoopFX to set the FX before each knockback if you want something different than the default.

 

[Bribe]

Huge update to the code in the system! Split the one giant trigger into four smaller ones to make things easier to ubderstand. Along the way, I made some good performance improvements and some necessary sacrifices.

When Knockback2DPauseUnit is true, it applies the setunitpropwindow/cargo hold trick. If you want the unit's abilities to be disabled, use a dummy unit to stun or silence it. With Knockback2DPauseUnit set to false, the knockback behaves exactly like it did in version 1.0 (using SetUnitX/Y instead of SetUnitPosition).

A new boolean, Knockback2DAmphibious, has been added to allow units to move over deep water if desired, so naga fighters, naval vessels and Dragonball Z characters can fight above otherwise-illegal ground. Toolordie in particular should finally have the system working with this addition.

Previously, stopping a knockback was a chore for non-JASS fluent users. Now, just run the trigger Knockback 2D Destroy <gen> after setting the UDex variable to the custom value of the unit whose knockback you want to stop.

In all, the system is more efficient than version 2, and accurately detects building collision with as little performance degradation as possible.

Edit: I found a bug ... Easy to fix, though! If you use the amphibious option, scroll slightly down the Knockback 2D System - you will see an if/else block with four conditions. Change the top condition to "TempBool Equal to True" instead of not equal.

Edit 2: Fixed the bug. If there are any issues, please let me know.

 

[Bribe]

Optional update! I will be using this update in at least one spell I plan to release soon, so nothing urgent.

3.1.0.0 - Updated the Knockback 2D and Knockback 2D System triggers to add an option called "Knockback2DSimple". When this boolean is true, all normal pathing is ignored except to make sure the unit is within the world bounds.

Edit: I'm going to be adding another feature to adjust the size of (or disable) collision when using Knockback 2D Collider. I will also change the FX type when over water for the Knockback 2D FX trigger. Any additional features you guys want?

 

[Bribe]

The system has been updated to 4.0.0.0! Please read the change log here to see most of the things that I've changed.

To add to what's there, I have added a "Knockback2DOverride" boolean which prevents a unit from being knocked back by an additional knockback while it's being knocked back by that more important one.

Please use (Checking conditions) when running Knockback2D to ensure that it gets checked properly.

 

[KILLCIDE]

Great update, Bribe. I love all the documentation you put into the system I would have been so lost without it.

 

[Bribe]

After seeing the cool new Meteor Strike by KILLCIDE, I have updated this to version 4.2.0.0. This way, the second phase of the meteor can be moved using Knockback 2.5D instead of needing to code all that movement into his system.

You can specify the friction of the knockback to a value between 0 and 1 (outside those bounds will result in a kind of boomerang-style movement which users can experiment with). 0 is frictionless and ideal for missiles or ice maps. 1 is a gradual deceleration to a natural stop.

The knockback collision now also uses much more realistic deflection. Instead of a secondary-applied knockback completely overwriting the first, the distance/time/angle are averaged between the existing knockback and the new one.

Edit: Also inspired by KILLCIDE's Meteor Strike, I have made it so you can customize the destructable death radius per-knockback.

 

[theoligarch]

I loved the demo for this and wanted to use this in my own map, but every attempt has resulted in a compiling error that disables all of my other triggers. Is there something I must obviously be doing wrong that would cause this?

 

[Bribe]

I can copy into a new map without getting disabled triggers, so we gotta find out what's different on your setup.


- Have you selected "automatically create unknown variables when pasting trigger data"?

- Did you also copy the Unit Indexer trigger?

- What compile errors are you getting?

 

[theoligarch]

I can copy into a new map without getting disabled triggers, so we gotta find out what's different on your setup.


- Have you selected "automatically create unknown variables when pasting trigger data"?

Yup.

- Did you also copy the Unit Indexer trigger?

Yup. Copied over everything except the test triggers for the demo. (Also tried keeping the triggers for the demo, no luck there either.)

What compile errors are you getting?

313 errors, all of which appear to be "Expected a reserved type or handle type." The errors kick in when I attempt to test the map and it systematically disables every trigger. My map is a pretty simple altered melee too, so nothing fancy.

Thanks for your help!

 

[Bribe]

Is your World Editor and WarCraft 3 fully up-to-date? For example, can you connect to Battle.net?

Another question: can you screenshot the errors for me?

 

[theoligarch]

I am up to date and can login to Battle.net. The error occurs even when I copy the triggers into a blank map. I've attached the error message.

 

[Bribe]

Hmm.. if I had to guess, you copied the Knockback first and then the Unit Indexer (or put Unit Indexer below it in the category before copying). There seems to be a weird error when that happens, and I'll likely just remove the indexer event from Knockback 2D to compensate. Meanwhile, the fix should be to go into Variable Editor, delete UnitIndexEvent and create a new variable called UnitIndexEvent as a real type, non array. Then, any variables which got disabled from Knockback 2D and Unit Indexer will need that re-assigned (or you could copy Unit Indexer again and just re-assign Knockback's event).

 

[theoligarch]

Great! That did the trick. One last thing though: New damage during a knockback causes the game to freeze up (I have to use task manager to shut off WC3 during the test.) I tried turning on Knockback2DOveride to prevent this, but that just makes it so that each unit can only be knocked back the very first time they are attacked and never again. Do you know what my mistake in installation must be?

 

[Bribe]

I don't know exactly what th issue is. Maybe there's a recursive damage thing going on which causes your game to crash. Would you mind PMing me the map you imported it to so that I can debug it?

 

[theoligarch]

Sure, here's the map (dunno how to add attachments to PMs). Thanks so much for checking this problem out for me, I hope the issue isn't something idiotic on my end (I just started using the WE a month and a half ago). Careful with testing it though, I've had to power down my computer just to get out of the freeze this bug causes.

 

[Bribe]

In the Knockback 2D trigger, enable the line where the trigger "Knockback 2D Destroy" is run.

That's a problem with importing this system. I will eventually make a patch to correct that issue, but for any future users, that is the fix.

 

[theoligarch]

In the Knockback 2D trigger, enable the line where the trigger "Knockback 2D Destroy" is run.

That's a problem with importing this system. I will eventually make a patch to correct that issue, but for any future users, that is the fix.

That fixed it and it looks fantastic. Thank you so much for helping me through these issues!

 

[IcemanBo]

TreeKiller should get harvest ability in case user chooses only "harvest" and not "attack" as string.
As you use a default ghoul as TreeKiller it can't get ensured else that he can harvest at all.

And in case the user chooses "attack" as string, it would also be unable to destroy
something if the MovementSpeed of unit was changed to "0" or the unit has no movement type. (in object editor)

The cases are probably more rarely, especially the second, but it's a potential bug.

 

[Bribe]

Yeah, that's why I mentioned that the user should have a harvest-capable unit. If they literally modified peons, peasants, naga slaves and ghouls to not have harvest and to have 0 movespeed, I think that is a scenario so far out of logic that it's not worth addressing unless you're Nestharus

 

[IcemanBo]

"not have harvest and to have 0 movespeed"

Not "and" but "or" would be enough to have a bug.

I can see only good to add harvest ability
and it should be standard for all harvest systems.
It's not like the one line more in init will kill anyone.

 

[Bribe]

Trù. I will add this next update

 

[Bribe]

can you show me the map or post the triggers?

 

[Bribe]

Update to fix a bug when implementing this resource which would cause numerous Var_AsString syntax errors when trying to save, and to fix a bug where the Knockback 2D Destroy trigger was not run properly from the Knockback 2D trigger if there was a second knockback applied to a unit, causing an infinite loop.