gurpreetraju / risk Goto Github PK

• Calculation of correct number of reinforcement armies according to the Risk rules.
• Players place reinforcement armies on the map.

Logging window that clearly demonstrates that the game phases and rules are properly applied.

Saving a map to a file exactly as edited (using the “conquest” game map format).

Loading a map from an existing “conquest” map file, then editing the map. 3

include condition all nodes are connected and form connected graph.
(ex. o-o, o-o)

@amittbhardwj

• Player can declare an attack by selecting attacker and attacked country.
• Attacker and attacked player decide how many dice to roll.
• Proper number of armies are deducted from attacker/defender country.
• If defender is conquered, attacker can move any number of its armies in the conquered country. If it results in conquering the whole map, the attacker is declared the winner and the game ends.
• Player may decide to attack or not to attack again. If attack not possible, attack automatically ends.

User-driven creation of map elements, such as country, continent, and connectivity between
countries.

Implementation of a valid fortification move according to the Risk rules.

• Game starts by user selection of a user-saved map file, then loads the map as a connected graph.
• User chooses the number of players, then all countries are randomly assigned to players.
• Players are allocated a number of initial armies, depending on the number of players.
• In round-robin fashion, the players place one by one their given armies on their own countries.

should not include exchange of cards

• Implementation of a “phase view” using the Observer pattern.
• Implementation of a “players world domination view” using the Observer pattern.

Verification of map correctness upon loading and before saving (at least 3 types of incorrect maps).