No More Room in Hell Server Hosting

What can you run on a No More Room in Hell server?

A private NMRiH server runs both of the game's core modes, in whatever order you like: Objective maps, which carry the nmo_ prefix, and Survival maps, which use nms_. On objective maps the team works through a chain of tasks that can shift between playthroughs, ending with a push toward extraction. Survival is about holding a shelter while wave after wave of undead tests your ammo discipline.

The whole game is built on scarcity. There is no crosshair, the HUD only appears while aiming, ammo is rare, voice chat depends on distance and a bitten player is racing an infection timer. Because of that, server rules shape the experience more than in most shooters. Friendly fire, difficulty and the map rotation decide whether your group plays cautiously or chaotically.

The official co-op format is eight players, and map balance assumes that number. A server that boots into nmo_broadway by default can grow into the regular meeting point for a survival community, with rules and plugins that reflect how your group likes to play.

How much RAM does an NMRiH server need?

For most groups the entry Bronze 4GB plan is plenty. An eight-player Source co-op server uses only a fraction of that memory, even with a handful of plugins loaded. What actually limits NMRiH is single-core CPU speed: srcds handles game logic, zombie AI and physics mostly on one thread, so when the horde gets dense and your team jams into the same corridor, that one core carries the load. The Ryzen 9 9950X leaves comfortable headroom there.

There are only a few reasons to size up. If you stack dozens of SourceMod plugins, keep an archive of hundreds of custom maps or want long log history on disk, Silver 6GB or Gold 8GB adds memory and NVMe space. For a single NMRiH server, Platinum and above are more than the game can use, and we would rather tell you that than sell you idle capacity. If your needs grow later, you can upgrade to a higher plan whenever you want.

Plugins and custom maps: how do you add them?

Because NMRiH is a Source game, you can extend it with Metamod:Source and SourceMod. Upload both into the nmrih directory as addons, restart, and add your admins by SteamID to addons/sourcemod/configs/admins_simple.ini. The community has written NMRiH plugins for translating map objective text, team healing mechanics, weapon stat tweaks and general quality-of-life fixes. Check which game version each plugin supports before installing it, since an untested plugin on a current build can stop the server from starting.

Custom maps are simple: put the .bsp file in nmrih/maps and add its name to mapcycle.txt. Players can download maps straight from the server with sv_allowdownload, but that path is slow for large files. Host the files on a FastDL web directory and set sv_downloadurl, and downloads become dramatically faster. Maps you pick up from the Steam Workshop can be added the same way. Load any new map on an empty server first and confirm the objectives trigger properly before your group shows up for the night.

Which server.cfg settings matter most?

Most of your server's personality lives in nmrih/cfg/server.cfg. hostname sets the name shown in the browser, rcon_password protects remote administration, and sv_password decides whether the lobby is private; leave it empty and anyone can join. sv_difficulty ships as classic and can be adjusted to your group's experience. mp_friendlyfire toggles team damage, and in NMRiH that single line can decide whether a panicked squad survives a narrow hallway.

mp_timelimit and mp_maxrounds control how long a map runs, while mapcyclefile points at the file that holds your rotation. To make bans stick, exec banned_user.cfg and banned_ip.cfg and update them with writeid and writeip. Turning on log and sv_logfile gives you a timeline to check when something breaks.

Take a manual backup from the panel before changing anything important. When the game updates on Steam, the server files need updating too, otherwise players will be refused with a version mismatch.

How do players join, and how do you keep it smooth?

Your friends can join in two ways: search for the server name in the in-game browser, or open the developer console and type connect followed by the IP and port shown in your panel. Source servers default to port 27015, but your exact port is listed in the panel's connection details. If the lobby is password protected, players either enter the password when prompted or set it first with the password console command.

Most performance trouble comes from plugins. If the server starts hitching, disable the most recently added plugin and test again; SourceMod writes its error logs to addons/sourcemod/logs. Restarting long-running Source servers at regular intervals is also good practice. The status command lists connected players and their latency, and if only one player shows a high number, the problem is usually on their end. Since the server sits in İstanbul, players in Türkiye typically enjoy low latency, and friends across Europe and the Middle East get a solid connection too.