tedeviatings
Warlord
- Joined
- Jan 16, 2015
- Messages
- 126
Alright, I searched the forums and I didn't find any thread about this bug so here is mine.
Game version is 1.0.1.611
Description
There are variations of the bug, I'll limit myself to describing the most common version in more detail, just a couple of words on the variations.
The bug occurs when you're in city screen, trying to micromanage the tiles your city is working. What occasionally happens when you try to lock all your citizens unto specific tiles is that the last one will appear to be unlocked when you try to lock it on any workable tile belonging to the city. In fact upon removal of the apparent reasons for this behavior (as described later) this citizen will be redistributed by the governor / city-ai. So it really is not locked (else it couldn't be redistributed).
Therefore your last citizen is essentially unlockable unless you find and remove the underlying reason which is a bothersome task and not always easily possible.
There are variations of this bug with this happening to several of your citizens instead of just one. It's also possible that when you try to lock your last citizen it actually works but another citizen that was locked before is now unlocked.
Reproduction:
I can reproduce the situation I described as well as versions with more than one unlockable citizen. I'm not quite sure on how to reproduce the last variation mentioned.
That said I want to present one way to reliably reproduce the bug using two cities A and B that share at least one tile T (i.e. both cities can work tile T, just not at the same time).
To reproduce you go to city A's city screen and lock any citizen on tile T. If necessary assign the tile to city A first. Then you go to city B and reassign T to city B. Going back to city A's city screen you'll notice the citizen formerly locked on T has now been redistributed (since the tile does no longer belong to A). It is now unlockable, that is it is unlocked and you can not lock it on any tile that is not T. If you reassign T to city A and lock the citizen on T everything works again.
In general citizens seem to become unlockable whenever their tile becomes unworkable for whatever reason. That's my theory based on the fact that this also happens whenever enemy units block tiles on which citizens were locked before. I suspect the citizen might still be locked unto the unworkable tile and since it can't be locked to two tiles at once you can't relock it anywhere but the tile it's already locked on.
Why this is annoying:
Since I can't say with 100% certainty that this is not exactly working as intended I want to give an example of why this should be unwanted behavior.
Imagine you are trying to micromanage one of your cities. Imagine you have a lot of shared tiles with various other cities since you try to get a lot of cities into the limited space you have. Now you open the city screen and notice that one or two or more of your citizens are unlockable. You may have 10 shared tiles and don't know which ones your citizens are locked to. You can just try but after 3 or 4 unsuccessful reassignment of tiles you not only haven't succeeded, you have also potentially made other citizens in other cities unlockable. Of course you know which tiles those are locked to, but still. You have to go there and remeber which tile it was locked to and relock it on that tile - for every citizen you made unlockable. And god forbid this city has more than one unlockable citizen and you don't know where both of them come from...
Screenshots:
Overview:
Magan city view before any changes:
Ayaan city view before any changes:
Ayaan city view after changing shared tile (also locking citizen on that tile, that's not strictly necessary):
Magan city view after changes in Ayaan:
Trying to reassign the citizen in Magan:
Closing and reopening the city screen of Magan shows it really was not locked:
Game version is 1.0.1.611
Description
There are variations of the bug, I'll limit myself to describing the most common version in more detail, just a couple of words on the variations.
The bug occurs when you're in city screen, trying to micromanage the tiles your city is working. What occasionally happens when you try to lock all your citizens unto specific tiles is that the last one will appear to be unlocked when you try to lock it on any workable tile belonging to the city. In fact upon removal of the apparent reasons for this behavior (as described later) this citizen will be redistributed by the governor / city-ai. So it really is not locked (else it couldn't be redistributed).
Therefore your last citizen is essentially unlockable unless you find and remove the underlying reason which is a bothersome task and not always easily possible.
There are variations of this bug with this happening to several of your citizens instead of just one. It's also possible that when you try to lock your last citizen it actually works but another citizen that was locked before is now unlocked.
Reproduction:
I can reproduce the situation I described as well as versions with more than one unlockable citizen. I'm not quite sure on how to reproduce the last variation mentioned.
That said I want to present one way to reliably reproduce the bug using two cities A and B that share at least one tile T (i.e. both cities can work tile T, just not at the same time).
To reproduce you go to city A's city screen and lock any citizen on tile T. If necessary assign the tile to city A first. Then you go to city B and reassign T to city B. Going back to city A's city screen you'll notice the citizen formerly locked on T has now been redistributed (since the tile does no longer belong to A). It is now unlockable, that is it is unlocked and you can not lock it on any tile that is not T. If you reassign T to city A and lock the citizen on T everything works again.
In general citizens seem to become unlockable whenever their tile becomes unworkable for whatever reason. That's my theory based on the fact that this also happens whenever enemy units block tiles on which citizens were locked before. I suspect the citizen might still be locked unto the unworkable tile and since it can't be locked to two tiles at once you can't relock it anywhere but the tile it's already locked on.
Why this is annoying:
Since I can't say with 100% certainty that this is not exactly working as intended I want to give an example of why this should be unwanted behavior.
Imagine you are trying to micromanage one of your cities. Imagine you have a lot of shared tiles with various other cities since you try to get a lot of cities into the limited space you have. Now you open the city screen and notice that one or two or more of your citizens are unlockable. You may have 10 shared tiles and don't know which ones your citizens are locked to. You can just try but after 3 or 4 unsuccessful reassignment of tiles you not only haven't succeeded, you have also potentially made other citizens in other cities unlockable. Of course you know which tiles those are locked to, but still. You have to go there and remeber which tile it was locked to and relock it on that tile - for every citizen you made unlockable. And god forbid this city has more than one unlockable citizen and you don't know where both of them come from...
Screenshots:
Spoiler :
Overview:
Spoiler :

Magan city view before any changes:
Spoiler :

Ayaan city view before any changes:
Spoiler :

Ayaan city view after changing shared tile (also locking citizen on that tile, that's not strictly necessary):
Spoiler :

Magan city view after changes in Ayaan:
Spoiler :

Trying to reassign the citizen in Magan:
Spoiler :

Closing and reopening the city screen of Magan shows it really was not locked:
Spoiler :
