blue-client-v43

byQasim DevMC

Thing to modify: https://cdn.droptocdn.com/files/ad59122e-9ae3-45f2-a951-0c6a5eed76a4/blue-client-v43.zip The prompt is attached.

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document

1. Introduction

This document specifies the requirements for a master engineering, stability, performance, UI, and content overhaul of Blue Client — a custom Minecraft client developed for the Blue Network ecosystem.

Blue Client is intended to be a polished custom client that feels like a single cohesive product, not a random collection of modules. The overhaul must make Blue Client substantially more stable, performant, polished, customizable, and complete while keeping the implementation maintainable.

This is not a request to blindly add features. It is a deliberate sequence: inspect the existing client and evidence, diagnose real problems and their causes, design a master engineering plan and detailed implementation specification, review that specification for unnecessary work, then execute, test, fix, and package.

The requirements below preserve every explicit capability, constraint, control rule, workflow, phase, and delivery item from the source material.

Page 1 of 44

2. System Overview

Blue Client is a Fabric-based Minecraft client built for the Blue Network. It provides PvP functionality, performance improvements, a module system, HUD functionality, custom interfaces, cosmetics, emotes, Blue Network integration, customization, and quality-of-life features.

Project Identity

AttributeValue
NameBlue Client
EcosystemBlue Network
Primary Minecraft VersionMinecraft 1.21.11
Mod LoaderFabric

Blue Network Resources

ResourceValue
Discordhttps://discord.gg/DmEPAb3NFU
Xhttps://x.com/bluewuztaken
Logohttps://i.postimg.cc/BnJqF9X0/Blue-Network-Logo-New.png
Minecraft Serverplay.sennahosting.com

External resources must not be unnecessarily embedded into the client, unnecessary network requests must not be made, and secrets must not be hardcoded.

Page 2 of 44

Known Current Issue (highest priority): The attached logs contain a serious Blue Client problem. The log shows blueclient.mixins.json:BlockEntityRenderManagerMixin failing to apply because the injection descriptor does not match the target method. The log reports an expected parameter type different from the injected Object parameter, resulting in an InvalidInjectionException. This must be fixed first, and no new features may be built on top of a known broken initialization path.

Attached material is evidence. Attached material represents the current state of Blue Client and/or its runtime environment. It must be treated as evidence. Not every warning is necessarily caused by Blue Client; the SRD requires distinguishing between (a) Blue Client problems and (b) problems caused by other mods, resource packs, Fabric, the environment, or unrelated software.

Delivery shape: An engineering overhaul producing a compiled Blue Client JAR, source, conditional backend and database schema, assets, documentation, progress notes, version folders, and a final ZIP.

Deliverable type (authoritative): The primary deliverable is a JAR file — a compiled Fabric Minecraft client mod for the Blue Network, not a website. All design, user flows, and functionality must target the Java/Fabric client and remain compatible with the Java Runtime Environment (JRE). Website-specific technologies such as HTML, CSS, and JavaScript are not the product output and must not be produced as the deliverable, except where the JAR itself legitimately embeds web technologies. All project artifacts, workflows, and documentation must recognize and refer to the JAR deliverable, avoiding misalignment with website or web-service outputs.

3. Functional Requirements

Page 3 of 44

3.1 Diagnosis, Planning & Engineering Process

  • FR-1.1 As the lead engineer, I want to inspect the attached project/source/files before coding, so that changes are grounded in the actual current state.
  • FR-1.2 As the lead engineer, I want to inspect the attached logs and evidence before coding, so that problems are identified from real runtime data.
  • FR-1.3 As the lead engineer, I want to understand the current Blue Client architecture, so that changes fit the existing design.
  • FR-1.4 As the lead engineer, I want to identify the actual problems in the client, so that work targets real defects.
  • FR-1.5 As the lead engineer, I want to identify the causes of those problems, so that fixes address root causes rather than symptoms.
  • FR-1.6 As the lead engineer, I want to determine what is already implemented, so that working systems are preserved.
  • FR-1.7 As the lead engineer, I want to determine what is broken, so that those systems are prioritized for repair.
  • FR-1.8 As the lead engineer, I want to determine what should be preserved, so that working functionality is not disturbed.
  • FR-1.9 As the lead engineer, I want to determine what should be rewritten, so that unrecoverable systems are rebuilt deliberately.
  • FR-1.10 As the lead engineer, I want to determine what should be optimized, so that performance work is targeted.
  • FR-1.11 As the lead engineer, I want to determine what should be removed or simplified, so that unnecessary complexity is reduced.
  • FR-1.12 As the lead engineer, I want to design a complete implementation strategy, so that the overhaul proceeds in a coherent sequence.
  • FR-1.13 As the lead engineer, I want to create an internal BLUE CLIENT MASTER ENGINEERING PLAN, so that engineering direction is documented.
Page 4 of 44
  • FR-1.14 As the lead engineer, I want to turn that plan into a detailed implementation prompt/specification, so that execution is precise.
  • FR-1.15 As the lead engineer, I want to review my own plan for unnecessary work and credit usage, so that the resource budget is respected.
  • FR-1.16 As the lead engineer, I want to begin making changes only after the plan and specification exist, so that coding is not started blindly from the requirement set.
  • FR-1.17 As the lead engineer, I want to think and act like the lead engineer responsible for the entire client, so that cross-cutting decisions are coherent.
  • FR-1.18 As the lead engineer, I want the deliverable to be treated as a JAR file (a Fabric Minecraft client mod) rather than a website, so that all design, user flows, and functionality target the Java/Fabric client and remain compatible with the Java Runtime Environment (JRE).
  • FR-1.19 As the lead engineer, I want website-specific technologies such as HTML, CSS, and JavaScript to not be produced as the product output, so that effort is not spent building toward the wrong packaging target; this does not prohibit the JAR from legitimately embedding web technologies where required.
  • FR-1.20 As the lead engineer, I want all project artifacts, workflows, and documentation to recognize and refer to the JAR deliverable, so that no artifact is misaligned with website or web-service outputs.
Page 5 of 44

