• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!

Damage Engine 5.A.0.0

This bundle is marked as director's cut. It exceeds all expectations and excels in every regard.
Damage Engine

Three GUI Damage systems for the community of The Hive,
Seven vJass Damage systems for the JASS-heads on their pedestals high,
Nine competing Damage systems, doomed to die,
One for Bribe on his dark throne
In the Land of the Hive where the Workshop lies.
One Damage Engine to rule them all, One Damage Engine to find them,
One Damage Engine to bring them all and in cross-compatibility unite them.


Whether you're looking for a simple DDS (Damage Detection System), need to modify damage or even if you want a complex network of damage pre-and post-processing, this resource is for you. Damage Engine is the most adapted DDS in existence to take full advantage of the new damage detection natives, and is constantly evaluated and scrutinized by both the community and myself for performance improvements, bug fixes and new features alike.

What started with humble beginnings to bring a Unit Indexer-based version of DDS to GUI users to improve on the previous standard (at the time it was Weep's GDDS) would eventually evolve to incorporate other aspects of damage systems out there. @looking_for_help had identified an extremely useful technique with negative spell resistance being used to detect spell damage, and for a time his Physical Damage Detection system became the new standard. It wouldn't be until much later when Damage Engine would resurface and use the same technique in order to be more useful for the community.

Fast forward to 2020, and you'll find not only that cross-compatibility with Weep's and LFH's systems are incorporated, but the most popular DDS systems in existence - even vJass ones - are fully supported via stripped-down API wrappers. All of the functionality of prior DDS systems has been infused into Damage Engine 5.7, and as such the transition to a "one size fits all" DDS is complete. I hope you find this to be useful, and I also hope that it will help you in developing your map to be more dynamic what than you had previously thought possible.

Features

Legacy Code & Requirements

How it works

How to install/upgrade

Video Guides

FAQs

Thanks


  • Damage Type, Attack Type, Weapon Type, Armor Type and Defense Type detection and modification to alter/understand the fundamentals of WarCraft 3's damage processing;
  • Access to the view and change the damage amount before and/or after reduction by armor, armor type and shields.
  • Fully cross-compatible with every major DDS - vJass and GUI alike.
  • Correctly distribute/negate Spirit Link damage.
  • Differentiate between Ranged, Melee, Spell or other types of attack.
  • Does not require any Object Editor data nor Unit Indexer.
  • As of 5.4, it is now completely recursion-proof.
  • Other features:
    • Damage Blocking, reducing, amplifying and/or conversion to healing
    • Does not require you to know nor use Jass NewGen Pack nor any custom script
    • Custom DamageType association available to be set before and/or during damage event
    • Detect when multiple targets were hit simultaneously via DamageEventAOE > 1.
    • Detect when the same unit was hit simultaneously by the same source via DamageEventLevel > 1.
  • Detect damage: use the event "OnDamageEventEqual to <any value>". You have access to the following variables for reference:
    • DamageEventSource - the unit dealing the damage
    • DamageEventTarget - the unit receiving the damage
    • DamageEventAmount - the amount of damage the unit will receive
    • DamageEventPrevAmt - the amount of damage prior to being modified by the game engine.
    • DamageEventAttackT - the attack type (Chaos, Spells, Pierce, etc.)
    • DamageEventDamageT - the damage type - for comprehensive info, click here.
    • DamageEventWeaponT - the weapon type determines if an attack plays some kind of sound on attack (ie. Metal Heavy Bash). It is always NONE for spells and almost always NONE for ranged attacks.
    • DamageEventArmorT - the armor type (Flesh, Stone, Ethereal, etc.)
    • DamageEventDefenseT - the defense type (Hero, Fortified, Unarmored, etc.)
    • DamageEventArmorPierced - if DAMAGE_TYPE_NORMAL, how much armor was set to be ignored by the user.
    • IsDamageSpell, IsDamageRanged, IsDamageMelee - determine the source category of damage dealt.
    • IsDamageCode - Determine if the damage was dealt natively or by the user. This can give incorrect readings if the user has not identified to Damage Engine that it is code damage. Therefore I recommend setting NextDamageType prior to dealing damage.
    • DamageEventType - An integer identifier that can be referenced by you for whatever extra differentiation you need. You can also create your own special damage types and add them to the definitions in the Damage Event Config trigger. If you the unit should explode on death by that damage, use a damage type integer less than 0. If you want the damage to ignore all modifications, use DamageTypePure.
  • To change damage before it's processed by the WarCraft 3 engine: use the event "PreDamageEvent Becomes Equal to <any value>". Whether you just want to use one monolithic trigger for all damage modification like I do in the demo map, or use the different modifier events here, is up to you.
  • To interact with damage after it's been factored for armor and resistances, use "ArmorDamageEvent Becomes Equal to <any value>". This is typically useful for custom shields. If you fully block or absorb DamageEventAmount (setting it to 0 or less), this event doesn't run.
  • To set the DamageEventType before dealing triggered Damage, use:
    - Set NextDamageType = DamageTypeWhatever
    - Unit - Cause...
  • You can modify the following variables from a "PreDamageEvent" trigger:
    • DamageEventAmount
    • DamageEventAttackT/DamageT/WeaponT/ArmorT/DefenseT
    • DamageEventArmorPierced
    • DamageEventType
    • DamageEventOverride - You can set this if you want to remind yourself not to modify the damage further. If you use the UNKOWN damage type from a Unit - Damage Target native or set "NextDamageType = DamageTypePure" before that function, damage modification is skipped.
  • To catch a unit the moment before it would die from damage, use LethalDamageEvent Becomes Equal to 1.00. Instead of modifying the DamageEventAmount here, modify LethalDamageHP to let the system know how much life to keep the unit alive with. Or you can just reference that LethalDamageHP value in order to know how much "overkill" damage was dealt.
  • To catch a unit as soon as the damage is applied against its Hit Points, use AfterDamageEvent Equal to 1.00.
  • Usage of the "<Event> becomes EQUAL to <value>" can be extrapolated as per the below:
    • EQUAL works as it always has - will run for any damage.
    • NOT EQUAL only runs for code damage.
    • LESS THAN only runs for damage from attacks but not coded attacks.
    • LESS THAN OR EQUAL only runs for melee attacks but not coded attacks.
    • GREATER THAN OR EQUAL only runs for ranged attacks but not coded attacks.
    • GREATER THAN only runs for Spell damage but not coded spell damage.

  • Damage Engine 5 and higher requires the latest Warcraft 3 patch (currently 1.32).
  • For people who did not update their game to Reforged / have not updated to Reforged yet. Alternatively, adding the below JASS script to the top of the DamageEngine library SHOULD enable it to work too:

    JASS:
    function BlzGetEventIsAttack takes nothing returns boolean
         return BlzGetEventDamageType() == DAMAGE_TYPE_NORMAL
    endfunction
  • I have created a Pastebin for all information pertaining to Damage Engine 3.8, including the link to download it, via: Damage Engine 3.8.0.0 | HIVE.
  • As of 20 June 2020, JNGP users who are still on WarCraft 3 1.26 can benefit from Damage Engine 3A, which integrates many of the design choices added in various stages of Damage Engine 5. This is a special update which only requires the JASS script be replaced (no new GUI variables added). Can be found here: Damage Engine 3A.0.0.0 and 3.8.0.0 | HIVE

1
Unit attacks or casts a spell. The pure damage is assessed at this point - damage dice, evasion, critical strike. There is currently no event to affect or modify these at source.
→ →
2
The projectile or weapon hits the target unit
→ →
3
EVENT_UNIT_DAMAGING is fired before any modifications to the damage are made.
→ ↓
↓ ←
6
User changes to DamageEventAmount and/or to DamageEventDamageT/AttackT/WeaponT are saved into the WC3 engine.
← ←
5
If any recursive damage is detected from any of those events, it is postponed and the current damage will continue first.
← ←
4
Damage Engine deploys the PreDamageEvent
7
WarCraft 3 processes the user damage.
→ →
8
WarCraft 3 then distributes the user damage into Spirit Link (before armor)
→ →
9
WarCraft 3 runs any interrupting events, such as spirit link or defensive damage like Thorns Aura
→ ↓
↓ ←
12
The EVENT_UNIT_DAMAGED event runs. This is the original event we have always had access to. Damage Engine will either keep using the original variables from the DAMAGING event, or if there was Spirit Link/defensive damage it will freshly retrieve the event values from WC3 and only retain DamageEventPrevAmt.
← ←
11
Once any potential recursive WarCraft 3 damage is processed, the armor/mana shield modifications to the damage are performed.
← ←
10
If such events such as Spirit Link were detected, they fire their own EVENT_UNIT_DAMAGING & EVENT_UNIT_DAMAGED, and DamageEngine processes it along the way for the user.
13
If the damage is above zero, ArmorDamageEvent will run. If any recursive damage is detected, it is postponed.
→ →
14
The user can make modification to the damage here with the after-damage amount.
→ →
15
The user can access DamageEventPrevAmount if they want to know the damage amount before user changes/WarCraft 3 changes.
→ ↓
↓ ←
18
The user can specify whether or not to change LethalDamageHP in order to stop the unit from dying.
← ←
17
If the damage is still above zero, check if the damage is lethal. If so, run LethalDamageEvent 1.00. If any recursive damage is detected, it is postponed.
← ←
16
If the user wants the value that DamageEngine used to have with DamageEventPrevAmt (after WarCraft 3 processing but before user changes) they multiply DamageEventPrevAmt x DamageScalingWC3.
19
Once all modification is done, run OnDamageEvent. If any recursive damage is detected, it is postponed.
→ →
20
After a new damage instance is detected, or the 0.00 timer expires, run AfterDamageEvent. If any recursive damage is detected, it is postponed.
→ →
21
Run all potential recursive Unit - Damage Target function calls in chronological order (first in, first out).

How to install Damage Engine:
  1. Use WarCraft 3 Version 1.32
  2. If you're upgrading from 3.8 or prior, please delete the entire "Damage Engine" category from your map.
  3. Copy & Paste the Damage Engine category from the attached map to your own map.
How do I upgrade to the latest Damage Engine?
- Depending on the complexity, you'll either need to re-copy the Damage Engine category or just the Damage Engine script. Generally, you can use this as a guide:

  • Damage Engine _._._.x - only requires copying of the JASS script
  • Damage Engine _._.x._ - generally only needs copying of the JASS script, but read the patch notes in case there are changes you may want to make to your own code in order to utilize the changes.
  • Damage Engine _.x._._ - delete your current Damage Engine category or manually add the missing variables to your Variable Editor, and update your JASS script.
  • Damage Engine x._._._ - this occurs very infrequently. Typically requires changes to the way Damage Engine needs to be installed and used.

Notes about upgrading from Damage Engine 4.0 or prior:
  • Revert any custom Object Editor changes made (such as Life Drain reversal, Spell Damage Reduction inversion, etc).
  • You can safely delete the custom spells "Spell Damage Detection" and "Cheat Death Ability"
  • You can delete the Unit Indexer trigger if you do not use it or would prefer to use a different indexer.
  • You should delete any "Mana Shield fix" or "Finger of Death fix" you may have imported, as well as revert any Object Editor data that was required to make it work, as these are no longer needed.
  • !!!DEPRECATED FEATURE!!! As of 5.4, do not bother to take any recursive damage mitigation - Damage Engine will now handle all of that for you!
  • !!!DEPRECATED FEATURE!!! Do not use "ClearDamageEvent" - it does nothing. Just delete it.
  • !!!DEPRECATED FEATURE!!! Do not use "NextDamageOverride" - set NextDamageType = DamageTypePure instead.
  • !!!CHANGED FEATURE!!! If the system detects code damage and the user did not specify it as any particular DamageEvenType, the system will assign it DamageTypeCode automatically.
  • !!!CHANGED FEATURE!!! DamageModifierEvent 1.00-3.00 now run prior to armor reduction. This enables the user to modify the damage before armor and resistance changes are applied - also before Mana Shield and Anti-Magic shell kick in, so no more need for special triggers.


  • Q: Why am I getting a bunch of 'trigger was disabled' errors when I save my map?
  • A: This issue is not unique to Damage Engine, but to all vJass resources. Blizzard has taken the very confusing decision to make JassHelper 'disabled' by default, meaning that every new map that uses a vJass resource has to manually enable JassHelper. Please see this thread if you want to know where to find the Enable JassHelper option.
    .
  • Q: How can I detect when a unit gets damaged?
  • A: Create a trigger with the event: "Game - Value of Real Variable <DamageEvent> becomes Equal to 1.00".
    • Use the following custom variables to reference the event responses:
      • DamageEventSource - the unit dealing the damage
      • DamageEventTarget - the unit getting damaged
      • DamageEventAmount - how much damage is being dealt
      • DamageEventAttackT - which attack type was used by DamageEventSource to damage DamageEventTarget
      • DamageEventDamageT - which damage type was used to damage the target (ie. UNIVERSAL for ultimate damage, or NORMAL for damage that gets reduced by armor).
      • DamageEventDefenseT - which defense type does the target unit have (ie. Hero, Fortified, Unarmored).
      • DamageEventArmorT - which armor type does the target unit have (ie. Flesh, Ethereal, Stone).
      • DamageEventPrevAmt - what the value of the damage was before being modified by armor, ethereal/item bonuses or user changes.
        .
  • Q: How do I modify the damage that is dealt to a unit?
  • A: Create a trigger with the event: "Game - Value of Real Variable <PreDamageEvent> becomes Equal to <any value>".
    • You can change the following variables to affect the damage that will be dealt:
      • DamageEventAmount - how much damage will be dealt (before armor reductions)
      • DamageEventAttackT - which attack type will be used by DamageEventSource to damage DamageEventTarget
      • DamageEventDamageT - which damage type will be used to damage the target.
      • DamageEventDefenseT - which defense type should the target unit have during this attack.
      • DamageEventArmorT - which armor type should the target unit have during this attack.
      • DamageEventArmorPierced - how much armor value to ignore when dealing this damage (applies to DAMAGE_TYPE_NORMAL only, otherwise all armor is ignored).
        .

  • Q: How do I deal Pure damage to a unit (bypassing armor/skipping user modification)?
  • A: Use the following actions:
    • Set NextDamageType = DamageTypePure
    • Unit - Cause Source to damage Target for Amount using attack type Spells and damage type Universal
      .

  • Q: How do I protect against recursive damage?
  • A: Damage Engine 5.4 and above is completely recursion-proof, using vJass hooks to detect registered Damage Event triggers.
    .

  • Q: I've been using <insert Damage system here>. Can I use those with Damage Engine?
  • A: Better - Damage Engine has integrated cross-compatibility with all other approved Damage systems and even the major ones from outside of Hiveworkhop.
    .

  • Q: Can I cause an attack to 'Miss' its target?
  • A: Kind of. Ranged attacks will still explode on the target, and on-hit effects will still apply, but you can do the following:
    • Use the event "PreDamageEvent becomes Equal to 1.00"
    • Use the following actions:
      • Set DamageEventAmount = 0.00
      • Set DamageEventArmorT = ARMOR_TYPE_NONE
      • Set DamageEventWeaponT = WEAPON_TYPE_NONE
    • Setting the weapon type and armor type to none like the above will stop any on-hit sounds from playing. When the Peasant attacks in the demo map, this is the trick I'm using. Instead of saying "MISSED!" I have the Floating Text saying "FAIL!" because - again - it's not exactly a "miss".

Thank you to Blizzard for continuing to work on this amazing game to give us awesome new natives that have the best possible control over incoming damage. Damage Engine brings that power to GUI. Also, a very special thank you to @KILLCIDE for getting me motivated to start up the 5.0 project in the first place.

Thank you to the users of this system who have helped me mold this project into the stable, powerful form it is in today!

For versions 3.8 and prior:

Thank you @looking_for_help for finding the spell damage detection method used in Damage Engine 3 - it was the greatest find since the undefend bug.

Thanks to Jesus4Lyf and @Nestharus for building the inspiration that originally led me to create DamageEngine.

Thank you Wietlol and looking_for_help for challenging me on this project to integrate solutions to problems I had not been made aware of, such as the importance of an After-Damage Event.

Thanks to @Spellbound for several crucial bug reports.


Damage Engine Config

Damage Engine vJass

Damage Engine Lua

Changelog


  • Damage Engine Config
    • Events
      • Map initialization
      • Game - DamageModifierEvent becomes Greater than 0.00
      • Game - LethalDamageEvent becomes Less than or equal to 0.00
      • Game - DamageEvent becomes Not equal to 0.00
      • Game - AfterDamageEvent becomes Less than 0.00
      • Game - AOEDamageEvent becomes Greater than or equal to 0.00
      • Game - SourceDamageEvent becomes Equal to 0.00
      • Game - PreDamageEvent becomes Equal to 0.00
      • Game - ArmorDamageEvent becomes Equal to 0.00
      • Game - ZeroDamageEvent becomes Equal to 0.00
    • Conditions
    • Actions
      • -------- You can add extra classifications here if you want to differentiate between your triggered damage --------
      • -------- Use DamageTypeExplosive (or any negative value damage type) if you want a unit killed by that damage to explode --------
      • -------- - --------
      • -------- The pre-defined type Code might be set by Damage Engine if Unit - Damage Target is detected and the user didn't define a type of their own. --------
      • -------- "Pure" is especially important because it overrides both the Damage Engine as well as WarCraft 3 damage modification. --------
      • -------- I therefore gave the user "Explosive Pure" in case one wants to combine the functionality of the two. --------
      • -------- - --------
      • Set VariableSet DamageTypePureExplosive = -2
      • Set VariableSet DamageTypeExplosive = -1
      • Set VariableSet DamageTypeCode = 1
      • Set VariableSet DamageTypePure = 2
      • -------- - --------
      • Set VariableSet DamageTypeHeal = 3
      • Set VariableSet DamageTypeBlocked = 4
      • Set VariableSet DamageTypeReduced = 5
      • -------- - --------
      • Set VariableSet DamageTypeCriticalStrike = 6
      • -------- - --------
      • Custom script: call DamageEngine_DebugStr()

BribeFromTheHive/DamageEngine

Lua 1.0.2.3 - Fixed to match adjustment made in vJass version 5.4.2.3.
Lua 1.0.2.2 - Fixed to match adjustment made in vJass version 5.4.2.2.
Lua 1.0.2.1 - Fixed to match adjustment made in vJass version 5.4.2.1.
Lua 1.0.2.0 - Added support for Lua Fast Triggers ([Lua] Ridiculously Fast Triggers). Fixed an issue where the AfterDamageEvent wasn't always timed the correct way like it was in the JASS verion.
Lua 1.0.1.0 - Fixed encapsulation issue and recursion issue with DamageEngine_inception. Now hooks UnitDamageTarget.
Lua 1.0.0.0 - Release based on Damage Engine 5.4.2.0

5.9.0.0 - Added the following clearer event names to make things less confusing for new users:
  • PreDamageEvent - can be used in place of DamageModifierEvent pre-armor modification
  • ArmorDamageEvent - can be used in place of DamageModifierEvent post-armor modification
  • OnDamageEvent - can be used instead of a non-zero DamageEvent
  • ZeroDamageEvent - can be used instead of a zero damage DamageEvent
  • SourceDamageEvent - runs at the same time as AOEDamageEvent, but doesn't need to hit multiple units.
Added "DamageFilterRunChance" - odds for the trigger to BE run (works inversely to DamageFilterFailChance).
Shortened the Configuration trigger so that it focuses primarily on what the user can modify.
Organized all variables into categories to help users better understand what does what.
Installation or updating from a previous version will require re-copying the entire Damage Engine folder.
Updated the demo map's text tag production to include a new custom update for ArcingTextTag, thanks to @Ugabunda and @Kusanagi Kuro.
Side note - the Demo Map's triggers have been heavily cleaned up and will now no longer cause crashes when being imported into a new map.
5.8.0.0 -
  • Added a new functionality to the AOEDamageEvent, which allows it to fire even when only one unit is hit, if the AOEDamageEvent is registered as "Not Equal" instead of "Equal to". This is useful in a very specific scenario where an AfterDamageEvent may not be able to be relied upon to properly deallocate data from a running instance that needs to be able to function when multiple units are hit, but also needs to not fail when only one unit is hit.
  • Added additional filters for GUI users to avoid using trigger conditions in even more scenarios:
    • DamageFilterSource/TargetI (has item)
    • DamageFilterSource/TargetA (has ability)
    • DamageFilterSource/TargetC (has a certain classification, like hero or Tauren)
    • DamageFilterFailChance - odds for the trigger to not be run (ideal for critical strike or evasion)
  • Provided a way for GUI to un-register a Damage Event by setting "RemoveDamageEvent" to true from within their trigger's actions.
  • Moved the CreateTimer/CreateTrigger/CreateGroup calls that had been included in the globals block down to the onInit block as per request of @Ricola3D
  • Minor performance improvements thanks to @BLOKKADE
5.7.1.2 - Fixed an issue with armor penetration sometimes bugging out.
5.7.1.1 - Fixed an issue with the eventFilter not retaining its value during an AOE event. Fixed an issue with eventFilter when USE_MELEE_RANGE was set to false. Both issues reported by @lolreported
5.7.1.0 -
I have fixed several potential points of failure reported by multiple users that stopped Damage Engine from working for the rest of the game. In any case there should no longer be ANY SITUATION where Damage Engine just "stops working", even in ways I can't predict. The most likely issue was with DamageScalingWC3/User having possible 0-division errors.​
Fixed the "configured" issue reported by @lolreported where manual configuration didn't work unless the damage and attack type checks were initialized tto -1.​
In addition to these fixed bugs, I have added several more static ifs so that advanced users have more control over getting rid of features they might not care about.​

5.7.0.3 - Fixed the issue reported by @KitsuneTailsPrower wherein the DamageInterface extension wasn't working. This needed to be fixed both in the Damage Engine source as well as the DamageInterface plugin itself.
5.7.0.2 - Fixed the issue reported by @Wazzz where the armor reduction wasn't taken into consideration. Actually there was a much bigger flaw that I had overlooked that was prompting this.
5.7.0.1 - Improved the logic of the 0 damage event.
5.7.0.0:

  • Usage of the "DamageEvent becomes EQUAL to 1.00" now can be extrapolated further than ever before:
    • EQUAL works as it always has.
    • NOT EQUAL only runs for code damage.
    • LESS THAN only runs for damage from attacks.
    • LESS THAN OR EQUAL only runs for melee attacks.
    • GREATER THAN OR EQUAL only runs for ranged attacks.
    • GREATER THAN only runs for Spell damage.
  • Fully adapted Damage Engine to work with every other major DDS
  • Rewrote the internal script to use vJass structs: Damage and DamageTrigger.
  • Changed some of the vJass API. You can find the API listed in the Damage Engine trigger. Notably:
    • I removed UnitDamageTargetEx. You can replace this with Damage.apply.
      • The reason for this change is because of cross-compatibility. Rising Dusk's IDDS uses a different set of parameters for this function, so I removed it from my library to allow this to work seamlessly.
    • TriggerRegisterDamageEvent -> TriggerRegisterDamageEngine
    • RegisterDamageEvent -> RegisterDamageEngine
      • The reason for the above two changes is, like for UnitDamageTargetEx, because Rising Dusk's IDDS uses them. I don't want to make the same mistake I did with Table's API and preferred to walk back my API choices before things got out of hand again.
  • Various performance tweaks, bug fixes and re-commenting of variables.
  • Recursive damage is now processed more intelligently and possibly be more performance-friendly.
  • Adapted the cross-compatibility libraries for Weep and LFH's systems to use textmacros to insert themselves into Damage Engine (this might have been in the 5.6 update, but these two updates were both tailored to achieve similar goals).
5.6.2.0 - Fixed a bug with Damage modification and laid groundwork for a bunch of optional vJass compatibility addons.
5.6.1.0 - Patchwork on Melee/Ranged detection, recursion tracking. Also added the ability to modify damage from a DamageEvent to make it easier on beginners.
5.6.0.1 - Fixed an issue where the DamageEventType for recursive damage that used NextDamageType would always default to DamageTypeCode.
5.6.0.0
Rewrote a significant amount of the internal code so that struct and GUI syntax both work - and are synchronized with each other. vJass-exclusive users can disable the GUI synchronization if they don't use any GUI damage events in their maps.​
Four new variables must be added to your variable editor:​
  • boolean NextDamageIsAttack
  • boolean NextDamageIsMelee
  • boolean NextDamageIsRanged
  • integer NextDamageWeaponT
Struct syntax should not need too much introduction - Damage.index is the triggering event ID, and the syntax is Damage.index.amount/source/target/etc. To initialize a JASS damage event, use:​
JASS:
function RegisterDamageEvent takes code c, string eventName, real value returns nothing
The string is simplified: "Modifier", "" (for simple DamageEvent), "After", "Lethal", "AOE"​
Finally, a neat QOL improvement is that I have assigned weight to each of the events. When registering an event, you can include numbers different than 1, 2, 3 or 4 (for modification) or just the plain "1" for the others. Now you can set your own sequencing and use 1.5, 3.14 or even -1 to give an even more extreme priority to something. Lower numbers run first, higher ones last.​
5.5.0.0 - Added support for the new native BlzGetEventIsAttack via "IsDamageAttack". Also updated the Config trigger to make importing a bit easier
5.4.2.3 - Fixed a mis-flag of the IsDamageSpell value when not being actual spell damage.
5.4.2.2 - Actually fixed the Cold Arrows issue (division by 0.00001 or something ...somehow... either way, it is fixed).
5.4.2.1 - A fix which should hopefully quell the recent reports of damage events failing in complex situations involving Cold Arrows.
5.4.2.0 - A ton of fixes to repair the issues plaguing Sunken City and anyone else who might be pushing this engine well beyond what I imagined it would be used for. Also added a couple of variables intended to be used to ricochet damage: CONVERTED_ATTACK_TYPE and CONVERTED_DAMAGE_TYPE. Check the demo map for how they can be used in a Unit - Damage Target action.
5.4.1.0 - The "Inception" update. Advanced users can interact with Damage Engine via custom script to set DamageEvent_inception = true to allow their damage to potentially go recursive (to a fixed extent).
5.4.0.1 - Hotfixed that modifiers 2 and 3 weren't running.
5.4.0.0 - By using an innovative approach of hooking TriggerRegisterVariableEvent, I've permanently eliminated all risks of recursion in the engine.
5.3.0.1 - Fixed unexpected behavior with DamageTypePure when it is affected by Anti-Magic Shell or Mana Shield. DamageTypePure now no longer ignores DamageScalingWC3.
5.3.0.0 - Fixed an issue with AfterDamageEvent sometimes being delayed. Added DamageScalingUser to track the ratio of user modified damage, as well as DamageEventArmorPierced which allows the user to define how much armor to ignore when working with DAMAGE_TYPE_NORMAL.
5.2.0.1 - Fixed an issue where with the final unit in a Spirit Link chain or the retaliating damage of Thorns/Carapace would not deploy an AfterDamageEvent. Also fixed an issue where AfterDamageEvent would still fire from DAMAGE_TYPE_UNKNOWN if it was greater than 0. Simply copy over the JASS from this post in order to update your own implementation.
5.2.0.0

  • Now features DamageEventArmorT and DamageEventDefenseT, which pull from the target unit's Object Editor data in order to allow you more complete access to detect and even MODIFY those defenses. Changes must be made in a DamageModifierEvent, and they are reverted as soon as armor is calculated.
  • Re-introduced AfterDamageEvent, which is the moment after the unit's life is changed, but before any recursive damage has run.

5.1.3.1 - Bug fixes and performance improvements. No, really. Fixed an issue with the DAMAGED event running even though it was turned off (who would've guessed that?)
5.1.3.0 - Engine re-tooling to improve accuracy and get Spirit Link/Defensive damage out of hardcoded mode - it will now work even in circumstances I haven't tested for (in case those weren't the only issues). Also fixed the Is Unit Moving resource.
5.1.2.1 - Fixed an issue with Spiked Carapace and Thorns Aura where the melee attacker would not get recorded correctly. This required the same fix as I needed to apply for the initial target in a spirit link chain.
5.1.2.0 - Tweaked recursion and fixed a few bugs. Re-introduced the zero damage event now that patch 1.31.1 brought it back.
5.1.1.1 - Minor tweak to Spirit Link in rare situation.
5.1.1.0 - Fixed issues related to Spirit Link. Now works intuitively as expected.
5.1.0.0 - Crazy improvements - check out the details in "How to upgrade from Damage Engine 4.0 or earlier" and "How to use Damage Engine 5.1"
5.0.0.0 - Oh man. Where do I even start?
  • You can now set/compare DamageEventDamageT, DamageEventAttackT or DamageEventWeaponT
  • No longer needs Unit Indexer nor any custom Object Editor data nor modifications.
  • Requires WarCraft 3 1.31 or higher.
  • Changed vanilla JASS code to vJass to clean up a lot of things such as making certain variables private.
  • Look for more details in "How to upgrade from Damage Engine 4.0 or earlier"

4.0.0.0 - Never officially released, but was the first iteration which used SetEventDamage.
For 3.8.0.0 and prior, see: Damage Engine 3.8.0.0 | HIVE


Cross-Compatibility:

BribeFromTheHive/DamageEngine

Keywords:unit indexer, damage detection, damage event, weep, nestharus, looking_for_help, EVENT_PLAYER_UNIT_DAMAGED, damage engine, spell, physical, EVENT_PLAYER_UNIT_DAMAGED, attacktype, damagetype, weapontype, armortype, defensetype, BlzSetEventDamage
Previews
Contents

Damage Engine Demo Map (Map)

Lua Damage Engine 2.0.0.0 (Map)

Reviews
23:20, 11th Jan 2015, BPower Criticism: On the one hand Damage Engine offers extremely high utility to every spell, system and map maker independent of the coding style ( GUI, JASS, vJass, .... ) on the other hand it's very easy to import and...
Level 2
Joined
Aug 6, 2022
Messages
9
Is there any chance that someone still has a version of this that works for 1.31 (pre-reforged)? There seems to be a link for people like myself in the "requirements" section, but it doesn't send to anywhere useful... or maybe I missed something?
 
Level 3
Joined
Oct 5, 2019
Messages
8
Is there any chance that someone still has a version of this that works for 1.31 (pre-reforged)? There seems to be a link for people like myself in the "requirements" section, but it doesn't send to anywhere useful... or maybe I missed something?
you can still use the 5.9 version tho, but with a little bit of edit of BlzGetEventIsAttack() by adding this at the top of the Damage Engine script
JASS:
function BlzGetEventIsAttack() takes nothing returns boolean
    return BlzGetEventDamageType() == DAMAGE_TYPE_NORMAL
endfunction
Or you can use the 3.A or 3.8 version here (as if you like)
 
Last edited:
Level 2
Joined
Aug 6, 2022
Messages
9
you can still use the 5.9 version tho, but with a little bit of edit of BlzGetEventIsAttack() by adding this at the top of the Damage Engine script
JASS:
function BlzGetEventIsAttack() takes nothing returns boolean
    return BlzGetEventDamageType() == DAMAGE_TYPE_NORMAL
endfunction
Or you can use the 3.A or 3.8 version here (as if you like)

I downloaded the 5.9 map today, but trying to open it in the editor gives me this error... Editor is version 1.31b (6072), downloaded from around here actually.
 

Attachments

  • 2022-09-05_21h16_14.png
    2022-09-05_21h16_14.png
    47.8 KB · Views: 16
Level 3
Joined
Oct 5, 2019
Messages
8
I downloaded the 5.9 map today, but trying to open it in the editor gives me this error... Editor is version 1.31b (6072), downloaded from around here actually.
The newest map is saved on reforged editor so any editor version below wont able to open it, you may need some one had access to reforge to export the trigger data or you can manually copy from preview triggers.

1662405973149.png
 
Level 18
Joined
Jan 1, 2018
Messages
728
The newest map is saved on reforged editor so any editor version below wont able to open it, you may need some one had access to reforge to export the trigger data or you can manually copy from preview triggers.

View attachment 406505
You can also use my tool: Map Adapter

Here the maps trigger data i exported, dunno will it able to import to .31
The triggers seem to be compatible with 1.31, but in the war3map.j I can see the map uses 'BlzGetEventIsAttack', which is not compatible.
Fortunately there is a solution for this: Damage Engine 5.9.0.0
 
Level 4
Joined
Dec 17, 2020
Messages
28
I use the reforged and now that the world editor has been updated 1.33.0 some resources like this are bugged, can I use an older editor without problems? And if so, how do I install it?
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
I use the reforged and now that the world editor has been updated 1.33.0 some resources like this are bugged, can I use an older editor without problems? And if so, how do I install it?
Sorry, what's bugged? You have to enable JassHelper at the top menu of the trigger editor if you're having issues saving
 
Level 4
Joined
Dec 17, 2020
Messages
28
Sorry, what's bugged? You have to enable JassHelper at the top menu of the trigger editor if you're having issues saving
Sorry bro 😅! I had it disabled since I updated a few weeks ago, too bad :cute:, I thought the update was the cause. Everything's fine :peasant-ok-hand:.
 
Level 2
Joined
Jun 19, 2021
Messages
6
Hey,
Is it possible to set a minions movement speed to 0 without getting the number bug?
The first attack shows that the unit get's health in return, which is not the case. I assume it is linked to unit moving, but cannot connect the dots.
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
Hey,
Is it possible to set a minions movement speed to 0 without getting the number bug?
The first attack shows that the unit get's health in return, which is not the case. I assume it is linked to unit moving, but cannot connect the dots.

Are you referring to how the demo map triggers are set up? If so, you can remove the portion which checks if a unit is moving (as that was just a showcase, and the demo trigger was never intended to be copy&pasted to actual maps).

Hello, I am writing from a translator. I would like to intercept damage with the condition - if the target (the one who receives damage) the type of attack is common, but I can't figure out how to check for it. Please tell me and thank you in advance!
If I understand correctly, a "common" type of attack would mean "normal" (e.g. from a Footman, Knight, Grunt, Tauren) but not other types of attacks (e.g. Pierce, Hero, Siege, Chaos). To do this:

  • Normal Attack Check
    • Events
      • Game - Value of PreDamageEvent becomes Equal to 0.00
    • Conditions
      • DamageEventAttackT Equal to ATTACK_TYPE_NORMAL
    • Actions
      • -------- Do stuff --------
(Sorry had this typed earlier today but had forgotten to submit it).
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
Thank you all for the answers. I checked, and it doesn't work. I suspect that this check checks that the attacker's attack type is normal. And I need the target's attack type to be checked.





View attachment 407657
Well, you can check the armor type of the target:

DamageEventDefenseT Equal to DEFENSE_TYPE_NORMAL

But to check its attack type, you need to use one of the new functions that Blizzard added (which works in GUI):

(Unit: DamageEventTarget's Weapon Integer Field: Attack Attack Type ('ua1t') at Index:0) Equal to ATTACK_TYPE_NORMAL

This checks the first attack type of the unit, but wouldn't check the second attack type of the unit (because a unit sometimes has a different attack type for ground and air, e.g. Batrider/Siege Engine).
 
Level 2
Joined
Jun 19, 2021
Messages
6
Are you referring to how the demo map triggers are set up? If so, you can remove the portion which checks if a unit is moving (as that was just a showcase, and the demo trigger was never intended to be copy&pasted to actual maps).

I can explain it in another way. I am making a spell, that makes a wall of units surrounding the caster. All of the units movement speed are set to 0 so they can't move. As I do that, the first hit will always say: +50
As if the units is getting a heal. Tho I tried to disable "Is unit moving" Trigger, and it still happens.
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
I can explain it in another way. I am making a spell, that makes a wall of units surrounding the caster. All of the units movement speed are set to 0 so they can't move. As I do that, the first hit will always say: +50
As if the units is getting a heal. Tho I tried to disable "Is unit moving" Trigger, and it still happens.
If you give the units more than 0 movement speed, does the healing text go away? If so, you'd need to send me over a testable map to work with to try to help you to find the root cause.
 
Level 2
Joined
Jun 19, 2021
Messages
6
If you give the units more than 0 movement speed, does the healing text go away? If so, you'd need to send me over a testable map to work with to try to help you to find the root cause.
Yes, if I set the speed above 0 the heal text disappear. So this is not a function in the base code? It is something I have done wrong?
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
Yes, if I set the speed above 0 the heal text disappear. So this is not a function in the base code? It is something I have done wrong?
It sounds like there is a trigger somewhere in your map that is checking or changing the health of the unit differently, depending on if it has movement speed above 0 or not. Either by giving them +2 strength or by giving them an item that increases their health directly. But it doesn't make sense in the context of the systems that I've built. That's why it might be good if I take a look at your map to see if I can isolate it.
 
Level 2
Joined
Jun 19, 2021
Messages
6
It sounds like there is a trigger somewhere in your map that is checking or changing the health of the unit differently, depending on if it has movement speed above 0 or not. Either by giving them +2 strength or by giving them an item that increases their health directly. But it doesn't make sense in the context of the systems that I've built. That's why it might be good if I take a look at your map to see if I can isolate it.
I just realised how stupid I am. Forgot that I added "Healing Engine" to display healing amounts. So the error is within Healing Engine, rather than Damage Engine.
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
I don't know if I did something different, but in version 3A.0.. that I recently used it, when I use a group that captures units in an area to deal damage, the second unit that is damaged its health goes up to +50000 health .

JASS:
call GroupClear(G)
call GroupEnumUnitsInRange(G,GetUnitX(target),GetUnitY(target),300,Condition(function True))
call GroupRemoveUnit(G,target)
set dam = 20
loop
     set a = FirstOfGroup(G)
     exitwhen a == null
     call GroupRemoveUnit(G,a)
     call UnitDamageTarget(source,a,dam,false,false,ATTACK_TYPE_CHAOS,DAMAGE_TYPE_UNIVERSAL,null)
endloop
View attachment 407948
I deactivated all the damage codes, but it keeps happening, I don't know if it's because I can't use it in the same line of the event to do this. 🤔
Note 1: In the gui version, this strange thing does not happen...
I can't recall off-hand, but it could be that Damage Engine 3A might need some kind of ClearDamageEvent functionality to notify the system that it needs to be reset. I will review the code next week, and it's possible that this is just a bug that I never accounted for (and 3A has been completely untouched from version 1.0, surprisingly).
 
Level 7
Joined
Mar 14, 2021
Messages
43
I can't recall off-hand, but it could be that Damage Engine 3A might need some kind of ClearDamageEvent functionality to notify the system that it needs to be reset. I will review the code next week, and it's possible that this is just a bug that I never accounted for (and 3A has been completely untouched from version 1.0, surprisingly).
Ah, oks, I thought that designing a function similar to the "static method apply takes..." method for this version caused that error, but it was repeated in several events that it did not apply said function, I only needed it to save a damagetype variable in the library lol.
 
Level 19
Joined
Feb 27, 2019
Messages
590
I tried to save my map but this happen,

View attachment 408860

any idea?
It might be an error that occured when you imported the variables. Open up your variable editor from the trigger editor and make sure the variables with errors mentioned in jasshelper have the variable type real and initial value 0.
 

Attachments

  • variable editor.png
    variable editor.png
    11.3 KB · Views: 6
Last edited:
Level 6
Joined
Jul 12, 2017
Messages
139
It might be an error that occured when you imported the variables. Open up your variable editor from the trigger editor and make sure the variables with errors mentioned in jasshelper have the variable type real and initial value 0.
Thank you, that works but now I encounter new problem which is,

1664124053311.png


and this one too,

1664124082567.png
 
Level 19
Joined
Feb 27, 2019
Messages
590
Undeclared variable would mean that the variable does not exist or cant be used in that stretch of code but since its global, the latter should not be it. It could be related to the same problem, that the variable has not initiated correctly or even might not exist. Try the same step as before and also make sure that it actually exists.

Take a look at the latest changelog for 5.9.0.0. Bribe stresses that "Installation or updating from a previous version will require re-copying the entire Damage Engine folder."
 
Level 6
Joined
Jul 12, 2017
Messages
139
Undeclared variable would mean that the variable does not exist or cant be used in that stretch of code but since its global, the latter should not be it. It could be related to the same problem, that the variable has not initiated correctly or even might not exist. Try the same step as before and also make sure that it actually exists.

Take a look at the latest changelog for 5.9.0.0. Bribe stresses that "Installation or updating from a previous version will require re-copying the entire Damage Engine folder."
I see, that explains why when I copied it in new map, it works but not on my old map.
 
If I have 2 triggers:
* Trigger 1: Event - DamageModifierEvent = 1.00 (runs for all damage)
above
* Trigger 2: Event - DamageModifierEvent < 1.00 (runs for attack damage)

I understand that the trigger above runs before the trigger under. An attack damage instance causes Trigger 1 to run, and the action block sets DamageEventOverride = true. Will that damage cause Trigger 2 to run after Trigger 1 finishes running?
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
If I have 2 triggers:
* Trigger 1: Event - DamageModifierEvent = 1.00 (runs for all damage)
above
* Trigger 2: Event - DamageModifierEvent < 1.00 (runs for attack damage)

I understand that the trigger above runs before the trigger under. An attack damage instance causes Trigger 1 to run, and the action block sets DamageEventOverride = true. Will that damage cause Trigger 2 to run after Trigger 1 finishes running?

That's an interesting scenario you've outlined. EDIT: I just checked the code, and this would not work unless you modified the registerVerbose method to allow the same trigger to be added twice (right now, it would just add the extra conditional, which in this case is unnecessary). Therefore, out of the box, this would not work.

I'd personally just use an if/then/else block to handle the logic, rather than running two events on one trigger. This would leave nothing to the imagination of "what if" scenarios like what you've just given me.

Bear in mind that Lua Damage Event is getting a MAJOR overhaul sometime before the end of the year, which will make events behave differently than they do now with one trigger (as in, you can tell your trigger to "wait" until the next event).
 
Last edited:
That's an interesting scenario you've outlined. EDIT: I just checked the code, and this would not work unless you modified the registerVerbose method to allow the same trigger to be added twice (right now, it would just add the extra conditional, which in this case is unnecessary). Therefore, out of the box, this would not work.

I'd personally just use an if/then/else block to handle the logic, rather than running two events on one trigger. This would leave nothing to the imagination of "what if" scenarios like what you've just given me.

Bear in mind that Lua Damage Event is getting a MAJOR overhaul sometime before the end of the year, which will make events behave differently than they do now with one trigger (as in, you can tell your trigger to "wait" until the next event).
So the "< 1.00" trigger will not execute if DamageEventOverride = true is executed on the "= 1.00" trigger that runs before "< 1.00". Well, it's the behavior I want anyway.
But these are two separate triggers and not two events on one trigger, so we may not be talking about the same thing?
Not really into Lua much because what I'm working on is still very JASS heavy 🥲
 
Level 7
Joined
Mar 14, 2021
Messages
43
and it's possible that this is just a bug that I never accounted
Doing certain things on a test map, Damage Engine 3.8, I got the +500000 health bug, this happened to me after detecting an attack damage and then in a different damage detection event adding a tornado slow aura to the attacker to increase his speed, a 0 damage is caused by the aura to the attacker, but it appears in messages that an AoE damage was done to the attacked unit, I suppose that the recursion will be the problem, I'll pass you the test map. Perhaps using the event call TriggerRegisterVariableEvent( t, "udg_DamageEvent", EQUAL, 0 ) to detect is the problem, and not setting it to a value of 1, but it could also be something else.
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
Doing certain things on a test map, Damage Engine 3.8, I got the +500000 health bug, this happened to me after detecting an attack damage and then in a different damage detection event adding a tornado slow aura to the attacker to increase his speed, a 0 damage is caused by the aura to the attacker, but it appears in messages that an AoE damage was done to the attacked unit, I suppose that the recursion will be the problem, I'll pass you the test map. Perhaps using the event call TriggerRegisterVariableEvent( t, "udg_DamageEvent", EQUAL, 0 ) to detect is the problem, and not setting it to a value of 1, but it could also be something else.
Does the bug still occur on 3A? I don't advise using 3.8 anymore as its only advantage was that it worked without JassHelper.
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
Oks, using version 3.A, the error doesn't happen. 👍. Only area damage in this version is buggy.
Could you please let me know what about area damage appears to be buggy? I've modified your test map with 3A, but I'm not sure what I would need to do to replicate the bug behavior you are describing.
 
Level 7
Joined
Mar 14, 2021
Messages
43
Could you please let me know what about area damage appears to be buggy? I've modified your test map with 3A, but I'm not sure what I would need to do to replicate the bug behavior you are describing.
Edit 3: The +500000 health bug in the "Mod" event still occurs when dealing damage to other units within version 3.A.

JASS:
//Bug life 3.A, +500000 on first unit: gg_unit_h002_0002
function Trig_On_Hit_Actions1 takes nothing returns nothing
    local unit u = udg_DamageEventSource
    local unit a = udg_DamageEventTarget
    local real dam = 20
    if udg_DamageEventAmount > 0 and udg_IsDamageSpell == false and udg_DamageEventType != 1 then
        set udg_NextDamageType = 1
        call UnitDamageTarget(u, gg_unit_h002_0002, dam,false,false,ATTACK_TYPE_CHAOS,DAMAGE_TYPE_UNIVERSAL,null)
        set udg_NextDamageType = 1
        call UnitDamageTarget(u, gg_unit_h005_0003, dam,false,false,ATTACK_TYPE_CHAOS,DAMAGE_TYPE_UNIVERSAL,null)
    endif
    set u = null
    set a = null
endfunction

function Init takes nothing returns nothing
    local trigger t = CreateTrigger()
    call TriggerRegisterDamageEngine(t,"Mod",1.00)
    call TriggerAddAction(t, function Trig_On_Hit_Actions1)
    set t = null
endfunction
If the attack is ATTACK_TYPE_NORMAL, it will be given as negative damage and taken as "udg_IsDamageSpell", the health error will not occur but the second unit "gg_unit_h005_0003" will not receive the damage put in this event. The same thing happens when doing a group damage (AoE) within this Event, the units will have error life or will not take damage, that's why it does not work to do code damage to a group of units.

In the version 3.8 issue the tornado slow aura bug remains causing additional damage to the attacked unit, this problem generates the bug of +500000 life to the attacked unit. This bug is generated in 3.8, if the source unit does damage to itself, within the event, damage 0 is the one that causes the most bugs.
JASS:
//Bug life 3.8, This problem generates the bug of +500000 life to the attacked unit.
function Trig_On_Hit_Actions1 takes nothing returns nothing
    if GetUnitAbilityLevel(udg_DamageEventSource,'A009') > 0 and udg_DamageEventSource != udg_DamageEventTarget and udg_IsDamageSpell == false then
        if udg_DamageEventAmount > 0 then
            call UnitAddAbility(udg_DamageEventSource,'A000') //Bug life for Aure
            call UnitRemoveAbility(udg_DamageEventSource,'A000') //Bug life for Aure
            call UnitRemoveAbility(udg_DamageEventSource,'Basl') //Bug life for Aure
        endif
    endif
endfunction

function Init takes nothing returns nothing
    local trigger t = CreateTrigger()
    call TriggerRegisterVariableEvent( t, "udg_DamageModifierEvent", EQUAL, 1.00 )
    call TriggerAddAction(t, function Trig_On_Hit_Actions1)
    set t = null
endfunction

Note: Check if there were any more bugs but they are the only ones I found at the moment so I update the test maps only with what I specify. I've been trying a few things in my case to resolve this data, but in the end I ended up changing the recursion, and I don't want to touch that part since maybe there is another better way to solve this.

Note 2: If these bugs are maintained en 3.A, during the course of the game when several of these come together, the game will close, I don't know if it is due to recursion or null variables. Greetings...
 

Attachments

  • Test Damage 3,A Bug Life 2.w3x
    63.2 KB · Views: 2
  • Test Damage 3,8 Bug Life 2.w3x
    52.9 KB · Views: 3
Last edited:
No i mean, within the DamageEvent i want to deal damage like 'Unit - cause unit to damage bla bla with Attack Type and DamageType'
I want to autodetects the AttackType and DamageType
You mean something like this? (This it literally what Bribe said)
This example is: Cause the damage source to damage the target with the same attack and damage type dealing 500 damage.
  • Unit - Cause DamageEventSource to damage DamageEventTarget, dealing 500.00 damage of attack type CONVERTED_ATTACK_TYPE[DamageEventAttackT] and damage type CONVERTED_DAMAGE_TYPE[DamageEventDamageT]
 
Level 5
Joined
Dec 25, 2014
Messages
111
You mean something like this? (This it literally what Bribe said)
This example is: Cause the damage source to damage the target with the same attack and damage type dealing 500 damage.
  • Unit - Cause DamageEventSource to damage DamageEventTarget, dealing 500.00 damage of attack type CONVERTED_ATTACK_TYPE[DamageEventAttackT] and damage type CONVERTED_DAMAGE_TYPE[DamageEventDamageT]
Oh sorry that Converted vars is exist? I guess my Damage Engine is outdated then. Which version started using them? I'm still on classic w3 tho.

EDIT : Oh sorry again i get it now, thank you very much.
 
Last edited:
Oh sorry that Converted vars is exist? I guess my Damage Engine is outdated then. Which version started using them? I'm still on classic w3 tho.
I'm unsure what you mean by "classic". There are many versions before 1.32 and some introduced big changes.
The code say that these were introduced in 5.4.2. All 5.X versions require Warcraft 1.31 or later
 
Level 5
Joined
Dec 25, 2014
Messages
111
I'm unsure what you mean by "classic". There are many versions before 1.32 and some introduced big changes.
The code say that these were introduced in 5.4.2. All 5.X versions require Warcraft 1.31 or later
What i mean classic is that because i thought that was in Damage engine 5.8 and up. 5.8 and up is coded in reforged isn't it? and i can't really using them for now.
And to be honest i don't know which version i am using right now since it has been a few years and i can't really found the latest version which are not coded in refoged.
 

Bribe

Code Moderator
Level 50
Joined
Sep 26, 2009
Messages
9,464
What i mean classic is that because i thought that was in Damage engine 5.8 and up. 5.8 and up is coded in reforged isn't it? and i can't really using them for now.
And to be honest i don't know which version i am using right now since it has been a few years and i can't really found the latest version which are not coded in refoged.
As long as you have bought the (non-reforged) game, it's not some illegal copy of the game, and it is up-to-date, it should work. The Reforged thing is only about graphics/campaign, but it doesn't change the common.j/blizzard.j API.
 
Top