Rust Server Setup and Development

The official Rust server does not run plugins on its own; you need a modding framework for that. Oxide (uMod) is the long-established option with the largest plugin library. Carbon is newer, built with performance in mind, and runs most Oxide plugins without changes. On both, plugins are written in C#.

We choose based on where your server stands. Moving a server that has run smoothly on Oxide for years, with a settled plugin list, just for the sake of something new is not always sensible. For new servers aiming at high player counts, Carbon is worth considering. Before any switch we check each of your plugins for compatibility on a test server.

Ready-made plugins cover most needs, but what makes your server stand out is usually what gets written for it: your own economy and shop, clan and team rules, custom events, raid hours, starter kits, or a link that brings player stats onto your website. We write these in C# against Oxide and Carbon hooks, taking care not to inflate the server's tick time.

We also adapt plugins you bought or downloaded from uMod to your language, your rules and your other plugins. Because Rust updates every month, plugins that depend on the game's internals break from time to time, and fixing them is a big part of the job. You receive the source code of plugins written for you, so your server never depends on us.

Facepunch releases a mandatory update on the first Thursday of every month, and it forces a map wipe on every server. Stopping the server at update time, installing the new build and a matching Oxide or Carbon version, resetting the map and bringing the server back up is error-prone when done by hand. We automate this, together with your mid-month wipes and blueprint wipe preferences, on a fixed schedule.

If you want your own map instead of a procedural one, we build custom maps, monuments and prefabs with RustEdit. The thing to watch on custom maps is performance: too many prefabs and poorly placed structures lower frame rates for players and add load on the server. We test the map on a staging server and fix the problem areas before it goes live.

The entity count that builds up over a wipe, meaning bases, doors, boxes and dropped items, is the most common reason a Rust server's tick rate drops. Badly written plugins add to the load by doing needless work every tick. We measure how much time each plugin takes, set up cleanup of abandoned structures and entities, and tune server settings to your player count.

Easy Anti-Cheat catches a large share of client-side cheats, but not all of them. On the server side we add checks that log suspicious hit rates and movement, a player report system and tools that let admins decide quickly. Ban and report logs go to Discord so your team can follow what is happening without being in game.