Advanced FiveM ESX Mechanic Job Script for Vehicle Repair and Management

Create a comprehensive and advanced mechanic job script for the FiveM ESX framework that encompasses the following key features:
– Vehicle Repair and Part Replacement:
Enable mechanics to repair and replace specific vehicle parts, including:
– Engine
– Battery
– Tires
– Brakes
Implement detailed physical interactions, such as removing and swapping wheels with different types.
– Breakdown Risk System:
Develop a mileage-based system that tracks vehicle usage, triggering random breakdown risks (e.g., battery failure, engine trouble, tire blowouts) when vehicles approach or exceed approximately 100,000 km.
Use timers and mileage tracking to realistically simulate wear and tear.
– Tire Management:
Permit mechanics to physically remove tires with appropriate animations and install various tire or wheel types, affecting vehicle performance in-game accordingly.
– Realistic Animations:
Integrate suitable mechanic animations throughout interactions, such as:
– Tool usage
– Removing parts
– Inspecting vehicles
– Replacing components
Utilize FiveM’s animation capabilities.
– Boss Features:
Include comprehensive boss management functionalities, such as:
– Recruitment and firing of staff
– Payroll management
– Access to business-related menus
Fully integrate with ESX and ox_lib.
– Integration with ox_target, ox_lib, and ox_inventory:
Use ox_target for precise, contextual player interactions;
ox_lib for utility and UI features;
ox_inventory to manage all inventory-related tasks, including:
– Part storage
– Tool usage
– Stock control.
– High Interaction Depth:
Design an immersive, feature-rich job experience with:
– Dynamic player roles
– Detailed UI/UX where applicable
– Seamless interaction flow.
# Steps
1. Define vehicle parts with detailed states (working, damaged, broken).
2. Implement vehicle mileage tracking and trigger random breakdown events based on use.
3. Develop repair and replacement mechanics with physical part representation (e.g., tire removal).
4. Create and integrate animations for every mechanic action.
5. Build boss menus enabling staff recruitment/firing and financial management using ESX and ox_lib.
6. Utilize ox_target to enable contextual targeting and interaction prompts.
7. Link all inventory actions for parts and tools to ox_inventory.
8. Conduct thorough testing for realism, performance, and balanced gameplay.
# Output Format
Deliver a complete, modular, and well-documented FiveM ESX Lua job script along with all necessary resource files, including:
– Client-side scripts
– Server-side scripts
– Animations
– Configuration files
Organize all files and ensure they are ready for deployment. Include extensive inline comments explaining critical functionality, clear instructions on installation and configuration, and usage guides for integrating ox_target, ox_lib, and ox_inventory.
If external dependencies, assets, or third-party libraries are required, specify versions and provide clear instructions on how to acquire/install them.
# Notes
– Emphasize performance optimization and modularity to enable future extensions and maintenance.
– Confirm compatibility with the latest stable releases of ESX, ox_target, ox_lib, and ox_inventory.
– Implement safeguards against edge cases, such as attempts to repair already functional parts or replace missing components.
– Ensure animations are smooth, non-invasive, and synchronized for all nearby players.
# Response Formats
Respond with a structured, well-commented Lua script and related resource files arranged for immediate use or straightforward adaptation within a FiveM ESX server environment.