3.2 Diagnosis Audit Scope

  • FR-2.1 As the lead engineer, I want the diagnosis to inspect Gradle configuration, so that build integrity is understood.
  • FR-2.2 As the lead engineer, I want the diagnosis to inspect Fabric Loom, so that the mod development toolchain is understood.
  • FR-2.3 As the lead engineer, I want the diagnosis to inspect Minecraft mappings, so that mapping correctness is verified.
  • FR-2.4 As the lead engineer, I want the diagnosis to inspect Fabric Loader, so that loader compatibility is understood.
  • FR-2.5 As the lead engineer, I want the diagnosis to inspect Fabric API, so that API usage is understood.
  • FR-2.6 As the lead engineer, I want the diagnosis to inspect entrypoints, so that initialization wiring is verified.
  • FR-2.7 As the lead engineer, I want the diagnosis to inspect mixins, so that injection correctness is verified.
  • FR-2.8 As the lead engineer, I want the diagnosis to inspect client initialization, so that startup flow is understood.
  • FR-2.9 As the lead engineer, I want the diagnosis to inspect the module framework, so that the module system is understood.
  • FR-2.10 As the lead engineer, I want the diagnosis to inspect module registration, so that registration counts and behavior are understood.
  • FR-2.11 As the lead engineer, I want the diagnosis to inspect the settings framework, so that setting handling is understood.
  • FR-2.12 As the lead engineer, I want the diagnosis to inspect the GUI framework, so that interface structure is understood.
  • FR-2.13 As the lead engineer, I want the diagnosis to inspect the rendering framework, so that draw paths are understood.
  • FR-2.14 As the lead engineer, I want the diagnosis to inspect the HUD, so that HUD rendering is understood.
Page 6 of 44
  • FR-2.15 As the lead engineer, I want the diagnosis to inspect the pause menu, so that its structure is understood.
  • FR-2.16 As the lead engineer, I want the diagnosis to inspect the Right Shift menu, so that the ClickGUI structure is understood.
  • FR-2.17 As the lead engineer, I want the diagnosis to inspect the configuration system, so that persistence behavior is understood.
  • FR-2.18 As the lead engineer, I want the diagnosis to inspect networking, so that client/server communication is understood.
  • FR-2.19 As the lead engineer, I want the diagnosis to inspect assets, so that bundled resources are understood.
  • FR-2.20 As the lead engineer, I want the diagnosis to inspect textures, so that visual resources are understood.
  • FR-2.21 As the lead engineer, I want the diagnosis to inspect fonts, so that typography resources are understood.
  • FR-2.22 As the lead engineer, I want the diagnosis to inspect sounds, so that audio resources are understood.
  • FR-2.23 As the lead engineer, I want the diagnosis to inspect cosmetics, so that cosmetic systems are understood.
  • FR-2.24 As the lead engineer, I want the diagnosis to inspect existing emote code, so that prior emote work is understood.
  • FR-2.25 As the lead engineer, I want the diagnosis to inspect existing Blue Network integration, so that server-side integration is understood.
  • FR-2.26 As the lead engineer, I want the diagnosis to inspect backend code, so that any existing backend is understood.
  • FR-2.27 As the lead engineer, I want the diagnosis to inspect configuration storage, so that stored data layout is understood.
  • FR-2.28 As the lead engineer, I want the diagnosis to inspect performance-sensitive code, so that optimization targets are known.
  • FR-2.29 As the lead engineer, I want the diagnosis to focus on Blue Client's own code rather than exhaustively inspecting every dependency, so that effort is not wasted.
Page 7 of 44

3.3 Master Engineering Plan Phases

Page 8 of 44
  • FR-3.1 As the lead engineer, I want a Phase 0: Baseline and recovery in the master plan, so that a recovery point is established.
  • FR-3.2 As the lead engineer, I want a Phase 1: Crash and stability fixes in the master plan, so that the client launches reliably.
  • FR-3.3 As the lead engineer, I want a Phase 2: Performance investigation and optimization in the master plan, so that real performance problems are addressed.
  • FR-3.4 As the lead engineer, I want a Phase 3: Core architecture cleanup in the master plan, so that the codebase is made maintainable.
  • FR-3.5 As the lead engineer, I want a Phase 4: UI/UX overhaul in the master plan, so that the interface is unified.
  • FR-3.6 As the lead engineer, I want a Phase 5: Module/settings overhaul in the master plan, so that modules and settings are complete.
  • FR-3.7 As the lead engineer, I want a Phase 6: Pause menu and Right Shift overhaul in the master plan, so that core interfaces are rebuilt.
  • FR-3.8 As the lead engineer, I want a Phase 7: Emote system in the master plan, so that the emote framework is built.
  • FR-3.9 As the lead engineer, I want a Phase 8: Blue Stars in the master plan, so that the cosmetic currency is built.
  • FR-3.10 As the lead engineer, I want a Phase 9: Cosmetic shop in the master plan, so that the shop is built.
  • FR-3.11 As the lead engineer, I want a Phase 10: Backend integration where required in the master plan, so that server authority is added only where needed.
  • FR-3.12 As the lead engineer, I want a Phase 11: Testing in the master plan, so that verification is planned.
  • FR-3.13 As the lead engineer, I want a Phase 12: Packaging/documentation in the master plan, so that delivery is planned.
  • FR-3.14 As the lead engineer, I want the ability to change this order if analysis shows a better technical sequence, so that the plan reflects the actual project rather than a blind checklist.
Page 9 of 44

3.4 Implementation Specification Content

Page 10 of 44
  • FR-4.1 As the lead engineer, I want the implementation specification to answer what exactly needs changing, so that scope is explicit.
  • FR-4.2 As the lead engineer, I want the specification to answer which files need changing, so that work is targeted.
  • FR-4.3 As the lead engineer, I want the specification to answer why changes are needed, so that rationale is preserved.
  • FR-4.4 As the lead engineer, I want the specification to answer what can remain untouched, so that working code is protected.
  • FR-4.5 As the lead engineer, I want the specification to answer what is causing the crash, so that the crash is understood before fixing.
  • FR-4.6 As the lead engineer, I want the specification to answer what is causing performance problems, so that optimization is grounded.
  • FR-4.7 As the lead engineer, I want the specification to answer which systems are expensive, so that cost centers are identified.
  • FR-4.8 As the lead engineer, I want the specification to answer which UI components need rebuilding, so that UI scope is defined.
  • FR-4.9 As the lead engineer, I want the specification to answer which modules lack settings, so that module work is scoped.
  • FR-4.10 As the lead engineer, I want the specification to answer what the new settings architecture should look like, so that settings are designed coherently.
  • FR-4.11 As the lead engineer, I want the specification to answer how emotes should work, so that the emote framework is designed.
  • FR-4.12 As the lead engineer, I want the specification to answer how Blue Stars should work, so that the currency is designed.
  • FR-4.13 As the lead engineer, I want the specification to answer what needs backend authority, so that trust boundaries are defined.
  • FR-4.14 As the lead engineer, I want the specification to answer how the final result will be tested, so that verification is defined up front.
  • FR-4.15 As the lead engineer, I want to make normal engineering decisions without requiring user approval unless a genuine decision is needed, so that the project is not blocked.
Page 11 of 44

3.5 Stability Fixes

