GUI Knockback 2.5D v4.2.5.0

[KILLCIDE]

Update to fix a bug when implementing this resource which would cause numerous Var_AsString syntax errors when trying to save

Woohoo!! Thank you

 

[KILLCIDE]

I was running some tests on Knockback 2D in a group of ground/flying units. When I applied the knockback to the group, only the ground units had LoopFX appear on them while air units were just knocked back with no SFX. Is this intentional, Bribe?

EDIT: I also found it that if you add an "air unit" filter to knockback in an area with ground units, the ground units will ONLY be knocked back if the air units are also knocked back. Not sure what the interaction here is.

 

[Bribe]

Yes, the knockback effects should look differently between ground and air units, but I never came up with a solution for what air knockbacks should look like (and if they should be configurable).

What I can do in a future update is simply make the loop FX attach to the origin of any flying units.

What do you mean by "air filter"?

 

[KILLCIDE]

Yes, the knockback effects should look differently between ground and air units, but I never came up with a solution for what air knockbacks should look like (and if they should be configurable).

It's not that. The knockback effect does appear at all for air units (right now I'm using Flak because it has the "cloud" effect. Glaive Missle would have been perfect if the missle didnt show up).

What do you mean by "air filter"?

A knockback that ONLY hits air units. When applied to a group of ground units nothing happens, but when applied to a group of air and ground units, they both get knockbacked.

 

[Bribe]

"It's not that. The knockback effect does appear at all for air units"

> Correct, that's the way it currently works - air units don't show an effect.

"A knockback that ONLY hits air units."

> Which part of the code did you change to make it only hit air units? The system treats air and ground equally when it comes to collision as it's designed to allow both air and ground. I should make it configurable whether air or ground can be targeted, however.

 

[KILLCIDE]

Correct, that's the way it currently works - air units don't show an effect.

Ahh misunderstood your statement. Thank you for the clarification.

Which part of the code did you change to make it only hit air units? The system treats air and ground equally when it comes to collision as it's designed to allow both air and ground. I should make it configurable whether air or ground can be targeted, however.

I didn't change anything in the code. I'm working on a spell that filters out a unit group to only air units and runs the knockback system.

Unit Group - Pick every unit in (Units within AoE of Loc) and do (Actions) Loop - Actions Set TempUnit = (Picked unit) If (All Conditions are True) then do (Then Actions) else do (Else Actions) If - Conditions (TempUnit is A flying unit) Equal to True (TempUnit is Magic Immune) Equal to False (TempUnit is alive) Equal to True (TempUnit belongs to an enemy of Owner) Equal to True Then - Actions Set TempLoc = (Position of TempUnit) Set Knockback2DAngle = (Angle from Loc to TempLoc) Set Knockback2DTime = KBTime Set Knockback2DDistance = Distance Set Knockback2DUnit = TempUnit Set Knockback2DLoopFX = SFX_KB Trigger - Run Knockback 2D <gen> (checking conditions) Custom script: call RemoveLocation(udg_TempLoc) Else - Actions

Ground units are unaffected by this knockback when there are just ground units. However, once an air unit is hit in the area, they will suddenly have the knockback applied to them.

 

[Bribe]

OK, in the next update I will hardcode it so the knockback collision only applies to ground or air, depending on who's being knocked back.

 

[KILLCIDE]

Sounds good so what is the reason I'm having the issue I currently have? Am I doing something wrong?

 

[Bribe]

The issue is that knockback collision currently doesn't care if you're air or ground.

 

[Bribe]

Update thanks to KILLCIDE!

- Flying units no longer knock back ground units and vice-versa.
- Special effect art for flying units now attaches to their origin instead of not appearing at all.
- Flying units' pathing has been simplified so they no longer bounce off of walls.

 

[Killd0zer]

Is this workable into a missile system, or should i wait for an official one?

 

[Bribe]

I use it as a missile system in The Big Dipper, featured in Spell System. The arc is not good, though. I understand BPower intends to make a GUI version of Missile.

 

[BPower]

Is this workable into a missile system, or should i wait for an official one?

You can use this system to run a missile motion in 2D plane.
That's very solid assuming Warcraft III mainly takes place in 2D plane.
I would use it.

I understand BPower intends to make a GUI version of Missile.

I started then stopped after 10 minutes, because I'm not sure how
to design a good and understand-able API for GUI users.

I could either fire triggers via variable event upon certain events ( 1.00 == onUnit, 2.00 == onPeriod, ... )
and the user must determine via condition if the action function should run or not ( Example udg_Missile_Type == 54 ).
Meaning this action code only runs for missile of type 54 and you could set the 54 upon missile creation.

