Vehicle MC

Vehicle MC already supports GROUND, TANK, BOAT, HELICOPTER, and PLANE controllers, and the shipped content proves that range with dirt bikes, jeeps, tanks, helicopters, planes, boats, trucks, and more experimental hybrid rigs.

The plugin also covers the systems around the vehicle instead of stopping at movement: seats, trunks, keys, pickup and store flow, catalog browsing, terrain response, spawn pools, fuel containers, repair tools, and world service tanks.

That is the difference between a novelty vehicle plugin and something you can actually build a server around.

The public build targets Paper 1.21.10+ on Java 21. PacketEvents is the one hard dependency, so install that first, then drop in Vehicle MC and let the plugin generate its working files on first boot.

The main files you will actually use after that first restart are config.yml, vehicles.yml, catalog.yml, ui.yml, surfaces.yml, spawns.yml, and fuel_tanks.yml.

modules:
  storage:
    enabled: true
  ui:
    enabled: true
  fx:
    enabled: true
  surfaces:
    enabled: true
  fuel:
    enabled: true
  repair:
    enabled: true
  spawns:
    enabled: true
  keys:
    enabled: true
  pickup:
    enabled: true
  catalogMenu:
    enabled: true
  fuelTanks:
    enabled: true
  combat:
    enabled: false

That is the right starter posture for a public server too: keep combat off, keep the core vehicle systems on, and prove one dirt bike or jeep before you start showing off the bigger runway.

/vehicle menu
/vehicle spawn dirtbike
/vehicle give <player> dirtbike
/vehicle fuel list
/vehicle repair list

Use /vehicle menu or /vehicle spawn dirtbike to prove one loop end to end: spawn, mount, drive, store, redeem, and if needed refuel or repair. Once that feels good, the rest of the platform has a trustworthy base.

For a public page, the important thing is not listing every subcommand. It is showing that the plugin already has clean lanes for player access, fleet administration, service tooling, and spawner tooling.

Player-facing
/vehicle menu
 
Core admin
/vehicle list
/vehicle reload
/vehicle spawn <type> [variant]
/vehicle give <player> <type> [variant] [amount]
 
Fuel and repair
/vehicle fuel list
/vehicle fuel <containerId> [units]
/vehicle repair list
/vehicle repair <toolId> [uses]
 
World service and spawns
/vehicle tanks editor
/vehicle tanks spawn <tankId>
/vehicle spawns editor

There is also a combat command namespace in the source, but in the current public build that route is intentionally unavailable until the combat module is wired back in.

Vehicle MC gives players the basic use nodes they need for placing and picking up vehicles, while keeping menu access opt-in and admin tools under the vehiclemc.admin family.

Player nodes
vehiclemc.player.place     (default: true)
vehiclemc.player.pickup    (default: true)
vehiclemc.player.menu      (default: false)
vehiclemc.use              (legacy, default: true)
 
Admin nodes
vehiclemc.admin            (legacy umbrella)
vehiclemc.admin.*
vehiclemc.admin.spawns.*

That vehiclemc.player.menu default matters on a public server because it lets you choose whether /vehicle menu is a normal player feature or an admin or donor-facing route.

Vehicle MC requires PacketEvents. It also bundles SQLite JDBC for storage, so you are not asked to install a separate database driver just to persist vehicles.

On top of that, ModelEngine, WorldGuard, and WorldEdit are optional. That means the core install can stay lean, while better presentation and world-aware tooling can be added later if your server actually needs them.

This is also the right place to be honest about bridge lanes: ModelEngine is a real implemented presentation path, while the Duck Shot combat bridge should still be treated as an advanced lane rather than a first-boot promise.

Does Vehicle MC require ModelEngine?
No. The core engine runs without it. ModelEngine is an optional rendering and animation path on top of Vehicle MC's own controller, collision, and seat authority.

Does it only do cars?
No. The source supports ground, tank, boat, helicopter, and plane controllers, and the shipped content already proves bikes, jeeps, tanks, boats, helicopters, planes, and trucks.

Can players store a vehicle and get it back later?
Yes. Pickup and stored-key flow already exists, and the source preserves health, fuel, and trunk contents when that vehicle is converted back into a stored key.

Is armed vehicle combat part of the first install?
No. Keep combat off for first boot. The docs and source include bridge scaffolding, but in the current public build the combat route is not available by default.

Can I start small?
Yes. That is the intended rollout. One dirt bike, one menu path, and one simple fuel or repair loop is a healthy public starting point.

Vehicle MC keeps physics, collision, seats, and controller logic authoritative while letting you choose how the rig is presented. That makes DISPLAY rigs, native wheel systems, and ModelEngine-backed vehicles feel like real upgrade paths instead of disconnected hacks.

It also exposes the boring but important operator controls: module toggles, tick cadence, autosave cadence, surfaces, spawn caps, anti-dupe switches, audio budgets, VFX budgets, and service-world rules. That is why it can stay practical on a real server instead of collapsing under its own ambition.

Why it scales
- one controller engine across multiple vehicle families
- swappable render backends without giving up authority
- real player loops through keys, pickup/store, catalog, and spawns
- real world loops through fuel, repair, tanks, hoses, and depots
- data-driven config surface instead of hardcoded content only

That is why it is fair to market Vehicle MC as an engine to build on, not just a set of sample rides.