Running on a Cloud Server

A cloud server, often called a VPS (Virtual Private Server), is a Windows computer in a data centre that you control over the internet. It stays on day and night with a stable connection, so your accounts keep running when your own PC is off. You connect to it with Remote Desktop and use Lords Bot there just like on your own PC.

What the server needs #

• Windows Server 2016 or later (or Windows 10 version 1607 or later), 64-bit. Older versions such as Windows Server 2012 are not supported.
• Outbound internet access on port 443 (HTTPS). Lords Bot also tries port 80 if 443 is blocked.
• Enough memory and CPU for the number of accounts you run. As a rough starting point for up to about 50 accounts: 2 to 4 GB of RAM, 2 to 4 virtual CPUs and 20 GB of free disk space. Run more accounts, and you need more. If accounts often lag or disconnect, the server is probably too small.

You don’t need to install .NET or anything else first. LordsBotSetup installs what the bot needs.

Connect to the server #

Your VPS provider gives you the server’s IP address, a username and a password.

1. On your PC, open Remote Desktop Connection: press Windows key + R, type mstsc and press Enter.
2. Type the server’s IP address in Computer and click Connect.
3. Enter the username and password when asked.
4. You now see the server’s desktop. Download and run LordsBotSetup there, as in Install Lords Bot.

When you close the Remote Desktop window, the server keeps running and so does Lords Bot. Connect again at any time to check on it.

Keep it running #

Servers restart now and then, for example for Windows updates. Use Lords Monitor so the bot comes back by itself:

1. In Lords Bot’s sign-in screen, tick Remember Me and Auto Start, and tick Auto-Start for each account on the grid.
2. Open Monitor.exe in the Lords Bot folder. In its settings, tick Run at Windows startup and leave Auto-login on (it is on by default). The Monitor signs the bot in, so Auto Login on the sign-in screen isn’t needed.
3. Set Windows on the server to sign in to your user automatically after a restart (autologon). The Monitor starts when your user signs in, then starts and signs in the bot.

Note: Don’t run the Monitor as a Windows service, or as a scheduled task set to “Run whether user is logged on or not”. It then runs where there is no desktop, and the bot it starts has no window you can open. Use Run at Windows startup instead.

Note: Run the Monitor and the bot as the same Windows user. If they run as different users, the Monitor can’t see the bot and starts a second copy.

Disconnecting and reconnecting Remote Desktop doesn’t affect the Monitor or the bot.

Tips for servers #

• Keep Windows updated. A server that is far behind on updates can stop Lords Bot from starting. Install updates regularly at a time that suits you, so restarts don’t catch you by surprise.
• Check the clock and time zone. If the server’s clock is wrong, signing in fails with Token expired. See Token Expired.
• Use Performance Mode on small servers. In the main window, open Settings > Options and turn on Performance Mode. It cuts down the battle simulations the bot runs and slows some background refreshing, which lowers CPU use.
• Avoid antivirus web filters that block the bot’s connection. See “Couldn’t connect to the server”.