Or I could let the user to set triggers directly to variables. ( Example: udg_Missile_OnCollide[index] = MyCollideTriggerForFireballs < gen > ).
That would be more performant, but creates a unusual design for GUI triggers. It would take time to understand it at all

 

[Bribe]

The key is to simplify it so the user just needs onCollide and onDestroy. My plan A was to make Knockback 2D support 3D projectile movement, but I threw in the towel as I'm not good at parabolic math. I could do it, but I'd have to copy someone else's mathmatics and I don't feel right about it. I guess I should read up on some tutorials.

 

[Killd0zer]

If you made a missile system it would actually be the best thing ever

 

[KILLCIDE]

Do you mind adding a changelog/version number in the test map? I sometimes forget when I last updated the knockback

 

[warcraftmodding123]

Not bad, but for my own part jass version is much more efficient and, most importantly, a much simpler.
Anyway,this was done perfectly.5/5
And remember,BEAUTY IS IN SIMPLICITY!!!

How do I use the jass codes? I just copy paste the codes in World Editor Triggers?

 

[Bribe]

When you import the system, instead of copying each trigger, individually, copy the folder (aka category) which contains them.

Edit: updated Config trigger to include the version number. Not an actual update.

 

[warcraftmodding123]

When you import the system, instead of copying each trigger, individually, copy the folder (aka category) which contains them.

Edit: updated Config trigger to include the version number. Not an actual update.

I have copied the 3 trigger folders contained in the Knockback 2_5D.w3x over to my map, will this be enough to make it function in my map?

Btw I got this message when saving my map:
Trigger 'Unit Indexer' has been disabled due to errors

And also got stuck in a progress bar: Generating Map Script

 

[Bribe]

It may have been disabled if you already had Unit Indexer in your map. Do you want to PM me your map and I'll install it for you?

 

[warcraftmodding123]

It may have been disabled if you already had Unit Indexer in your map. Do you want to PM me your map and I'll install it for you?

I will upload my map here cause I don't have the attachments options in PM.

These triggers will automatically make knights, deathknight and all cavalry knock back enemies, right?

Thanks for your help.

 

[Bribe]

The map you uploaded only has these 2 triggers:

• Melee Initialization
  • Events
    • Map initialization
  • Conditions
  • Actions
    • Melee Game - Use melee time of day (for all players)
    • Melee Game - Limit Heroes to 1 per Hero-type (for all players)
    • Melee Game - Give trained Heroes a Scroll of Town Portal (for all players)
    • Melee Game - Set starting resources (for all players)
    • Melee Game - Remove creeps and critters from used start locations (for all players)
    • Melee Game - Create starting units (for all players)
    • Melee Game - Run melee AI scripts (for computer players)
    • Melee Game - Enforce victory/defeat conditions (for all players)

• Limit Heroes to two
  • Events
    • Map initialization
  • Conditions
  • Actions
    • Player Group - Pick every player in (All players) and do (Actions)
      • Loop - Actions
        • Player - Limit training of Sylvanas to 1 for (Picked player)
        • Player - Limit training of Malfurion to 1 for (Picked player)
        • Player - Limit training of Grom Hellscream to 1 for (Picked player)
        • Player - Limit training of Arthas Arthas to 1 for (Picked player)
        • Player - Limit training of Heroes to 2 for (Picked player)

 

[warcraftmodding123]

Sorry I thought it would be better of giving it to you without the triggers in it, for a fresh install.

Here's the map with the trigger folders.

 

[Bribe]

Thanks - found the problem. None of the variables got brought over with the triggers. You need to make sure you have "automatically create variables for unknown names" selected in the World Editor Preferences.

 

[warcraftmodding123]

Hey thanks, it's working now

I noticed that the knockback also affects catapult rocks. And the knockback is too intense. Is there a way to reduce the power of the knockback and remove the knockback from the catapult rocks?

 

[Bribe]

If you give the rocks the Locust (unit) ability, they will not be knocked back. Also, for the power of the knockback to be diminished you just reduce the Knockback2DDistance or increase the Knockback2DTime accordingly

 

[warcraftmodding123]

Ok I fixed the distance. How do I add the Locust ability though? I don't know where the unit - missiles are so I can add it an ability.

 

[Bribe]

You can either add Locust via triggers when you create the rock units, or you can make the rocks have that ability in Object Editor. It is a "unit" ability - not the hero one.

 

[ZiBitheWand3r3r]

Hello, I got a question about Knockback 2D Destroy trigger.
quote: "This trigger destroys any knockback; you can execute it yourself by first setting UDex to the custom value"

