Wiki

Vehicle MC Wiki

Vehicle configuration, rig backends, service systems, terrain handling, and combat-ready admin workflows.

Quick access

Plugin downloadsVehicle MC All wikisOfficial docs hub AssetsMarketplace SupportHelp routes

Getting Started

Start here for the real first-boot checks, module setup, and the runtime surfaces that affect every server.

Wiki Home Install and First Boot Free Starter Dirt Bike Quick Start and Upgrade Path Core Config, Runtime, and Rig Backends Runtime Modules, Physics, and Safety Rig Backends, Display Parts, Wheels, and ModelEngine Native Wheels, Suspension, Axles, and Hybrid ModelEngine Rigs

Vehicle Authoring

Learn the top-down YAML flow so you know what belongs in config.yml, vehicles.yml, service files, and player-side UI files.

Vehicle YAML Authoring Order, File Splitting, and Starter Fleet Planning Advanced Rig Examples: Dirt Bikes, Jeeps, Tanks, Helicopters, and Input-Driven Parts Rig Debug Commands, Pivot Tools, and Live Diagnostics

YML File Guides

Jump straight into the exact YAML file guide you need when you already know the filename and want the public explanation fast.

Catalog YML: Browse Layout and Variant Entry Flow UI YML: Bossbars, Thresholds, and Driver HUD Keys YML: Key Items, Redeem Flow, and Stored Vehicle Handoff Spawns YML: Pools, Tables, and Display Spawn Modes Messages YML: Player Language, Errors, and Support Feedback Fuel Tanks YML: Service Stations, Hoses, Respawn, and Hazards Duck Shot Bridge YML: Filters, Routing, and Armed-Vehicle Handshake

Vehicle Content

Build readable vehicle families, terrain behavior, browse layers, and driver feedback.

Vehicle Families, Variants, Fuel, and World Service Systems Vehicle Bases, Controllers, Stats, Seats, and Hitboxes Vehicle Interactions, Entry, Exit, Trunks, Horns, and Pickup Lifecycle, Persistence, Variants, and Alias Publishing Fuel Tanks, Repair Stations, and World Service Catalog, UI, Surfaces, and Driver Feedback Keys, Claims, and Vehicle Redemption Spawn Pools, Tables, and Display Props Messages, Bossbars, and Driver Feedback Surfaces, FX, and Terrain Response Catalog, Keys, Spawns, Messages, and Driver UI

Service and World

Handle vehicle servicing, repair tools, fuel tanks, spawnpoints, and station behavior.

Fuel Containers, Repair Tools, and Service Sessions Fuel Tanks, Spawnpoints, Hoses, and Station Behavior

Combat and Ecosystem

Connect Vehicle MC to Duck Shot and the combat stack without losing control of performance or readability.

Duck Shot Bridge, UI, and Operator Workflows Weapon Presets, Turret Groups, and Loadout Staging Combat Components, Duck Shot Bridge, Projectiles, and Loadouts Damage Routing, Collision Damage, and Destruction Safety

The three main building blocks Choosing the right spawn mode Pools: where server safety starts Tables: curating what players actually see Spawnpoints should be authored last Related pages

Vehicle Content

Spawn Pools, Tables, and Display Props

Separate world props, weighted tables, and physical spawnpoints so distribution stays readable and safe.

Plugin downloadsVehicle MC

spawns.yml is the world-distribution layer for Vehicle MC.

It is not just a random spawner file. It decides how public vehicle props appear, how often they come back, and whether interacting with them should:

spawn a live drivable vehicle
hand out a redeemable key
act like a decorative but interactive display

The three main building blocks

The file is organized around:

pools: global rules like caps, respawn timers, and activation radius
tables: weighted selection lists for vehicle bases and variants
spawnpoints: physical world entries that use a pool and a table

The current example shape is:

YAML

scheduler:
  tickIntervalTicks: 20
 
pools:
  default:
    enabled: true
    maxActive: 25
    respawnSeconds: 900
    activationRadius: 128
 
tables:
  default_table:
    dirtbike:
      weight: 40
      variants:
        default: 35
        red: 5
 
spawnpoints: [item]

Choosing the right spawn mode

Vehicle MC already documents three important spawnpoint modes:

DISPLAY_ENTER
DISPLAY_REDEEM_KEY
DIRECT_SPAWN

Use them for very different jobs:

DISPLAY_ENTER: best for showroom props, garages, hubs, and event areas where clicking should become instant vehicle entry
DISPLAY_REDEEM_KEY: best for rewards, displays, crates, island claim systems, and safe one-item redemption flow
DIRECT_SPAWN: best for controlled world service points or dedicated spawn pads where a full vehicle should appear immediately

If you mix these up, the system feels confusing very quickly.

Pools: where server safety starts

The pool layer protects the world from runaway spawn behavior:

YAML

pools:
  default:
    enabled: true
    maxActive: 25
    respawnSeconds: 900
    activationRadius: 128

These fields mean:

enabled: lets you disable a pool without deleting its structure
maxActive: caps how many active props or spawns that pool can maintain
respawnSeconds: controls how quickly missing props come back
activationRadius: avoids running the full logic for nobody

If you are still tuning a public hub, keep these conservative first.

Tables: curating what players actually see

Tables are how you prevent vehicle props from feeling random or sloppy.

YAML

tables:
  default_table:
    dirtbike:
      weight: 40
      variants:
        default: 35
        red: 5
    jeep:
      weight: 20

This lets you control:

which base families are common
which ones are rare
which variants dominate that family

That means tables should reflect your server identity, not just every vehicle you own.

Spawnpoints should be authored last

The file notes that spawnpoints are a managed list and are usually created through admin commands or the editor.

That is the right workflow.

Do not start by hand-authoring a giant list of spawnpoints. Start by:

creating one stable pool
building one good table
testing one spawnpoint mode
checking respawn and interaction behavior
only then scaling up across the world

PreviousKeys, Claims, and Vehicle Redemption Messages, Bossbars, and Driver FeedbackNext