Advanced ESX Car Dealership

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 === - Begin by outlining the entire file structure. - Deliver the code in organized, step-by-step portions. - Provide all files: client.lua, server.lua, manifest file, config.lua, config.js, and UI files. - Present all code in well-structured, clear code blocks. # Steps 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.