Make Chisel fit your pack.

Get the right versions, add blocks from other mods to Chisel families, and adjust a few settings to suit your pack.

Data-pack friendlyServer configurableNeoForge

Dependencies and versions

Chisel needs CTM, so include both in your pack and choose versions that work with your Minecraft release.

Component	Current project baseline	Role
Chisel	`26.1.2.18`	Blocks, tools, recipes, menus, and family logic
CTM	`26.1.2.8`	Required connected-texture rendering library
NeoForge	`26.1.2.106+`	Mod loader and platform APIs

Install Chisel on both sides. Include it on the client and server. Before releasing your pack, test it on a dedicated server as well as in single-player.

Add blocks to a variant family

Every Chisel family has a common block tag, typically c:chisel/<family_name>. A datapack can add blocks from Minecraft or another mod to that family, allowing conversion in both directions.

Find the family name, such as aluminum.
Create data/c/tags/block/chisel/aluminum.json in your datapack or KubeJS data resources.
Add the external block IDs under values.
Reload, then check that each block has an item form and converts as expected.

data/c/tags/block/chisel/aluminum.json

{
  "replace": false,
  "values": [
    "minecraft:iron_block",
    "examplemod:aluminum_block"
  ]
}

Keep the existing family entries. Keep "replace": false unless you want to remove all the entries from Chisel and other datapacks.

Configure durability

Chisel's common startup configuration controls durability for each tool tier. The generated file is config/chisel_common.toml.

config/chisel_common.toml

[general]
iron_chisel_durability = 512
diamond_chisel_durability = 5096
obsidian_chisel_durability = 10048

Set a durability value to 0 to disable durability for that chisel. Because these are startup settings, restart the game or server after changing them.

Getting everything working together

Prefer tags for simple family membership. They're the simplest way to add a block to an existing family.
Let the owning mod provide resources. Chisel does not generate models, textures, loot tables, or translations inside another mod's namespace.
Test connected textures with resource packs. Model overrides can change or remove the texture slots CTM expects.
Check recipes with JEI. Chisel exposes its conversions through JEI when that integration is present.
Avoid duplicate memberships. A block should not belong to conflicting Chisel families.

If your integration needs a new family, custom registration, or model metadata—not just membership—use the developer addon API.

Pack release checklist

Launch a clean client with the exact exported pack files.
Join a dedicated server and open both Chisel and Auto Chisel menus.
Verify custom family-tag blocks convert in both directions.
Place connected glass and at least one multiblock texture across a chunk boundary.
Check that chisel durability feels right for your pack.
Keep the full log and exported mod list for issue reports.