Re: Who's up for a little game?
- Posted by bill Jan 21, 2011
- 2198 views
I have a criticism to make, not about any particular procedure but abot the general approach of:
> move or shoot (m/s)? m > to room? 12Points:
1 we need different prompts for each thing a player can do:
getting instructions (1)
moving (2)
shooting (2)
new game (2)
quit (1)
2 it is not possible to ask for help, or to start a new game, or quit (except by quitting the interpreter) while you are in the game loop.
3 responses to actions are scattered through the code.
4 the game is leading the player - do this or this, do this here, etc,. The player should be controlling what happens.
I suggest a command language - like the CLI.
> move 10 -- moves to room 10 if possible, the status report each round
-- indicates whether the move was successful)
> move 21 -- an error (no room 21)
-- response
-- > ? (laconic but explaining the error is overkill)
-- > (ask again)
> move -- another error
Appropriate commands would be:
move <room> shoot <room-list> help <commands | instructions> new replay quitA command is a space delimited list. All commands and word parameters can be abbrevated (m, mo, mov are all equivalent to move).
I will write a procedure to do this if you think it is a good idea and in the spirit of the game.
