Deadlock mechanics.
Card by card.

A hit has several stages

The build-6698 Bullet/Spirit resistance stage multiplies damage by 1 − net resistance/100, then clamps negative damage to zero. Negative resistance increases damage. Amplification, other reductions, absorption and special states are separate stages; the processed floating-point amount is not necessarily the integer health loss.

Still open. Complete effect-specific shield, bypass and penetration behavior remains unresolved.

Bullet, Spirit & melee

Weapon damage, Spirit damage and melee have separately named properties and reporting categories. An ability's animation does not tell you which protection applies: a projectile is a delivery method, not a damage type. Read the effect and its damage category separately.

Resistance contributions

In build 6698, ordinary Bullet and Spirit resistance contributions combine through their remaining fractions: 1 − (1 − 0.30)(1 − 0.20) = 44%. Eligible resistance-reduction magnitudes combine in a separate pool, which is subtracted afterward. Item ownership alone does not establish which contributions are active.

Still open. This shortcut excludes innate/inherited stats and the NPC branch; component replacement and activation still need item-specific rules.

Resistance reduction & penetration

The item data has target-side armor reduction, while the bullet-processing survey also identifies a penetration field. These are distinct inputs. The name of a field does not establish whether it subtracts percentage points, multiplies a value, affects a surface, or runs before another modifier.

Still open. The aura's complete evaluator and the penetration field's meaning are not established by those numbers.

Conditional defense

Some protection is conditional rather than permanently active. Keep its trigger, its bonus and any duration together when comparing items. In particular, a low-health bonus is not automatically an extra bonus at full health, and a post-cast buff is not an always-on resistance.

The Rift's three resistances

The Rift aura contributes Bullet, Spirit and Status Resistance to its eligible team's nearby heroes. Here q is the team's current relative deficit, scaled from zero to full strength at a 15% deficit. The team is chosen when the Rift spawns; its resistance strength follows the live gap.

Still open. This is the Rift contribution—not total resistance, and not an Urn buff.

Small hits can retain a remainder

The earlier health-mutation path uses integer health but retains fractional damage between applications. It floors the processed damage, combines the fraction with the stored remainder and carries a whole point when that sum reaches one. Rounding every hit independently would describe a different system.

Still open. This is an earlier-build code finding, not a fresh September measurement.

Healing, regeneration & lifesteal

Direct healing, regeneration over time and damage-linked lifesteal have separate properties. A bonus to one should not be treated as a blanket multiplier to all three. Cast-side healing amplification, received healing and regeneration also have distinct fields.

Anti-heal has scope and duration

Healing reduction is not damage and is not a reduction to maximum health. Keep the affected healing channel and the debuff duration beside the percentage. The captured settings can describe both received-healing and regeneration penalties without proving how several anti-heal sources combine.

Still open. The combined anti-heal cap and stacking order remain unresolved.

Stored healing stacks

A charge-based heal has at least three questions: how charges are earned, how many can be stored and what a charge is worth. Do not confuse the storage cap with the amount healed by one activation. Other healing modifiers may still affect the result.

Barriers, immunity & evasion

Absorption tracks damage taken by a protective layer; evasion describes an avoided hit; immunity or a damageability gate can prevent an eligible damage application. None is simply extra maximum health. Their exact interaction with resistance and damage categories needs effect-specific rules.

Still open. A universal barrier-versus-resistance order is not established.

Reflection & deferred damage

Reflection creates a separate question about damage returned to the attacker. Deferral moves some damage into a later process. Neither means that the original hit was automatically erased. Source attribution and timing matter when interpreting these effects or a death recap.

Still open. Reflection mitigation and deferred-damage settlement are not fully mapped.

An item's parts

An item can grant an intrinsic modifier, listen for a trigger and expose an active ability. Tier, shop filters and tooltip grouping describe it, but do not themselves execute the effect. A passive stat and an active buff on the same item may have different lifetimes.

Components & upgrades

A component link connects item definitions; it is not permission to add every stat of every linked record together. To evaluate a finished build, distinguish the item actually owned from its components and any consumed-component state. Tier is a classification, not a universal stat multiplier.

Still open. Full component-consumption and duplicate-item rules are outside the reconstructed scope.

Weapon bonuses use two groups

Ordinary weapon and bullet increases add within one group. All-damage and bullet-damage multipliers add within a later group; the groups multiply each other. Flat level damage comes before scaling, while a separate flat bullet modifier comes afterward. Different activation conditions do not automatically create separate arithmetic pools.

