In Dicevaders, matching the enemy defense target is intended to count as a successful clear. However, players have reported losing a heart during encounters where their total attack displayed the exact same number as the required defense threshold.

If you hit what appeared to be an exact tie—such as 500 attack against 500 defense—and still suffered a penalty, you are not alone. Here is an explanation of how the game treats matching values, what forum discussions have said about the issue, and why visual rounding might be costing you hearts.

Intended Mechanics: Does Attack Equal Defense Count as a Pass?

Under normal game design, meeting a defense target in Dicevaders should pass the encounter. On the official Steam community forums, when a player reported losing a heart after reaching 500 attack against 500 defense, a reply stated:

"Sounds like a bug, should be a pass! will take a look"

According to that reply, hitting the required defense threshold should be a pass. If your run penalizes you when your attack exactly matches defense, the game is not behaving as intended.

Why Do Players Lose on Matching Numbers?

While forum discussions point to a bug, they also highlight a likely technical cause behind the failure: hidden decimal rounding in attack calculations.

In Dicevaders, various units and abilities alter attack through percentage-based scaling. For instance, a player noted using the Warped Pixie, a unit that gets 3% extra attack on move. Percentage increases frequently produce fractional values rather than whole numbers.

When combat resolves:

  • The user interface often rounds displayed numbers up to the nearest whole integer.
  • A true attack value of 499.9 may display on screen as 500.
  • If the game backend checks whether true attack is strictly greater than or equal to defense, 499.9 falls short of 500.
  • As a result, the game registers an encounter failure despite the visual display showing a match.

Until an update resolves floating-point rounding or tie-breaker evaluation, relying on an exact visual match carries a risk of failure if percentage modifiers are active on your board.

How Combat Scoring Functions in Dicevaders

Understanding how Dicevaders calculates your damage output helps prevent close calls where rounding issues can occur.

Combat in Dicevaders relies on a turn-based grid where alien units are organized into columns beneath a row of rolled dice:

  • Column Activation: Units only contribute their attack when their specific column's die is scored. An empty column generates zero damage, regardless of die value.
  • Base Formula: A column's damage equals the combined strength of all units in that column multiplied by the scored die value.
  • Molt Multipliers: Molt acts as an end-of-turn multiplier that scales total damage across all scored columns. Stacking molt artifacts can push modest rolls into high-damage spikes.
  • Dice Manipulation: Mechanics like Budge (+1 or -1 to a die face) and Chrono (rerolling dice or shop choices) allow you to aim for pairs and triples that trigger additional payoffs.

Because units like Martian gain strength from spent resources (15 strength per budge or chrono used), tracking your additive strength versus percentage modifiers helps you gauge whether your attack total is a clean integer or an approximation.

Failure Penalties in Boss and Pilot Encounters

Failing to meet the target defense—whether due to falling short or running into the tie-score bug—has immediate gameplay consequences:

  • Heart Depletion: Failing a combat target drains one heart.
  • Extra Turn Retry: Losing a heart against an act-ending Pilot grants an extra turn to hit the target score.
  • Run Over: If you run out of hearts, the invasion ends.

To protect your run from fractional rounding losses, avoid aiming for exact defense thresholds when using percentage-scaling units. Banking an extra Budge or using Chrono to push your scored dice into a clear surplus ensures your true attack safely exceeds target defense.

Frequently Asked Questions

Does attack equal defense win the round in Dicevaders?

According to forum replies on the Steam community, matching the target defense should be a pass. If your run registered a loss on equal values, it is treated as a bug.

Why did I lose a heart at 500 attack vs 500 defense?

This issue typically happens when percentage-based buffs create hidden decimal values (such as 499.9 attack). The user interface rounds the number visually to 500, but the underlying check evaluates the score as lower than the 500 defense requirement.

How can I avoid losing to the attack equals defense bug?

Whenever possible, aim to exceed the target defense by at least several points. Using Budge to adjust a die or leveraging Molt multipliers will push your score safely past the target threshold, eliminating the risk of fractional rounding errors.