Answers without
the support maze.

This redesign presents Germany as the only hosting region, keeping location messaging simple and consistent across the site.

The current Monolith site advertises provisioning in around 60 seconds. Actual setup time can vary with the game and install workload.

Yes. The hosting pages expose normal file management and SFTP workflows for configs, worlds, mods, plugins and other server files.

Yes. Backups are part of the hosting workflow and should be used before version upgrades, wipes, map changes and major mod changes.

The current Monolith site advertises protected or DDoS-ready networking for game traffic.

The current Monolith homepage advertises no slot caps. The real practical limit is the resources required by the game, player count and mod/plugin workload.

Console, files, schedules, backups and game-specific controls are surfaced from the Monolith control panel. Database tooling is available for workloads that need it.

Usually yes. Full file access makes world/save/config migration possible, but always keep the original copy untouched until the new server is validated.

Yes. Back up first, and treat major version changes carefully when worlds, plugins or mods may not be compatible.

Yes. Monolith has a dedicated Paper flow for selecting a Minecraft release and compatible Paper build.

Yes. The Forge flow is designed around selecting Minecraft and Forge versions explicitly rather than forcing one generic latest install.

Yes. Modpack hosting is built around exact software requirements, full files, backups and SFTP.

Older and newer Minecraft generations can expect different Java versions. Matching the runtime to the selected server software helps avoid launch failures.

Yes. The Unturned hosting workflow is designed around Workshop-heavy community servers.

Yes. The service is intended for plugin-ready Unturned communities, with the exact framework depending on your server setup.

Yes. Move maps and configuration through file access and keep the original server backed up while you test.

Yes. Schedules are part of the control panel workflow for long-running servers.

Yes. Rust hosting exposes the files and control surface needed for server-side mod frameworks and configuration.

Yes. The Rust hosting flow is designed around normal RCON administration.

Take a backup, decide whether map data, blueprints or both are changing, and schedule the restart window so players know what to expect.

CPU, memory, plugins and world activity all add load. Size the plan around the actual community instead of just the slot count.

Yes. Garry's Mod hosting is built around Workshop-heavy community setups.

Yes. The public Monolith Garry's Mod page specifically presents DarkRP, TTT and sandbox-style communities.

The public Garry's Mod offering advertises MySQL support for community setups and addons that need persistence.

The ARK hosting flow is designed for normal server-side mod and configuration workflows.

Yes. Full file access allows save migration. Keep an untouched backup during the move.

Yes. Scheduling controls can be used for predictable restart windows.

Yes. The CS2 hosting flow is built around normal Workshop and custom-map configuration.

Yes. RCON is part of the standard CS2 administration workflow.

Full file access supports extension-based setups where the current CS2 ecosystem remains compatible.

Yes. Full file access and SFTP are available for resource files and configs.

The hosting platform includes database tooling for workloads that need persistent data.

Yes. Scheduling is part of the control panel.

Yes. The Project Zomboid flow exposes the file and configuration workflow needed by modded servers.

Yes. Preserve the original save while validating the migrated server.

Yes. Use schedules to keep maintenance predictable for long-running worlds.