Still open. Range/NPC branches, inherited values and upgrade replacement are excluded from the simple calculator.

Active duration versus cooldown

Duration describes an effect's window; cooldown describes its reuse constraint. There may also be a cast delay or a separate buff duration. Dividing duration by cooldown does not establish real uptime when cast timing, interruptions or recharge rules are unknown.

Ability and item cooldown bonuses

The captured items distinguish ability-cooldown reduction from item-cooldown reduction. A number on one channel cannot automatically be applied to the other. Charges and the gap between uses add another timing layer, so one generic haste equation would leave out important behavior.

Still open. The universal combination formula, limits and final rounding are not established.

Range, radius & duration bonuses

Cast range limits where an effect can be placed or targeted. Radius describes its area. Duration describes how long it lasts. These have separate properties, even when an item affects more than one. Imbued or selected-ability effects also require the correct recipient.

Still open. These are configured bonuses, not proof that every ability scales or combines them identically.

Shots, bursts & sustained fire

Build-6698 fire-rate bonuses add; slows combine through remaining fractions and subtract from them. Positive stats shorten the firing interval reciprocally, but negative stats lengthen it linearly. The ordinary default minimum stat is −50. Burst spacing, magazines, reloads and missed pellets still affect sustained damage.

Still open. The minimum is configurable. The shortcut excludes cycle-percentage modifiers, inherited stats and gameplay-time scaling.

Falloff & critical hits

Weapon data distinguishes damage-falloff start and end ranges and critical-hit parameters. Range is therefore more than whether a crosshair can point at a target. A headshot indicator or a range warning is useful feedback, but not a complete calculation of final damage.

Still open. Interpolation, per-weapon critical rules and their order with mitigation remain incomplete.

Spread, recoil & aim

Aiming, bullet spread, recoil and projectile origin are separate parts of firing. Zoom state and weapon-specific settings can change the presentation or firing context. A tidier crosshair is not evidence that server-side spread has changed.

Projectile delivery & collision

A projectile can carry damage, apply a modifier or create an area effect. Travel speed, collision and targeting are distinct from the damage type and amount. A visible impact is not enough to tell whether direct damage, a later tick, or both caused the health change.

Still open. That historical example is not a claim about every September projectile.

Ricochet & secondary targets

A bounced shot needs target eligibility, a search radius and a damage setting. The original target and a secondary target are not interchangeable. The captured Ricochet definition excludes invisible targets and allows small deployables; other chaining effects may use different filters.

Still open. The tooltip-only count is not independent proof of the runtime target-selection loop.

Melee & parry are distinct actions

Heroes bind a melee ability separately from their primary weapon. Melee damage, reach, timing and a parry interaction must be read from the appropriate action, not inferred from gun damage. Movement also has separate settings for a parry-cancel transition.

Still open. These transition settings are not the parry hit window or a universal melee timing formula.

Use the ability actually equipped

A hero's slot binding identifies which definition belongs to that slot. Internal names, alternate versions and unused abilities can coexist in the files. Finding a definition with an impressive effect does not establish that the playable hero uses it.

A coefficient is not the whole formula

Scaling can reference one stat, several stats, a curve, healing rules or a specialized ability function. A coefficient alone does not settle the operation order, limits or rounding. The general scale-function implementations have not all been reconstructed, so this guide does not turn every coefficient into a damage formula.

Upgrade bonuses have a target

An upgrade can change damage, charges, duration or another property rather than multiplying the whole ability. It may change a coefficient as well as a base value. Read the upgraded property and its operation before applying the bonus to an entire tooltip.

Still open. The historical coefficients should not be reused as current balance values.

Charges, recharge & use spacing

Charge count describes how many uses can be stored. Recharge describes how uses return. A separate between-charge cooldown can limit consecutive activations. A full stock therefore does not necessarily allow every use at once, and a recharge bonus is not the same as adding a charge.

Cast delay, channel & interruption

Abilities can enable different states before, during and after a cast, and declare states that interrupt them. A channel does not automatically grant immunity. Movement permissions, shooting restrictions and interruption rules need to be checked independently.

Damage over time

A ticked effect has an amount, a cadence, a lifetime and sometimes stacks. Those are separate variables. In the earlier Shiv code path, a tick multiplies evaluated bleed DPS per stack by the tick scalar and stack count, then sends that amount through the damage pipeline.

