Upon researching grapeshot for the organ guns, organ guns fails to move a 'long' distance after [...]

:arrow_forward: GAME INFORMATION

  • GAME BUILD #: latest 04/08
  • OPERATING SYSTEM: Windows 11

:arrow_forward: ISSUE EXPERIENCED

Upon researching grapeshot for the organ guns, organ guns fails to move a ‘long’ distance AFTER they have attacked some enemy units at least once.

After that the following happens:

  1. you click on the minimap to move them: it bugs, they don’t move.
  2. you try to move them a long distance, they don’t
  3. you use attack move long distance; they don’t move
  4. The only way for you to move them is make them do small steps

:arrow_forward: FREQUENCY OF ISSUE

  • 100% of the time / matches I play (ALWAYS)

:arrow_forward: REPRODUCTION STEPS

Here’s the steps to reproduce the issue:

  1. Research GrapeShot
  2. Attack some units
  3. Organ guns fails to follow comand

:arrow_forward: EXPECTED RESULT

Organ guns not failing to move.


Kinda a big bug, probably related to the change in grapheshot that removed the time to change stance for the unit; this bug means that organ guns can’t be effectively used in games.


i experienced the exact same issue as you did on Windows 10.

  1. As for you, the bug does not occur for me for new organ guns fresh from the artillery foundry. In this state, the icons for the two artillery states (firong, moving) are still both visible.
  2. As soon as at least organ gun from the selected group switched to the firing mode, the bug affects all organ guns in the selected group. The icon for the moving state is no longer visible.
  3. The small steps you mentioned, i found out being exactly the width of the screen. As soon as all currently selected organ guns are within the current view, they can be moved to any point on the screen (excluding a point on the minimap).
  4. The bug does not affect other units in the selected group with mixed units, only organ guns. The non-bugged units leave the organ guns behind.
1 Like

yep, card is unusable.

There are now 3 (including this one) reports of - as it seems - the exact same issue:

We need a hotfix asap !!!


1 Like

please make a video of this, on my experience i will tell you that devs wont give a solution if there is not a video that show it clearier, probably will tell you “we couldn’t reproduce the problem”

https://www.youtube.com/watch?v=KUe_n0biCqQ i did it for you

1 Like

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.*

i made the same mistake that you, i didnt read ALWAYS ATTACH A PICTURE OR VIDEO.

1 Like

Thanks for the video!