CSC 8310 -- Prolog Assignment
Section 001: Tuesday & Thursday 4:30 to 5:45pm in Mendel G30
Section 002: Thursday 6:15 to 8:45 in Mendel G30
Spring 2000, Villanova University

Write an adventure game in Prolog. The "Spider" sample game has some code that you can use, and you can look at it for ideas on how to do things in Prolog. But be creative! You cannot just replace the text descriptions and call it a new adventure game; that will get you a very poor grade. (Somebody tries this every time I give this assignment!) You must have a new room layout, a new set of actions, and new code that you have written yourself. This is a programming assignment, and you are expected to do some programming, not just replace text strings.

Pick any theme you like for your adventure game: rescue, survival, treasure hunt, "a day in the life," or whatever appeals to you. A good size for your game is 5 to 10 rooms, and maybe 5 to 10 objects.

You can copy and use some source code from the sample game; in particular, you probably want to take the code for picking up and dropping things, and for moving from place to place (take/1, drop/1, and go/1). But again, you are expected to write a reasonable amount of Prolog code of your own, not just object descriptions and room descriptions.

I'll ask for the following specifics:

• At least two objects with special "behaviors:" for example, a flashlight that only works when it has fresh batteries, a safe that has to be unlocked to get the contents, a vending machine, a time machine, a marker that you can use to write on room walls, etc.
• At least four new verbs specific to your game (for example, kill/0 in the spider game).
• Documentation that tells us about your special objects and your new verbs. If you don't point these out, we might not see them, and you won't get credit for them..
• A start/0 predicate that gives brief instructions, so that if we want to play your game, we know how to get started.

Grading will not be 100% objective. If we like your game, we may give you extra points for it. If your game seems to lack creativity and interest, you may lose points.

Please turn in:

• On paper: A listing of your source code.
• On paper: A transcript of a sample run of your program.
• On floppy: Source code in machine-readable form..

Due date: March 30.