Vehicle MC Wiki Home

Vehicle MC is the drivable-systems platform inside Block Arsenal. It covers rigs, seats, trunks, fuel, repair, service infrastructure, browse and claim flow, driver feedback, and the advanced armed-vehicle bridge into Duck Shot.

This wiki mirrors the public Vehicle MC download page and is meant to help admins and builders move from first boot into a believable live vehicle ecosystem without trying to solve the entire garage on day one.

Start here

If you are brand new to Vehicle MC, use this order:

1. Get the plugin online cleanly
Start with install and First Boot so you confirm the generated files, module toggles, and one working test vehicle.

2. Build the starting path around the dirt bike first
Use free Starter Dirt Bike Quick Start and Upgrade Path before you branch into larger or more specialized rigs.

3. Lock down runtime and physics rules early
Read core Config, Runtime, and Rig Backends and runtime Modules, Physics, and Safety before you start building a full fleet.

4. Learn the file split before you edit everything at once
Use vehicle YAML Authoring Order, File Splitting, and Starter Fleet Planning to understand what belongs in config.yml, vehicles.yml, catalog.yml, ui.yml, and the service or combat lanes.

5. Move into the bigger runway only after the starting path feels solid
That is the right time for larger rigs, service infrastructure, and the Duck Shot bridge.

What Vehicle MC actually covers

Vehicle MC is not only "spawn a car and drive it."

It lets you build:

• dirt bikes, jeeps, tanks, boats, planes, helicopters, and hybrid rigs
• display rigs, native wheel systems, and ModelEngine-backed bodies
• browse surfaces, keys, claims, and driver feedback
• fuel tanks, repair stations, and wider service infrastructure
• armed vehicles that cooperate with Duck Shot

The file map that matters most

Global runtime files

• config.yml for modules, runtime cadence, physics defaults, rig backend, pickup rules, and safety
• surfaces.yml for terrain response
• fx.yml for engine, collision, skid, and movement feedback

Vehicle-definition files

• vehicles.yml for vehicle families, variants, seats, hitboxes, stats, controllers, and per-vehicle overrides
• armor_profiles.yml for reusable armor and damage profile definitions

player-side browse files

• catalog.yml
• keys.yml
• spawns.yml
• messages.yml
• ui.yml

Service and combat files

• fuel_tanks.yml
• duckshot_bridge.yml
• the combat, turret, and loadout files used once the armed-vehicle lane is ready

Documentation map

Getting Started

• install and First Boot
• free Starter Dirt Bike Quick Start and Upgrade Path
• core Config, Runtime, and Rig Backends
• runtime Modules, Physics, and Safety

Fleet and Rig Authoring

• vehicle YAML Authoring Order, File Splitting, and Starter Fleet Planning
• rig Backends, Display Parts, Wheels, and ModelEngine
• native Wheels, Suspension, Axles, and Hybrid ModelEngine Rigs
• advanced Rig Examples: Dirt Bikes, Jeeps, Tanks, Helicopters, and Input-Driven Parts

player-side Systems

• catalog, UI, Surfaces, and Driver Feedback
• keys, Claims, and Vehicle Redemption
• messages, Bossbars, and Driver Feedback

Service and World Infrastructure

• fuel Containers, Repair Tools, and Service Sessions
• fuel Tanks, Repair Stations, and World Service
• fuel Tanks, Spawnpoints, Hoses, and Station Behavior

Armed Vehicles and Cross-Plugin Systems

• duck Shot Bridge, UI, and Operator Workflows
• weapon Presets, Turret Groups, and Loadout Staging
• combat Components, Duck Shot Bridge, Projectiles, and Loadouts

Good first goals for a live server

Before you build a huge vehicle catalog, get these right:

• one believable base vehicle
• one clean variant
• one readable browse or claim path
• one safe pickup or storage loop
• one fuel or repair flow
• one world service point

Once those feel dependable, the rest of Vehicle MC becomes much easier to scale without confusion.