0.12.0-alpha.7 · FPS performance engine

A sharperMinecraft client.

Blood Client is a client-only Fabric mod for 1.21.11, 26.2 and 26.3 with a deep HUD/module system, skins and cosmetics, a Blood/Normal UI switch, and an optional Windows launcher.

Latest in alpha.7: the internal FPS performance engine from alpha.6 stays on every Minecraft version — lighter HUD rendering, bounded caches, and measured diagnostics via /bloodperf — with Sodium as the recommended (optional) rendering engine. The bugged Shield Banner Studio has been removed completely. Exclusive packs, online + offline Blood appearances and Player Ping Display remain included.

⬇ Download launcher Download .jar ▼

Alpha/beta software: back up worlds and configs first. Launcher 0.3.0-beta.3 now bundles the same alpha.7 jars for 1.21.11, 26.2 and 26.3, with maintenance tools — instance verification, mods backups, profile export/import, crash reports and resumable downloads. With an update channel set, it can check for new launcher versions automatically at startup.

73implemented modules
39floating HUD modules
234validated options
658passing client tests
PLAYER PING DISPLAYInterface · default off
Interactive illustration using sample players — not a gameplay screenshot. In game, Blood only adds ping when vanilla already shows the name tag and the server has provided latency.
What’s new

Alpha.7 keeps the FPS engine — minus Shield Banner.

Every Alpha.7 jar carries Blood’s internal FPS performance engine: lighter HUD rendering, bounded text/cosmetic caches, faster catalog and sidebar paths, renderer compatibility checks, and measured frame diagnostics with /bloodperf. Sodium remains the recommended optional renderer — Blood never bundles it and makes no invented FPS-percentage claims. Shield Banner Studio is gone entirely; appearance sync, exclusive packs and Player Ping Display remain.

⚡
Latest alpha.7

FPS performance engine

Built into the 1.21.11, 26.2 and 26.3 jars. Blood reduces its own repeated HUD measuring, bounds fitting and cosmetic lookups, while every cache stays small and clears safely when settings, worlds or resources change. Alpha.7 also deletes the broken shield-banner editor/rendering path instead of leaving a toggle behind. In game, /bloodperf reports measured average FPS, p50/p95/p99 frame times, stutters and 1% lows. For the biggest renderer gains, add Sodium separately: 0.8.14 for 1.21.11 or 0.9.2 for 26.2/26.3.

◈
Included since alpha.5

Exclusive packs

Six original voxel designs in two packs — Bloody Crown, Blood Pagoda Cape and the rotating-cube Mage Staff for Owners; Bear Hood & Poncho, Ruby Waist Sword and Jeweled Gold Crown for Co-Owners. Equipping asks for that tier’s password in game (no UUID gate). The equipped cosmetics sync to other Blood users on your presence service, online or standard offline-mode.

◉
New

Player Ping Display

Shows ping beside visible player name tags with left/right placement, latency colors, optional ms, own-tag support and a range limit. Missing or negative latency is skipped.

▣

Blood UI / Normal Minecraft

Switch between the full Blood interface and vanilla menus/HUD from Blood Settings or the launcher. Vanilla screens get a “Use Blood UI” button to switch back.

✦

Skin-only frozen previews

Wardrobe and skin previews show only the skin — no cape, cosmetics, armor, held items or nameplate — held in a fixed mid-punch pose that never animates.

🕷

Three spider cosmetics

Webbed Kicks cape, Spider Buddy hat and Webspinner companion join the 26-design Blood wardrobe. Back items share one slot; horns stay separate.

⬢

Drop Cube identity

The Drop Cube mark carries across the mod and launcher with a dark crimson interface, capsule controls and slim, modern dialogs/scrollbars and the 0.3 maintenance toolkit.

⚖

Same safety boundaries

Client-only presentation and information. No reach, damage, attack timing, hit-registration, authentication bypass or name-only unlocks.

Downloads

Two options. That’s it.

Pick the Launcher for managed Windows profiles, or pick a single .jar file for your exact Minecraft version. No giant bundle maze.

Option 01 · Windows

Blood Client Launcher

Per-user installer for Windows 10/11 with managed Alpha.7 Blood profiles, live Modrinth modpacks, automatic dependency checks, local skins, the Blood/Normal interface switch, and maintenance tools: instance verification, mods backups, profile export/import, redacted crash reports, modpack update checks and resumable downloads.

InstallerBloodClientLauncher-Setup-0.3.0-beta.3.exe
Size10.8 MB
Bundled Blood jar0.12.0-alpha.7