Page 12 of 44
  • FR-5.1 As a player, I want Minecraft to launch reliably with Blue Client installed, so that the client is usable.
  • FR-5.2 As a player, I want Blue Client to initialize correctly, so that its systems start up.
  • FR-5.3 As a player, I want existing Blue Client functionality to work, so that prior features are not lost.
  • FR-5.4 As the lead engineer, I want mixin crashes fixed, so that injection failures do not abort startup.
  • FR-5.5 As the lead engineer, I want invalid injections fixed, so that mixins apply against correct descriptors.
  • FR-5.6 As the lead engineer, I want broken entrypoints fixed, so that initialization wiring is correct.
  • FR-5.7 As the lead engineer, I want initialization failures fixed, so that the client starts cleanly.
  • FR-5.8 As the lead engineer, I want configuration crashes fixed, so that config loading/saving is safe.
  • FR-5.9 As the lead engineer, I want rendering crashes fixed, so that the render path is stable.
  • FR-5.10 As the lead engineer, I want module registration crashes fixed, so that modules register reliably.
  • FR-5.11 As the lead engineer, I want settings crashes fixed, so that settings handling is safe.
  • FR-5.12 As the lead engineer, I want null states eliminated, so that missing values do not cause faults.
  • FR-5.13 As the lead engineer, I want broken lifecycle handling fixed, so that init/teardown ordering is correct.
  • FR-5.14 As the lead engineer, I want the specific BlockEntityRenderManagerMixin InvalidInjectionException fixed first, so that the known broken initialization path is repaired before anything is built on top of it.
  • FR-5.15 As the lead engineer, I want new features layered only after Blue Client launches, initializes, and existing functionality works, so that stability precedes expansion.
Page 13 of 44

3.6 Performance

  • FR-6.1 As the lead engineer, I want render thread workload investigated, so that render cost is reduced where costly.
  • FR-6.2 As the lead engineer, I want client tick workload investigated, so that per-tick cost is reduced where costly.
  • FR-6.3 As the lead engineer, I want module update frequency investigated, so that modules do not run more often than needed.
  • FR-6.4 As the lead engineer, I want entity scanning investigated, so that scanning cost is bounded.
  • FR-6.5 As the lead engineer, I want block/entity rendering investigated, so that rendering is efficient.
  • FR-6.6 As the lead engineer, I want HUD rendering investigated, so that HUD draw cost is acceptable.
  • FR-6.7 As the lead engineer, I want GUI rendering investigated, so that GUI draw cost is acceptable.
  • FR-6.8 As the lead engineer, I want animations investigated for cost, so that animation work is bounded.
  • FR-6.9 As the lead engineer, I want particle systems investigated for cost, so that particle work is bounded.
  • FR-6.10 As the lead engineer, I want target finding investigated, so that target computation is not wasteful.
  • FR-6.11 As the lead engineer, I want repeated calculations identified, so that redundant work is removed.
  • FR-6.12 As the lead engineer, I want allocations investigated, so that avoidable allocation is reduced.
  • FR-6.13 As the lead engineer, I want garbage generation investigated, so that GC pressure is reduced.
  • FR-6.14 As the lead engineer, I want collections usage investigated, so that data structures are appropriate.
Page 14 of 44
  • FR-6.15 As the lead engineer, I want configuration access investigated, so that frequent config reads are handled cheaply.
  • FR-6.16 As the lead engineer, I want filesystem access investigated, so that unnecessary I/O is eliminated.
  • FR-6.17 As the lead engineer, I want networking behavior investigated, so that unnecessary traffic is eliminated.
  • FR-6.18 As the lead engineer, I want mixins assessed for performance impact, so that injection overhead is controlled.
  • FR-6.19 As the lead engineer, I want event registration investigated, so that handlers are not duplicated or excessive.
  • FR-6.20 As the lead engineer, I want duplicated work eliminated, so that identical computation is not repeated.
  • FR-6.21 As the lead engineer, I want unnecessary polling removed, so that work is event-driven where possible.
Page 15 of 44

3.7 Performance Methodology & Budget

  • FR-7.1 As the lead engineer, I want to identify each expensive operation, so that optimization starts from facts.
  • FR-7.2 As the lead engineer, I want to determine how often each expensive operation runs, so that frequency is known.
  • FR-7.3 As the lead engineer, I want to determine whether it needs to run that often, so that unnecessary frequency is removed.
  • FR-7.4 As the lead engineer, I want to determine each operation's cost, so that priorities are justified.
  • FR-7.5 As the lead engineer, I want to determine whether results can be cached, so that repeated work is avoided.
  • FR-7.6 As the lead engineer, I want to determine whether work can become event-driven, so that polling is replaced where appropriate.
  • FR-7.7 As the lead engineer, I want to determine whether work can be reduced, so that computation is minimized.
  • FR-7.8 As the lead engineer, I want to implement the smallest safe optimization, so that risk is minimized.
  • FR-7.9 As the lead engineer, I want to test again after each optimization, so that results are verified.
  • FR-7.10 As the lead engineer, I want to avoid optimizing code purely because it "looks inefficient," so that effort targets measured cost.
  • FR-7.11 As the lead engineer, I want Blue Client to coexist properly with performance mods such as Sodium/ImmediatelyFast when present, so that the rendering pipeline is not fought.
  • FR-7.12 As the lead engineer, I want to avoid replacing efficient rendering systems with slower custom rendering, so that performance is not regressed.
  • FR-7.13 As the lead engineer, I want to avoid duplicating chunk rendering, so that rendering cost is not doubled.
Page 16 of 44
  • FR-7.14 As the lead engineer, I want to avoid unnecessary render passes, so that frame cost stays low.
  • FR-7.15 As the lead engineer, I want expensive calculations performed beforehand rather than during rendering, so that the render thread is not burdened.
  • FR-7.16 As the lead engineer, I want every new feature to have a performance budget, so that features do not degrade performance.
  • FR-7.17 As the lead engineer, I want animations to not create hundreds of objects every frame, so that animation cost is bounded.
  • FR-7.18 As the lead engineer, I want cosmetics to not continuously perform expensive scans, so that cosmetic overhead is bounded.
  • FR-7.19 As the lead engineer, I want the shop to perform shop logic only while relevant UI is open, so that idle shop cost is zero.

3.8 Platform Compatibility (Rendering Integrations)

  • FR-8.1 As the lead engineer, I want Blue Client to work alongside the Sodium-oriented rendering integration present in the attached environment, so that both systems operate together.
  • FR-8.2 As the lead engineer, I want Blue Client to remain compatible with performance mods when present, so that the client does not conflict with common optimization mods.

3.9 UI/UX Overhaul

