Overview
This prompt aims to create a detailed mechanic job script for the FiveM ESX framework, enhancing gameplay realism. Programmers and game developers will benefit by having a comprehensive template for implementing advanced mechanics in their projects.
Prompt Overview
Purpose: This script enhances the mechanic job in FiveM ESX, providing immersive vehicle repair functionalities.
Audience: It targets FiveM server developers looking to enrich gameplay through advanced mechanic features and interactions.
Distinctive Feature: The script includes a breakdown risk system based on vehicle mileage, adding realism to vehicle maintenance.
Outcome: Players will experience a dynamic mechanic role, fostering deeper engagement and interaction within the game environment.
Quick Specs
- Media: Text
- Use case: Analysis, Classification & Categorization, Content Creation
- Techniques: Role/Persona Prompting, Scratchpad Reasoning, Structured Output
- Models: ChatGPT, Claude, Gemini AI
- 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 and advanced mechanic job script for the 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 for 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 such as 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 physically remove tires from the vehicle using proper animations.
– Install different types of tires or wheels, ensuring that these changes affect vehicle performance accordingly.
4. Realistic Animations:
– Integrate fairly realistic mechanic animations throughout the interaction process, including:
– Using tools
– Removing parts
– Replacing components
– Inspecting vehicles
5. Boss Features:
– Include boss-level management functionalities such as:
– Recruiting new mechanics
– Firing staff
– Managing payroll
– Accessing business-related menus
6. Integration with ox_target, ox_lib, and ox_inventory:
– Maximize interaction using the ox_target system for targeted interactions.
– Utilize ox_lib for utility functions.
– Handle all inventory-related processes, including parts management, tool usage, and stock control with ox_inventory.
7. High Interaction Depth:
– The job should be feature-rich and immersive, enabling dynamic player roles and interactions within the mechanic job.
– Ensure detailed UI/UX where applicable.
# Steps
8. Define vehicle parts and their states (working, damaged, broken).
9. Track vehicle mileage and incorporate a system to trigger random breakdown events based on usage.
10. Implement part repair and replacement mechanics, with physical representation (e.g., removing a tire).
11. Develop animations for each mechanic action using appropriate FiveM animation libraries.
12. Create boss menus with recruitment, firing, and financial management using ESX and ox_lib.
13. Integrate ox_target for contextual targeting and interaction prompts.
14. Connect all inventory actions (storing parts, tools) to ox_inventory.
15. Test the system thoroughly for realistic behavior and game balance.
# Output Format
– Provide a 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, installation and configuration instructions, and usage guidelines for integrating ox_target, ox_lib, and ox_inventory.
– Specify any external dependencies or assets 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 nearby players.
# 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.
Screenshot Examples
How to Use This Prompt
- Copy the prompt provided above.
- Paste the prompt into your coding environment.
- Follow the outlined features and steps closely.
- Implement the Lua script according to the specifications.
- Test the script in a FiveM ESX server environment.
- Adjust based on testing feedback and performance requirements.
Tips for Best Results
- Vehicle Repair: Implement a system for mechanics to repair and replace vehicle parts like engines and tires, ensuring physical interactions.
- Breakdown Risk: Create a mileage-based system that triggers random breakdowns when vehicles reach 100,000 km, simulating realistic wear.
- Tire Management: Allow mechanics to remove and install various tire types, affecting vehicle performance and requiring proper animations.
- Boss Features: Develop management functionalities for hiring and firing mechanics, payroll management, and business oversight.
FAQ
- What features should a mechanic job script include?
It should have vehicle repair, breakdown risk, tire management, realistic animations, and boss features. - How does the breakdown risk system work?
It triggers random breakdowns based on vehicle mileage, especially after reaching 100,000 km. - What is the role of ox_target in the script?
Ox_target enhances interaction by providing contextual targeting and interaction prompts for players. - What should be prioritized in the script design?
Performance and modular design should be prioritized for future extensions and compatibility.
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.
