Wiki
Vehicle MC Wiki
Vehicle configuration, rig backends, service systems, terrain handling, and combat-ready admin workflows.
Getting Started
Start here for the real first-boot checks, module setup, and the runtime surfaces that affect every server.
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.
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.
Vehicle Content
Build readable vehicle families, terrain behavior, browse layers, and driver feedback.
Service and World
Handle vehicle servicing, repair tools, fuel tanks, spawnpoints, and station behavior.
Combat and Ecosystem
Connect Vehicle MC to Duck Shot and the combat stack without losing control of performance or readability.
messages.yml is the language file that decides how Vehicle MC speaks to real players, moderators, and support staff.
This file is more important than people think. A working plugin can still feel confusing if the language is rough, unclear, or too technical.
What the current file already contains
The current resource file is organized around:
prefixusageerrorssuccessactionbarinfo
Example:
messages:
prefix: "&6VehicleMC &8ยป &7"
ย
usage:
spawn: "%prefix%&cUsage: /vehicle spawn <type> [variant]"
ย
errors:
vehicleNotFound: "%prefix%&cVehicle not found."
ย
success:
pickup: "%prefix%&aPicked up vehicle. A stored key was added to your inventory."That means the file is already responsible for:
- command help
- player-side errors
- success feedback
- actionbar feedback
- info output for staff and support
prefix
This is the voice anchor of the plugin.
Use it to keep the plugin recognizable and clean, but do not overstyle it so hard that normal lines become hard to read.
usage
This is where the plugin teaches the command format.
Good usage text should:
- say the command clearly
- avoid extra filler
- stay consistent across commands
errors
This is one of the most important sections in the file.
The current file already has dedicated branches for things like:
- vehicle not found
- no permission
- pickup problems
- stored-key problems
- spawn redemption problems
That is good because the system already recognizes that not all failures are the same.
Use this section to make the plugin feel helpful instead of cold.
success
Success lines are where the plugin should confirm what just happened without sounding bloated.
This is especially important for:
- pickup
- redeem
- claim
- spawn
- give
Players should not have to guess whether the action actually worked.
actionbar
This is the quick-feedback lane.
Use it for:
- short redemption feedback
- inventory-full warnings
- quick live prompts
Keep it brief. Actionbar lines are not the place for long explanations.
info
The info block is one of the best support tools in the whole file.
The current resource file already includes lines for:
- type
- id
- state
- hp and fuel
- speed
- controller
- occupants
- chunk and world
- rig wheels
- hitbox and step-up details
This is excellent for support because it gives staff one place to inspect the state of a vehicle without digging into random systems.
Suggested order
- Rewrite the harshest or most confusing error lines first.
- Make pickup and redeem wording extremely clear.
- Keep actionbar lines short.
- Keep the info block compact and consistent.
- Test the language with a player who does not already know the plugin.