Page 17 of 44
  • FR-9.1 As a player, I want UI centering fixed, so that elements appear where expected.
  • FR-9.2 As a player, I want UI spacing fixed, so that layout is consistent.
  • FR-9.3 As a player, I want UI padding fixed, so that content is not cramped or clipped.
  • FR-9.4 As a player, I want UI sizing fixed, so that components are consistently proportioned.
  • FR-9.5 As a player, I want UI scaling fixed, so that the interface renders correctly at different scales.
  • FR-9.6 As a player, I want UI alignment fixed, so that elements line up correctly.
  • FR-9.7 As a player, I want UI clipping fixed, so that content is not cut off incorrectly.
  • FR-9.8 As a player, I want text positioning fixed, so that text renders in the correct place.
  • FR-9.9 As a player, I want UI animations fixed, so that motion is correct and consistent.
  • FR-9.10 As a player, I want hover effects fixed, so that hover feedback is accurate.
  • FR-9.11 As a player, I want click states fixed, so that interaction feedback is correct.
  • FR-9.12 As a player, I want scrolling fixed, so that scrollable content behaves correctly.
  • FR-9.13 As a player, I want transitions fixed, so that state changes are smooth.
  • FR-9.14 As a player, I want responsive layouts, so that the interface adapts properly.
  • FR-9.15 As a player, I want the UI to feel like one product, so that the client does not look like a collection of separate parts.
Page 18 of 44

3.10 Right Shift Menu / ClickGUI

  • FR-10.1 As a player, I want category navigation to work correctly, so that I can move between module categories.
  • FR-10.2 As a player, I want module cards to render and behave correctly, so that modules are presented clearly.
  • FR-10.3 As a player, I want search to work correctly, so that I can find modules quickly.
  • FR-10.4 As a player, I want scrolling to work correctly in the ClickGUI, so that I can browse the full module list.
  • FR-10.5 As a player, I want settings to be reachable from the ClickGUI, so that I can configure modules.
  • FR-10.6 As a player, I want toggles to work correctly, so that modules can be enabled and disabled.
  • FR-10.7 As a player, I want hover states to be accurate, so that hover corresponds to actual component bounds.
  • FR-10.8 As a player, I want click handling to be correct, so that clicks act on the intended component.
  • FR-10.9 As a player, I want ClickGUI animations to be correct, so that motion is smooth and consistent.
  • FR-10.10 As a player, I want hitboxes to match visible components, so that there are no phantom hover areas and no click regions that differ from what I see.
  • FR-10.11 As a player, I want resizing to behave correctly, so that the ClickGUI adapts without breaking layout.
  • FR-10.12 As a player, I want centering to be correct, so that the ClickGUI is positioned properly.
  • FR-10.13 As a player, I want no buttons to visually respond when the mouse is elsewhere, so that feedback is truthful.
Page 19 of 44

3.11 Custom Pause Menu

  • FR-11.1 As a player, I want a clean custom pause menu, so that it looks polished.
  • FR-11.2 As a player, I want a responsive custom pause menu, so that it adapts correctly.
  • FR-11.3 As a player, I want a centered custom pause menu, so that its layout is correct.
  • FR-11.4 As a player, I want an animated custom pause menu, so that it feels part of the client.
  • FR-11.5 As a player, I want the pause menu consistent with Blue Client's design, so that the experience is unified.
  • FR-11.6 As a player, I want the pause menu to remain functional, so that standard actions still work.
  • FR-11.7 As a player, I want necessary Minecraft functionality preserved, so that no vanilla functionality is removed without a suitable replacement.
Page 20 of 44

3.12 Module System Audit

  • FR-12.1 As the lead engineer, I want to determine what "112 modules" represents, so that the reported count is explained.
  • FR-12.2 As the lead engineer, I want to determine what "41 modules registered" represents, so that the registration count is explained.
  • FR-12.3 As the lead engineer, I want to determine whether modules are loaded lazily, so that load behavior is understood.
  • FR-12.4 As the lead engineer, I want to determine whether there are duplicate registries, so that duplication is ruled out or removed.
  • FR-12.5 As the lead engineer, I want to determine whether some modules come from another system, so that origins are established.
  • FR-12.6 As the lead engineer, I want to determine whether initialization is inconsistent, so that the discrepancy is resolved.
  • FR-12.7 As the lead engineer, I want to audit the actual module architecture, so that the module system is coherent.
Page 21 of 44

3.13 Module Settings

  • FR-13.1 As the lead engineer, I want to audit modules individually, so that each module is reviewed.
  • FR-13.2 As the lead engineer, I want to understand each module's purpose, so that appropriate settings can be defined.
  • FR-13.3 As the lead engineer, I want to identify the settings each module logically requires, so that missing settings are added.
  • FR-13.4 As the lead engineer, I want to implement those settings, so that modules are configurable.
  • FR-13.5 As the lead engineer, I want settings connected to actual behavior, so that settings have real effects.
  • FR-13.6 As the lead engineer, I want settings to persist, so that configuration survives restarts.
  • FR-13.7 As the lead engineer, I want sensible defaults, so that modules work out of the box.
  • FR-13.8 As the lead engineer, I want the UI to display settings correctly, so that users can edit them.
  • FR-13.9 As the lead engineer, I want to never add fake settings, so that a setting that does nothing is treated as a bug.
Page 22 of 44

3.14 Settings Types

  • FR-14.1 As a user, I want Boolean settings supported where appropriate, so that toggle options can be configured.
  • FR-14.2 As a user, I want Integer settings supported where appropriate, so that whole-number options can be configured.
  • FR-14.3 As a user, I want Decimal settings supported where appropriate, so that fractional options can be configured.
  • FR-14.4 As a user, I want Slider settings supported where appropriate, so that ranged values can be adjusted.
  • FR-14.5 As a user, I want Enum settings supported where appropriate, so that fixed option sets can be selected.
  • FR-14.6 As a user, I want Mode settings supported where appropriate, so that operation modes can be selected.
  • FR-14.7 As a user, I want Color settings supported where appropriate, so that colors can be configured.
  • FR-14.8 As a user, I want Keybind settings supported where appropriate, so that keys can be bound.
  • FR-14.9 As a user, I want Text settings supported where appropriate, so that text input can be configured.
  • FR-14.10 As a user, I want Multi-select settings supported where appropriate, so that multiple options can be chosen.
  • FR-14.11 As a user, I want Range settings supported where appropriate, so that ranges can be configured.
  • FR-14.12 As a user, I want Timing settings supported where appropriate, so that timing values can be configured.
  • FR-14.13 As a user, I want Target mode settings supported where appropriate, so that target selection modes can be configured.
  • FR-14.14 As the lead engineer, I want not every module to have every setting type, so that settings remain meaningful.
Page 23 of 44

