# Known limitations

Worth reading before asking for something that isn't here. Most of these are consequences
of one deliberate design decision, explained at the bottom.

## Content

- **Furniture does not emit neighbour updates and carries no redstone.** Walls, fences,
  panes, stairs and slabs are display entities plus hitboxes, so they are not blocks to
  redstone or comparators. The **five nether brick fences are the exception** — they are
  served as real blocks drawn over vanilla's own nether brick fence, so they connect
  and behave like the real thing. For decorative building that is the right trade; it is not
  right for anything that needs to react.
- **Cinch stairs do not form corners with vanilla stairs**, in either direction. A CMB
  stair next to a vanilla stair will not join.
- **Pieces need CraftEngine's shulker hitbox**, so the pack is CraftEngine-specific by
  design. There is no Citadel or equivalent fallback.
- **Tinted glass panes are served as furniture**, so they take several hits to break and
  carry no crack animation, like the other furniture families.

## Versions

- **1.20.x and older, 1.8 included, are not supported, and cannot be.** CraftEngine's
  oldest supported version is 1.20.1, and CraftEngine applies the shulker hitbox scale
  only from 1.20.5. Below that, every CMB furniture piece would collide as a full block.
- **Vanilla materials the server does not have are omitted.** On a server older than 26.3
  the vertical slabs and horizontal stairs of cinnabar, sulfur and poplar are left out;
  before 1.21.4, pale oak and resin bricks too. This is automatic, not a configuration
  error — the pack filters against the live registry.

## Overlays and external tools show carrier blocks

**Jade, WorldEdit and similar tools report the vanilla carrier block, not the CMB piece.**

If Jade says "Red Mushroom Block" over polished end stone bricks, that is not a bug in
this pack — it is the design working. CMB borrows **no real vanilla blockstate**: every
block is drawn on a state CraftEngine allocates at load time. That guarantee is why no
barrel, crafter or chiseled bookshelf on your server ever changes appearance.

The consequence is that a tool which asks the client "which vanilla block is this?"
gets the carrier, because that is genuinely what the client received. Jade has no
CraftEngine integration and its lookup path only accepts a vanilla `Block`, so there is
nothing to configure.

The same applies to WorldEdit: a CraftEngine **default-pack topaz ore** may be reported as
nether bricks, since both use `auto_state: solid` and share one carrier identity.

What is *not* affected: in-world models, collision, and breaking behaviour are all CMB's
own. The overlay is showing the wrong **name**; the block itself is correct.

## Why it is designed this way

Three things were traded for "no real blockstate is ever borrowed":

1. **Furniture instead of blocks** for every family that cannot get a safe carrier —
   walls, fences, panes, stairs, slabs. Vanilla wall blockstates are multipart, and
   overwriting one strips the rules from thousands of real wall states, leaving them
   with no model at all.
2. **Client-side names from overlays** are the carrier's, as above.
3. **State budget is shared.** CMB uses 368 CraftEngine internal states out of 5,056,
   so it is a small consumer — but every pack on the server draws from that one pool.
   A server running CMB plus a resource-heavy pack is what approaches the ceiling.

## Not yet investigated

- **Tinted glass panes on top of walls do not connect.** Known, being worked on.
- **Stonecutter coverage.** Chiseled CMB pieces are stonecuttable because the upstream
  mod defines those recipes; vanilla does not cut its own chiseled stone bricks. CMB
  keeps the mod's behaviour for fidelity.