The Anglian thing is in the latest patch notes, so it isn't a bug. If this was intentional, it is the dumbest design decision I think I've ever seen CA make. Problem is that East Anglia is the most obvious target for Wessex right out of the gate. I think this is most certainly a bug as the previous event mission has still yet to appear in the game thus making East Anglia un-attackable. As usual CA never fails to dissapoint me.ĮDIT: Upon further investigation I've found that I can declare war on most if not outright all settlements EXCEPT for East Anglia. So I decided that today would probably be the best day to come back and give it a try. Originally posted by zzman305:I haven't played ToB since its first week because I wanted to wait for it to be patched and expanded more. So much for 'fixing' the game CA, my first playthrough in 3 months and I've already abandoned my campaign due to bugs/boredom.ĮDIT: Upon further investigation I've found that I can declare war on most if not outright all settlements EXCEPT for East Anglia. I thought this game was Total War, not Total farm property management. If I remember correctly, when I played the game on day one an event allowing me to declare war on East Anglia appeared fairly soon, but I'm pushing my tenth turn and the game absolutely refuses to let me declare war on them. But no matter what I try I can't declare war on East Anglia. Maybe in that collage of patch notes I missed something but has the ability to declare war on another faction been entirely removed? I started my Wessex campaign like normal, beat some rebels, invested in some farms, built a small half-stack army and then marched it to the Thames to take London. As usual CA never fails to dissapoint me. I haven't played ToB since its first week because I wanted to wait for it to be patched and expanded more.
0 kommentar(er)
