RESOLVING REVHELPER ERRORS
#1 ERROR - missing config variable(s)
< script error (_sst_new.zrx b.135) : missing config variable(s): sd >
< if this is a serious problem, email me at:
the.reverend@coastgames.com >
< SCRIPT _sst_new.zrx, BUILD 135, DATE 2003-11-01 >
< ZOC VERSION '4.12', OS 'WINNT 501', LOCATION 'bbs.fament.com:23' >
this type of error is easy to resolve. go to the [CONFIG] user menu in revhelper and click the game_data.ini button. this should open up your zoc/log/game_data.ini file. you will notice a section titled [settings] with a bunch of information underneath it. what this error is telling you is that you are missing a variable in the [settings] section. in this example, you are missing the 'sd=1234' variable. 'sd' is the variable for stardock location. just put in a new line with the correct information. problem solved.
#2 ERROR - timeout
< script error (_sst_new.zrx b.135) : timeout >
< if this is a serious problem, email me at:
the.reverend@coastgames.com >
< SCRIPT _sst_new.zrx, BUILD 135, DATE 2003-11-01 >
< ZOC VERSION '4.12', OS 'WINNT 501', LOCATION 'bbs.fament.com:23' >
this type of error usually cannot be resolved. what happened is one of two things: a) the game lagged out or booted you and the script ran out of time waiting for the game to respond, or b) the game put you in a position that the script did not unexpect and it ran out of time waiting for a certain game response that never happened. if you suspect there is something wrong with the script, please email me full details including a game log starting a few pages before the error, the server and game letter, and any other information that you think might be helpful. just sending me the error message is not enough.
#3 ERROR - PMAP2 errorlevel 123
this type of error only happens when you have gotten cim data and the script is trying to send the fresh data to the PMAP2 parser for analysis. there are many causes of this error: a) another script is using your game.map file, so PMAP2 cannot open it to rewrite it; or b) your fig file is corrupted, e.g. it has sectors listed that are either not numbers or too large, i.e. >5000 in a 5000 sector game; or c) your game_log.txt file is corrupted with bogus information; or d) any one of your game.sct, game.prt, game_ref.sct, game_ref.prt files are corrupted with values that are bogus or out of range; or e) your game files have an invalid name, e.g. they cannot have dashes in them like fament-a.sct - so try renaming your game to something with just letters, numbers, and underscores; or f) you have any of the above data files open in another program like microsoft excel or any other file-locking editor.
i hope this information is useful. i will be adding onto this list as more problems are brought to my attention.