====== Command line ======

===== The game: Linux and Windows =====
<code>
lord -d <drop file or node dir> [-r rows] [-n node] [-p gamedir]
lord -l [-u name] [-p gamedir]       sysop local play
lord 0                               local play as node 0, as LORD 4.06
lord -d <drop file> -i               show what the drop file says
</code>
^ Option ^ What it does ^
| ''-d <file or dir>'' | The drop file, or the node directory holding one (see [[drop_files]]). On Windows, a ''DOOR32.SYS'' with connection type 2 gives the caller's socket (see [[windows]]). |
| ''-r <rows>'' | The caller's screen rows (DOOR32.SYS has none; default 24). |
| ''-n <node>'' | The node number, if the drop file doesn't give it. |
| ''-p <dir>'' | The game directory; default is the directory the program is in. |
| ''-l'' | Local play on your terminal, as ''$USER''. |
| ''-u <name>'' | With ''-l'': play as this name. |
| ''-i'' | Show what the drop file says, and stop. |
| ''-debug'' | Log LADY scripts to ''lady.log'' (see [[lady_scripts#testing_scripts|testing scripts]]). |
| ''0'' | Local play as node 0. |
The caller is on stdin/stdout.

===== The game: DOS =====
<code>
LORD.EXE <node>          play on <node>, as set up in NODE<n>.DAT
LORD.EXE 0               local play (START 0); node 0 needs no NODE0.DAT
LORD.EXE <node> /L       local play on <node>
LORD.EXE <node> /DEBUG   LADY script testing
</code>
Set ''LORDTRACE=<file>'' and ''LORD.EXE'' writes a trace to that file, for debugging.

===== lordcfg =====
<code>
lordcfg [-p gamedir]                 set-up
lordcfg -p <gamedir> -reset          reset the game, no questions (for scripts)
lordcfg -406 -p <LORD 4.06 dir>      tools for a DOS LORD 4.06 game
LORDCFG.EXE                          set-up, on the local screen (DOS)
LORDCFG.EXE /C<port>                 set-up over COM<port> (from a BBS sysop menu)
LORDCFG.EXE /406                     LORD 4.06 tools (DOS)
</code>
See [[lordcfg]].