Recipes

Neroland Core ships the standard compaction recipes for its materials. Every recipe is plain data under data/nerolandcore/recipe/*.json, so a datapack can replace, remove, or add recipes freely. No code path hard-codes a material item, and recipes reference the c:/neroland: tags rather than item ids.

Compaction set#

Void Crystal compacts along the chain block <-> gem <-> shard.

Storage blocks#

Core ships crafting recipes for its passive storage blocks — Battery, Fluid Tank, Gas Tank, Item Store, and the Trash Can. These are the same recipes the blocks shipped with previously; like every Core recipe they reference the #c: material tags rather than item ids, so a pack can substitute the metal or retune the cost. (The Creative variants have no recipe — they are creative-tab only.)

Because the ingredients are tag-based, the exact metal is whatever a pack maps into the #c: ingot tags; reference the tag, never a specific item id.

Overriding and extending#

Because recipes are plain data and ingredients are tag-based, a pack can:

• replace any Core recipe by shipping the same recipe id
• remove a recipe
• add new recipes that consume the c: or neroland: material tags

Reference materials by tag (for example c:ingots/nero_alloy), never by item id. See Tags and Datapacks.

Loot tables and mining#

Material block loot tables live at data/nerolandcore/loot_table/blocks/*.json. Each material block drops itself by default; packs can override these for silk touch or bonus drops.

Mining tags list the solid blocks so tool requirements are pack-tunable:

• minecraft:mineable/pickaxe
• needs_iron_tool

For developers#

Tag and datapack details for mod authors live in ../docs/TAGS-AND-DATAPACKS.md.

See also#

• Materials
• Tags and Datapacks
• Getting Started
• Home