lordsrv:files
Table of Contents
Files and backups
The server folder
| File or folder | What it is |
|---|---|
lordsrv.exe | The server and its console. |
lord.exe | The game; one copy runs for each player. |
lordcfg.exe | The game set-up program. |
dosbox\ | DOSBox-X, LSFOSSIL.COM and its source, for IGMs and the DOS prompt (see DOS In-Game Modules). |
template\ | The files a new game folder starts with. |
lordsrv.ini | The server's settings (see Server settings). |
users.dat | The accounts (tab-separated; passwords salted and hashed). |
bbses.dat | The BBSes with keys (the keys as hashes) (see Linking a BBS). |
lordsrv.log | The log. |
lordsrv.run | Held open while the server runs, so only one runs in the folder. |
lordsrv.key | The console's key, while the server runs. |
lordsrv.stop | Create it to stop the server. |
games\A\ … | Each game: lord.ini, player.bin, state.bin, the daily news, mail, error.log, 3RDPARTY.DAT, MAINT.BAT, its IGMs and their files. |
nodes\A1\ … | Each node's DOOR32.SYS (and DOOR.SYS, DOSBOX.CONF for IGMs). |
text\ | Your own screens (see Screens). |
QUICKSTART.TXT, README.TXT | Getting started, and the full manual. |
The drop file
For each player the server writes DOOR32.SYS in the node folder and runs lord.exe -d <drop file> -p <game folder> -r <rows>. Its real-name line is the account name (Bob@EXB), which the game knows the player by; its alias line is the name on their BBS (Bob).
Backups
Back up the whole server folder. What matters: games\, users.dat, bbses.dat and lordsrv.ini. Copies taken while the server runs can catch a game file being written; stopping the server first is safest, or take the copy at a quiet time.
Before upgrading, a copy of lordsrv.ini and the program files lets you go back.
lordsrv/files.txt · Last modified: by 127.0.0.1