Lootr Jade Compat — Fabric 26.2

A tiny Jade plugin that displays the current player's already-generated Lootr inventory.

Intended versions

• Minecraft 26.2
• Fabric Loader 0.19.3+
• Fabric API 0.156.0+26.2
• Lootr Fabric 26.2 / 1.24.39.121
• Jade Fabric 26.2.x
• Java 25

Behavior

The server resolves the Lootr block entity, loads its LootrInventoryStore, and calls getInventory(player UUID). This is deliberate: it does not call Lootr's DataStorage.getInventory(...), so looking at an unopened chest with Jade does not generate loot.

If an inventory exists, the item stacks are sent through Jade's server-data channel and rendered client-side. If it does not exist, Jade shows "Loot not generated for you yet".

Build

Use JDK 25:

./gradlew build

The jar will be under build/libs/.

Current verification status

The Lootr 26.2 API used here was checked against Lootr's mdg-26.2 source, notably:

• DataStorage.getData(ILootrContainerInstance)
• LootrInventoryStore.getInventory(UUID)
• LootrInventory#getItem / getContainerSize
• LootrAPI.wrapBlockEntity

Jade's 26.x plugin registration and StreamServerDataProvider pattern were checked against Jade's 26.x developer documentation.

This project was not locally compiled in the generation environment because that environment cannot reach Maven/GitHub. The most likely compile-sensitive point is Minecraft 26.2's exact ItemStack stream-codec field name. If ItemStack.OPTIONAL_STREAM_CODEC differs in the resolved 26.2 mappings, replace it with the equivalent optional ItemStack StreamCodec exposed by 26.2.

Installation

Install the built jar on both server and client, alongside Fabric API, Lootr and Jade.

0.1.4

• Suppresses Jade's generic item-storage / jade.loot_not_generated tooltip for a Lootr container once the current player's Lootr inventory has been generated.
• Leaves Jade's normal "What could it be?" hint intact before generation.
• Uses a client-side Mixin against Jade's ItemStorageProvider.Client; the server-side Lootr inventory sync is unchanged.