📄
pasted-code-1791788721346.txt
txt
286 lines
▶
# PROJECT: PRESTIGE CLIENT — FULL RECREATION
## Minecraft Java 1.21.11 | Fabric | Java 21 | macOS Apple Silicon
You are an expert Minecraft client developer, Java engineer, Fabric mod developer, UI/UX designer, and performance engineer.
Your task is to build a complete, polished Minecraft client inspired by Prestige Client. Recreate its premium aesthetic, navigation, customization, HUD, module management, and overall user experience as faithfully as possible without copying proprietary source code or assets.
**IMPORTANT: Build a real, functional project, not a mockup, tutorial, or collection of incomplete code snippets.**
## 1. TECHNICAL REQUIREMENTS
- Minecraft Java Edition 1.21.11.
- Fabric Loader and Fabric API versions compatible with Minecraft 1.21.11.
- Java 21.
- Gradle with Fabric Loom.
- Must run on macOS, including Apple Silicon M-series Macs.
- Compatible with Prism Launcher.
- Proper `fabric.mod.json`, entrypoints, mixins where necessary, resources, and build configuration.
- Produce a working distributable JAR.
- Use correct Minecraft 1.21.11 mappings and APIs.
- Verify all dependencies and method signatures before implementing features.
- Never invent methods or use outdated Minecraft APIs.
## 2. PREMIUM CLIENT INTERFACE
Create an exceptionally polished interface.
Visual direction:
- Dark charcoal interface with subtle gradients.
- Refined orange and amber accent colors.
- Rounded panels, subtle borders, tasteful shadows, and clean typography.
- Smooth transitions, hover states, animated toggles, and responsive sliders.
- Consistent spacing and alignment.
- Minimal clutter and excellent readability.
- High-quality icons rather than emoji placeholders.
- No oversized text, overlapping panels, or unfinished-looking components.
The interface should feel like a professionally developed PvP client.
### Click GUI
Implement:
- A configurable keybind to open and close the interface.
- Searchable modules.
- Category navigation.
- Expandable module settings.
- Animated toggles.
- Sliders with editable numeric values.
- Dropdowns and color pickers.
- Keybind configuration.
- Reset-to-default buttons.
- Scrollable panels.
- Persistent settings.
- A responsive layout that works at different GUI scales and resolutions.
Categories:
1. Combat
2. Movement
3. Player
4. Render
5. HUD
6. World
7. Miscellaneous
8. Settings
The interface must be easy to navigate using both mouse and keyboard.
## 3. MODULE FRAMEWORK
Build a proper module-management architecture.
Every module must support:
- Unique name and description.
- Category.
- Enabled and disabled states.
- Toggle keybind.
- Configurable settings.
- Lifecycle methods.
- Error handling.
- Persistent configuration.
- Clear separation between UI and gameplay logic.
Implement reusable settings types:
- Boolean.
- Integer.
- Decimal.
- Enum.
- Color.
- Keybind.
- String.
Modules must register automatically through a central registry. Avoid giant classes containing the entire client.
## 4. COMBAT CATEGORY
Implement legitimate combat utilities and training features.
Include:
- CPS display.
- Attack cooldown indicator.
- Target information HUD.
- Hit-confirmation indicator.
- Reach measurement for private-world testing.
- Attack timing visualizer.
- Shield-break timing trainer.
- Combo counter.
- Click-pattern trainer.
- Combat statistics.
- Configurable crosshair.
- Target highlighting for designated practice dummies.
Keep experimental reach measurement and combat automation restricted to a controlled local test environment. Do not implement anti-cheat bypasses, packet manipulation intended to evade detection, or hidden combat automation for public multiplayer.
## 5. MOVEMENT CATEGORY
Implement:
- Movement speed display.
- Jump statistics.
- Sprint status HUD.
- Direction indicator.
- Coordinates and velocity display.
- Strafe-training visualizer.
- Practice tools for analyzing movement.
- Configurable movement keys and visual indicators.
Provide clear indicators when a feature is unavailable or incompatible with the current environment.
## 6. PLAYER CATEGORY
Implement:
- Armor durability HUD.
- Item durability warnings.
- Potion-effect display.
- Inventory status.
- Hunger and saturation information where available.
- Totem counter.
- Held-item information.
- Status-effect timers.
- Configurable positioning and scale.
## 7. RENDER CATEGORY
Implement:
- Custom crosshair editor.
- Hit-color effects.
- Damage indicators.
- Custom HUD colors.
- Entity highlighting for permitted practice targets.
- Configurable particles.
- FPS counter.
- Frame-time graph.
- Ping display.
- World information overlays.
- Visual customization settings.
Prioritize compatibility with Fabric rendering APIs and other common client-side mods.
## 8. HUD EDITOR
Create a complete HUD editor with:
- Drag-and-drop positioning.
- Element resizing.
- Visibility toggles.
- Scale controls.
- Alignment guides.
- Snap-to-grid.
- Preview mode.
- Reset layout.
- Separate saved layouts.
Include customizable widgets for:
- FPS.
- CPS.
- Coordinates.
- Ping.
- Keystrokes.
- Potion effects.
- Armor.
- Target information.
- Session statistics.
- Enabled modules.
Widgets must render correctly at different GUI scales and window sizes.
## 9. CONFIGURATION SYSTEM
Create a robust configuration system using JSON.
Requirements:
- Automatically create configuration files.
- Save settings when changed.
- Restore settings on restart.
- Validate configuration values.
- Recover gracefully from corrupted files.
- Support named profiles.
- Import and export configurations.
- Provide default settings.
- Never overwrite user configurations without permission.
## 10. PERFORMANCE
Optimize for macOS and Apple Silicon.
Requirements:
- Minimize allocations during rendering.
- Avoid unnecessary per-frame calculations.
- Avoid blocking the render thread.
- Cache reusable rendering data.
- Avoid excessive mixins.
- Keep animations lightweight.
- Ensure all HUD elements scale properly.
- Avoid memory leaks and unnecessary background threads.
The client should remain responsive while Minecraft is running at high frame rates.
## 11. KEYBINDS AND INPUT
Implement:
- Configurable GUI toggle key.
- Individual module keybinds.
- Keybind conflict detection.
- Rebindable keys.
- Support for mouse buttons where appropriate.
- Escape-to-close behavior.
- Reliable input handling that does not interfere with typing in text fields.
## 12. CODE QUALITY
Use a clean project structure, for example:
`src/main/java/`:
- `client/` — initialization and main client.
- `module/` — module framework.
- `module/combat/`
- `module/movement/`
- `module/player/`
- `module/render/`
- `module/hud/`
- `gui/` — click GUI and components.
- `config/` — serialization and profiles.
- `input/` — keybinds.
- `render/` — shared rendering utilities.
- `util/` — reusable helpers.
Adapt the structure when a better architecture is justified.
Do not create empty placeholder classes and claim that the features are finished.
## 13. BUILD AND TESTING
Before declaring the project complete:
1. Verify the Minecraft and Fabric versions.
2. Generate all required source files.
3. Compile the complete project.
4. Fix every compilation error.
5. Run available automated tests.
6. Verify configuration loading and saving.
7. Verify the GUI opens and closes.
8. Test keybinds and module toggles.
9. Inspect the final JAR contents.
10. Provide exact installation instructions for Prism Launcher on macOS.
If a feature cannot be implemented reliably, explain why and implement the closest working alternative.
## 14. REQUIRED DELIVERABLES
Provide:
- Complete source code.
- Gradle wrapper and build files.
- Fabric metadata.
- All required resources.
- Configuration examples.
- A README.
- Build instructions.
- Installation instructions.
- A compiled JAR if the environment permits.
- A list of implemented and tested features.
## FINAL INSTRUCTION
Start implementing the project immediately. Work through the architecture, UI, modules, configuration system, and build process systematically.
Prioritize a beautiful, intuitive interface and reliable implementation over adding a large number of broken features.
Do not stop after producing a plan. Create the actual project, compile it, resolve errors, and report exactly what works.
Scaffold a client-only Fabric 1.21.11 project.
Add a reusable module/settings framework and persistent JSON config.
Implement practice-focused HUD utilities and input bindings.
Build the owo-ui click GUI, then add resources and usage documentation.
Created the Fabric 1.21.11 client project with an owo-ui click GUI, a module/settings framework, and persistent JSON configuration.
Implemented: searchable category tabs, module toggles and key rebinding; HUD modules for FPS, coordinates, movement speed, sprint status, and keystrokes; editable HUD positions and colors; debounced config saves, named-profile and import/export APIs, and safeguards against overwriting malformed configs. No combat automation, packet manipulation, or anti-cheat bypasses are included.
Not implemented yet: the requested combat and target-training utilities, armor/potion/ping HUDs, HUD drag-and-snap editor, and populated modules for categories other than HUD. I have not verified a successful compile or runtime test, so this is a functional foundation—not the complete feature list in the brief.
To get the JAR:
Click Compile in Kodari’s top bar; on a phone, tap ⋮ → Compile Project.
Click Compile in the window that opens.
After success, click Download. In Prism Launcher, add the JAR to the Mods tab of a Fabric 1.21.11 instance. Install Fabric API; owo-lib is bundled with the download.
package dev.kodari.emberclient;
import net.fabricmc.api.ClientModInitializer;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
public final class EmberClient implements ClientModInitializer {
public static final String MOD_ID = "emberclient";
public static final Logger LOGGER = LoggerFactory.getLogger(MOD_ID);
@Override
public void onInitializeClient() {
ClientRuntime.initialize();
}
}