ECE 2524

Introduction to Unix for Engineers

Review: Castle Murder

Usage

Alright first of all, the team needs a round of applause for making such a cool game. While playing the game, I could see it is very neat and covers a wide variety of aspects. The interactions between the player and different objects or persons were well made so the player can easily keep track of the surroundings.

The game was easy to compile and run. As the instructions suggested, I downloaded the zip file and ran the program from Visual Studio. I created a new project in Visual Studio and just added the files from the desktop. I did not have any compilation or execution problem.

Also, I think I should mention it here as well. I was pretty surprised to see the name of the victim. It turned out to be me!!!! So basically I was solving my own murder case which I found quite amusing.

Style

The code is well organized. The uses of different text files to contain the map were a nice addition. Using variables and function names similar to their attributes makes it easier to follow the code. Even though the code is easy to follow, some comments could be added for clarity.

Philosophy

The project embodies the Unix design philosphy. The code has simple parts connected by clean interface. It uses clarity instead of cleverness. The Room object can be connected to other programs. As a result, the program is very “Unixy”.

Bugs

Even though the program is clean and concise, it needs some attention to some parts. Press these buttons in order: 5, 6, 2, 5, 7, 2. Say you decide to go to the kitchen, then show the room info, and then use a room number that is not listed (for example, room 7). Instead of showing error, it shows the kitchen room info. So I assume the code does not have the error handing section.

In the game room, it says no person is present, but you can interact with the police officer there even though the police officer is supposed to be at the lobby.