Formation Bug

:play_button: GAME INFORMATION

  • GAME BUILD #: 100.19.18309.0
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 11

:play_button: ISSUE EXPERIENCED

Previously, it was possible to alter the shape of a formation of units by right clicking on different parts of the ground/map. For example, right clicking on a far waypoint would change the formation to have longer columns and narrower rows and clicking on a closer waypoint would give the formation wider rows and shorter columns. Players could use this to manipulate units (especially cavalry) to escape or attack faster. Now, the whole unit formation moves around like a box and isn’t as maneuverable.

:play_button: FREQUENCY OF ISSUE

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

:play_button: REPRODUCTION STEPS

Here’s the steps to reproduce the issue:

  1. Start any skirmish game

  2. Make 10-15 heavy cavalry units of the same type

  3. right click on different parts of the map and notice the formation is rigid

:play_button: EXPECTED RESULT

Formations should be more fluid as illustrated in this video guide

yeah this bug has been here since forever and it doesnt look like its going to be fixed anytime soon

Basically if you use the box formation it will overide the shifting of the other formations permanently

you misunderstood

the bug before this patch:

unit formations stay rigid AFTER switching to other formations and going back to default (eg melee for melee cav, volley for range inf)

the bug now:

unit formations are always rigid

ok that is a huge difference if this a bug it really needs to be noted or reverted

Do try it in game when you get the chance.

for instance if you take 12 hussar, the standard formation is 2 x 6

BEFORE : click far waypoint, it would switch to 6 x 2
NOW : click far waypoint, it switches to 3 x 4 (visibly blockier)

Also noticed this, especially terrible for cav. Virtually impossible to push tight bases which has unintended consequence of further buffing turtle or power spike civs that already do extremely well in this meta.

@FatTony thanks for the detailed report, the team is tracking this issue :slight_smile: