Overview
This prompt aims to guide developers in creating a comprehensive car dealership script for ESX Legacy. Programmers and game developers will benefit by receiving structured instructions and detailed requirements for implementation.
Prompt Overview
Purpose: This project aims to create a comprehensive car dealership script for ESX Legacy, enhancing player experience.
Audience: The intended users are game developers and server administrators looking to implement a car dealership system in their game.
Distinctive Feature: It includes customizable job ranks, a vehicle catalog, and a modern NUI interface for seamless interaction.
Outcome: The final product will be a fully functional, user-friendly car dealership system that can be easily expanded and modified.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Data & Analysis, General Business Operations, Inventory Management
- Techniques: Decomposition, Plan-Then-Solve, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
Create a comprehensive, advanced, and fully functional car dealership script for ESX Legacy, incorporating all the detailed features and requirements specified below.
The system must include these key components:
=== KEY FEATURES ===
🏢 **Owned Car Dealership System:**
– Allow players to buy, name, and own their own car dealership.
– Enable dealership owners to manage employees, set vehicle prices, and configure dealership settings.
🧑💼 **Custom Job Ranks:**
– Support customizable dealer-specific job ranks (e.g., Owner, Manager, Salesperson, Trainee).
– Ensure ranks control access to UI features appropriately.
📍 **Custom Blip, Job Name & Vehicle Prices:**
– Allow each dealership to have a unique map blip.
– Support custom job names for each dealership.
– Enable unique vehicle pricing per dealership.
📘 **Vehicle Catalog with Images:**
– Admins must be able to add vehicles to a catalog.
– Each vehicle entry must include an image, price, and description.
🎨 **Full Color System:**
– Incorporate all GTA vehicle colors.
– Provide live color previews in the vehicle selector UI.
🚗 **Test Drives & Display Vehicles:**
– Enable players to test drive vehicles.
– Allow dealers to spawn display vehicles.
📊 **Sales & Performance Stats:**
– Track employee sales and overall company performance statistics.
🧑🏆 **Best Employee Highlight:**
– Automatically select and display the top-selling employee.
– Include a mugshot image using MugShotBase64.
📦 **Order & Inventory Management:**
– Manage vehicle catalog, purchasing, deliveries, stock, and order history.
🖥️ **Custom UI (Computer + Tablet):**
– Build modern, clean, and fully NUI-based (HTML/CSS/JS) UIs for:
– Vehicle Catalog
– Inventory
– Order History
– Open Orders
– Price Lists
– Dealership Configuration
– Employee Management
=== CONFIG FILES ===
**config.lua:**
– Manage all server/client settings, translations, and texts in Lua.
**config.js:**
– Handle UI texts, layout settings, colors, and labels.
=== LANGUAGES ===
– Include English and German languages.
– Ensure easy addition of more languages.
=== CUSTOMIZABLE ELEMENTS ===
– Vehicles, colors, prices, dealership names, and ranks must be easily configurable.
=== TECHNICAL NOTES ===
– The script must be compatible with ESX Legacy.
– Include and require MugShotBase64 (included).
– Optionally support a custom vehicle image folder.
– Code clarity is essential; comment extensively.
– UI must avoid NativeUI; use only modern NUI (HTML/CSS/JS).
– Use ESX callbacks, events, and ox_lib where appropriate.
– Partial code obfuscation is allowed but maintain open config files.
=== DEVELOPMENT PROCESS ===
1. Define the full file and folder structure for the project.
2. Create config files (config.lua and config.js) with all necessary settings and translations for both English and German.
3. Implement the server-side logic in server.lua covering dealership ownership, employee management, vehicle catalog, sales tracking, and order processing.
4. Implement client-side logic in client.lua for UI interaction, test drives, vehicle spawning, color selection, and blip management.
5. Build the NUI interfaces (HTML/CSS/JS) for all required UIs, ensuring a modern and clean look.
6. Integrate MugShotBase64 functionality to provide mugshot images where needed.
7. Implement necessary manifest and metadata files compatible with ESX Legacy.
8. Ensure all code is thoroughly commented.
9. Use ESX callbacks, events, and ox_lib usage properly in client-server communication.
# Output Format
– All code must be delivered in well-formatted markdown code blocks specifying the language.
– Include file path comments to indicate each file’s location.
– Separate sections logically and present them clearly for easy review and implementation.
# Notes
– Project should allow easy expansion and modification.
– Prioritize clear communication between client and server.
– Keep UI responsive and user-friendly.
**Build this system step-by-step, starting with the full directory and file structure.**
Screenshot Examples
How to Use This Prompt
- Copy the prompt provided above.
- Paste it into your preferred coding environment.
- Follow the outlined steps to create the car dealership script.
- Ensure to implement all key features as specified.
- Test each component for functionality and performance.
- Document your code thoroughly for future reference.
Tips for Best Results
- Plan Your Structure: Start by outlining a clear directory and file structure for your car dealership script to ensure organization.
- Define Configurations: Create config files for server/client settings and translations to allow easy customization and language support.
- Implement Server Logic: Develop server-side scripts to handle dealership ownership, employee management, and vehicle catalog functionalities.
- Build Modern UI: Design a clean and responsive NUI using HTML/CSS/JS for all dealership interactions, ensuring a user-friendly experience.
FAQ
- What features does the car dealership system include?
It includes owned dealerships, custom job ranks, vehicle catalogs, sales tracking, and more. - Can players customize vehicle prices in their dealership?
Yes, dealership owners can set unique vehicle prices for their specific dealership. - Is there a way to track employee performance?
Yes, the system tracks employee sales and highlights the top-selling employee. - What languages are supported in the system?
The system supports English and German, with easy addition for more languages.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (February 2026): Initial release.


