Lodestone coords

Evidence

Ran on Kiln's test stand (2026-11-04): client entrypoint started, 1200 ticks without errors, nothing drawn on the HUD. Its Mixins were not applied, so that part of it is missing.

What it needs from Kiln

• Mixin
• com.mojang.blaze3d.platform.InputConstants.Key
• net.fabricmc.fabric.api.client.command.v2.ClientCommandRegistrationCallback
• net.fabricmc.fabric.api.client.command.v2.ClientCommands
• net.fabricmc.fabric.api.client.command.v2.FabricClientCommandSource
• net.fabricmc.fabric.api.client.item.v1.ItemTooltipCallback
• net.fabricmc.fabric.api.client.screen.v1.ScreenEvents
• net.fabricmc.fabric.api.client.screen.v1.ScreenEvents.AfterInit
• net.fabricmc.fabric.api.client.screen.v1.ScreenKeyboardEvents
• net.fabricmc.fabric.api.client.screen.v1.ScreenKeyboardEvents.BeforeKeyPress
• net.fabricmc.loader.api.ModContainer
• net.fabricmc.loader.api.metadata.ModMetadata
• net.minecraft.client.KeyboardHandler
• net.minecraft.client.gui.screens.inventory.AbstractContainerScreen
• net.minecraft.core.GlobalPos
• net.minecraft.core.component.DataComponents
• net.minecraft.world.inventory.Slot
• net.minecraft.world.item.Item.TooltipContext
• net.minecraft.world.item.component.LodestoneTracker
• FabricLoader.getAllMods()
• KeyMapping.getDefaultKey()
• KeyMapping.matches()
• Minecraft.keyboardHandler
• Component.copy()
• ItemStack.get()
• ItemStack.getCustomName()
• ItemStack.getHoverName()
• ItemStack.is()
• Items.COMPASS

On the roadmap: Minecraft's libraries and client API (0.2), Code next to data (0.3), Machines (0.4), Mixin (0.5)

In the author's words

Lets you see the coordinates that a lodestone compass is pointing to

Scan

Scanned on 4 November 2026 against Kiln 0.2.0, file lodestone-coords-v1.1.1-26.3.jar. The scan reads the mod's classes; it does not run them.