ForgeCraftPLUGIN WIKISDocumentationSupport ↗
Server reference

Validation and remaining work

ForgeHUD & Classes · 1.4.2 Starter

Starter 1.4.2 — 10 November 2026

The isolated Paper 1.21.11 runtime passed 45 live starter checks: six working abilities, resource/cooldown enforcement, failed/no-target actions, 27-node trees, real player selection commands, companion payloads, point purchases/refunds, increased skill damage, and reconnect persistence. Three live expansion checks confirmed starters can be disabled while an independently installed full Nightblade class retains its 72-node tree. All four existing full class sources compile against the new API; those premium JARs are not in the Starter bundle.

Server rule suites and the production Fabric build passed. Delivered client classes have Java 21 bytecode and exclude development capture hooks. The new starter icon references were checked against the actual Minecraft 1.21.11 assets. The new compact starter tree was protocol-tested and compiled, not visually captured in the native client in this pass. Public hosting, every client/mod/display combination, long-term balance and load remain separate checks. The older screenshots and tests below are historical evidence, not fresh 1.4.2 UI captures.

Compact layout 1.4.1 — 10 November 2026

Seven live native self-panel checks, eight real Minecraft layout-control checks and standalone geometry bounds/anchor/drag-coordinate tests passed. The 18 dungeon integration checks and vanilla/no-pack fallback were rerun. The production client build passed, with developer capture hooks excluded from the delivered companion. New panel sizing is 50–150%, independent for party/dungeon/player. Physical mouse dragging and every class-provider combination were not exercised here.

Dungeon tracker 1.4.0 — 10 November 2026

18 live integration checks and a separate vanilla/no-pack fallback check passed on Paper 1.21.11. The actual Minecraft client rendered party frames, the run card and native phase-two boss display, and the F8 tracker button was toggled both ways. A production companion build passed and contains no developer capture classes or file-control hooks. The separately packaged free pack contains only HUD/menu assets and their dependencies; equipment and arsenal defaults are empty. The DungeonForge 1.7.2 candidate passed 157 unit tests, including party disconnect cleanup. See the free tracker guide for scope and requirements. Other versions, Folia, public hosting and full gameplay completion remain unqualified.

ForgeHUD 1.3.0 is a local preview built against Paper 1.21.4 and Java 21. The Fabric companion targets Minecraft 1.21.4.

Connected-client testing covers the vanilla talent menu, 72-node companion data, point spending, locked prerequisites, exclusive branches, actual health modifiers, insufficient points, confirmed refunds, the level-60 point budget, skill ordering, normal payload casting, cooldown/malformed-message rejection, invitations, leadership permissions, ready state, private party chat, friendly-fire protection, and the hosted pack's ZIP bytes and SHA-1.

The companion was launched in Minecraft and its skill tree, binding screen, icons, pack fonts and party HUD were visually inspected. DungeonForge 1.2.0 was loaded alongside ForgeHUD; shared membership, invitations, leadership changes, readiness, dungeon-browser entry and invalid-dungeon checks passed. Separate rule checks cover cycles, unknown prerequisites, overlapping slots, scoped effects and rank caps. Hardware keypress combinations and a complete dungeon run remain manual qualification items.

The test server is loopback-only. These checks do not certify external network port forwarding, public pack hosting, every client mod combination, every display size, or all dungeon gameplay paths.

Remaining product work

  • Fine-tuning weapon angles in hand and class balance remains a separate pass.
  • Boss, pet, dragon, NPC and build store packs are separate products and are not created by this update.
  • Broader server/client-version qualification and public-server gameplay testing remain outstanding.

Fellowship and Armory verification

The 1.2.0 checks cover 40 collections/240 items, all-class and collection menus, preview-item theft prevention, non-admin grant rejection, actual 2/4/6-piece health changes, wrong-hand duplicate rejection, class and level gates, invalid configuration reload recovery, GUI invitations/acceptance/readiness, HUD snapshots, show-self/visibility preferences, and safe confirmation/cancel flows.

Asset validation checks every item definition, texture reference, cuboid bounds/UVs, all wearable texture pairs, forty distinct weapon meshes and valid font ascents. Actual Minecraft screenshots cover all four classes, the party HUD, party menu and layout screen. Natural-drop frequency and long-term economy/balance still need playtesting.

Equipment remake 1.3.0

The final server build passed 37 equipment/party integration checks and 9 particle/add-on checks. Asset validation passed 9 checks; distribution validation passed 11, including assembling all four bundles into a complete pack. The Java rule suite passed 11 checks. The wiki passed 24 checks with no broken local links.

All forty suits were rendered through the actual Minecraft 1.21.4 client. Four capstone suits, early tiers, in-world particles, first-person equipment and controls were visually inspected. The final client session had no missing collection models or rejected armor assets. The release client was built cleanly after removing the development capture hooks, and the package validator confirms they are absent. This does not replace long-session, public-server or balance testing.

Search all plugin wikis.