v3.6.5 Stable Release

Define a block in Python.
Get the whole datapack.

StewBeet is a Beet framework for Minecraft datapacks. Describe your content once. Models, recipes, loot tables, translations and an in-game manual are all built from it on every compile.

Get Started🧪 Try it live, edit the codeRuns a real build in your browser without needing to install anything.

MIT licensed · Python 3.14+ · no account needed

definitions/additions/equipments.py

Block(
    id="life_crystal_block",
    vanilla_block=VanillaBlock(id="minecraft:glass"),
    manual_category="equipment",
    components={
        "item_name": {"text": "Life Crystal Block"},
        "lore": [{"text": "Break it to get the crystal back"}],
    },
    # Broken without Silk Touch, it hands the crystal back
    no_silk_touch_drop=NoSilkTouchDrop(
        id="life_crystal", count=1,
    ),
    recipes=[CraftingShapelessRecipe(
        category="equipment", result_count=1,
        ingredients=8 * [Ingr("minecraft:glass")]
            + [Ingr("life_crystal")],
    )],
)
# Single-block veins, deep in the overworld, carved into stone
CustomOreGeneration.all_with_config({
    "life_crystal_block": [CustomOreGeneration(
    dimensions=["minecraft:overworld"],
    minimum_height=-32, maximum_height=50,
    veins_per_region=1.5,
    provider=["#minecraft:overworld_carver_replaceables"],
)]})

build/

16 files generated

└

└silk touch, else the crystal

└the recipe, NBT-aware

└world gen

└

└its manual page

└

└translation keys

Placement, destruction, the Silk Touch branch, the recipe and its drawn crafting grid, world generation, models and textures. The manual page and the translation keys come with it.

v3.6.5

released 13 days ago

public projects built with it

GitHub stars

Why this exists

One custom block, written by hand, is at least eight files across two packs in four formats. Miss one and nothing errors. The block just quietly never drops.

By hand

8files to keep in sync

function/place.mcfunctionplacement
function/destroy.mcfunctiondestruction
loot_table/block.jsondrops
recipe/block.jsonvanilla recipe
function/calls/crafter.mcfunctionNBT recipe
items/block.jsonitem definition
models/item/block.jsonmodel
lang/en_us.jsontranslation key

With StewBeet

1definition to maintain

definitions/blocks.py

The other eight are derived from it on every build, so they cannot drift apart.

A definition is a name, some values and a list of recipes. If you can read datapack JSON, you can read one.

Your datapack documents itself

Every item you define gets a manual page: its recipe drawn from the ingredients you declared, its description, and clickable navigation between categories. Players craft the book in-game and it is already up to date.

Recipes rendered from your definitions, not screenshotted by hand
New item today, new manual page on the next build
Custom pages, hooks and button layouts when you need them

How the manual works

What you stop writing

Six things StewBeet generates from definitions you already wrote.

definitions/ores.py

One ingot texture, and the tools and armour registered from it

the whole tier from one entry

DIAMOND_PICKAXE = VanillaEquipments.PICKAXE.value[DefaultOre.DIAMOND]

ORES_CONFIGS: dict[str, EquipmentsConfig | None] = {
    "solarium_ingot": EquipmentsConfig(
        # Solarium behaves like diamond,
        equivalent_to=DefaultOre.DIAMOND,
        # but the pickaxe lasts three times longer,
        pickaxe_durability=3 * DIAMOND_PICKAXE["durability"],
        # and it hits harder, protects more, mines faster
        attributes={"attack_damage": 1, "armor": 0.5},
    ),
}
generate_everything_about_these_materials(ORES_CONFIGS)