Adapter Guide

The Minecraft adapter is the API layer behind MinecraftApi. Use it when mod code needs Minecraft-facing services such as registries, text, NBT, commands, events, client helpers, generated data or data packs.

Most code starts from a NowsContext:

RegistryApi registries = MinecraftApi.registries(context);
TextApi text = MinecraftApi.text(context);
GameEvents events = MinecraftApi.events(context);
NbtApi nbt = MinecraftApi.nbt(context);

Prefer Stable Inputs

Use stable specs when your mod is describing common content or data:

BlockEntry machine = registries.registerBlockWithItem(
        BlockSpec.builder("my_mod:machine")
                .material(BlockMaterial.METAL)
                .strength(3.0F, 6.0F)
                .requiresCorrectTool()
                .item(ItemSpec.builder("my_mod:machine").build())
                .build());

The adapter returns native Minecraft objects where that is useful:

Block block = machine.block();
BlockItem item = machine.item();

That means you can use Nows for stable setup, then continue with normal Minecraft APIs when the feature needs native behavior.

Use Native Code When Needed

Nows does not try to hide all Minecraft differences. Use native Minecraft classes for behavior that is inherently version-specific:

• block entity ticking and persistence
• entity AI, renderers and models
• custom world generation
• complex screens and widgets
• low-level packet encoding

Use stable specs for setup and generated data. Use native Minecraft APIs for gameplay systems that need full control.