Перейти к основному содержимому

Vehicle

Official compatibility

ElementReference
TypeWriterRequired. Use the official TypeWriter release supported by the extension release.
Related extensionsInstall the related extensions listed on this page before using entries that depend on them.

Vehicle Extension

The Vehicle extension provides a comprehensive set of actions, events, facts, manifests, and artifacts for managing vehicles in your server.

Entry Types

TypeCountDescription
Action9Trigger vehicle-related actions
Event7Listen for vehicle-related events
Fact4Query vehicle-related data
Manifest3Define vehicle configurations
Artifact1Vehicle data persistence

Actions

Actions are entries that perform operations when triggered.

Events

Events are entries that fire when something happens.

Facts

Facts are entries that provide queryable data.

Manifests

Manifests are entries that define configurations.

Artifacts

Artifacts are entries that handle data persistence.

User guide

  1. Create vehicle_config and the vehicle_definition entries required by your vehicles.
  2. Add vehicle_storage when ownership and progression data must persist.
  3. Trigger spawn_vehicle or open_vehicle_garage from a command, interaction, or another Typewriter entry.
  4. Use actions such as vehicle_attack, vehicle_ability, vehicle_charge, repair_vehicle, and refill_vehicle_fuel to build the gameplay.
  5. Connect on_vehicle_attack, on_vehicle_destroyed, on_vehicle_collision, on_vehicle_fuel_empty, and on_vehicle_level_up to your scenario reactions.
  6. Add vehicle_stamina_fact, vehicle_charge_meter_fact, vehicle_limit, and vehicle_owned_count for conditions and display.

Test one vehicle, its garage, and its persistence first. Add events and ownership limits afterwards.

Troubleshooting

The extension is not visible

Check that the installed release matches the supported TypeWriter release and that the related extensions listed in the compatibility section are present.

An entry is missing

In the Typewriter Web panel, use the Search bar or the + button to find or create the entry with its exact identifier. Entry IDs and field names are case-sensitive; do not translate them.

The entry saves but nothing happens

Check that the entry is connected to the trigger, command, objective, event, or menu interaction required by its type. Test with optional permissions and criteria removed, then add them back one at a time.

An integration does not work

Verify the dependency and version shown in the extension card, then check the server log for the first error. Do not replace a missing dependency with a similarly named plugin unless the extension source explicitly supports it.