3.15 Settings UI

  • FR-15.1 As a user, I want the settings interface to support many settings, so that complex modules remain configurable.
  • FR-15.2 As a user, I want the settings interface to support scrolling, so that long settings lists are navigable.
  • FR-15.3 As a user, I want the settings interface to support descriptions, so that I understand each setting.
  • FR-15.4 As a user, I want the settings interface to support tooltips, so that additional help is available.
  • FR-15.5 As a user, I want the settings interface to support sliders, so that value ranges can be adjusted.
  • FR-15.6 As a user, I want the settings interface to support toggles, so that booleans can be switched.
  • FR-15.7 As a user, I want the settings interface to support dropdowns, so that enumerated options can be selected.
  • FR-15.8 As a user, I want the settings interface to support keybinds, so that keys can be assigned.
  • FR-15.9 As a user, I want the settings interface to support colors, so that colors can be picked.
  • FR-15.10 As a user, I want the settings interface to support enums, so that fixed option sets can be chosen.
  • FR-15.11 As a user, I want the settings interface to support reset/default behavior, so that I can restore defaults.
  • FR-15.12 As a user, I want the settings interface to support responsive positioning, so that it lays out correctly.
  • FR-15.13 As a user, I want excessive visual complexity avoided, so that settings remain clear.
Page 24 of 44

3.16 Emote System — Framework

  • FR-16.1 As a player, I want a proper emote system built once the core client is stable, so that expressive content is available.
  • FR-16.2 As the lead engineer, I want a reusable emote system rather than 20 hardcoded separate systems, so that the framework is maintainable.
  • FR-16.3 As the lead engineer, I want each emote to have a unique ID, so that emotes are individually addressable.
  • FR-16.4 As a player, I want each emote to have a display name, so that it is identified in the interface.
  • FR-16.5 As a player, I want each emote to have a rarity, so that presentation and organization are possible.
  • FR-16.6 As a player, I want each emote to have a price, so that it can be purchased.
  • FR-16.7 As a player, I want each emote to have a preview, so that I can see it before acquiring it.
  • FR-16.8 As a player, I want each emote to have an unlock state, so that I know whether I own it.
  • FR-16.9 As a player, I want each emote to have an equipped state, so that I know which one is active.
  • FR-16.10 As a player, I want each emote to have an animation/state, so that it plays correctly.
  • FR-16.11 As a player, I want each emote to have a proper UI representation, so that it displays consistently.

3.17 Emote System — Content (20 Initial Emotes)

Page 25 of 44
  • FR-17.1 As a player, I want 20 initial emotes created, so that there is a substantial starting collection.
  • FR-17.2 As a player, I want the initial collection to avoid being 20 boring variations of the same animation, so that emotes feel varied.
  • FR-17.3 As a player, I want recognizable/fun emotes included, so that the collection is enjoyable.
  • FR-17.4 As a player, I want a Griddy-style dance emote, so that a popular dance concept is represented.
  • FR-17.5 As a player, I want a dance emote, so that a general dance option exists.
  • FR-17.6 As a player, I want celebratory emotes, so that I can express celebration.
  • FR-17.7 As a player, I want funny reactions, so that I can express humor.
  • FR-17.8 As a player, I want victory poses, so that I can celebrate wins.
  • FR-17.9 As a player, I want meme-style reactions, so that community-style expression is available.
  • FR-17.10 As the lead engineer, I want copyrighted character animations, branded assets, or ripped animations from another client to not be copied, so that the collection is original and legally safe.
  • FR-17.11 As a player, I want a significant portion of the collection to be genuinely original Blue Client-style concepts, so that the emotes feel brand-native.
  • FR-17.12 As a player, I want original Blue Client-style emotes such as Blue Energy, Blue Bounce, Blue Victory, Pixel Shuffle, Network Wave, Blue Spin, Cosmic Float, GG Celebration, Glitch Dance, and Victory Flex, so that the collection reflects the Blue Client aesthetic.
  • FR-17.13 As a player, I want the emote collection designed around the actual Blue Client aesthetic, so that emotes feel like Blue Client cosmetics rather than random Minecraft mod animations.
Page 26 of 44

3.18 Emote Rarities

  • FR-18.1 As a player, I want emote rarities such as Common, Uncommon, Rare, Epic, and Legendary, so that the collection is tiered.
  • FR-18.2 As a player, I want rarity to be cosmetic only and not affect gameplay, so that fairness is preserved.
  • FR-18.3 As a player, I want rarity used for shop presentation, so that items are presented by tier.
  • FR-18.4 As a player, I want rarity used for collection organization, so that emotes are grouped sensibly.
  • FR-18.5 As a player, I want rarity used for visual styling, so that tiers are visually distinguishable.
  • FR-18.6 As a player, I want rarity used for pricing, so that tiers have differentiated cost.

3.19 Blue Stars Economy

  • FR-19.1 As a player, I want Blue Stars added as the Blue Client cosmetic currency, so that cosmetics can be acquired.
  • FR-19.2 As a player, I want 1 Blue Star to equal 1 minute played on Blue Network, so that the economy is tied to playtime.
  • FR-19.3 As a player, I want Blue Star playtime earnings to be credited through the intended architecture on play.sennahosting.com, so that rewards are legitimate.
Page 27 of 44

3.20 Blue Stars Security

  • FR-20.1 As the lead engineer, I want the client not to be trusted with authoritative economy data, so that a modified client cannot claim arbitrary playtime (e.g., "I played 10,000 minutes").
  • FR-20.2 As the lead engineer, I want the client not to be trusted with authoritative balances, so that a modified client cannot assert an arbitrary balance (e.g., "My balance is 999,999").
  • FR-20.3 As the lead engineer, I want the design to use server-side verification where required, so that economy integrity is enforced.
  • FR-20.4 As the lead engineer, I want secure authentication if a backend is needed, so that only legitimate requests are accepted.
  • FR-20.5 As the lead engineer, I want player identity validated, so that balances attach to the correct player.
  • FR-20.6 As the lead engineer, I want playtime validated, so that rewards reflect actual play.
  • FR-20.7 As the lead engineer, I want purchases validated, so that only legitimate purchases are granted.
  • FR-20.8 As the lead engineer, I want duplicate transactions prevented, so that the same transaction cannot be applied twice.
  • FR-20.9 As the lead engineer, I want negative balances prevented, so that the system cannot go below zero.
  • FR-20.10 As the lead engineer, I want price manipulation prevented, so that prices cannot be altered by the client.
  • FR-20.11 As the lead engineer, I want replayed purchase requests prevented, so that requests cannot be re-executed.
  • FR-20.12 As the lead engineer, I want secrets not placed inside the client, so that sensitive data is not exposed.
Page 28 of 44

