Coding

Create a fully functional and advanced FiveM ESX admin menu script. This admin menu should include features typical for server administration such as player management (kick, ban, teleport), vehicle management (spawn, delete), server announcements, and other common admin tools. The script should be comprehensive and written with clear, maintainable code following ESX framework conventions. # Steps 1. Define the resource manifest and set up necessary dependencies. 2. Create server-side scripts handling admin commands, permissions, and logging. 3. Build client-side scripts for the menu UI, input handling, and command triggering. 4. Implement a permission system to restrict access to admin players. 5. Ensure the menu is dynamic and can handle real-time data (e.g., online players, vehicles). 6. Add thorough comments and organize the code for readability and extensibility. # Output Format Provide the complete codebase for the admin menu, including: - `fxmanifest.lua` or `__resource.lua` file defining the resource - server-side Lua scripts - client-side Lua scripts - any config files - (optional) HTML/CSS/JS files if UI uses NUI Ensure each file's code is clearly labeled and separated for easy understanding and deployment. # Notes - Assume the latest ESX framework version. - Use best practices for security and performance. - Include example usages in comments. # Response Formats Output the complete code files with clear labels indicating file names and contents, without additional explanation, strictly adhering to the above structure.

Create a highly advanced mechanic script for FiveM that significantly enhances in-game vehicle interactions and repair systems with a focus on realism and immersion. The script must implement comprehensive vehicle damage detection for multiple components including engine, tires, brakes, and transmission. It should feature a realistic part replacement system supporting a wide variety of vehicle components, and diagnostic tools allowing players to identify vehicle issues clearly. Repair durations must be dynamic and adjusted based on the severity and complexity of the damage. Additionally, ensure seamless integration with FiveM's inventory and job systems, an interactive repair process involving player engagement such as minigames or progress bars, and compatibility across diverse vehicle models and categories within FiveM. # Steps 1. Analyze existing FiveM vehicle damage and mechanic systems for baseline functionality. 2. Architect a modular, scalable script structure to support advanced mechanic features. 3. Implement hooks and data tracking for vehicle damage per component (engine, tires, brakes, transmission). 4. Develop in-script diagnostic tools to allow players to identify vehicle faults effectively. 5. Build a comprehensive part replacement system with component compatibility verification. 6. Create interactive repair mechanisms with visual feedback, timed progression, and player involvement. 7. Test extensively across multiple vehicle types and damage scenarios for accuracy and robustness. 8. Optimize for performance and ensure multiplayer synchronization to prevent lag and desync. # Output Format Provide a complete Lua script tailored for the FiveM environment include detailed inline comments explaining the purpose and functionality of each major code segment. Supply a README document outlining: - Installation instructions - Configuration options - Available commands - Usage examples including format placeholders like '/diagnose vehicle', '/replace tire 1', and 'start repair: engine' # Notes - Focus on realistic mechanics aimed at improving player immersion. - Optimize code to minimize server lag. - Design for extensibility and future feature additions. # Examples Use placeholder examples such as: - '/diagnose vehicle' to trigger diagnostics - '/replace tire 1' to replace the front-left tire - 'start repair: engine' to begin engine repairs Implement all elements with clarity, modularity, and performance in mind.

Create an advanced car wipe script for a FiveM server framework, compatible with Qb-core, Qbox, and ESX frameworks. The script should include the following features: 1. A visual countdown timer in a clean NUI format displayed at the top of the screen, showing how many seconds remain before all vehicles are wiped. 2. Vehicle wiping will occur automatically when the timer reaches zero. 3. Implement whitelisted zones where vehicles will not be wiped. These zones should be defined using radius-based detection with vector coordinates. 4. Access control: only users whose identifiers are listed in a configuration file (e.g., config.admins) should have permission to use or trigger the wipe functionality. # Steps - Design and implement an NUI interface that displays a countdown timer prominently at the top of the player's screen. - Configure a timer mechanism that triggers periodic vehicle wiping after the countdown completes. - Define configurable whitelisted areas using vector positions and radius to exempt vehicles within these zones from being wiped. - Incorporate admin whitelist checking by validating user identifiers against a config that lists admins with permission. - Ensure compatibility and integration with Qb-core, Qbox, and ESX frameworks to manage player data and permissions. # Output Format Provide the complete script code with configuration comments, structured and modular for ease of integration. Include: - NUI HTML/CSS/JS components for the timer display. - Server-side and client-side scripts to handle vehicle wiping, zone detection, and admin verification. - Configuration file examples for admin identifiers and whitelisted zones with vector and radius specifications. # Notes - Make sure the NUI interface is clean, responsive, and updates in real-time. - Ensure asynchronous handling to avoid server or client lag. - Use precise vector math to detect whether a vehicle is inside a whitelisted zone. - Use consistent identifier formats supported by the frameworks (Steam, Discord, etc.) for admin checks.

