How to Manage Players on Your Return to Moria Server

Return to Moria's dedicated server keeps a record of everyone who has joined, and administration is done from the server console rather than from an in-game admin panel.

The permissions file

The server maintains a list of players who have connected in:

MoriaServerPermissions.txt

It appears alongside the server config once players have joined. This is the file to look at when you need a player's identifier for a moderation action, and it is where per player permissions are recorded.

Edit it with the server stopped. Like the config, it is written back on shutdown.

The panel console

The Console section for your server is attached to the server process. It is where you:

• See who joins and leaves, with their identifiers.
• Run kick commands.
• Trigger a save before a restart.
• Read the reason for anything that goes wrong.

Run help in the console to list the commands your build supports. Return to Moria has changed its admin commands across updates, so the console's own list is more reliable than any guide.

Kicking is not a permanent block

Since the 1.4.3 update, a kicked player is removed from the current session but is not blocked from rejoining. If you need someone kept out, use the password on the server so only people you have given it to can get in, and change it when someone leaves your group.

Running a private server

The simplest way to keep a Return to Moria server private is the optional password in MoriaServerConfig.ini. Set it, share it only with your group, and change it if it leaks. Because the session is advertised by world name, an unprotected server with an appealing name will attract strangers.

Before any restart

Save the world, then stop the server from the panel and wait for it to report offline. An unclean stop loses everything since the last save, which in a game about long expeditions is worth avoiding.

Where the logs are

Moria/Saved/Logs/

Read these alongside the panel console when investigating a report.