Skip to main content

​
Maintaining Performance Standards

In the high-fidelity environment of BeamNG.drive, not all vehicles are architected with multiplayer synchronization in mind. Certain entities - specifically the heavy T-Series semi-trucks, high-vertex specialized trailers, and complex physics props like the Cannon or Flail - can trigger significant server-side “Hitching” and localized client-side crashes. These assets use a massive number of physical vertices (JBeams), placing an immense load on the server’s CPU during every frame calculation. Implementing a strategic restriction policy is essential for maintaining community performance.

Difficulty

Beginner

Time

5 Minutes

​
Technical Implementation Workflow

Because the vanilla BeamMP server binaries do not include a native blacklisting utility, administrators must use a specialized server-side plugin to enforce vehicle restrictions.
1

Initialize Plugin Infrastructure

Download a reputable Vehicle Management plugin (e.g., VehicleRestriction) and deploy the folder into your /Resources/Server/ directory.
2

Access the Registry

Open the plugin’s config.json file situated within the newly created directory.
3

Define Blacklist Identifiers

Input the technical internal names of the vehicles or props you wish to restrict within the blacklist array.
  • Example Syntax: ["tseries", "cannon", "flail", "ball", "box"]
4

Initialize Enforcement

Restart your server. The plugin will now programmatically intercept spawn requests; if a player attempts to spawn a restricted entity, the request is silently discarded.

​
Strategic Resource Recommendations

For servers targeting 12 to 20+ players, we highly recommend restricting all heavy machinery and multi-part trailers. Forcing participants to use optimized civilian cars or race vehicles ensures that the physical simulation remains fluid for everyone, even during large-scale collisions.
To find the technical name of a modded vehicle for your blacklist, open the modification’s .zip file and navigate to the vehicles/ folder. The name of the subdirectory within is the identifier required by your configuration.

​
Proactive Limitation

Beyond blacklisting specific vehicles, consider implementing a Global Vehicle Limit (e.g., 1 per player) within your ServerConfig.toml to prevent individual users from saturating the server thread by spawning multiple complex cars simultaneously.

​
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 | Stability: Better performance for all.