Act as an advanced programmer and problem solver. When given a programming or algorithmic question, follow these steps to provide a comprehensive answer: 1. **Understand the Problem**: Clearly restate the problem to ensure understanding. 2. **Identify the Requirements**: List out what is required to solve the problem, including inputs and expected outputs. 3. **Outline the Steps to Solve**: Break down the solution into smaller, manageable steps. 4. **Execute Each Step**: Solve each part one by one, providing explanations for your reasoning and approach. 5. **Present the Final Solution**: Compile all steps and present the complete solution at the end, including any code, output, and an overall summary. Use examples whenever relevant to clarify concepts and steps. Provide additional comments on the efficiency or complexity of your solution if applicable.

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.

Create a heavily advanced mechanic script for FiveM, designed to enhance in-game vehicle interactions and repair systems. The script should provide realistic and immersive vehicle maintenance features, including but not limited to engine diagnostics, part replacements, damage assessment, and dynamic repair times based on the severity of the damage. The mechanic script must include the following functionalities: - Comprehensive vehicle damage detection affecting engine, tires, brakes, and transmission. - Realistic part replacement system with a variety of vehicle components. - Diagnostic tools accessible through the script for players to identify vehicle issues. - Dynamic repair durations reflecting the complexity and severity of repairs. - Integration capabilities with FiveM’s in-game inventories and job systems. - Interactive repair processes providing player engagement through minigames or progress indicators. - Compatibility with different vehicle models and categories within FiveM. # Steps 1. Analyze the existing FiveM mechanics and vehicle damage systems. 2. Design a modular script architecture supporting scalable mechanics features. 3. Implement damage detection hooks and data structures to track vehicle health per component. 4. Develop diagnostic tools within the script for players to identify issues. 5. Create a part replacement system with compatibility checks. 6. Integrate repair processes with visual feedback and appropriate timing. 7. Test the script extensively on various vehicles and scenarios. 8. Optimize performance and ensure synchronization across multiplayer sessions. # Output Format Deliver the full Lua script compatible with the FiveM environment. Include comprehensive inline comments explaining each major section and functionality. Provide a README documentation outlining installation, configuration, commands, and usage examples. # Notes - Prioritize realistic mechanics to enhance player immersion. - Ensure the script is optimized to prevent server lag. - Consider extensibility for future enhancements or additional mechanic features. # Examples [Provide placeholder examples illustrating mechanic command usage or repair interactions, e.g., '/diagnose vehicle', '/replace tire 1', 'start repair: engine']

You are tasked with developing a sophisticated, high-quality ESX framework script named "mv-scripts" that manages an advanced company management system within a FiveM server environment. The script must integrate server-side logic and SQL database interaction, provide real-time client-server interactions using callbacks, and be optimized to ensure resource usage remains under 0.01ms on resmon. The script must adhere to these technical requirements: - Use the ox_lib library, but not ox_core, along with ox_inventory, ox_lib notify, ox_lib context menu, ox_lib alert dialog, and ox_target. - Remove any UI (NUI) components and replace user interfaces exclusively with ox_context menu and other ox_lib components to keep the script modern, lightweight, and server-friendly. - Include robust logging features with detailed audit logs, Discord webhook integration using rich embed messages for significant events. - Implement strict permission controls and configurable settings accessible within the script. - Support multilanguage localization for all user-facing text. Functionality and features to implement: 1. Company Creation: - Players can establish companies with attributes: name, industry, description. 2. Employee Management: - Ability to hire, fire, and manage employees including setting and distributing salaries. 3. Financial Management: - Company accounts to handle deposits, withdrawals, and transfers. - Implement detailed transaction logs. - Include a billing system for customers and payments. 4. Customer and Sales Management: - Inbuilt customer relationship management (CRM). - Sales invoicing system. 5. Data Display and Reporting: - Use ox_context menus to show tables, forms, and company reports without NUI. 6. Rankings & Leaderboards: - Maintain a small business ranking list based on income. You must provide: - A fully functional and optimized script structured as a FiveM ESX resource in a zipped archive. - High-quality code with comprehensive comments. - Use of modern ESX patterns and idioms without UI overlays. - Appropriate server-client communication via callbacks. Step-by-step guidance: - Initialize a new ESX resource named mv-scripts. - Configure SQL database schema for company, employee, financial, customer, and audit log data. - Implement server-side logic for all business operations, including permission checks. - Develop client-side ox_context based menus for company and employee management, financial operations, and reporting. - Integrate Discord webhook logging with rich embeds for major events such as company creation, hiring/firing, large transactions. - Optimize all code and database queries to keep resmon under 0.01ms. - Include multilanguage support via localization files. Please generate the complete script ready for deployment and zipped for immediate use. # Output Format Provide the entire source code for the ESX resource "mv-scripts" as a ready-to-use project structure in a zip file format. Include: - server and client scripts - SQL schema files - localization files - resource manifest - configuration files Ensure all files reflect best practices for ESX scripting and make extensive use of ox_lib components as specified. # Notes - Prioritize performance and maintainability. - Avoid any deprecated ESX design patterns. - Do not include NUI or web-based UI elements. - The script should be compatible with a current stable version of ESX and FiveM. - Make sure to document any assumptions or configuration steps in a README file inside the zip. # Examples - For context menu usage: Use ox_lib context menu for all interactive menus instead of NUI tables or forms. - For notifications: Use ox_lib notify system. - Use ox_target for entity and object targeting in the game world. Create this advanced and complete ESX company management script as mv-scripts with all specified criteria and features, ready to deploy on a server with minimal configuration.

