⚠️Stable : Version 26.1 !

Stable identifiers (com.soleapixel.bmcmod.api.BmcModIds)

Use these ResourceLocation constants in addons to avoid hard-coded strings. They match registry paths for the current version.

Note: Gameplay still resolves blocks/items through ModBlocks / ModItems in the main mod; BmcModIds is for cross-mod references, recipes, and conditions in your own code or datapacks.

Tag conventions (datapack & cross-mod)

Tags live under data/bmcmod/tags/…. Use #bmcmod:… in JSON where Minecraft expects a tag.

Mayor / village integration (extend in your addon)

Example (your addon’s datapack):

{
  "replace": false,
  "values": ["yourmod:golden_mayor_bell"]
}

If you add a custom bell block that must ring and use BellBlockEntity:

1. Your block should behave like a bell (e.g. extend BellBlock or mirror behavior).
2. Register it on BlockEntityType.BELL via NeoForge BlockEntityTypeAddBlocksEvent (same pattern as this mod for MAYOR_BELL).
3. Add your block/item to #bmcmod:mayor_bells so other mods and datapacks can target all mayor bells at once.

Other useful namespaces in this mod

• #c:… (common / convention) — e.g. c:tags/item/tools/scythe is used for compatibility. Add your items to the c / forge / neoforge tags your ecosystem expects.
• Item tags under data/bmcmod/tags/item/ (e.g. scythes, foundry_shards, boreal_ingots, enchantability lists) are datapack-driven; addon items can be merged in with "replace": false.

Registries (code entry points)

Village saved data (per dimension): BmcVillageSavedData — key = village anchor (long from BlockPos).

Events (NeoForge) — where to hook

These use @EventBusSubscriber(modid = "bmcmod", …) on the game bus unless noted. Add-on mods should subscribe with EventPriority appropriately and not assume load order unless you declare an explicit dependency in mods.toml.

Compatibility tip: prefer listening to NeoForge events or datapacks (tags, loot tables) over mixin targets inside com.soleapixel.bmcmod.mixin, which may change between BMC releases.

Mixins

• Configuration: resources/bmcmod.mixins.json.
• Treat mixin targets as fragile API: they can break on Minecraft or NeoForge updates.
• For addons: avoid shadowing BMC mixins; use NeoForge events, tags, or ASM-free registry hooks when possible.

Datapacks & resource paths

• Recipes: data/bmcmod/recipe/
• Loot tables: data/bmcmod/loot_table/
• Loot modifiers: data/bmcmod/loot_modifiers/
• Structures / worldgen: data/bmcmod/worldgen/ and patched vanilla pools under data/minecraft/ where shipped
• Tags: data/bmcmod/tags/<type>/<path>.json

mods.toml dependency snippet (addon mod)

[[dependencies.yourmod]]
modId = "bmcmod"
type = "required" # or "optional" if soft-compat only
versionRange = "[26.0.3,)" # align with the BMC major you tested against
ordering = "NONE"
side = "BOTH"

Adjust version range to match gradle.properties → mod_version for the BMC build you test against.

API & docs changelog

(Append new rows whenever integration surfaces change.)

License / redistribution

Follow the license declared in the BMC jar / repository (SOLEA PIXEL as shown in user mods.toml). When redistributing this dev guide, keep the changelog section honest with your fork.