3.21 Cosmetic Shop

  • FR-21.1 As a player, I want a polished Blue Client cosmetic shop, so that cosmetics can be browsed and acquired.
  • FR-21.2 As a player, I want the shop to initially contain the 20 emotes, so that there is starting inventory.
  • FR-21.3 As a player, I want each shop item to show an icon/preview, so that I can see the cosmetic.
  • FR-21.4 As a player, I want each shop item to show a name, so that items are identifiable.
  • FR-21.5 As a player, I want each shop item to show a rarity, so that tier is visible.
  • FR-21.6 As a player, I want each shop item to show a price, so that I know the cost.
  • FR-21.7 As a player, I want each shop item to show an owned state, so that I know what I already own.
  • FR-21.8 As a player, I want each shop item to show an equipped state, so that I know what is active.
  • FR-21.9 As a player, I want each shop item to show a purchase state, so that I understand transaction state.
  • FR-21.10 As the lead engineer, I want the shop easy to expand later, so that new cosmetics can be added.
Page 29 of 44

3.22 Shop UX

  • FR-22.1 As a player, I want the shop to feel like part of Blue Client, so that it is not visually disconnected from the rest of the client.
  • FR-22.2 As a player, I want category navigation in the shop, so that I can browse by category.
  • FR-22.3 As a player, I want rarity presentation in the shop, so that tiers are communicated clearly.
  • FR-22.4 As a player, I want purchase confirmation, so that purchases are deliberate.
  • FR-22.5 As a player, I want an insufficient currency state, so that I understand when I cannot afford an item.
  • FR-22.6 As a player, I want an owned state, so that I can distinguish owned items.
  • FR-22.7 As a player, I want an equipped state, so that I can see and manage my equipped item.
  • FR-22.8 As a player, I want hover animation in the shop, so that interaction feels responsive.
  • FR-22.9 As a player, I want a preview in the shop, so that I can evaluate before purchasing.
Page 30 of 44

3.23 Backend

  • FR-23.1 As the lead engineer, I want backend infrastructure built only if required, so that unnecessary backend work is avoided.
  • FR-23.2 As the lead engineer, I want the backend to handle player ID, so that identity is recorded.
  • FR-23.3 As the lead engineer, I want the backend to handle playtime, so that Blue Stars can be earned legitimately.
  • FR-23.4 As the lead engineer, I want the backend to handle Blue Stars balances, so that currency is authoritative.
  • FR-23.5 As the lead engineer, I want the backend to handle owned emotes, so that ownership is authoritative.
  • FR-23.6 As the lead engineer, I want the backend to handle the equipped emote, so that equip state is persisted.
  • FR-23.7 As the lead engineer, I want the backend to handle transactions, so that purchases are recorded.
  • FR-23.8 As the lead engineer, I want a database used only where appropriate, so that architecture stays simple.
  • FR-23.9 As the lead engineer, I want to avoid building an enormous backend for a small cosmetic system, so that scope stays proportional.
Page 31 of 44

3.24 Multi-Version Support

  • FR-24.1 As the lead engineer, I want the primary version to be 1.21.11 Fabric, so that the main target is clear.
  • FR-24.2 As the lead engineer, I want the project to support separate version builds where required, so that other Minecraft versions can be targeted.
  • FR-24.3 As the lead engineer, I want to avoid creating a fake universal JAR, so that builds are honest and correct.
  • FR-24.4 As the lead engineer, I want each supported Minecraft version to have its own Gradle configuration, so that builds are version-specific.
  • FR-24.5 As the lead engineer, I want each supported version to have its own Fabric API version, so that dependencies match.
  • FR-24.6 As the lead engineer, I want each supported version to have its own Fabric Loader version, so that loader compatibility matches.
  • FR-24.7 As the lead engineer, I want each supported version to have its own mappings, so that names resolve correctly.
  • FR-24.8 As the lead engineer, I want each supported version to have its own source, so that code is version-appropriate.
  • FR-24.9 As the lead engineer, I want each supported version to have its own mixins, so that injections match version signatures.
  • FR-24.10 As the lead engineer, I want each supported version to have its own resources, so that assets match.
  • FR-24.11 As the lead engineer, I want each supported version to have its own README, so that documentation is local.
  • FR-24.12 As the lead engineer, I want each supported version to have its own build configuration, so that builds are independent.
  • FR-24.13 As the lead engineer, I want to avoid blindly copying 1.21.11 mixins into older versions, because Minecraft method signatures can change.
Page 32 of 44
  • FR-24.14 As the lead engineer, I want to avoid spending the majority of the budget supporting every historical version before 1.21.11 is fixed, so that priorities are respected.
  • FR-24.15 As the lead engineer, I want to document a version as incompatible rather than waste effort if it is technically incompatible, so that effort is not squandered.
Page 33 of 44

3.25 Testing

  • FR-25.1 As the lead engineer, I want startup tested for client launch, so that the client boots.
  • FR-25.2 As the lead engineer, I want startup tested for absence of mixin crashes, so that injection issues are caught.
  • FR-25.3 As the lead engineer, I want startup tested for absence of initialization crashes, so that init issues are caught.
  • FR-25.4 As the lead engineer, I want modules tested for toggling, so that enable/disable works.
  • FR-25.5 As the lead engineer, I want modules tested for settings working, so that settings take effect.
  • FR-25.6 As the lead engineer, I want modules tested for settings saving, so that configuration persists.
  • FR-25.7 As the lead engineer, I want modules tested for settings loading, so that configuration restores.
  • FR-25.8 As the lead engineer, I want the GUI tested for Right Shift working, so that the ClickGUI opens.
  • FR-25.9 As the lead engineer, I want the GUI tested for hover working, so that hover accuracy is confirmed.
  • FR-25.10 As the lead engineer, I want the GUI tested for clicking working, so that interaction is confirmed.
  • FR-25.11 As the lead engineer, I want the GUI tested for scrolling working, so that navigation is confirmed.
  • FR-25.12 As the lead engineer, I want the GUI tested for centering working, so that layout is confirmed.
  • FR-25.13 As the lead engineer, I want the pause menu tested for opening, so that it is reachable.
  • FR-25.14 As the lead engineer, I want the pause menu tested for closing, so that it exits correctly.
Page 34 of 44
  • FR-25.15 As the lead engineer, I want the pause menu tested for buttons working, so that its actions function.
  • FR-25.16 As the lead engineer, I want emotes tested for all 20 registering, so that the collection loads.
  • FR-25.17 As the lead engineer, I want emotes tested for previews working, so that previews render.
  • FR-25.18 As the lead engineer, I want emotes tested for equipping working, so that equip state applies.
  • FR-25.19 As the lead engineer, I want emotes tested for ownership working, so that ownership is tracked.
  • FR-25.20 As the lead engineer, I want the shop tested for prices working, so that pricing is correct.
  • FR-25.21 As the lead engineer, I want the shop tested for purchases working, so that buying succeeds.
  • FR-25.22 As the lead engineer, I want the shop tested for duplicate purchases being prevented, so that double-buy is blocked.
  • FR-25.23 As the lead engineer, I want the shop tested for invalid purchases being rejected, so that bad requests fail safely.
  • FR-25.24 As the lead engineer, I want Blue Stars tested for correct balance, so that balances are accurate.
  • FR-25.25 As the lead engineer, I want Blue Stars playtime rewards tested through the intended architecture, so that earning works legitimately.
  • FR-25.26 As the lead engineer, I want Blue Stars transactions tested for validation, so that integrity is enforced.
  • FR-25.27 As the lead engineer, I want performance tested for no obvious FPS regression, so that optimization did not regress.
  • FR-25.28 As the lead engineer, I want performance tested for no render-thread abuse, so that the render path stays healthy.
  • FR-25.29 As the lead engineer, I want performance tested for no memory leak, so that long sessions remain stable.
  • FR-25.30 As the lead engineer, I want performance tested for no repeated exceptions, so that recurring errors are caught.