Enhance an existing AI prompt interface by integrating advanced coding functions, specifically including Python functions, JSON handling functions, and other relevant programming utilities. Ensure that these functions are designed to operate seamlessly within the interface and produce outputs that can be embedded or executed directly. The ultimate goal is to generate a comprehensive and fully functioning HTML code that incorporates these advanced features, allowing users to interact with or utilize the coding capabilities effectively within the AI prompt interface. # Requirements - Include advanced Python functions suitable for the AI prompt environment. - Incorporate JSON manipulation functions to handle, parse, and generate JSON data efficiently. - Add other relevant coding functions (e.g., JavaScript utilities, data processing functions) that enhance functionality. - Ensure all code components are compatible and integrate smoothly within the interface. - Output a complete, fully functioning HTML code snippet that encapsulates all these features cohesively. # Steps 1. Identify key advanced Python functions to include, focusing on interactivity and data processing. 2. Develop robust JSON functions to parse, validate, and manipulate JSON data. 3. Add additional coding functions (could be JavaScript or other relevant languages) to increase interface capabilities. 4. Combine these elements into a single HTML file with proper scripting and styling. 5. Test the resulting HTML code for full functionality and smooth user experience. # Output Format Return a single, complete HTML file as a code block containing all necessary components — HTML structure, embedded scripts for Python (if applicable), JSON handling, and other coding functions — ready to be used or deployed as a standalone interface. # Notes - If embedding Python directly isn't feasible in the browser environment, emulate Python functionality via JavaScript or use transpiled tools. - Ensure JSON functions support common operations like stringification, parsing, and validation. - Make the interface user-friendly and optimized for performance.

Develop an advanced pregnancy script for FiveM, focusing on accurate simulation and interactive gameplay features. This script should include functionalities such as: - **Player Character Interaction**: Allow players to engage in activities that can lead to pregnancy, with appropriate animations and prompts. - **Gestation and Birth Process**: Implement a gestation period with realistic stages, tracking the pregnancy duration, and providing players with notifications. - **Health Monitoring**: Include health metrics for both the mother and the unborn child, impacting gameplay based on the characters’ actions and choices. - **Roleplay Elements**: Create immersive roleplay experiences, allowing players to choose options related to prenatal care, childbirth planning, and nursery setup. - **Family Integration**: Facilitate interactions between parents and the newborn, featuring options for family dynamics and responsibilities. - **Events and Milestones**: Introduce events such as baby showers or milestones that provide in-game rewards and recognition. Ensure that the script is well-documented for ease of installation and adjustment by server admins. Optimize for performance and compatibility with existing server features.

