Jump to content

[V6.29.0 - ground combat] when a soldier is crouching, previewing accuracy of move-then-attack by holding down shift key shows the wrong hit chance - as if the soldier will still be crouching after they move


Recommended Posts

Posted (edited)

Description:

During tactical combat, when holding down the shift key to preview move-then-attack from a soldier whose is currently crouching, when displaying hit chances & accuracy debuffs, the previewed hit chances appears not to model that the soldier will actually be standing at the end of the move when they attack, and will no longer be crouching.
 

What happened:

Please see attached recording (recorded today from v6.29.0) for a concrete example.

In this example I'm holding down shift to preview options for lobbing a grenade around a corner after moving the active solider up behind the shield soldier.

What happened when I preview move-then-attack:
- preview shows a red "-20%" accuracy debuff on the crouching shield soldier
- the previewed chances to land a grenade in the tile around the corner & the tile one back is 46% and 40% respectively

What happened when I actually execute the move only then preview the throw only:
- soldier moves to stand behind the crouching shield soldier
- the preview no longer shows the red "-20%" accuracy debuff to hit the crouching shield soldier
- the previewed chances to land a grenade in the tile around the corner & the tile one back is 57% & 50% respectively

Further info:

This example is taken from v6.29.0 and involves lobbing a grenade, but I see this issue consistently in every ground combat in v6.26.0 and v6.29.0 when previewing any move-then-attack to move a crouched soldier behind a crouched buddy, regardless of the weapon etc.

 

Speculation:

The move-then-attack preview appears to calculate hit chances & accuracy debuffs as if the soldier will still be crouching once they finish moving, i.e. the preview appears to combine the soldier's initial crouch state with their final position and facing when previewing the hit chance, rather than combining the soldier's final crouch state with their final position and facing.

Edited by fusion-waffle
copyedit
Posted
45 minutes ago, gG-Unknown said:

This issue  was fixed about  2 years ago, and here we go again.

Anyway, I see your vid is somewhat cropped, so I dont see the the right down corner table o chances.

Thank you for the background -- I only started playing since v6.26 but suspected this quirk might be an older issue / limitation of the preview logic.

Whoops, my mistake, yes it would have been clearer to include the bottom right table of hit modifiers. I can record a better example if that'd help, but I suspect this issue is easy to reproduce given that it happens every time.

Posted (edited)

I saw this issue again immediately in the campaign I am playing -- so here's a much clearer example including the details in the hit chance explanation box.

This time we're previewing move-then-shoot for crouched soldier with a shotgun. Again this is captured from v6.29.0.

 

When previewing the move-then-shoot to move behind a crouched buddy, the hit chance explanation:

* has a x0.80 multiplier (-20% debuff) for "intervening object" -- this is the crouched buddy. this seems incorrect. I'd expect there to be no intervening object penalty for a standing soldier adjacent to a crouching soldier.

* does not have any x1.1 multiplier for the crouch bonus. This is correct.

After separately executing the move, and then previewing the shot only without any move, the x0.80 multiplier for "intervening object" vanishes.

 

The shotgun hit chance improves from 36% x 3 to 45% x 3 when we compare what the move-then-shoot preview said vs the shoot-only preview after moving.

Edited by fusion-waffle
Posted
On 1/14/2026 at 4:32 PM, fusion-waffle said:

Description:

During tactical combat, when holding down the shift key to preview move-then-attack from a soldier whose is currently crouching, when displaying hit chances & accuracy debuffs, the previewed hit chances appears not to model that the soldier will actually be standing at the end of the move when they attack, and will no longer be crouching.
 

What happened:

Please see attached recording (recorded today from v6.29.0) for a concrete example.

In this example I'm holding down shift to preview options for lobbing a grenade around a corner after moving the active solider up behind the shield soldier.

What happened when I preview move-then-attack:
- preview shows a red "-20%" accuracy debuff on the crouching shield soldier
- the previewed chances to land a grenade in the tile around the corner & the tile one back is 46% and 40% respectively

What happened when I actually execute the move only then preview the throw only:
- soldier moves to stand behind the crouching shield soldier
- the preview no longer shows the red "-20%" accuracy debuff to hit the crouching shield soldier
- the previewed chances to land a grenade in the tile around the corner & the tile one back is 57% & 50% respectively

Further info:

This example is taken from v6.29.0 and involves lobbing a grenade, but I see this issue consistently in every ground combat in v6.26.0 and v6.29.0 when previewing any move-then-attack to move a crouched soldier behind a crouched buddy, regardless of the weapon etc.

 

Speculation:

The move-then-attack preview appears to calculate hit chances & accuracy debuffs as if the soldier will still be crouching once they finish moving, i.e. the preview appears to combine the soldier's initial crouch state with their final position and facing when previewing the hit chance, rather than combining the soldier's final crouch state with their final position and facing.

 

Thanks for the very detailed report! Yeah, it looks like having your soldier crouched affects the move attack preview's accuracy calculation, we'll get it fixed.

Posted (edited)
On 1/14/2026 at 11:54 AM, fusion-waffle said:

Thank you for the background -- I only started playing since v6.26 but suspected this quirk might be an older issue / limitation of the preview logic.

I  found it, reported it, several times, several times they try to fix, then  finally It was fixed. it happened about 2 years ago.  Now it  re-appeared again.  I do not test  every bug every week. But it happens to this team, that they re-introduce old bugs  again. Just to be clear mate :=]

Edited by gG-Unknown

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...