Still open. Do not assume every effect applies an immediate first tick or shares Shiv's refresh behavior.

Speed and stamina are separate

Movement speed changes travel; stamina supplies a resource for movement actions; stamina recovery governs replenishment. Air-movement bonuses are another property. Combining all of these into one mobility number hides their different uses and conditions.

Ground dash versus air dash

Dash data separates ground and air behavior, including acceleration, drag, end velocity and interruption. The velocity left after an action matters as well as its starting speed. A distance seen in one context does not establish the distance in another.

Dash-jump timing

The jump definition has separate start and end timing parameters for a dash-jump, plus a distance parameter. These describe an intended transition window, not a promise that every input at those times succeeds regardless of state, collision or latency.

Still open. These are configuration values, not measured travel distances.

Slides, wall jumps & recovery

Slide entry and exit have their own timing settings. Jump data also declares a hidden wall-jump stamina-regeneration modifier. The action and its temporary recovery effect should be considered separately; a hidden modifier can matter without being a visible ability icon.

Still open. The complete application and stacking behavior is not established by the declaration.

Ziplines, boosts & teleporters

Zipline traversal, boosts and teleporters have their own world and movement settings. Camera-facing direction and movement direction are distinct attachment inputs in the earlier survey. Travel effects and the camera that follows them should not be treated as the same mechanic.

Still open. Static route placements do not prove when a route is active in a live match.

Stun, sleep, immobilize & silence

The data names separate control states rather than one universal crowd-control switch. An action's interrupting-state mask determines which restrictions it checks. Preventing movement, interrupting an ability and preventing shooting are different questions—even when one effect does several of them.

Status Resistance

Status Resistance is a separate modifier property from Bullet and Spirit Resistance. An effect can grant one, several or none of them. Its presence does not by itself provide a complete duration-reduction equation for every stun, slow or other debuff.

Still open. Universal duration scaling, caps and stacking are not established.

Stacks versus separate instances

A modifier can have a stack counter, a maximum and attributes allowing multiple instances. These describe different ways an effect may accumulate. A visible stack count alone does not prove whether repeated applications refresh one timer, add another instance or extend a shared duration.

Refresh, expiration & cleanup

A short-lived child modifier can be kept alive by an aura refreshing it. Leaving the area stops eligibility for refresh, rather than necessarily deleting the effect on the exact boundary-crossing frame. Persistent and timed modifiers require different lifetime handling.

Cleanse, suppression & prevention

Removing an existing debuff, suppressing an effect while a state lasts and preventing a new application are different operations. An active item can also grant a heal or a movement buff independently of its removal behavior. An item's name is not a complete list of what it removes.

Still open. A complete dispel eligibility and immunity interaction matrix is not available.

Visible does not mean targetable

Visibility state, target filters, line-of-sight checks and damageability gates belong to different systems. An entity can be drawn by the client without satisfying an ability's target rules. Conversely, a legal target still has to pass the relevant damage or effect application checks.

Friendly, enemy & unit filters

Targeting distinguishes team relationships and unit classes such as heroes, troopers, bosses, minions, props and neutrals. A hero-targeted heal and a bouncing weapon effect therefore need different candidate sets. Being inside the area is not enough when the type filter excludes you.

Invisibility & detection exceptions

An explicit no-invisible-target flag is evidence about that effect's targeting rules. It is not a global statement that invisible entities cannot be damaged, revealed or affected by an area. Detection and application rules must be checked independently.

Range, radius, cone & height

A range chooses reach; a radius chooses spread; cones add angle; cylinders add vertical bounds. Ground previews can omit information that matters in a three-dimensional fight. The effect's actual target shape should be kept separate from the artwork that illustrates it.

Collision & line of sight

Camera occlusion checks, projectile collision and target visibility serve different purposes. A camera repositioning around an obstacle does not establish a clear firing path. Likewise, a targeting preview is not proof that a later projectile will avoid world geometry.

Rift capture speed

The reconstructed Rift capture path uses spawn-selected bias to favor one side and hinder the other. Its capture timing is separate from the live-gap resistance calculation: changing the current gap does not mean every spawn-time decision is recomputed.

Rift Trooper count & cadence

The stored spawn bias determines the ordinary Rift Trooper count, from five to fourteen. Spawning is paced rather than treated as one simultaneous award. A Rift modifier and a stored Rift identity connect the Troopers to the event that produced them.

Still open. This is the reconstructed ordinary branch; alternative selector behavior is discussed in the economy guide.