so to destroy knockback I should set Udex = custom value of knocked back unit, and then run 'destroy trigger' ?
in other words I have to know all units in order to destroy knockback on them?

edit
with this settings knockback system wont run 2nd time, but after I use shockwave then units affected by spell can be hit once by knockback, and then again knockback is not applied:
its from demo map

TRIGGER

• On Damage
  • Events
    • Game - DamageModifierEvent becomes Equal to 1.00
  • Conditions
  • Actions
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • IsDamageSpell Equal to False
        • (Owner of DamageEventSource) Equal to Player 1 (Red)
      • 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 = 1.00
        • Set Knockback2DDistance = 100.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 optional variables you can consider when issuing a knockback --------
            • -------- If they are not set, "0.00, false, null" or their default states assigned in the Knockback 2D Config trigger will be used --------
            • -------- --------
            • -------- Knockback2DAmphibious -------- Allows the unit to pass over deep water, but it is more performance-intensive --------
            • -------- -------- If you aren't ToolOrDie from TheHiveWorkshop, you probably won't use this --------
            • -------- Knockback2DBounces -------- if the unit will bounce off of walls or remain stunned there. --------
            • -------- --------
            • -------- 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. --------
            • -------- --------
            • -------- Knockback2DDestRadius -------- If debris is to be killed, how far away must it be? --------
            • -------- Knockback2DFriction -------- How quickly the unit will slow down from its initial speed. --------
            • -------- Knockback2DFX -------- What kind of special effect will occasionally be played on the ground of the unit --------
            • -------- Knockback2DFXRate -------- How often should the effect appear? --------
            • -------- Knockback2DGravity -------- If you want to specify a custom gravity for each knockback, you can --------
            • -------- Knockback2DHeight -------- How high you want the unit to go during the knockback --------
            • -------- Knockback2DKillTrees -------- If you want surrounding trees to die, this is for you --------
            • -------- Knockback2DOnImpact -------- this trigger is run when the unit hits a wall or structure. --------
            • -------- -------- 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 --------
            • -------- Knockback2DOverride -------- Set this to true to prevent future knockbacks from interrupting this one --------
            • -------- Knockback2DPause -------- confines the unit to its knockback velocity (no running to change course) --------
            • -------- Knockback2DSimple -------- Only checks to make sure unit movement is within the map bounds --------
            • -------- Knockback2DSource -------- If you need to store this unit to deal damage on-impact or within the timer loop --------
            • -------- Knockback2DUnbiasedCollision -------- Should adjacent knockbacks consider alliances or be neutral? --------
            • -------- --------
            • -------- -- boomerang: Knockback2DFriction=2.00 and Knockback2DGravity=0.50 --------
            • Set Knockback2DBounces = True
            • Set Knockback2DCollision = 16.00
            • Set Knockback2DGravity = 0.71
            • Set Knockback2DHeight = 300.00
            • Set Knockback2DOnImpact = On Impact <gen>
            • Set Knockback2DOverride = True
            • Set Knockback2DPause = False
            • Set Knockback2DSource = DamageEventSource
          • Else - Actions
• THE REST IS THE SAME AS IN TEST MAP

 

[Bribe]

Ideally, you as a user never need to run the K2D destroy trigger manually. However, you may want to stop all knockbacks before running a cinematic.

The trigger you posted doesn't have any second recurrence issues. Is your Knockback system up-to-date? A short-lived older version had a similar problem.

 

[ZiBitheWand3r3r]

Ideally, you as a user never need to run the K2D destroy trigger manually. However, you may want to stop all knockbacks before running a cinematic.

Excactly, I plan to use it right before arena battle, when all units paused, heroes moved to arena, then play short introduction /cinematic/ and so on,
Thats the only reason I want to interrupt runing knockbacks. If I understand right, I should do it like this?

• esc
  • Events
    • Player - Player 1 (Red) skips a cinematic sequence
  • Conditions
  • Actions
    • Set UDex = (Custom value of Nerubian Queen 0012 <gen>)
    • Trigger - Run Knockback 2D Destroy <gen> (ignoring conditions)

The trigger you posted doesn't have any second recurrence issues. Is your Knockback system up-to-date? A short-lived older version had a similar problem.

I just downloaded system yesterday. Today I made test again, the problem still exist for me. So its look like this /demo map/: my hero attacks nerubian queen, attacked unit is knockedback--Ok, second/3rd hit and so on --> knockback wont work, no matter I made pause between 1st and 2nd attack or not. If casted shockwave on nerubian, then knockback is applied by shockwave, then after that 1st hit /by normal attack/ can trigger knockback, next normal attacks wont trigger knockback.
I belive its comes from Knockback2DOverride = true
Im using setting from my previous post here.

 

