code-newbies / python-thursday-adventure Goto Github PK

Not all commands are available when the player has not typed 'begin', for example, movement is illegal. menu and commands should be limited at any time to valid commands

This is to replace the closed issue #39. I plan to use a prompt at the beginning of the game (When the player's name is asked for) to set the input keys.

Key and gold remain on the map after picking them up. They should be removed from the room when they are placed in inventory.

I can't seem to get the assigned westward movement working. It takes the command, but the map doesn't update.

After adding the first monster there are probably going to be some maintenance items that need to be addressed.

After exiting a level nothing changes and the player remains on the same level.

For example: a particular monster starts to follow the player after a number of keystrokes

This data is stored as a list of tuples. It would probably work better as a Dict or OrderedDict with the keyboard command as the key. This will allow for cleaner, more pythonic lookups.

Some items in a room should be removable. These include keys, gold and super awesome swords.

Other items should be non-removable. These include doors, fountains, and soda dispensers.

Currently there is no generic way to tell these apart. Adding this would be helpful for making the pickup function generic.

Player should be able to move around the map using arrow keys without having to press enter in between.

The documentation for getting up and running with this project is lacking. The current README.md offers no information about the game's goal or current state.

Also, the code needs documenting.

The Room() will generate a map and it is used when you type 'begin', currently it is not displayed after that. A process for displaying this map should be added either by command or automatically.

add weapon class with name, description, and damage.

The map drawing should include other items in the room such as the player and other things.

The automated tests are missing some spots (poor coverage) and the codebase has been refactored without substantial review of the tests. Finally we have migrated from unittest to py.test.

This issue is to review and improve automated testing.

Obey the testing goat!

Add an attack that does not require a weapon.

Engine and Room have too many responsibilities and the methods aren't clear. Clean these up.

Currently the room has a size, but the game allows you to travel outside it's walls.

the combat system should select a player's best weapon to attack with based on damage points