The launcher installs the matching alpha.7 jar for each profile automatically — including the FPS engine, exclusive packs and online/offline appearance sync. Shield Banner Studio is not included.

SHA-256Installer checksum
360a93b38bf12fa3a25809063c2b67b66816c892454ce5e1dc83c2b78441c725
⬇ Download launcher
Option 02 · Latest alpha.7

Single .jar download

Select your Minecraft version. The button updates to the one correct Blood Client jar — put only that file in your instance’s mods/ folder with the matching Fabric API.

Remove any older bloodclient jar first. Do not put all three jars in the same instance.

Filebloodclient-0.12.0-alpha.7+mc1.21.11.jar
RequiresJava 21+ · Loader 0.18.4 · API 0.141.6+1.21.11
Size9.9 MB
Tests24 unit tests passing
7937f289df3b6500696f5e34621559fca072406d4cf2ddb07949e26d8b08bc62
⬇ Download 1.21.11 .jar

Both options now ship alpha.7

The standalone .jar files and launcher 0.3.0-beta.3 both contain Blood 0.12.0-alpha.7 with the FPS performance engine and no Shield Banner Studio. Pick the launcher for managed profiles and maintenance tools, or the single .jar for an existing instance. Exclusive passwords are entered in game either way.

Compatibility

Exact targets. No vague version ranges.

MinecraftRuntime jarJavaFabric LoaderFabric APIUnit tests
1.21.11bloodclient-0.12.0-alpha.7+mc1.21.11.jar21+0.18.40.141.6+1.21.1124
26.2bloodclient-0.12.0-alpha.7+mc26.2.jar25+0.19.30.154.2+26.223
26.3bloodclient-0.12.0-alpha.7+mc26.3.jar25+0.20.10.165.0+26.323

No performance mods or AppleSkin are bundled. Sodium (0.8.14 for 1.21.11, 0.9.2 for 26.2 and 26.3) is the recommended optional rendering engine — add it to your mods folder from Modrinth for the biggest FPS gains. Mod Menu remains optional.

Module catalogue

73 real modules. Search the actual list.

This catalogue is generated from alpha.7’s shipped module defaults. Shield Banner Studio was not a module and no longer appears anywhere in the client. “Default on” means the fresh-profile state; HUD modules can be moved and styled per module in game.

73 modules
Windows launcher

One clean place to launch Blood.

The optional native launcher manages Blood Fabric, Vanilla and modpack profiles without pretending to be a store or social network.

▶

Automatic profiles

Create a profile for 1.21.11, 26.2 or 26.3 and the launcher prepares Minecraft, Java, Fabric Loader, pinned Fabric API and its bundled Alpha.7 Blood jar.

⬡

Live Modrinth modpacks

Search and install from the live catalog with hash, safe-path, loader and version checks. Local JAR/modpack dependencies are resolved only when compatibility is provable.

♟

Skins & interface

Import local skins, choose Slim/Classic/Auto and set Blood UI or Normal Minecraft before launch. With Blood presence opted in, your equipped skin and cosmetics show to other Blood users on your host.

✎

Polished, static UI

Blood-themed account/profile/device-code dialogs and slim scrollbars replace old native popups, while the approved v4 layout stays still after its one opening reveal.

⬇

Verified downloads

Game files, libraries, assets and runtimes use allowlisted HTTPS sources with upstream hashes and clear failure states instead of silent guessing.

🔒

Account honesty

Microsoft device-code sign-in is implemented but needs Blood’s own approved application ID. Local accounts are explicitly unauthenticated; no borrowed client ID is bundled.

Install

Running in a few steps.

1

Back up

Back up important worlds, screenshots and your Blood config before changing alpha jars.

2

Pick one jar

In Option 02 above, choose your Minecraft version from the dropdown and download the single matching .jar.

3

Add Fabric API

Install the exact Fabric Loader/API pair from the compatibility table. Remove any older bloodclient jar.

4

Open Blood

Launch the game and press Right Shift. Enable Player Ping Display under Interface.

First settings to try

  • Player Ping Display: Right side, colors on, ms on, 64-block range.
  • Keep the HUD Ping module for your own latency and Tab List for numeric tab pings.
  • Use “Ping on my name tag” only if you also use third-person own-tag display.

Please don’t install these as mods

  • The outer release ZIP itself.
  • The nested source ZIPs or -sources.jar files.
  • Two Blood Client runtime jars in the same mods/ folder.
Verification

Evidence, stated plainly.

