Abnormal behavior related to immortals and walls

[Hexereticdoom]

Hello, it's been a while since I logged in here...

I thought it appropriate to make the following bug being known, which I recently discovered playing vs CPU. I don't know if it's been reported before, so if it has, I apologize...

Well, the thing is, while playing a 3v3 game with Persians on the "Fortress" scenario, I had the idea to garrison the walls of my base with several units of immortals, in their 'archer' mode. I defended myself against enemy invasions in that way for some time, until I decided to attack one of the enemy bases... The thing is, I make all the immortals in my base switch to melee mode, while they were still up on the walls, and in the most unexpected way -once ungarrisoned- they remain "floating" in the air, as if they were still perched on an invisible wall... I tried switching them back to their long-range mode, but they were still hovering in the air like dragonflies...

Obviously this shouldn't happen, so I imagine the developers should fix the issue accordingly for the next release...

That's all for now, and thank you for your attention. In case you need more information, please let me know... See you!

Edited 36 minutes ago by Hexereticdoom

[Thalatta]

On 06/09/2026 at 3:31 PM, Thalatta said:

you could make ranged infantry fly, and have coherent tactics and balanced gameplay, but that's not what's stated as the vision for this game

And here I was just 3 days ago thinking this was not how the game was supposed to be

I can confirm, right now I was having some fun with my flying ranged infantry.

 

1 hour ago, Hexereticdoom said:

I tried switching them back to their long-range mode, but they were still hovering in the air like dragonflies...

You bring them down by, while on ranged mode, posting them again on the walls, and then unposting them.

[Hexereticdoom]

15 hours ago, Thalatta said:

You bring them down by, while on ranged mode, posting them again on the walls, and then unposting them.

Thanks, I'll keep that in mind for next time!

In any case, hopefully this little glitch gets fixed by release 29, or maybe a possible 28.1 patch...