====== Quick start ======
The short version, from download to the first player. The other pages have every setting and command.
===== 1. Install =====
Download ''LORDSRV-1.4.1-setup.exe'' from [[https://games.theiguru.au/lordsrv/]] and run it as an administrator. Keep the default folder, ''C:\LORDSRV'', and tick **Firewall rule**. Tick **Windows service** if the server should run with no one logged on and start with Windows. See [[installing]] for the MSI and the zip.
===== 2. Start the server =====
Start menu > LORD Server > **LORD Server (console)**.
If you installed the service, the server is already running and this opens its console (''[attached]'' in the title bar). Otherwise the server runs in that console window while the window is open. Type ''help'' for the commands.
===== 3. The first settings =====
In the console type ''settings''. Up and Down choose a setting, Enter changes it, **S** saves.
^ Setting ^ What to put ^
| Server name | Shown on the log-in screen and menus. |
| Telnet port | 23 by default. |
| RLogin port | 513 by default. On a computer that also runs TWGS, 513 is usually taken: use another, such as 5130. |
| RLogin without a key from | Your own BBS's address (see step 8). |
| Address for BBSes | Your server's internet name and rlogin port, for other BBSes (''bbs.example.com:5130''). |
| Sysops | Your account name (see step 4). |
After saving, the console offers to restart the server, which it needs to use the new settings. If you changed the ports, the installer's firewall rule already covers them (it allows ''lordsrv.exe'' on any port).
===== 4. Make yourself a sysop =====
Telnet to the server (''telnet localhost 23'' on the server itself), choose **NEW** and make an account. Then in the console:
sysop
A sysop gets **[!]** on the game menu, which runs the game set-up program over the connection, so you can look after the games from anywhere.
===== 5. Set up the game =====
config A
opens LORD's set-up program for game A in a new window: game options (forest fights per day, player fights, bank transfers, clean mode ...), tournaments, the player editor, the item and monster tables, and LADY events. Changes take effect for the next player who enters; no restart is needed. See [[games]].
===== 6. More games =====
In ''settings'' choose **Add a game**, give it a name, save and restart. Each game has its own folder (''games\B'' and so on), made and filled with LORD's files when the server starts.
===== 7. Add-ons (DOS IGMs) =====
- Unzip the IGM into a folder of its own in the game folder, e.g. ''games\A\VAULT''.
- In the console type ''dos A''. A DOS prompt opens in the game folder, which is ''C:\LORD\'' there.
- Run the IGM's set-up (''CD VAULT'' then ''VAULTCFG''). Tell it: LORD is in ''C:\LORD\'', the port is COM1 with a FOSSIL driver, the drop file directory is ''D:\''. Let it add itself to Other Places. ''EXIT'' closes the window.
- If it didn't add itself: ''config A'' > **O** and add it.
- Try it: in the town square press **O** and pick it.
See [[igms]].
===== 8. Link your BBS =====
On Synchronet, add an external program with this command line and no drop file:
?rlogin : -t xtrn=A -P
and put the BBS's address in **RLogin without a key from**. Players' accounts are made from their BBS names the first time they come. Other BBSes can sign up for a key themselves: see [[linking_a_bbs]]. For BBSes on the internet, forward the rlogin port on your router: see [[networking]].
===== 9. Everyday commands =====
^ Command ^ What it does ^
| ''who'' | Who is on, and in which game and node. |
| ''%%kick <#>%%'', ''kick all'' | Disconnect someone (# from ''who''); their game saves them first. |
| ''users'' | The accounts. |
| ''passwd '' | Set someone's password. |
| ''disable '' | Stop an account logging in (''enable'' undoes it). |
| ''bbs'' | The BBSes that have signed up for keys. |
| ''config '' | Set up a game. |
| ''reset '' | Start a game again. |
| ''restart'', ''shutdown'' | Restart or stop the server. |
===== 10. As a Windows service =====
If you didn't choose it when installing: Start menu > LORD Server > **Install as a Windows service**, or type ''service install'' in the console. Windows asks for administrator rights. See [[running]].