Page 35 of 44
  • FR-25.31 As the lead engineer, I want to distinguish compiled, launched, manually tested, automated tested, and statically inspected states, so that testing claims are honest.
  • FR-25.32 As the lead engineer, I want never to claim "Tested successfully" if only compiled, so that reporting is truthful.
Page 36 of 44

3.26 Documentation & Progress

  • FR-26.1 As the next agent, I want a README.md created, so that the project is documented.
  • FR-26.2 As the next agent, I want a NEXT_AGENT.md created, so that I can understand the project without repeating the entire investigation.
  • FR-26.3 As the next agent, I want architecture documented, so that structure is clear.
  • FR-26.4 As the next agent, I want modules documented, so that the module system is clear.
  • FR-26.5 As the next agent, I want settings documented, so that configuration is clear.
  • FR-26.6 As the next agent, I want UI documented, so that interface structure is clear.
  • FR-26.7 As the next agent, I want rendering documented, so that draw paths are clear.
  • FR-26.8 As the next agent, I want mixins documented, so that injections are clear.
  • FR-26.9 As the next agent, I want networking documented, so that communication is clear.
  • FR-26.10 As the next agent, I want backend documented, so that server infrastructure is clear.
  • FR-26.11 As the next agent, I want database documented, so that schema is clear.
  • FR-26.12 As the next agent, I want Blue Stars documented, so that the economy is clear.
  • FR-26.13 As the next agent, I want emotes documented, so that the emote system is clear.
  • FR-26.14 As the next agent, I want shop documented, so that the shop is clear.
Page 37 of 44
  • FR-26.15 As the next agent, I want version differences documented, so that multi-version behavior is clear.
  • FR-26.16 As the next agent, I want build instructions documented, so that builds can be reproduced.
  • FR-26.17 As the next agent, I want testing documented, so that verification history is clear.
  • FR-26.18 As the next agent, I want known limitations documented, so that gaps are visible.
  • FR-26.19 As the next agent, I want unfinished work documented, so that remaining tasks are visible.
  • FR-26.20 As the lead engineer, I want a PROGRESS.md maintained, so that development progress is recorded.
  • FR-26.21 As the lead engineer, I want the progress file to record completed work, so that progress is visible.
  • FR-26.22 As the lead engineer, I want the progress file to record the current phase, so that state is clear.
  • FR-26.23 As the lead engineer, I want the progress file to record discovered bugs, so that issues are tracked.
  • FR-26.24 As the lead engineer, I want the progress file to record fixes, so that repairs are tracked.
  • FR-26.25 As the lead engineer, I want the progress file to record tests performed, so that verification is tracked.
  • FR-26.26 As the lead engineer, I want the progress file to record remaining issues, so that outstanding work is tracked.
  • FR-26.27 As the lead engineer, I want to avoid enormous repetitive logs, so that documentation stays useful.
Page 38 of 44

3.27 Project Structure & Packaging

  • FR-27.1 As the lead engineer, I want a clean final project structure, so that the deliverable is organized.
  • FR-27.2 As the lead engineer, I want the structure to include README.md, NEXT_AGENT.md, and PROGRESS.md at the top level, so that documentation is discoverable.
  • FR-27.3 As the lead engineer, I want the structure to include a 1.21.11/ directory containing source/, backend/, build/, README.md, and NEXT_AGENT.md, so that the primary version is self-contained.
  • FR-27.4 As the lead engineer, I want the structure to include a versions/ directory with per-version folders (e.g., 1.21.1/, 1.21.2/, … 26.2/), so that additional versions are organized.
  • FR-27.5 As the lead engineer, I want the structure to include a documentation/ directory, so that documentation is centralized.
  • FR-27.6 As the lead engineer, I want the structure adapted to the actual architecture, so that it reflects reality.
  • FR-27.7 As the lead engineer, I want to avoid unnecessary duplicate folders, so that the structure stays clean.
  • FR-27.8 As the lead engineer, I want the final deliverable to include a compiled Blue Client 1.21.11 JAR, so that the client can be run.
  • FR-27.9 As the lead engineer, I want the final deliverable to include source, so that the code is available.
  • FR-27.10 As the lead engineer, I want the final deliverable to include the backend if required, so that server authority is delivered.
  • FR-27.11 As the lead engineer, I want the final deliverable to include the database schema if required, so that persistence is defined.
  • FR-27.12 As the lead engineer, I want the final deliverable to include assets, so that client resources ship.
  • FR-27.13 As the lead engineer, I want the final deliverable to include documentation, so that the project is understandable.
Page 39 of 44
  • FR-27.14 As the lead engineer, I want the final deliverable to include progress notes, so that history ships.
  • FR-27.15 As the lead engineer, I want the final deliverable to include supported version folders, so that versions ship together.
  • FR-27.16 As the lead engineer, I want the final deliverable to include version-specific source, so that per-version code ships.
  • FR-27.17 As the lead engineer, I want the final deliverable to include version-specific configuration, so that per-version setup ships.
  • FR-27.18 As the lead engineer, I want the final deliverable to include version-specific mixins, so that per-version injections ship.
  • FR-27.19 As the lead engineer, I want the final deliverable to include version-specific README files, so that per-version docs ship.
  • FR-27.20 As the lead engineer, I want the final deliverable to include a final ZIP, so that the result is distributable.
  • FR-27.21 As the lead engineer, I want the primary deliverable to be a JAR file (a compiled Fabric Minecraft client mod for the Blue Network) rather than a website, so that the packaging target is unambiguous.
  • FR-27.22 As the lead engineer, I want the JAR deliverable to remain compatible with the Java Runtime Environment (JRE), so that the client can be run by players.
  • FR-27.23 As the lead engineer, I want website-specific technologies such as HTML, CSS, and JavaScript to not be produced as the product output, so that no web page, JavaScript, or CSS is delivered in place of the JAR; this does not prohibit the JAR from legitimately embedding web technologies where required.
Page 40 of 44

