Potential bug - Hayastan Imperial Seat

I am not 100% sure if this is a bug or not, but here it is:

The description of the Hai Imperial Seat says that this type of government can be built only in Armavir and one or two other important cities.

After 400+ turns I finally secured Babylon and triggered the culture change - from Eastern Tribal to Eastern Imperial. At this point I have 34 provinces, of which 3 are Allied Democracies. The option to change government also appeared - in Armavir and across all other non-allied provinces. I figured that the Imperial Seat provides excellent military units, so why not try to build it across all provinces. After spending some 240,000 mnai I did build an Imperial Seat in 30 provinces.

The question is, why the description of the Imperial Seat says it can be built only in two or three provinces, when in fact it can be done across the board? Is the description wrong or the algorithm?

Cheers,
Nick
P.S. By the way, I have played 400+ turns and the game is rock solid - virtually no crashes. I am playing on a business laptop which is 10 years old. Good work!

The Hayasdan govs have been reworked in v2.35, so this issue may not exist anymore. Still, I'll post it for internal review, just to be sure.

Good to hear that you're seeing excellent stability. Just curious - what's the O/S?

Originally Posted by Kull

The Hayasdan govs have been reworked in v2.35, so this issue may not exist anymore. Still, I'll post it for internal review, just to be sure.

Good to hear that you're seeing excellent stability. Just curious - what's the O/S?

The operating system is Windows8.1 N. I installed it about an year ago. Regarding the hardware, neither the processor, nor the ram or video are anything special.

I had one campaign which was plagued with crashes - also Hayastan. However, after I allowed for some windows updates everything started ticking and haven't had any problem since.

There was an error in the script that checks whether or not you've built a "second capital", which has recently been corrected.

bovi updated one of the checking tools, and it now reviews the campaign_script and picks up all sorts of things, which we've subsequently fixed. So 2.35 should be even more stable than 2.3 was, now many of those innocuous errors are gone.