Warhounds Ballistics, RNG, and Line-of-Sight Guide

Quick Answer

The current retail Steam page advertises one explicit no-point-blank-miss condition: flank plus close distance can produce a 100% hit chance. Both conditions matter; this does not mean every close-range attack is guaranteed or that Warhounds has no RNG.

Outside that advertised situation, Warhounds uses probability. An official pre-release technical explainer describes independent hit chances per bullet, variable damage, critical hits, and grazes; exact retail formulas still require in-game verification.

Read the labeled modifiers before spending AP. Our October 15, 2026 Distant Smoke test on SEASONED recorded how Aiming changed the same target’s preview and how two different shots both reached 55% through different range and cover modifiers. These are examples from BUILD 1.0.22(3313), not a reconstruction of the complete hit-chance formula.

Crow Aiming: compare the same target before and after

Aiming improved the next shot’s preview, then its bonus disappeared after that shot. Crow kept the same position and targeted the same Rookie throughout this comparison with his Upgraded Stylet Sniper Rifle:

Checkpoint	Precision	Crit	Modifier change	Evidence
Before Aiming	67%	26%	Accuracy 90, Range −8, Cover −15	Baseline
After activating Aiming	87%	36%	Added Skill bonus +20	Aimed preview
After firing, before a follow-up	67%	26%	Skill bonus no longer listed	Follow-up preview

Activating Aiming spent 1 AP and no ammunition. The preview gained 20 percentage points of Precision and 10 percentage points of Crit; its Damage 3–6 prediction did not change. The shot hit, but one hit cannot validate an 87% success rate or establish a critical-hit result.

For the third checkpoint, MayB’s Go, Go, Go! gave Crow another AP without ending the turn. Reopening the same target showed the original values again. Recheck bonuses before a follow-up shot, even when someone restores your AP. The Aiming sequence does not test cross-turn expiry, full cooldowns or interaction with Overwatch.

Read range and cover separately from the total percentage

The same total can hide different problems. Two Argument Shotgun previews from our session both displayed 55%:

Example	Accuracy	Range	Flanked	Cover	Precision
Distant, flanked Rookie	+80	−50	+25	Not listed	55%
Later shot after moving	+80	+5	Not listed	−30	55%

The first preview’s large penalty came from Range. The second had a positive Range modifier but a Cover penalty. These were different positions and targets, so the examples explain how to read the display; they do not define a fixed distance threshold or cover penalty for every shot.

To compare a move with your current shot:

1. Read the current target card and the selected target’s modifier panel.
2. Hover a destination and inspect both the route cost and the predicted shot from there.
3. After moving, inspect the target again. Do not confuse a further hovered destination’s percentage with the shot from your new position.

In the move preview, Fidget’s current card was 10% and the proposed 1 AP destination predicted 55%. After the move, his current card read 55%; the simultaneously hovered next tile’s 100% was still only a future-position prediction.

An earlier Crow shot showed 56% = 90 Accuracy − 4 Range − 30 Cover, then produced a visible Miss (preview, result). That is one observed outcome, not a reason to label 56% shots unreliable or infer hidden streak behavior.

Evidence status and the zero-RNG correction

• Released 1.0: The current Steam store describes lines of fire, flank angles, destructible cover, high ground, and “less fake RNG, more true ballistics.” It also explicitly states that flank plus close distance can produce 100% hit chance.
• Pre-release official explainer (historical — needs retail retest): The January 23, 2026 shooting article describes independent hit chances per bullet, an accuracy penalty on burst bullets after the first, critical hits versus grazes, and grazes or minimum possible damage on hits against high cover. These rules explain the design as officially documented before release, but exact retail formulas still need in-game verification against the current build.
• Demo-era: Distance penalties, armor interactions, interface percentages, and other exact values from older builds are not assumed current.
• Major Update 1.0.2: The release note improves the shot-accuracy window and lists a line-of-sight accuracy-calculation fix. It does not publish the formula or prove every accuracy edge case was independently re-tested here.
• Own October 15 playtest: The examples above verify selected preview changes, AP costs and individual outcomes. Bullet independence, graze probability, the complete range curve and line-of-sight edge cases remain untested.
• Source correction: The store’s “no point-blank misses” line is conditional, not universal. The current store emphasizes reducing unfair randomness, while the official pre-release explainer explicitly documents per-bullet hit probabilities and critical/graze outcome mechanics—RNG is part of the shooting model as described. Exact retail formulas should be retested in game.

When the store says 100% hit chance

The retail wording combines flanking with closing distance. Preserve that conjunction when applying the claim:

1. confirm that the target is actually flanked in the live attack preview;
2. close to the point-blank situation represented by the current interface;
3. verify that the preview displays 100% before committing;
4. do not extrapolate the result to a front-facing target, a longer shot, another weapon state, or an obstructed line.

The store does not publish the exact distance threshold, flank-angle threshold, weapon exceptions, cover interaction, or current calculation formula. Those fields remain hands-on test items. The safe editorial statement is “flank plus close distance can produce 100%,” not “all close shots hit.”

Read an attack as several events

A burst should not be treated as one all-or-nothing coin flip. If the current interface shows a chance per bullet, each projectile resolves against that probability. The number shown is still a probability, not a forecast of exactly how many rounds will land.

After a hit, damage may vary. Critical hits and grazes add further outcome ranges. This explains how two attacks with similar previews can produce different results without implying hidden cheating.

Do not calculate exact expected damage from an old video. Use the live preview, weapon information, target state, and current patch.

Improve line of fire before spending the attack

The official store makes geometry central to combat. Before firing:

1. Check whether allies, terrain, or cover obstruct the intended lane.
2. Compare a small reposition with the current shot.
3. Look for a flank angle that reduces the target’s protection.
4. Consider elevation if it opens a cleaner line.
5. Decide where the operative ends if the target survives.

A move that improves accuracy but strands the shooter can still be a poor trade. Position should improve both the attack and the next defensive state.

Plan around failure, not just average damage

Suppose an attack is likely to succeed but not guaranteed. A robust plan answers these questions before the trigger pull:

• Can another operative finish or suppress the same threat?
• Will the shooter remain protected?
• Does missing expose the objective carrier?
• Is smoke or another utility tool better than accepting the shot?
• Can the squad disengage or extract if the turn deteriorates?

This is the main difference between probability management and superstition. The player controls preparation and consequences, not the random result itself.

Avoid common probability mistakes

• “A high chance must hit.” Even a high displayed value leaves a miss chance.
• “Several misses make the next shot due.” Independent rolls do not create a guarantee.
• “Every bullet in a burst shares one roll.” Official wording describes independent chances per bullet.
• “Less fake RNG means no RNG.” Random damage, critical hits, and grazes directly contradict that reading.
• “The best percentage is always the best action.” Objective safety, cover, and fallback options also matter.

Pair this page with destructible cover and elevation and the conditional overwatch guide.

Frequently asked questions

Does point-blank range always guarantee a hit?

No universal guarantee is documented. The current Steam claim requires both a flank and close distance, and the live preview should still be checked for the actual attack.

Can a 90% attack miss?

Yes. Any displayed probability below 100% includes failure, and a multi-bullet attack can produce a mix of hits and misses.

Does Warhounds secretly help after a miss streak?

The sources reviewed do not support claiming hidden streak assistance. Use the documented per-bullet probabilities and the current in-game preview rather than assuming that a past miss changes the next roll.

Are critical hits deterministic?

Public combat descriptions include critical hits and grazes as possible outcomes, but this page does not publish an unverified formula. Check the live interface and current weapon details.