Rift Troopers have tiered stats

The captured Rift modifier has tier arrays rather than one stat package for every wave. Health and damage settings, resistance and model scale are separate fields. A larger model is not a formula for health or collision size.

Still open. Array values alone do not establish the final health or damage evaluator.

Rejuvenator lifetime & respawn settings

The Rejuvenator has separate drop, warning, buff and respawn settings. Its buff lifetime is not the same as the time needed for the object to drop. Respawn modifiers also need to be distinguished from the underlying respawn timer.

Still open. These settings do not by themselves settle tier selection or full respawn-timer arithmetic.

Troopers, neutrals & structures

Lane units, neutral camps, bosses and defensive structures should not share an assumed health, attack, targeting or lifecycle rule. The world catalog separates NPC units from other entities. A definition is evidence of a configured unit, not a guarantee that it spawns in every mode.

Breakables, explosions & loot

Props, explosion types and loot tables are separate data families. Breaking a prop does not make every listed loot entry certain; an explosion's visual presentation is not its entire damage or targeting rule. Conditions, selection and runtime activation still matter.

Still open. Loot probabilities and complete runtime interaction rules are not reconstructed.

Game modes, death & respawn

A lethal-damage path and a respawn schedule are separate systems. Mode-specific timing arrays should not be applied to every queue. Likewise, an objective or route found in map data does not prove that its activation conditions are met in a particular match.

Still open. The complete Normal-match respawn formula and objective lifecycle coverage remain open.

Hero stats & progression

Hero definitions contain their own base statistics, weapon links and ability slots. Growth, ability upgrades and purchased stats are different sources of change. An internal hero entry can be a template or development character, so the file count is not the playable roster count.

Summons & deployables

A summoned unit or deployable is an entity with its own lifetime and targeting category. Ownership connects it to a hero but does not imply that it inherits every hero stat, item proc or protection. Small-deployable exceptions can be explicitly allowed by an effect.

Still open. Universal summon inheritance, proc sharing and despawn rules are not established.

Grey Talon's guided bird

The Talon survey separates the bird-related ability and entity evidence from camera and steering controls. That distinction matters when reading a replay: following a guided entity is not the same as observing the hero's ordinary weapon view.

A dramatic ultimate is not immunity

In the earlier Mina investigation, the bound Batswarm channel listed movement and shooting restrictions but no declared defensive state of the kinds inspected. That was not a proof that every possible incoming-damage interaction had been eliminated or that a later patch could not change the ability.

Still open. Absence of a defensive declaration is not a complete runtime proof of vulnerability.

Zoom, field of view & sensitivity

Zoom state, zoom timing, field of view and zoom sensitivity are separately represented. Camera changes can alter how fast motion appears or how much of the world is visible without themselves proving a change to weapon damage, projectile spread or target eligibility.

Movement and ability cameras

Dash, zipline boost and individual abilities can declare camera sequences or overrides. These control presentation during a state or action. A change in camera angle or distance should not be used on its own to infer an equivalent change in the hero's hitbox or speed.

Crosshairs & hit markers

The crosshair has customization, clipping, range-warning and hit-marker settings. These describe visual feedback and can be weapon-specific. They do not expose the complete resistance calculation or prove the exact amount of health removed by an individual hit.

Previews, effects & audio cues

Ability previews, damage indicators, healing sounds and other feedback help communicate events. Their assets and timing are not the underlying combat rule. Cosmetic definitions, sound tags, decals and lighting were catalogued too, but are not counted as additional damage or movement mechanics.

Pings & position communication

Ping-wheel messages, target information and position-related communication are represented separately from aiming and damage. A map marker communicates a location or request; it is not itself proof that a unit remains there or is currently visible and targetable.

Four spectator viewpoints

The earlier client survey names four spectator modes: directed viewing, free camera, hero chase and player view. The viewpoint changes what the camera follows; it does not make a spectator camera interchangeable with the player's exact input or the server's hit calculation.

Observer targets & camera behavior

Observer state tracks a target separately from camera parameters and the currently observed team. Automatic camera alignment, roaming speed and chase distance concern how the view is presented. A camera motion in a replay should not automatically be attributed to a player's aim input.

Replays are observations, not omniscience

A replay or broadcast can expose an entity state without revealing the complete decision that produced it. Missing updates are not zero values. A partial broadcast is also different from a complete demo, and a displayed build number is not an attestation of the remote executable.