Vehicle Tool documentation

Start here

You need a Windows FiveM host, administrator access, its resources folder and server.cfg, and a ModOps account. The same account works in both portals.

1. Create an account and verify your email. Open the Server Portal and choose your workspace.
2. Pair the Windows agent in Integrations. Restart FXServer once to load its connector.
3. Connect Tebex if players must purchase submission access.
4. Upload, review and install a vehicle using the steps below.

A remote VPS needs a public HTTPS panel address. Localhost works only when the panel is on the same computer.

Plans & purchases

USD $50 per server per month. Each server needs its own subscription. No trial, annual plan or additional-server discount is enabled. Open Billing for configuration and verified subscription status. A checkout return alone does not activate access.

Server allowances include 5 GB archive storage and uploads up to 100 MB, subject to stricter server limits. ModOps takes no commission on store sales.

Player submission purchases are separate. Owners choose eligible packages in their own Tebex store. If purchase verification is enabled, players must use the email on their verified ModOps account at checkout.

1. Buy an eligible submission package from your community’s Tebex store.
2. Copy the transaction reference from your receipt, for example tbx-12345678-abcde (illustrative only).
3. Open Player Portal → Upload vehicle, select the server, paste the reference and verify.

Owners can upload to their own server without a player purchase. The local demo reference DEMO-VEHICLE-2026 is only for player@modops.local and Harbor Roleplay; it is not a real transaction.

Install & pair the agent

1. Open Server Portal → Integrations → Pair agent.
2. Download ModOps Setup and run it on your Windows FiveM VPS. Approve the administrator prompt.
3. Generate a pairing code and use Copy code. Codes are hidden, work once and expire after ten minutes.
4. Enter your panel address, select the FiveM resources folder, and paste the code. Setup detects server.cfg beside resources; use Advanced if your path differs.
5. Click Install and start agent. Setup creates the Windows service, Desktop and Start Menu shortcuts, and the server-only modops_connector resource.
6. Restart FXServer once. Setup adds the connector to server.cfg. No RCON password is required.
7. Wait for Online. Use Check Connection to refresh immediately.

The agent starts with Windows and restarts after failures. Closing the app does not stop the service. Use the shortcut to reopen configuration, or Windows Services to manage ModOpsAgent.

Heartbeats expire after 20 seconds. Server-only detection requires the current installer’s independent connector heartbeat.

Connect your Tebex store

1. Choose Continue to store after pairing.
2. In the Tebex Creator Panel, open Game Servers → your server → Edit. Copy its Secret Key.
3. Open Developers → Webhooks → Endpoints and copy the webhook secret.
4. Enter both secrets and eligible numeric package IDs, separated by commas.
5. Add the webhook path shown by ModOps to your public HTTPS panel address. Configure and validate that endpoint in Tebex.
6. Click Connect store. Finish setup when the store is verified and the connection is Online.

Blue information icons explain each field. Official references: Secret Key and webhooks.

Upload a vehicle

1. Prepare a ZIP containing the regular full .yft, textures (.ytd), vehicles.meta and handling.meta. Include other metadata your vehicle uses, such as carvariations.meta.
2. Open Player Portal → Upload vehicle, choose the server and verify purchase if required.
3. Continue to Upload package, select the ZIP and enable the rights/processing consent switch.
4. Click Upload & inspect. The original archive stays private.
5. Wait for analysis, then open Edit Vehicle and continue to review.

Submit only assets you have permission to use. Missing metadata, unsafe paths or unsupported content can block continuation. Uploaded executable scripts are not installed; ModOps generates its own manifest. The preview uses the regular .yft, not the _hi version.

Inspect & approve

1. Inspect geometry, textures and handling in Edit Vehicle. Vehicle tabs use spawn codes.
2. Right-click a model part to highlight it and select it in the Parts inspector. Drag to orbit, scroll to zoom, and right-drag to pan.
3. Read every analysis finding. Quarantine checks include branding markers and handling values; they do not guarantee every issue is detected.
4. When Ready, submit for review.
5. Staff open Review queue, inspect the exact version, and approve, reject or request changes.

Approval belongs to one exact version. Replacements need another inspection and approval. Preview supports unencrypted PC Legacy YFT/YTD; GTA shaders and in-game physics are not simulated.

Install & roll back

1. Check the workspace is Online and the version is approved.
2. Use the deployment action for that version. The agent verifies its exact approved bytes.
3. The connector refreshes resources and starts the generated modops_… resource. After successful activation, the agent adds its ensure line to server.cfg.
4. Check Deployments and the live console for Installed or failure details. Test the spawn code in-game before using it with players.
5. Use Rollback to undo a managed installation. The agent stops the resource, removes its ensure line and keeps a private backup.

If cleanup or rollback fails, restore the connection and retry. Queued does not mean installed. Duplicate stream filenames are rejected to avoid overwriting existing assets.

Team & account settings

Use Team & permissions to invite staff and grant only the access they need. Revoke access when someone leaves.

Use Validation limits for server policy and Billing → Player submissions to decide whether players need a Tebex purchase. Policy changes can require another review.

Click your profile for account settings: profile, appearance, notifications and security. Enable an authenticator and save recovery codes privately. Use the portal shortcut to switch views.

Discord logs

1. In Discord channel settings, open Integrations → Webhooks. Create a webhook and copy its URL.
2. Open Server Portal → Webhooks, paste the URL and enable logging.
3. Switch on the actions you want and click Save webhook.
4. Use Send test and check Recent deliveries.

Queued means waiting; Sent means Discord accepted it; Failed includes a safe error. Only owners can configure webhooks. Saved URLs are encrypted and never returned by the settings API. Temporary failures retry; duplicates are possible after a crash. Disconnect stops future logs.

Security & hosting

The panel needs hosting, private storage, a database, HTTPS and protected production configuration. Back up uploads, database records and the encryption key together. Never share pairing codes, integration secrets or credential files.

The service uses Windows credential protection and restricted permissions. The connector has no client scripts or public listener. Its independent heartbeat credential can only report presence; it cannot approve, download or deploy vehicles.

Keep Windows, FXServer, ModOps and dependencies updated. Host administrators are trusted and can read local credentials. Demo accounts are for development only. The installer is currently unsigned; real VPS restart and in-game installation testing remain necessary before release.

Troubleshooting & FAQ