This would include stuff like name, strength, satisfaction, (construction/units maybe?).

Could even go in the status overlay.

Also make it so pressing escape removes one layer of the overlay.

Show off how cool the game looks. Good first issue I suppose

If an AI user is eliminated by losing all their settlements, alert the user.

If an AI is close to a victory (not necessarily the same 'close' definition as in #2), they should attempt to win the game via that victory. Some complex logic may be required here.

While it does stop you most of the time if you don't have a blessing or construction, it is still weird that you would be able to end a turn while being notified that your settlement has levelled up.

The game just continues on, and the player even receives an elimination message like an AI player would.

Each faction should have one or two units that replace the standard units and provide some difference. Shouldn't be anything major, just an extra stamina point or an extra 5 power/health.

Currently, a settlement is only ever under siege by a single unit. This causes issues because when the settlement is taken, only the first unit is marked as no longer sieging.

As an expansion to this, multiple units placing a settlement under siege should quicken the loss of strength of the settlement.

Currently, the space key iterates through all of the player's units. In cases where a player may have upwards of 20 units, it would be better if they could iterate specifically through the units that still have stamina.

The M key makes the most sense for this. Would need to be added to the controls page.

When there are no movable units, the key does nothing.

Basically, the AI players shouldn't just stand idly by while other players win, including the human player.

Currently the AI players always deploy their units in the same location (one quad below their settlement), even if other players already have a unit there.
Logically can follow the first/second/third resort logic already in movemaker.py.

Probably in the home directory, this will make packaging work, hopefully. Could be somewhat difficult, though.

Essentially, if a unit investigates a relic and gets upkeep reduced to 0, it will affect all future recruitments of that unit, meaning they will be free. Let's not have this.

You need VLC to run the game. Mention that in the root README.

Also link to it in the README

The groundwork has already been laid for this: Settlements have a List of Quads, not just a single Quad. The calculation aspect of this also may already be implicitly supported.

Maybe restrict it to one per level?

Essentially, if an AI unit places another settlement under siege, and a unit from the settlement under siege is deployed to attack that AI unit, the AI unit will just continue its siege and ignore the deployed unit. This becomes problematic as it will certainly be killed. AI units should either attack back or move away when they are at medium to low health, and placing another settlement under siege.

(Thanks to Ollie)

Should also check that other keys can't be used before the tutorial is over.

If any player (user or AI) is 'close' to a victory, alert the user.

Close can be defined as the following:
Elimination: all settlements but one.
Jubilation: has achieved 100% satisfaction in 5 settlements
Gluttony: reached level 10 in 8 settlements
Affluence: accumulated 75k wealth
Vigour: has begun constructing the holy sanctum
Serendipity: has researched two of the three pieces of ardour

Probably the easiest way to do this is extract out the drawing functionality into a separate class.

Since the original unit plans were added, more blessings have been added.
Make some new higher-powered unit plans based on some of the newer, more expensive blessings.

Note: if you add quite a few, the Units part of the wiki will need to change to have the same 'boundaries' functionality that the blessings and improvements parts have.

Rather than be forced to continually pick new things, add some new constructions that yield some resource or another every turn.

Every 10 turns, probably.

If you're focused on a particular settlement, you may not realise that it has been placed under siege. Could involve changing the name colour or the strength icon colour.

• There should be a list of crusades for players to do for some reward (usually wealth).
• Can be faction or relic based.
• Add a crusades menu as well.
• Crusades should be unlockable based on improvements and/or blessings.

• Could involve night time, seasonal changes, disasters, etc.
• Open to discussion on this.

Currently nights last for a random number between 5 and 25 turns. If you are doing a lot on your turn, this can result in a long time between climatic changes.

Acceptance Criteria:

• Reduce the maximum night length from 25 to 20 turns.

Currently all AI players are effectively expansionist, so it would be good to change this so there are Expansionist, Neutral, and Hermit AIs. Probably just use existing functionality for Expansionist, settle at level 5 for Neutral and level 10 for Hermit.

Seems like the AI players tend to let their settlements descend into squalor. For example, in a game I just played, I had six settlements with satisfactions of 49, 73, 55, 58, 52, and 56. The other 5 AI players had settlements with satisfactions of 0, 2, 0, 16, 0, 22, 54, and 0. Clearly this will affect their ability to compete.

This could just be as easy as mandating the improvement that yields the most satisfaction when the settlement reaches below 40, or something.

Rather than having to move each unit individually, a transport unit would be useful to move multiple units in one. This would function similarly to a garrison, and would be unlocked mid-late game, and have fairly significant stamina. This would likely require large code changes. Deployment would also function in the same way as settlements.

Credit: Andrew

This has primarily been raised due to the Warrior vs Warrior cycle against an AI where you attack each other and eventually both units die on the same turn. Would be better if this didn't occur.

When pressing an arrow key while holding down the CTRL key, move the map by five tiles in the specified direction instead of the standard one. Use the same clamping logic that exists for standard panning.

Credit: Andrew

• There should be special tiles all over the map that house relics that may be explored by units.
• Players get a small reward for exploring (usually wealth).

Just so you don't have to make the decision if you don't want to.

When the user presses enter to save, add a new overlay prompting the user to enter a save name, read the input, and use that as the name for the save file.

This will likely be difficult, and may not even be possible with Pyxel's input reading.

Can be a bit annoying sometimes to accidentally select new game and not be able to return to the main menu.

Should be easy enough to do, can be based off other pages, e.g. Wiki.

• Update documentation to reflect that 3.10 is required.
• Use pattern matching (match) where if-elif-else chains are currently employed (where switch statements would usually be used).
• Replace typing.Union type hints with the new | type operator.
• Deal with any other warnings that may appear.

There should be some built-in VLC repeat or something that fixes this.

This would probably work by having some turn boundaries that would bump all newly-generated heathens to an upgraded unit plan. E.g. Every 25 turns, the next heathen unit plan is used. Would require more heathen unit plans in the catalogue, but potentially the existing get heathen method could be altered to take the current turn and return the correct unit. A fair upgrade could be +10 power and health every 25 turns.

There should probably be some advantage for units that are attacking from mountains, and a disadvantage for defending from the sea. Open to ideas on how this should work.
Credit: @jamesgiu and Andrew

Move further than their stamina allows, and auto-move the units on the next turn.

Some units should heal units rather than attack them when clicking on them while adjacent. This would involve adding a new property to the UnitPlan class, as well as a new outline on the map for healable units. There should also be different levels of healer units, for each tier.

Credit: Andrew

• Convert each colour to a faction
• Base factions mostly around one particular category (e.g. zeal, harvest, etc.)
• Each faction will have a bonus.
• Add a factions section to the wiki

Traceback (most recent call last): File "/home/suttono/tmp/microcosm/[game.py](http://game.py/)", line 182, in on_update self.board.selected_settlement.current_work = Construction(self.board.overlay.selected_construction) AttributeError: 'NoneType' object has no attribute 'current_work'
Happened when Ollie was choosing a construction for his settlement and he clicked away before choosing, deselecting his settlement.

I've noticed a similar thing happening when you're choosing a blessing and you press shift before choosing one, and the standard overlay disappears.

Seems like there are a few deselections that can occur in the overlay at the wrong times.

So that people know where their units are.

Simple change, once a save has gone through, change the text in the pause menu to:
Saved ✅ (saved should be green too)
This should reset every time the pause menu is reopened.