Welcome to our store – 20% off all products! NXD_StreamerPanel – Coming Soon. Welcome to our store – 20% off all products! NXD_StreamerPanel – Coming Soon. Welcome to our store – 20% off all products! NXD_StreamerPanel – Coming Soon. Welcome to our store – 20% off all products! NXD_StreamerPanel – Coming Soon. Welcome to our store – 20% off all products! NXD_StreamerPanel – Coming Soon. Welcome to our store – 20% off all products! NXD_StreamerPanel – Coming Soon.
PACKAGE

NXD_Repair [ESX]

FREE
NXD_Repair [ESX]
DETAILS

DE:
Das Script WVC_Repair ist ab sofort verfügbar. Es bietet ein flexibles und konfigurierbares Repair-System für ESX-Server.

Features:

  • Repair Kit Item

  • Custom Progressbar

  • Reparatur-Animation

  • Voll konfigurierbar

  • SQL inklusive

  • Inventory Bild inklusive

  • Notification Support (okokNotify, ox_lib & ESX)

  • Mechaniker-Check (Repair Kit nur nutzbar, wenn kein Mechaniker online ist)

  • Job frei konfigurierbar

Enthaltene Dateien:

  • fxmanifest.lua

  • config.lua

  • sql.sql

  • client/main.lua

  • server/main.lua

  • html/index.html

  • html/style.css

  • html/script.js

Installation:

  1. SQL-Datei in die Datenbank importieren

  2. Resource in den Server-Ordner kopieren

  3. ensure WVC_Repair in die server.cfg eintragen

  4. Server neustarten


EN:
The script WVC_Repair is now available. It provides a flexible and fully configurable repair system for ESX servers.

Features:

  • Repair Kit Item

  • Custom Progress Bar

  • Repair Animation

  • Fully configurable

  • SQL included

  • Inventory image included

  • Notification support (okokNotify, ox_lib & ESX)

  • Mechanic check (repair kit only usable if no mechanic is online)

  • Job configurable

Included files:

  • fxmanifest.lua

  • config.lua

  • sql.sql

  • client/main.lua

  • server/main.lua

  • html/index.html

  • html/style.css

  • html/script.js

Installation:

  1. Import the SQL file into your database

  2. Copy the resource into your server folder

  3. Add ensure WVC_Repair to your server.cfg

  4. Restart your server

For support or questions, feel free to reach out.