taimoorrana / risk Goto Github PK

If a country has already been clicked on once in a player's turn, the fortification dialog doesn't activate.

At the very end, we should aim to produce a document describing our architecture and provide a minimal diagram.

We should also run through important methods and add Doxygen headers to them. Note that our basic getters and setters don't need to be documented; their names alone are descriptive enough.

Search through the codebase!

From map editor. I would imagine we also need to check the result when browsing for files (MapEditor & PlayerNameDialog) as well.

My understanding is that the calculation is correct, we just can't accurately detect continent ownership yet.

We also need to integrate the phases it so that reinforcements are added at the start of every player's turn, instead of only once at the start of the game.

We may have a bug where we can attack disjointed countries per report from @adriannadiaz

User should be able to select their preferred save format at runtime (either via different buttons, or a drop-down in the file selection dialog)

• Add UI to show available cards
• New game phase slot to play cards
• Assign random cards to players upon conquest
• Give a player all of another player's cards after conquering their territory

We need to be able to:

• Have CPU players established at game start
• Have CPU player analyze the board and make a move
• Have CPU player AI type (i.e. their associated strategy class) changed at game play

Right now a player is not aware if he has a continent

(for @Elihar and @egimple)

I'll create an overview architecture diagram with our important classes again for explanatory purposes.

Logging needs to be available for all game events, and filterable by player or by phase.

After integration of @Taimoorrana1's code, we have to reimplement the bold typeface for the current player on the name decorator.

When a player is attacked on their last country they should be deleted from round robbin and also cards should be given to the opponent attacker.

Verify that all mutators call ->notifyObservers() so that the player widgets are always up-to-date. If our current code wants to avoid notifications, it should temporarily disable notifications using the methods available from the Observable class.

Make sure we didn't leave a feature out.