Skip to main content

​
Exploring New Horizons: Custom Maps

Launching specialized community events - such as high-stakes demolition derbies, long-distance highway cruises, or technical rock crawling - requires the perfect environmental foundation. Deploying a custom map on your BeamMP (BeamNG.drive Multiplayer) server involves a two-part technical process: authorizing the asset synchronization through the client repository and then defining the authoritative map path within your server configuration. This guide walk you through the professional deployment of custom world assets on the FREAKHOSTING platform.

Difficulty

Beginner

Time

5 Minutes

​
Technical Deployment Workflow

Follow these steps to initialize a new world on your dedicated instance.
1

Deploy Map Assets

Log in to the Game Panel and navigate to the Files tab. Upload your map .zip archive into the following directory: /Resources/Client/
2

Identify the Path String

Open the ServerConfig.toml file situated in your server’s root directory.
3

Configure the Engine

Locate the Map variable and update its value to point to the map’s internal manifest.
  • Example Syntax: Map = "/levels/derby_arena_v2/info.json"
4

Initialize the World

Restart your server via the console. The engine will now hash the map data and begin serving the level to every joining player.

​
Technical Reference: Determining Path Strings

If you are unsure of the precise technical identifier required for your configuration, you can verify it by inspecting the modification’s internal structure.
  1. Locate the Levels Folder: Open the map’s .zip file on your local workstation and navigate into the levels/ directory.
  2. Retrieve the Identifier: The name of the folder residing immediately within levels/ is the technical identifier used by the BeamNG engine.
  3. Construct the URI: The required format is always: /levels/[IDENTIFIER]/info.json.

​
Troubleshooting: The “Void” Glitch

If participants join the server and find themselves suspended within a black or empty void, it is a definitive indicator that the Map path defined in your ServerConfig.toml contains a typo or does not match the modification’s internal folder structure. Re-verify the capitalization and spelling within your configuration to resolve this immediately.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to get a new server? Use code KB20 at checkout for 20% off your first month!
Last Updated: January 2026 | Maps: Boundless exploration.