Advanced ESX Mechanic Job

Create a comprehensive and advanced mechanic job script for FiveM ESX framework that includes the following features: 1. **Vehicle Repair and Part Replacement:** Mechanics must be able to repair specific vehicle parts (engine, battery, tires, brakes, etc.) and replace them physically. Include detailed handling such as removing and swapping wheels with different types. 2. **Breakdown Risk System:** Implement a mileage-based breakdown risk system. When a vehicle reaches approximately 100,000 km, add random chances for breakdowns like battery failure, engine trouble, or tire blowouts. Use timers or mileage tracking to simulate wear and tear realistically. 3. **Tire Management:** Allow the mechanic to remove tires physically from the vehicle using proper animations, and install different types of tires or wheels. Ensure the mechanics affect vehicle performance accordingly. 4. **Realistic Animations:** Integrate fairly realistic mechanic animations throughout the interaction process, such as using tools, removing parts, replacing components, and inspecting vehicles. 5. **Boss Features:** Include boss-level management functionalities such as recruiting new mechanics, firing staff, managing payroll, and accessing business-related menus. 6. **Integration with ox_target, ox_lib, and ox_inventory:** Maximize interaction using the ox_target system for targeted interactions, ox_lib for utility functions, and ox_inventory to handle all inventory-related processes, including parts management, tool usage, and stock control. 7. **High Interaction Depth:** The job should be feature-rich and immersive, enabling dynamic player roles and interactions within the mechanic job, with detailed UI/UX where applicable. # Steps 1. Define vehicle parts and their states (working, damaged, broken). 2. Track vehicle mileage and incorporate a system to trigger random breakdown events based on use. 3. Implement part repair and replacement mechanics, with physical representation (e.g., removing a tire). 4. Develop animations for each mechanic action using appropriate FiveM animation libraries. 5. Create boss menus with recruitment, firing, and financial management using ESX and ox_lib. 6. Integrate ox_target for contextual targeting and interaction prompts. 7. Connect all inventory actions (storing parts, tools) to ox_inventory. 8. Test the system thoroughly for realistic behaviour and game balance. # Output Format Provide the complete, well-documented FiveM ESX Lua job script along with any additional resource files (client, server, animations, config), organized and ready to deploy. Include comments explaining critical parts, how to install and configure, and usage instructions for integrating ox_target, ox_lib, and ox_inventory. If external dependencies or assets are needed, specify them clearly. # Notes - Prioritize performance and modular design to facilitate future extensions. - Ensure compatibility with the latest stable versions of ESX, ox_target, ox_lib, and ox_inventory. - Include fail-safes for edge cases such as repairing already working parts or replacing missing components. - Make animations non-disruptive and sync appropriately for all players nearby. # Response Formats Output should be a structured and commented Lua script with supporting files, ready for direct use or adaptation in a FiveM ESX server environment.