[Bribe]

Would you mind sharing the map so I can run some tests this weekend?

 

[ZiBitheWand3r3r]

its system-test map,
try attack nerubian queen by tauren hero

 

[Bribe]

Thank you for reporting this bug! The fix is to add this line to the bottom of the Knockback 2D Destroy trigger:

Set K2DOverride[UDex] = False

I will update the system with this change in a couple of minutes.

 

[Almia]

I didn't know this runs on 60 fps lol

So that's why it is so smooth

 

[Bribe]

Yep, being insanely efficient has an added benefit of running at the same FPS as other systems while running twice as often.

 

[Almia]

It's actually good because each iteration is quite fast and so it doesn't cause that much strain :V

Good job

 

[ZiBitheWand3r3r]

I'm trying to use system's ability to detect when knockbacked unit hits something and then deal damage.
It doesnt work for me. Trigger OnImpact runs *not* only when unit hits a wall but also when knockback expires (looks like its a bug). Bribe can you please take a look at this problem?
My settings:

  set udg_Knockback2DDistance = 800.00
    set udg_Knockback2DTime = 1.00
    set udg_Knockback2DBounces = false
    set udg_Knockback2DKillTrees = false
    set udg_Knockback2DHeight = 0.00

to be more specific: for example there is no units around, no path blockers/destructables/doodads, just caster and target, when udg_Knockback2DTime expires trigger OnImpact is executed which is a bug,
do you think it will be a small hot-fix or bigger issue?

 

[Bribe]

You can check if IsUnitBeingKnockedBack is True before proceeding. That way, it only runs on bounces.

 

[ZiBitheWand3r3r]

oh, thanks for this tip
system works perfectly

 

[VitaminLight]

Hi Bribe, I'm having problems with your system for some weird reason. When I imported the Arcane Bomb 1.02 spell, it would knockback flying units just fine, but then ground units wouldn't be affected by knockback at all. Any reason why that would happen?

 

[Elprede]

It is intentional. The GIF for the spell shows the ground units being pulled at the end of a lightning strike. In addition, with recent updates of this system, flying units can no longer knock back ground units and vice versa.

 

[Sverkerman]

Okey I've read through all the comment pages and been looking into the code for 2 days, experimenting with it and I really, really love it, thanks Bribe!

However, I cannot for the life of me figure out how to exclude unit types from being checked by the collision. I have a unit that is mining ore and there is a 1/50 chance that his mining pick breaks, knocking him backwards and stunning him. The only problem is that the knockback interracts with both the dummy casters for the stun and the dummy unit representing the ore deposit. This results in him being stuck for the knockback duration since I cannot exclude the ore deposit and the dummy caster unit type from the collition-check-trigger.

Anyone that can aid me in figuring this out? Where should I add my (UnitType of (("Picked Unit I assume?")) Not equal to ThisUnitType)?
GUI pls

 

[Bribe]

If you add Locust (unit) to your dummy unit types then they can't be messed with by things like that.

 

[Sverkerman]

@Bribe Thanks for the fast reply

I can unfortunately not use Locust (unit) on the units that I don't want the system to check since I need these units still to be interractable. Would you please aid me further and show me a way to implement a condition like this into your system please?

 

[KILLCIDE]

Where should I add my (UnitType of (("Picked Unit I assume?")) Not equal to ThisUnitType)?

The same spot you would filter out other units...? I don't understand the confusion. Why would this have a special place?

 

[Sverkerman]

The same spot you would filter out other units...? I don't understand the confusion. Why would this have a special place?

Thanks for the reply KILLCIDE!

This is my issue. I'm not sure where I would go about filtering units from being knocked back, could you perhaps help me with where this condition should be added in the code? I would highly appreciate it, I'm having such a trouble finding where this should be filtered :/

 

[Bribe]

Thanks for the reply KILLCIDE!

This is my issue. I'm not sure where I would go about filtering units from being knocked back, could you perhaps help me with where this condition should be added in the code? I would highly appreciate it, I'm having such a trouble finding where this should be filtered :/

Just add an extra condition to Knockback 2D

 

[Sverkerman]

Just add an extra condition to Knockback 2D

Thanks for the reply Bribe!

Ah yes, this is clearly it, it was really simple just as I imagined it to be. Big +rep also, this system is awesome!

Which unit variable refers to the unit having Knockback2DUnit being knocked into it?

Thanks

 

[Bribe]

Hmm, surprisingly I overlooked that. The variable exists - Knockback 2D Source - but I didn't add it to the automatic collision filter for some reason (maybe it used to be in an older version).

I'll update the JASS code here on the site and update the map in 12 hours or so.