13. Known bugs

If a method of DestinyScript has not the defined effect then this is a bug (= software error). Some of these bugs depend on the target computer system, where the game is running. Hence here is a list of known bugs and solutions.

RPG_RT.exe

This is a bug which can occur if it was not possible to save/load a game. In this case the game will crash. The filename of a save file is quot;SaveXX.lsd", whereas XX is the respective save slot with two digits (e. g. "Save01.lsd"). If the game crashes during save then the save file is probably read-only. If the game crashes during load then the file probably doesn't exist (or that the save file is corrupt).

To check if the save file can be read/written you can simply open it with the Open method of the File object. If the opening works then you can probably save/load the save file.

RPG_RT.exe

If a picture has too huge coordinates then the game will crash (e. g. X = 5000 or Y = -5000).

If a graphic shall simply not be displayed then you can place it a little bit out of the visible range of the screen. Otherwise you could split the file into small pieces and move the small pieces using DestinyScript.

Betriebssystem

This is an error which can occur with firewalls (this includes all operating systems since Windows XP, which includes a firewall). All incoming connections are blocked by the firewall.

To solve this problem you must specify that the program/port may accept incoming connections. For Windows firewalls you can use the manual on Microsoft.com. If you have an external firewall (router, etc.) you must enable the "port forwarding"e;.

User

This problem occurs if an invalid index is used with objects of the RPG_RT. For example if you try to change the properties of the hero with the id 0 (the first hero id is usually 1). In such a case the game will crash.

To solve this problem you must look out to use valid indices.