Create an advanced FiveM ESX housing script that features premade houses using existing house locations and shells, fully leveraging ox_lib for integration and performance. The script should include the following core features: - **Premade Houses:** Register multiple predefined house locations using existing shells and placements. - **Stashes:** Use ox_inventory to provide secure storage within each house, accessible only to authorized users. - **House Management:** Provide owners with comprehensive property management options, such as settings configuration and access management. - **Key Access System:** Implement a robust key system managing entry permissions based on player identifiers. - **House Maker UI:** Design an intuitive and user-friendly house management interface using ox_lib UI components to perform all housing-related actions. Additional recommended features to enhance gameplay: - Mechanics for buying and selling houses. - Ability for owners to invite other players temporarily to their houses. - Customization options such as furniture placement or decorative changes. - Notification system for key or ownership changes. - Security features like alarm systems and access logs. # Steps 1. Define and register premade house data including positions, shells, and metadata. 2. Integrate ox_inventory stashes at each house location, ensuring only authorized access. 3. Establish a key-access control system linked to player identifiers to manage house entry permissions. 4. Develop a comprehensive House Management UI using ox_lib's UI framework enabling property control, invitations, and settings adjustments. 5. Implement additional features such as property transactions, invitations, notifications, and security monitoring. 6. Thoroughly test compatibility with ESX framework, ox_lib, and ox_inventory to guarantee smooth operation. 7. Optimize for performance and avoid conflicts with common server-side scripts. # Output Format - Provide fully commented Lua script files organized logically (client, server, config). - Include configuration files or Lua tables defining all premade houses with their properties. - Provide detailed usage and installation documentation outlining dependencies, configuration steps, and instructions to integrate into an ESX server. # Notes - Clearly list all dependencies on ox_lib and ox_inventory modules. - Follow FiveM and ESX scripting best practices, including event management and data persistence. - Focus on code modularity and readability ensuring easier customization and maintenance. - Prioritize security in access control and data handling. Produce the complete system prompt embedding these requirements for efficient and reliable generation of the specified script and documentation.

Create advanced FiveM scripts that demonstrate expert-level proficiency in Lua programming for the FiveM platform. Ensure each script is efficient, well-structured, and integrates seamlessly with the GTA V multiplayer mod, utilizing FiveM's native functions and APIs effectively. Key Requirements: - Use clear, maintainable Lua code with comments explaining complex sections. - Implement robust error handling and efficient resource management. - Include at least one example script demonstrating complex gameplay mechanics or server management features. - Follow best practices for FiveM development, including proper event handling and network synchronization. # Steps 1. Design the script to solve a specific use case or add a complex feature to a FiveM server. 2. Write clean and modular Lua code following FiveM scripting conventions. 3. Comment code extensively for clarity and maintainability. 4. Test the script for performance and compatibility issues. 5. Provide installation and usage instructions. # Output Format Provide the complete Lua source code for the FiveM script(s) enclosed in markdown code blocks labeled as 'lua'. Include in-line comments and a section of usage instructions as plain text below the code. # Examples // Example: An advanced vehicle control script that syncs custom vehicle modifications among players. # Notes Ensure the final scripts contain no dependencies on private resources unless clearly documented, and only use public FiveM native functions and resources.

Provide detailed and user-friendly assistance for programming tasks, focusing on generation, optimization, and debugging of code. You will act as CoderX, an advanced AI designed for comprehensive programming support. CoderX can generate high-quality code, optimize existing code, and offer debugging solutions. It can also browse the web for current coding resources using Bing Search and simulate code execution with the Code Interpreter tool. Multiple languages, especially Python, are supported. CoderX's responses should be concise and human-like, using emoticons to engage users. Ensure each interaction begins with a coding query prefaced by 'Create'. Maintain a clear dialogue, adhering to user input requirements and guiding users through coding tasks with user guide keys. **User Guide Keys:** - **P**: Proceed to the next task. - **C**: Continue current task interaction. - **O**: Optimize code. - **E**: Expand code. - **S**: Start a new coding query. Ensure all coding outputs are complete, robust, efficient, and presented in a clear bullet-point format, avoiding verbosity for clarity and directness. # Steps 1. Verify user query accuracy after it begins with 'Create'. 2. Follow up with code structure planning (Task 1). 3. Upon user confirmation, implement complete coding (Task 2). 4. After further confirmation, generate code files for download (Task 3). # Output Format - Human-like conversational style with concise and clear language. - Use emoticons in each response for engagement (e.g., 😄, 💻). - Clarify each step with bold text key points in a bullet-point format. # Examples - **Initializing..** - **Stand By. Task 1: Code Structure Planning.** - **Stand By. Task 2: Complete Coding Implementation.** # Notes - Maintain engagement with emoticons and clarity in responses. - Always include User Guide Keys after interactions. - Strictly adhere to coding tasks and avoid unrelated queries.