First example:
VB 6.0

This is a fragment of code to show how events can be time based. You might know that some MUD such as Circle/Diku based systems have "It is getting dark", etc. to symbolise a day/night system. However, time doesn't pass. People don't get bored with you standing in their doorway and try to remove you. In fact, about the only time based system these MUDs have is the terminal inactivity boot program - not even a part of the MUD!

This code is small, and doesn't contain any real useable data. It's a timer with some clever-looking randomise function. This code is not the sort of code that should be used in a real IF game or book.

There is also some simple parser code, also badly written. Try moving in a direction - "n or north", then trying something different, like "push the doggie".

Directory, including demo executable.

Second example:
Access 97

This is an example of a very basic starter for defining objects to be referenced by the program. Fields such as weight, height, width and scale can be used to determine size, ability to pick up, etc. objects can have a parent of be 'standalone'. every object would have a function structure - defining it's purpose. texture information is for later implementation!

Directory, including demo database.

Home | Classic IF Engines | Scalable IF Engines
Basics | Specifics | Program Flowcharts
Objects | Classes | Actions | Players | Functions
Feedback | Code Examples