Overview
This prompt guides a technical analysis to prevent menu conflicts in two game scripts. Developers and script maintainers will benefit from ensuring stable, user-friendly menu interactions.
Prompt Overview
Purpose: To analyze two boss menu scripts for conflicts and ensure independent operation.
Audience: Developers maintaining or integrating these specific FiveM scripts.
Distinctive Feature: Focuses on preventing simultaneous menu triggers and overlaps.
Outcome: A clear report with actionable code modifications to isolate each menu.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Development Tools & DevOps, Animation & VFX, Business Communications
- Techniques: Decomposition, Structured Output, System-First Instructions
- Models: GPT-4, Claude 3 Opus, Llama 4 Maverick
- 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
Analyze the provided boss menu script for a drug script to understand its structure and functionality. Then review the rh-animations boss menu script to identify potential conflicts with the drug script’s boss menu. Ensure that the boss ped menus in both scripts operate independently without triggering simultaneously, preventing any menu collisions or overlaps.
**Steps:**
1. Examine the drug script’s boss menu to understand its components, triggers, and how it opens/closes.
2. Analyze the rh-animations boss menu for similar elements.
3. Identify any shared resources, event listeners, or triggers that could cause both menus to open simultaneously.
4. Modify or suggest changes to isolate the boss menus, ensuring each menu opens exclusively when invoked.
5. Provide recommendations or code snippets to separate the menus effectively.
**Output Format:**
Provide a detailed analysis report including:
– Summary of each boss menu’s functionality
– Potential conflicts identified
– Suggested modifications or code adjustments to prevent collisions
– Clear explanations for each recommendation
Use code blocks for any script excerpts or proposed code changes to enhance readability.
Screenshot Examples
[Insert relevant screenshots after testing]
How to Use This Prompt
- Copy the prompt into your preferred text editor.
- Review the drug script’s boss menu structure and functionality.
- Analyze the rh-animations boss menu for potential conflicts.
- Identify shared resources or triggers causing simultaneous menu openings.
- Suggest modifications to ensure independent menu operation.
- Provide a detailed analysis report with code snippets if necessary.
Tips for Best Results
- Understand Menu Components: Review each script’s components, such as event listeners and triggers, to understand how they open and close.
- Identify Shared Resources: Look for shared variables or functions that could cause both menus to activate simultaneously.
- Isolate Event Listeners: Ensure each script has unique event listeners to prevent simultaneous triggering of both menus.
- Implement Conditional Checks: Add conditions to check if one menu is open before allowing the other to activate, preventing overlap.
FAQ
- What is the drug script’s boss menu structure?
The drug script’s boss menu includes components like triggers and event listeners for opening and closing. - How does the rh-animations boss menu operate?
The rh-animations boss menu has similar elements like triggers and event listeners for managing its display. - What causes both menus to open simultaneously?
Shared resources or event listeners might cause both menus to trigger at the same time. - How can menu collisions be prevented?
Isolate triggers and event listeners for each menu to ensure they operate independently.
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 (March 2026): Initial release.