3.28 Priority Order

  • FR-28.1 As the lead engineer, I want P0: Fix the current crash as the highest priority, so that the blocking defect is resolved.
  • FR-28.2 As the lead engineer, I want P1: Make Blue Client launch reliably, so that the client is usable.
  • FR-28.3 As the lead engineer, I want P2: Fix existing broken functionality, so that prior features work.
  • FR-28.4 As the lead engineer, I want P3: Investigate and improve actual performance, so that the client performs well.
  • FR-28.5 As the lead engineer, I want P4: Fix Right Shift / GUI / centering / hover problems, so that primary UI is corrected.
  • FR-28.6 As the lead engineer, I want P5: Fix module architecture and settings, so that configuration is complete.
  • FR-28.7 As the lead engineer, I want P6: Revamp pause menu, so that the pause interface is polished.
  • FR-28.8 As the lead engineer, I want P7: Build the emote framework, so that emote content can be added.
  • FR-28.9 As the lead engineer, I want P8: Create the 20 emotes, so that content is delivered.
  • FR-28.10 As the lead engineer, I want P9: Build Blue Stars, so that the currency exists.
  • FR-28.11 As the lead engineer, I want P10: Build cosmetic shop, so that cosmetics can be acquired.
  • FR-28.12 As the lead engineer, I want P11: Backend integration, so that server authority is added where required.
  • FR-28.13 As the lead engineer, I want P12: Additional Minecraft versions, so that multi-version support follows the primary target.
Page 41 of 44

3.29 Engineering Discipline & Resource Constraints

  • FR-29.1 As the lead engineer, I want to not use sub-agents, so that the credit budget is preserved.
  • FR-29.2 As the lead engineer, I want to not spawn additional agents, so that work stays within a single execution context.
  • FR-29.3 As the lead engineer, I want to not delegate tasks, so that overhead is avoided.
  • FR-29.4 As the lead engineer, I want to not ask another model/agent to analyze something, so that duplicate work is avoided.
  • FR-29.5 As the lead engineer, I want to not waste credits on unnecessary explanations, so that budget goes to implementation.
  • FR-29.6 As the lead engineer, I want to not repeatedly reread the same files, so that redundant effort is avoided.
  • FR-29.7 As the lead engineer, I want to not repeatedly rediscover the architecture, so that effort is not duplicated.
  • FR-29.8 As the lead engineer, I want to not rewrite working code without a technical reason, so that regressions are avoided.
  • FR-29.9 As the lead engineer, I want to not create unnecessary abstractions, so that complexity stays low.
  • FR-29.10 As the lead engineer, I want to not generate giant amounts of commentary, so that output stays useful.
  • FR-29.11 As the lead engineer, I want to not spend credits explaining planned actions for hundreds of lines, so that budget is preserved.
  • FR-29.12 As the lead engineer, I want the majority of the budget spent on actual implementation and testing, so that the budget produces results.
  • FR-29.13 As the lead engineer, I want to prefer the solution with fewer changes when two solutions are technically valid, so that risk is minimized.
Page 42 of 44
  • FR-29.14 As the lead engineer, I want to prefer the solution that is easier to maintain, so that future work is cheaper.
  • FR-29.15 As the lead engineer, I want to prefer the solution that uses fewer dependencies, so that the build is simpler.
  • FR-29.16 As the lead engineer, I want to prefer the solution that is less risky, so that stability is preserved.
  • FR-29.17 As the lead engineer, I want to prefer the solution that is easier to test, so that verification is feasible.
  • FR-29.18 As the lead engineer, I want to prefer the solution that consumes fewer development resources, so that the budget lasts.
  • FR-29.19 As the lead engineer, I want to optimize for quality × stability × performance × maintainability rather than feature count.
  • FR-29.20 As the lead engineer, I want a smaller feature set that actually works preferred over 100 half-finished features.
  • FR-29.21 As the lead engineer, I want to preserve working systems, fix broken systems, avoid faking functionality, and avoid faking testing.
  • FR-29.22 As the lead engineer, I want to not blindly obey individual feature requests when the existing architecture shows a better solution.

3.30 Blue Network Integration

  • FR-30.1 As a player, I want Blue Client integrated with the Blue Network, so that client features connect to the ecosystem.
  • FR-30.2 As the lead engineer, I want Blue Network resource values (Discord, X, logo, server) available where appropriate, so that official resources are used correctly.
  • FR-30.3 As the lead engineer, I want to avoid unnecessarily embedding external resources into the client, so that the client stays lightweight.
  • FR-30.4 As the lead engineer, I want to avoid unnecessary network requests, so that the client does not create needless traffic.
  • FR-30.5 As the lead engineer, I want to avoid hardcoding secrets, so that the client is secure.
Page 43 of 44

4. User Personas

Blue Client Player — A Minecraft player on the Blue Network using Blue Client. They launch the client via Fabric, toggle modules, configure settings, open the Right Shift/ClickGUI, use the pause menu, equip and preview emotes, browse the cosmetic shop, and earn/spend Blue Stars through playtime. Their visible surface is the client HUD, ClickGUI, pause menu, settings interface, emote collection, and shop.

Lead Engineer — Owns the entire client overhaul: inspects the attached project/source/files and logs as evidence, diagnoses real defects and root causes, produces the BLUE CLIENT MASTER ENGINEERING PLAN and a detailed implementation specification, reviews the plan for unnecessary work and credit usage, then executes stability fixes, performance work, UI/UX overhaul, module/settings overhaul, emote framework and content, Blue Stars, cosmetic shop, conditional backend integration, testing, and packaging/documentation. Success is a compiled, launchable, stable, performant, polished Blue Client delivered as a JAR, source, assets, documentation, progress notes, version folders, and a final ZIP.

Next Agent — The engineer who continues the project after handoff. They rely on README.md, NEXT_AGENT.md, PROGRESS.md, and the centralized documentation of architecture, modules, settings, UI, rendering, mixins, networking, backend, database, Blue Stars, emotes, shop, version differences, build instructions, testing, known limitations, and unfinished work so they can resume without repeating the entire investigation.

Page 44 of 44

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: Download client

Launch: Launch Minecraft with Fabric

Modules: Toggle module on

Settings: Adjust module settings

ClickGUI: Open Right Shift menu

ClickGUI: Search and open module

Pause Menu: Open pause menu

Emotes: Preview emote

Shop: Buy emote

Wallet: Check Blue Stars balance

Shop: See insufficient balance state

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: Download client

Launch: Launch Minecraft with Fabric

Modules: Toggle module on

Settings: Adjust module settings

ClickGUI: Open Right Shift menu

ClickGUI: Search and open module

Pause Menu: Open pause menu

Emotes: Preview emote

Shop: Buy emote

Wallet: Check Blue Stars balance

Shop: See insufficient balance state