AppleSkin: Food HUD Setup for Fabric and NeoForge

Current release check: AppleSkin 3.0.10+mc26.2 has separate Fabric and NeoForge files for Minecraft Java 26.2. The Fabric release declares Fabric API as required; the NeoForge release declares no Modrinth dependency relation. MineBrush checked the creator sources on August 24, 2026 but did not download, inspect, or run either JAR.

AppleSkin makes food information visible. It adds food-value tooltips, hunger and saturation previews, exhaustion information, and related HUD data without changing Minecraft’s underlying food mechanics. That makes it useful for planning a meal, but it does not buff food or rebalance hunger.

Pick the file for the loader you actually use

The files are alternatives, not a pair. Do not put both in one profile. The Fabric relation names Fabric API without pinning one exact version, so you still need a Fabric API release that matches Minecraft 26.2 and your Fabric Loader.

AppleSkin’s project page lists Fabric, Forge, NeoForge, and Quilt across its history. That aggregate list does not prove a Forge or Quilt build for the current 26.2 tuple. The checked 26.2 release list contains Fabric and NeoForge files only.

Know what each display is telling you

The creator describes these main features:

• food value information in item tooltips;
• saturation and exhaustion visualization on the HUD;
• predicted hunger and saturation restored by the food in your hand;
• predicted health restoration;
• hunger, saturation, and exhaustion data in the F3 debug overlay;
• client synchronization of saturation and exhaustion values when the server side supports it.

These are informational layers. If another mod or server changes the mechanics, AppleSkin may display the data it receives; it does not become the owner of that gameplay rule. MineBrush has not verified layout, timing, localization, accessibility, or coexistence with another HUD or food mod.

Client-only and server-synced values are not identical

Modrinth marks AppleSkin optional on both the client and server. The creator calls it mostly client-side but says server installation is needed for accurate saturation and exhaustion values on the client.

That means the tooltip and HUD experience can have a client-only route, while exact remote saturation/exhaustion data has a separate server boundary. Do not claim accuracy on a dedicated, vanilla, proxied, or plugin-based server without testing the exact client/server setup.

The creator links third-party plugins for some vanilla-server use cases. Those plugins are separate projects with separate maintainers, versions, licenses, and evidence. MineBrush did not review them for this AppleSkin package.

Install AppleSkin in one clean profile

1. Confirm the launcher profile is Minecraft Java 26.2.
2. Confirm whether it uses Fabric or NeoForge.
3. Choose the matching AppleSkin version ID from the creator’s versions page.
4. For Fabric, install a compatible Minecraft 26.2 Fabric API build in the same profile.
5. Place only the matching AppleSkin JAR in the profile’s mods folder.
6. Start without other food, tooltip, and HUD mods so the first result has one owner.

If you need the general Fabric workflow, follow the MineBrush Fabric installation guide. This article focuses only on AppleSkin’s release, loader, dependency, and client/server data boundaries.

Run a food-state check that means something

1. Open a disposable world and record the exact AppleSkin and loader tuple.
2. Use two or three familiar foods with clearly different hunger values.
3. Inspect the tooltip, the held-food preview, and the F3 data separately.
4. Change only one player state at a time: hunger, saturation, or health.
5. Restart the client and repeat the same foods before calling a display persistent.
6. For multiplayer, write down whether AppleSkin is present on the server and keep that result separate from client-only play.

This route is a test plan, not a claim that MineBrush already observed the HUD. Exact values need a controlled game state and a client/server tuple.

Troubleshoot the first mismatched layer

Update without mixing loaders

Record the current Minecraft version, loader, AppleSkin version ID, Fabric API version when applicable, and other HUD mods. Build the replacement in a separate profile, repeat the same food-state check, and keep the last-known-good instance until the new one passes.

Do not carry a Fabric JAR into NeoForge or copy an old Forge/Quilt assumption into 26.2. A matching project name is not enough; the release page must match the game and loader.

No performance guarantee

This source review contains no repeatable FPS, frame-time, memory, server-tick, bandwidth, or latency test. AppleSkin’s informational scope does not justify calling it “zero impact.” If performance matters, compare the same hardware, Java runtime, modpack, world, GUI state, and repeatable route with and without the exact file.

Creator-controlled sources

• AppleSkin project
• Official AppleSkin versions
• AppleSkin 3.0.10 Fabric for 26.2
• AppleSkin 3.0.10 NeoForge for 26.2
• Creator-linked source repository

Rights and evidence: The project is labeled The Unlicense, but that does not automatically grant reuse rights for every icon or screenshot embedded on a creator page. No AppleSkin JAR or original creator/gameplay screenshot is present locally, so MineBrush should link to the creator’s versions page and upload nothing for this revision.