Introduction

Installation

Configuring Objects

Spacecalls

Events

Coordinates

Tips & Tricks

Portable Space EngineBuilder's Guide

Please send comments to Mark Cooke <mpc@star.sr.bham.ac.uk> or vspace@geocities.com

>Space Troubleshooting

One of the first things you should do is create a debugging channel for space messages. The Portable Space Engine will produce debugging and error messages which are sent to the player or object defined by the set_debug_char spacecall.

For example, the following script creates a channel called Space, and an object to forward debugging messages to the channel.

@ccreate Space
@create Channel_Monitor
@set Channel_Monitor=MONITOR
@set Channel_Monitor=SAFE
@set Channel_Monitor=INHERIT
&LISTEN_SPACE Channel_Monitor=^SPACE- *:@cemit Space=%0
think sc(set_debug_char,[mid(num(Channel_Monitor),1,999)])

You should remember to add the spacecall to a startup attribute so that it is set to the correct value after a restart or crash.

Note also that the [mid(num(Channel_Monitor),1,999)] is just a fancy way to get the number of the Channel_Monitor object. You should replace it with the actual DB number when you add the command to a startup attribute or configuration file.


Last modified: 15th March 1998