What passed for alpha.7 + launcher beta.3

  • Clean Gradle builds on all three mod targets (1.21.11, 26.2 and 26.3).
  • 24 + 23 + 23 = 70 mod unit tests passing (frame statistics, version comparison, compatibility evaluation, bounded caches, cosmetic catalog indexes), zero failures.
  • The reconstructed 1.21.11 Alpha.6 source compiled at exact 193-class parity before removal; the 26.x editable projects were already baseline-proved during the FPS port.
  • Every Alpha.7 jar verified entry-by-entry against Alpha.6 — exactly seven Shield Banner classes removed, no entries added, no Shield Banner strings/mixin/defaults left, and no Sodium code bundled.
  • Sodium stays external and optional (“suggests” metadata only); the exact recommended Sodium jars were hash-verified against Modrinth.
  • Presence/appearance backend 0.8.0-alpha.1: 27 fresh deterministic tests passed.
  • Launcher 0.3.0-beta.3: 75 automated tests passed, compiled against Microsoft’s real .NET Framework 4.8 reference assemblies; Alpha.7 payload hashes staged/verified, NSIS installer built, and all seven launcher pages captured headlessly under Mono/Xvfb.

What still needs a real check

  • A live Minecraft visual check that the cosmetics screen has no Shield Banner button, a held shield stays vanilla in first/third person, the exclusive packs move correctly, and remote Blood skins/cosmetics, the tab badge and name-tag ping render.
  • Deployed HTTPS online-account and standard offline-mode-server presence sessions, plus multiplayer servers that mask or delay player-list latency.
  • Alpha.7’s first physical in-game launch, plus before/after FPS measurements with and without Sodium (in game: /bloodperf) — no FPS percentage claims are being made here.
  • Shader compatibility.
  • Launcher 0.3.0-beta.3’s real-Windows install/launch and maintenance dialogs on a physical PC.

Verify in PowerShell

Run this beside the downloaded file and compare it with the SHA-256 shown for your selected version above:

Get-FileHash .\bloodclient-0.12.0-alpha.7+mc1.21.11.jar -Algorithm SHA256

Hashes prove file integrity against this page’s published value; they are not a publisher signature.

FAQ

Questions, without the fog.

Is Player Ping Display the same as the Ping HUD?

No. The Ping HUD shows your own latency in a floating HUD. Player Ping Display adds each visible player’s server-reported latency beside their in-world name tag. Tab List is a third option that puts numbers in the tab list.

Can it show players through walls or while sneaking?

No new visibility is created. Blood only appends text after vanilla has already produced a visible player name tag for that render state. If vanilla hides the tag, Blood does not draw a replacement.

Why is someone’s ping missing?

The client may not have a matching player-list entry, or the server may report a negative/unavailable latency. Blood skips those instead of inventing a number.

Do skins and cosmetics show to other players?

Yes — to other Blood Client users who opt into the same hosted HTTPS Blood presence service. Online accounts are Mojang-verified; standard offline-mode accounts on offline servers use an explicitly unverified device-signed lane. They see your equipped imported skin and cosmetics on your player model, plus the Blood tab-list badge. Vanilla/other clients still see official account appearances; Blood never changes your Mojang skin, bypasses Minecraft server login or proves official cape ownership. No public presence endpoint is preconfigured.

Does Blood change combat?

No. Blood does not change reach, damage, attack timing, hit registration or server state. Modules present client-known information or alter local presentation.

How do the exclusive Owner / Co-Owner cosmetics unlock?

Everyone can preview them. Pressing Password & Equip in the wardrobe asks for that tier’s password; a correct code equips the design for any account type. The code is checked only on your client against a salted hash and is never sent to a server — treat it as a friendly lock, not DRM. Passwords are shared privately by the Blood team; they are not printed on this page.

How do I get the best FPS?

Use an alpha.7 jar and add Sodium to your mods folder (0.8.14 for 1.21.11, 0.9.2 for 26.2 and 26.3) from Modrinth — Blood recommends it but never bundles it, and works fully without it. In game, type /bloodperf to measure your real frame times, stutters and 1% lows.

Where did Shield Banner Studio go?

It was bugged, so alpha.7 removes it entirely — no editor, stored design, presence shield field, or shield-rendering hook. Existing settings with the old key still load; the key is ignored. The separate Shield status HUD and Low Shield viewmodel option remain.

Does the launcher include alpha.7?

Yes — launcher 0.3.0-beta.3 bundles the same three alpha.7 jars and verifies the matching jar by SHA-256 before installing it into a managed Blood profile. The standalone selector above gives the identical jar for an existing instance.