The waterlily from embraceltd

Remove compiler warning 'The field 'Program.safeBlownup' is assigned but its value is never used'

Add a turn counter to the prompt

The prompt should show the number of turns, like so:

1> get hammer

The nitroglycerine bottle can be broken with the hammer

Nothing happens if you break the bottle with the hammer. It should blow up!

Implement other directions

Implement moving southeast, southwest, northeast, northwest, up, down

Max number of carried items

A max number of items that the player can carry should be defined in the config. Setting it to -1 enables the player to carry an infinite number of items.

Create generic classes for commands, conditions, actions and operations

In order to create a truly customizable game engine, the available commands (TAKE, DROP etc) should be defined in the config rather than being hard coded. This requires the creation of classes for commands, conditions, actions and operations.

The idea is that a command should have a target action.

An action should have a list of conditions that must be fulfilled in order to perform the action.

The action should also have a list of operations. If all conditions are met, the operations are executed.

A condition typically consists of getting a property value of an item and comparing it to a certain value. If not equal, a message is output and execution of the action returns false. I.e. 'You don't have the hammer'.

An operation typically consists of setting a property of an item to a new value.

The completed action should output a description of what was done, i.e. 'You take the hammer'.

Example

Command: take hammer

The command is interpreted as a verb, 'take', and an object, 'hammer'.

The verb 'take' is defined in the config and associated with an action.

The action has a list of conditions for the object to be taken by the player.

Item.carry == false (that you don't have it already)
Item.location == userLocation (that the hammer is present)
Item.canTake == true (that it can be picked up unlike, let's say, a car)

It has a list of operations:

Set item.carry = true

The action has a CompletedMessage:

'You take the hammer'

A command object can have a list of synonyms (GET, TAKE, PICK, SNATCH, GRAB) etc.

Conclusion

A command object contains:

a list of command (verb) synonyms
a named target action

An action object contains:

a name for retrieval
a list of conditions
a list of operations
a CompletedMessage

A condition object contains:

a condition definition, a string that defines what item, what property, what value and what comparison operator to use.
a FailureMessage

An operation object contains

an operation, a string that defines what to do

Refactor locations to have generic properties

Locations should have generic properties just like items. The can even share the same entity.

Loading a game doesn't reset turn count

When you load a game the turn count is not reset.

Create human and animal entities

These classes should derive from Item and add properties that are specific for them.

Create "trig" instruction

Let triggerActions only be triggered by trig instruction. Remove option to trigger actions by conditions. TriggerActions can be triggered by Actions and other triggerActions.

Syntax: trig:{triggerActionName}

Example: "trig:takeBottleExplosionAction"

Validation of config

Configurations should be validated after load

Define pathways

People, animals and moving objects (like trains) could have a pathway, defined as an array of location numbers, which they move along, one step for every new turn. A pathway could optionally be started by triggering an event, otherwise it starts when the game starts.

Make turns time limited

A turn is defined as the events between two player commands. The 'wait' command was created to prepare for the concept of turns (in that it progresses one turn without doing anything).

In order to spice up the game, there should be a time limit of 1 minute after a player issues a command, after which the game engine sends a 'wait' command and forces a new turn.

If there is a pending detonation action, the player would be killed if he/she just sits idle without getting out of the location.