> For the complete documentation index, see [llms.txt](https://docs.c7scripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.c7scripts.com/paid/vms2/about.md).

# VMS2 Introduction

<figure><img src="/files/F5MhdaixSl7R3SkzYXeO" alt=""><figcaption></figcaption></figure>

## Script Features (TL;DR)

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>🟢 <strong>C7FW / Standalone Support</strong></td><td>Use with C7 Framework or run fully standalone via config toggle.</td></tr><tr><td>👨 <strong>Department Vehicle Access</strong></td><td>Vehicles are organised by department for role-based access.</td></tr><tr><td>🔐 <strong>Discord Role Integration</strong></td><td>Optional Discord roles control who can access departments.</td></tr><tr><td>⚙️ <strong>Config-Driven Vehicles</strong></td><td>All vehicles configured through config, no core edits needed.</td></tr><tr><td>📦 <strong>Vehicle Presets</strong></td><td>Set liveries, extras, and mods per vehicle entry.</td></tr><tr><td>🧰 <strong>Vehicle Modkits</strong></td><td>Apply performance and visual upgrades automatically on spawn.</td></tr><tr><td>🖼️ <strong>Vehicle Images</strong></td><td>Assign image URLs for vehicles in the UI menu.</td></tr><tr><td>🖼️ <strong>Department Images</strong></td><td>Assign image URLs for departments in the UI menu.</td></tr><tr><td>🖼️ <strong>Sub-department Images</strong></td><td>Assign image URLs for sub departments in the UI menu.</td></tr><tr><td>📋 <strong>Vehicle Ordering</strong></td><td>Control vehicle order per department menu.</td></tr><tr><td>🔢 <strong>Spawn Limits</strong></td><td>Limit how many times vehicles can be spawned.</td></tr><tr><td>🕒 <strong>Cooldown System</strong></td><td>Configurable cooldown to prevent rapid spawning.</td></tr><tr><td>🪪 <strong>Personal Plates</strong></td><td>Persistent player plate management and storage.</td></tr><tr><td>📍 <strong>Vehicle Tracking</strong></td><td>Tracks spawned vehicles per player to prevent duplication.</td></tr><tr><td>⌨️ <strong>Command Access</strong></td><td>Open the menu using a configurable command.</td></tr><tr><td>🌍 <strong>Multi-Language</strong></td><td>Fully configurable language strings for localisation.</td></tr><tr><td>💡 <strong>Performance Focused</strong></td><td>Highly optimized script maintains low resource use, even in large servers.</td></tr><tr><td>🔄 <strong>Server Sync</strong></td><td>OneSync Infinity state bags ensures performant effects and consistent data.</td></tr><tr><td>🧡 <strong>Support</strong></td><td>Lifetime updates, 7-day-a-week personalized support via Discord.</td></tr></tbody></table>

## **Purchase this Script**

{% embed url="<https://shop.c7scripts.com/package/7176503>" %}

## Script Showcase

{% embed url="<https://youtu.be/iqi8Q7-WRy8?si=6amD4LBeB6g4ZXnG>" %}

## Installation & Configuration

{% content-ref url="/pages/tIuTto0ouB9CooIra5H8" %}
[VMS2 Configuration](/paid/vms2/config.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.c7scripts.com/paid/vms2/about.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.