Skip to main content
/why is the player-facing command. Answers are Adventure chat (clickable actions, no inventory GUI). Console uses /cc why instead — see Commands.

/why — last death

After you die, /why (or /why death) prints HOW DID YOU DIE? and the captured chain, effect-first. No death recorded yet:
Permission: causechain.why.self (default true). With hints.on-death: true (default), CauseChain can hint you to run /why after a death. Hints do not change the graph.

/why deny — last cancelled build

After WorldGuard or GriefPrevention cancels a place or break, /why deny prints WHY CAN’T YOU BUILD? and names the plugin plus region or claim, for example:
  • WorldGuard spawn (visitor) / flag block-place deny
  • GriefPrevention Owner (visitor) / claim build permission
If two protection plugins both deny, both are listed. CauseChain does not invent a canceller. No deny recorded:
Wilderness with no claim is not a named GriefPrevention deny. Lands is not named. Permission: causechain.why.self.

/why inspect and /why here

Inspect looks at the block you target for captured chains inside land you can build in (causechain.why.claim, default true). Staff with causechain.why can inspect anywhere. Bare /why with no args: players get last death; staff (causechain.why) toggle inspect mode on/off instead.

Empty inspect

When CauseChain has no chain at that block, chat names the land when it can, then sends you to CoreProtect:
Inspect is not /co i. It will not invent a placer from CoreProtect or from “someone was here.” If you are not in your own claim or region, claim inspect replies that the land is not yours.

Audience: players vs staff

CauseChain shows less to players; it does not capture less. Unknown roots still print: Unknown is a valid answer. No parent was recorded. Staff lookups: /why player <name>, /why entity <uuid>, /why chain <id> require causechain.why.