MASTER PROMPT: BUILD A COMPLETE MINECRAFT FABRIC CLIENT — CUBESTORM
1. ROLE AND MAIN OBJECTIVE
Act as an expert Minecraft Java Edition developer, Fabric mod specialist, Java engineer, GUI designer, and software testing engineer.
Build a complete Minecraft client-side mod named CubeStorm Client, inspired by my reference screenshot.
The goal is to create a real, functional, buildable project with a custom ClickGUI and all requested modules. Do not create only a visual mockup or nonfunctional buttons.
Target specifications
* Minecraft Java Edition: 1.21.11 * Mod loader: Fabric * Language: Java * Build system: Gradle + Fabric Loom * Java version: Verify the official requirement for the selected Minecraft release and development toolchain * Platform: PC Java Edition and Android PojavLauncher where technically supported * Mod ID: cubestorm * Main package: com.cubestorm * Initial version: 1.0.0 * Mappings: Use one consistent mapping system compatible with the selected dependencies
Verify all dependency versions before writing code. Never invent Minecraft APIs, event methods, rendering methods, or dependency versions.
Generate the complete source code, project structure, configuration files, resources, build instructions, and tests.
If the answer is too long, continue in numbered parts until all required files are delivered. Do not silently omit requested modules.
---
2. CLICKGUI DESIGN
Create a custom dark ClickGUI inspired by my screenshot.
Visual requirements
* Dark gray interface * Rectangular gray module buttons * Dark borders and readable text * Separate category panels * Compact layout similar to the reference image * Configurable accent colors * Enabled/disabled indicators * Optional opening and closing animations * Responsive layout for small screens and desktop * Mouse and keyboard support * Scrollable category panels * Module search * Module descriptions * Settings panel * Configurable GUI scale * Reset settings button * Configurable ClickGUI keybind
Categories
- Player
- World
- Combat
- ESP
- Render
Every module button must connect to a real module implementation. Do not display a module as working if it is only a placeholder.
Clicking a module toggles it. Opening its settings must display the correct settings for that module.
---
3. MODULE FRAMEWORK
Implement the following architecture:
* Base Module class * ModuleCategory enum * ModuleManager * Setting base class * Boolean, number, mode, color, and keybind settings * GUI manager * HUD manager * Configuration manager * Client event integration * Logging and error handling
Every module must have:
* Unique internal ID * Exact display name * Category * Description * Enable and disable lifecycle * Optional settings * Optional keybind * Cleanup when disabled * Error handling
Register every module exactly once. Save settings and keybinds in the Minecraft config directory.
Modules should not automatically enable risky gameplay features on startup. Invalid configuration files must recover safely.
---
4. PLAYER CATEGORY
Implement these exact module names in this exact category:
1. Fly
Purpose: Flight-related movement practice in authorized environments.
Features:
* Configurable movement speed * Vertical movement settings where supported * Enable/disable controls * Restore movement state when disabled * Respect server-authorized movement
2. Speed
Purpose: Movement-speed information and supported movement settings.
Features:
* Configurable speed display * Movement-state information * Normal movement fallback * Restore modified state when disabled
3. NoFall
Purpose: Help prevent accidental falls.
Features:
* Fall-distance indicator * Configurable warning threshold * Optional warning notifications * Do not claim that client-side code can cancel server-authoritative damage
4. AutoTool
Purpose: Help select the appropriate tool for the targeted block.
Features:
* Detect targeted blocks * Evaluate hotbar tools * Select an appropriate tool when enabled * Handle empty slots and invalid targets * Preserve the user's preferred selection according to settings
5. FastUse
Purpose: Item-use information and supported convenience features.
Features:
* Detect the active item * Display item-use state * Respect ordinary game mechanics * Do not claim to bypass server restrictions
6. HighJump
Purpose: Jump-related practice and visualization.
Features:
* Jump-state information * Configurable practice settings * Normal behavior by default * Restore movement state when disabled
7. NoSlow
Purpose: Show movement slowdowns caused by item use.
Features:
* Detect supported slowdown states * Display slowdown information * Provide configurable indicators * Respect server-authoritative mechanics
8. AutoWalk
Purpose: Automatically maintain ordinary forward movement while explicitly activated.
Features:
* Dedicated toggle * Configurable keybind * Stop immediately when disabled * Stop safely when the game loses focus or the player becomes unavailable
9. BoatFly
Purpose: Boat movement diagnostics and practice tools.
Features:
* Detect whether the player is riding a boat * Display boat state and speed * Handle entering and exiting boats * Keep unsupported flight behavior disabled
10. ElytraSwaper
Purpose: Elytra equipment assistance.
Features:
* Detect equipped Elytra * Display equipment status * Provide supported equipment-slot assistance * Handle missing equipment and unavailable slots
Preserve the requested display name ElytraSwaper.
11. Climb
Purpose: Climbing-state information and practice tools.
Features:
* Detect ladders, vines, and supported climbable blocks * Display climbing state * Respect normal movement rules
12. Scaffold
Purpose: Assist with building and block-placement practice.
Features:
* Placement preview * Show the targeted placement location * Display selected block and available stack count * Highlight valid placement positions * Configurable preview color and distance * Handle missing blocks and invalid placement positions * Support manual placement and ordinary building mechanics * Do not falsely report that automatic placement is working when it is not implemented
Important: Player category must contain Scaffold, not SaveWalk.
---
5. WORLD CATEGORY
Implement these exact module names in this exact category:
13. Xray
Purpose: Highlight selected block types visually.
Features:
* Configurable block list * Highlight colors * Render-distance settings * Efficient rendering * Resource cleanup * Do not claim to reveal hidden server data that the client has not received
14. Fullbright
Purpose: Improve visibility in dark environments.
Features:
* Configurable brightness * Compatible client-side rendering * Restore the previous visual state when disabled
15. Freecam
Purpose: Detached-camera exploration and screenshots.
Features:
* Camera movement settings * Configurable camera speed * Restore the original camera when disabled * Do not move the actual player while the detached camera is active * Handle death, disconnects, and world changes safely
16. AutoMine
Purpose: Mining assistance.
Features:
* Detect targeted blocks * Display mining progress * Show block type and mining state * Display tool information * Respect normal block-breaking rules
17. Scaffold
Purpose: Provide a World-category building-placement utility if a separate implementation is needed.
Features:
* Placement visualization * Block availability information * Valid-position indicators * Reuse shared building utilities where appropriate * Avoid duplicate module IDs or conflicting settings
18. SpeedMine
Purpose: Display mining speed and progress.
Features:
* Mining progress meter * Tool effectiveness information * Configurable HUD * Respect normal block-breaking calculations
19. SaveWalk
Purpose: Help prevent accidental movement off ledges.
Features:
* Detect nearby ledges * Display safety warnings * Configurable visual or sound alerts * Manual safety toggle * Avoid unexpected movement or input changes
Important: World category must retain SaveWalk. It must be implemented as a separate World-category module with its own registration and settings. Do not replace it with Scaffold.
20. Antyafk
Purpose: Inactivity reminders for single-player and authorized environments.
Features:
* Inactivity timer * Warning notifications * Configurable reminder interval * Manual confirmation * No anti-cheat evasion or artificial server activity
Preserve the exact name Antyafk.
21. Autorespawn
Purpose: Assist with the ordinary respawn workflow.
Features:
* Detect the death screen * Configurable respawn reminder or supported normal respawn control * Handle hardcore mode * Do not falsely report that the player has respawned
22. Autoeat
Purpose: Help monitor hunger and food availability.
Features:
* Hunger indicator * Food-selection assistance * Configurable warning threshold * Inventory and food availability checks * Respect normal item-use mechanics
---
6. COMBAT CATEGORY
Create these exact module names in the Combat category.
Prioritize combat information, manual controls, and private-world practice. Do not implement multiplayer cheat automation or anti-cheat bypasses.
23. KillAura
Purpose: Combat-target information and practice.
Features:
* Target information display * Practice target selection in a private test environment * Distance and range visualization * Enable/disable control * Clearly distinguish practice visualization from actual automated attacks
24. MobAura
Purpose: Inspect nearby mobs.
Features:
* Display mob names and distances * Configurable entity filters * Highlight practice targets * No automatic attacks
25. BowAimbot
Purpose: Projectile-aim training.
Features:
* Projectile trajectory estimates * Target distance * Practice target selection * Manual aiming feedback * No automatic aiming or firing at multiplayer opponents
26. Reach
Purpose: Display interaction-distance information.
Features:
* Player-to-target distance * Configurable distance units * Visualize ordinary interaction range * Never claim to extend server-authorized reach
27. AimAssist
Purpose: Manual aiming practice.
Features:
* Crosshair feedback * Target-distance display * Private-world training targets * Accuracy statistics * No automatic tracking of multiplayer opponents
28. MaceSwap
Purpose: Assist with mace equipment preparation.
Features:
* Detect a mace in the inventory * Display equipment status * Supported manual equipment-slot assistance * Handle missing equipment
29. Macedamage
Purpose: Estimate mace damage.
Features:
* Display relevant attack attributes * Estimate damage using supported game mechanics * Explain estimate assumptions * Distinguish estimates from actual server results
30. AttributesSwap
Purpose: Compare equipment and attributes.
Features:
* Equipment comparison * Attack and movement attribute display * Manual equipment-selection assistance * Handle missing items
31. StunSlam
Purpose: Track mace-combat practice.
Features:
* Record practice attempts and outcomes * Display supported movement and impact information * Provide training feedback * Do not claim to force effects on other players
32. Autototem
Purpose: Assist with Totem of Undying inventory management.
Features:
* Detect available totems * Display offhand and hotbar state * Warn when no totem is available * Provide supported manual inventory assistance * Respect inventory and server interaction rules
33. AutoCrystal
Purpose: Crystal-combat practice information.
Features:
* Detect relevant crystals in the practice environment * Display distance * Show supported placement and damage estimates * Provide manual practice feedback * No automated attacks against multiplayer players
34. AutoAnchor
Purpose: Respawn-anchor practice information.
Features:
* Detect relevant anchors * Display item and distance information * Show supported damage estimates * Explain environment restrictions * No automated attacks against multiplayer players
---
7. ESP CATEGORY
35. ChestEsp
Purpose: Highlight visible chest locations.
Features:
* Configurable chest types * Highlight colors * Render-distance settings * Efficient block-entity handling * Clean rendering state when disabled
36. PlayerEsp
Purpose: Visualize players.
Features:
* Configurable outlines or bounding boxes * Name and distance labels * Color settings * Render-distance settings * Efficient entity iteration * Remove all ESP rendering when disabled
37. ItemEsp
Purpose: Highlight dropped items.
Features:
* Item-name labels * Distance labels * Configurable item filters * Highlight colors * Efficient rendering without unnecessary per-frame allocations
38. BlockEsp
Purpose: Highlight selected blocks.
Features:
* Configurable block list * Bounding-box rendering * Color and distance settings * Efficient updates * Resource cleanup
Use rendering APIs verified for Minecraft 1.21.11. Do not rely on incompatible or deprecated rendering methods.
---
8. RENDER CATEGORY
39. HUD
Purpose: Custom heads-up display.
Include:
* FPS counter * Coordinates * Direction * Movement-speed indicator * Target distance * Enabled-module list * Client watermark * Toggleable components * Configurable colors and positions * Adjustable scale
Do not display fabricated statistics.
40. Color
Purpose: Customize the client's appearance.
Include:
* Primary accent color * Secondary accent color * Button color * Text color * ESP colors * HUD colors * Live preview * Reset to defaults * Save and load settings
41. ClickGui
Purpose: Control the custom interface.
Include:
* Configurable keybind * Default Right Shift key * Category panels * Search * Scrolling * Module settings panel * GUI scale * Optional animations * Proper mouse-focus handling * Prevent accidental in-game input while using the GUI
---
9. CONFIGURATION AND SETTINGS
Implement persistent configuration.
Requirements:
* Save settings to the Minecraft config directory * Restore settings on launch * Save module keybinds * Save GUI scale and colors * Validate configuration values * Recover safely from corrupted or missing files * Preserve default values when settings are invalid * Avoid duplicate module registration
The Player Scaffold and World SaveWalk must remain separate modules with their correct categories.
If two modules share internal utilities, share the utility code rather than merging their category identities.
---
10. PERFORMANCE AND COMPATIBILITY
Requirements:
* Use verified Minecraft 1.21.11 APIs * Keep client-only code out of dedicated-server initialization * Avoid unnecessary dependencies * Avoid blocking the client thread * Handle missing player and world objects * Handle disconnects and dimension changes * Release rendering resources * Avoid memory leaks * Handle unsupported features gracefully * Document Android/PojavLauncher limitations * Document server-side permissions where required
No module should keep running after being disabled.
---
11. BUILD AND TESTING
Create automated tests where practical and perform real build verification when tools are available.
Test:
- Gradle configuration
- Source compilation
- Fabric metadata
- Minecraft 1.21.11 compatibility
- ClickGUI opening and closing
- Category navigation
- Every module registration
- Module enable and disable lifecycle
- Settings persistence
- Keybind persistence
- Corrupted configuration recovery
- World changes and disconnects
- Rendering cleanup
- Missing optional dependencies
- PojavLauncher compatibility where testable
- No duplicate module IDs
- Correct Player Scaffold registration
- Correct World SaveWalk registration
If compilation fails:
* Read the complete error log * Identify the incompatible API or dependency * Correct the source or dependency * Run the build again * Report any remaining failure honestly
Do not claim that something has been tested if it has not actually been tested.
---
12. REQUIRED DELIVERABLES
Produce:
- Complete project directory
- Gradle build files
- Fabric metadata
- All Java source files
- Custom ClickGUI
- Module manager and settings framework
- All requested module registrations
- HUD and color settings
- Configuration persistence
- Localization resources
- Tests where practical
- Installation instructions
- Build instructions
- Troubleshooting guide
- Module-by-module implementation status
- List of unsupported features and their limitations
- ZIP archive of the actual project, if file-generation tools are available
Do not provide a fake download link.
---
FINAL INSTRUCTION
Start by verifying all Minecraft 1.21.11 and Fabric dependency versions.
Then create the complete CubeStorm Client project. Implement every requested module to the extent technically supported, and clearly document any restricted or unsupported behavior.
The Player category must contain Scaffold instead of SaveWalk.
The World category must retain SaveWalk.
These must be separate category entries with the correct implementations. Build, test, fix, and document the project instead of stopping at a GUI mockup.
Prioritize working code, accurate compatibility, clean architecture, and honest test results.