Scripting advice

From OHRRPGCE-Wiki
Revision as of 00:23, 12 April 2005 by 83.192.152.224 (talk)
Jump to navigation Jump to search

Here is a list of advices you should follow if you don't want your scripts to bug too much often while testing.

If I am beginner I will use hssed.exe instead of the note pad and hspeak.exe to work and compile the scripts.

I erase the hsi, the hs, and sav files from my directory some times or another (in particular after I've wrote several ploscripts or if I start to work seriously on my game)

I start the game for the beginning (I don't use a previous save) when

I have changed the heroes menu
I have changed an option in the general game data
I have changed options on the map


I don't write too long scripts. I use several little scripts (even for big scenes). See also: how do I call a script directly from another script.

Before compiling I don't let an in-construction script on which I am working be compiled. I use the show text box command and ## (# always you to make comments. By putting the commands as comments you save time because have to write everything from the beginning) to prevent the commands to be compiled. => The scripts I compile are working scripts that have been tested several times.

I don't import the script in the games if there are error messages from Hspeak.exe

I always work with plotdictionary.html opened on a windows and an english dictionnary if necessary

As often as possible I tested the scripts I've just made several times just to be sure that what we want don't happen thanks to a bug