Triggers

Triggers are what activate dungeon functions. They listen for certain things to happen in the dungeon, and when they do, whatever function they're attached to will run. This includes mob kills, players entering an area, and even players right-clicking, breaking or placing a block at a location.

Common Trigger Options

All triggers have a set of configurable options when you edit them. Common options that are seen across many different triggers are listed here. Their default values are often different depending on the function or trigger in question.

• Trigger Conditions
  Applies to all triggers. Switches to the conditions editor hotbar. A trigger can hold up to 54 conditions.

• Allow Retrigger
  Only available on select triggers. Toggles whether or not the trigger (and consequently the function) can be triggered multiple times. Block Detector and Dungeon Start have no button for it: they start out with whatever the function they're attached to uses as its default, and after that they keep whatever value was saved with the dungeon.

• Delay
  Available on most triggers. How many ticks to wait after the trigger fires before the function runs. Defaults to 0 (no delay). There is no Delay button on Dungeon Start, the AND Gate, the OR Gate, Room Door Open/Close or Room Enter/Leave.

• Limit to Room
  Procedural dungeons only. When enabled, the trigger only reacts to things that happened in the same room as the trigger itself. The button is hidden while editing a dungeon that isn't randomly generated. Available on Signal Receiver, Player Detector, Chat Message, Player Death Counter and Mob Death Counter.

Trigger List

Icon	Name	Category	Description
	Dungeon Start	Dungeon	Activates when the dungeon begins. Trigger Conditions is its only option. A function saved without a trigger is given this trigger automatically.
	Signal Receiver	Dungeon	Activates when it receives a signal whose name matches its own, sent by a signal sender function. Signal names are case sensitive. "Wait For Conditions" (on by default) makes it keep re-checking its conditions once per second until they pass, instead of requiring them at the moment the signal arrives.
	Leave Dungeon Listener	Dungeon	Activates when a player leaves the dungeon. "Prevent Leaving" additionally stops the player from leaving.
	Right-Click Block	Player	Activates when a player clicks the block this trigger is located at. Click Type can be set to RIGHT, LEFT or BOTH. Spectators and off-hand clicks are ignored, and the click itself is cancelled.
	Player Detector	Player	Activates when a player, or a number of players, is within range of it. Distance defaults to 3 and is measured as a box around the trigger, not a sphere. Minimum Players accepts all for every living player in the dungeon. "For Each Player" makes it fire once per player in range instead of once for a single one. Only Survival and Adventure players are counted, and the check runs every 10 ticks.
	Key Item Detector	Player	Activates when a player uses a configured key item. The item can be consumed on use (on by default), and can be restricted to this function's block (or one block above or below it) or allowed anywhere in the dungeon. Click Type can be set to RIGHT, LEFT or BOTH, and MythicMobs items are supported.
	Chat Message	Player	Activates when a player sends a message matching a configured pattern in chat. "Exact Text" (on by default) requires the whole message to match; with it off, the message only has to contain the text. "Case Sensitive" is off by default. A matching message is blanked and cancelled, so it never reaches chat.
	Block Detector	Player	Activates when a player places or breaks a configured block type at the trigger location; the "Break or Place" toggle chooses which one, never both. The block filter defaults to ANY and also accepts a material name or mythic:<id> for a MythicCrucible custom block. "Toggle Place" controls whether blocks that don't match the filter may be placed there, and "Toggle Break" controls whether the matching block may be broken. Decorated Pots broken by player projectiles fire this trigger too. (v2.0.1)
	Player Death Counter	Player	Activates when a configured number of players have died. "Toggle Deaths Per Player" counts at most one death per player. The tally only resets if Allow Retrigger is on.
	Mob Death Counter	General	Activates when a configured number of specified mobs have died. Mob defaults to any, which matches any mob; with MythicMobs installed the name is also matched against Mythic mob IDs. Mob Radius limits how far from the function the kill may happen, and defaults to 0, which means anywhere. The killer becomes the function's target player; if the mob died with no killer, the function runs with no target.
	Redstone Receiver	General	Activates when the block at the trigger location becomes powered. It's edge triggered, so it only fires on the change from unpowered to powered. It fires with no player attached, so functions using it cannot target a single player or a party.
	AND Gate	Meta	Activates when all of several other configured triggers are activated. After it fires, every child trigger has to fire again before the next activation. Holds up to 54 triggers, and they all inherit the gate's Allow Retrigger setting.
	OR Gate	Meta	Activates as soon as any one of several other configured triggers is activated. Holds up to 54 triggers, and they all inherit the gate's Allow Retrigger setting.
	Room Door Open/Close	Room	(Procedural dungeons only) Activates when a door in the same room as the trigger opens or closes; the Action option picks which one, and defaults to OPEN. Set Door Name to any to match every door in the room, or to a specific door's name. Pairs with the Room Door Controller function.
	Room Enter/Leave	Room	(Procedural dungeons only) Activates when a player enters or leaves the room the trigger is in. "Trigger On" selects Player Enters Room, Player Leaves Room, First Player Enters or Room Emptied, and "Cause Filter" can narrow it to MOVE, TELEPORT, WORLD_CHANGE, QUIT or DEATH.

Note: A Room Door Open/Close trigger you have never opened the Door Name prompt on stores all, which matches no door. Type any into the Door Name prompt (or the exact door name) or the trigger will never fire.

Note: The Mob Death Counter is backed by two different internal triggers, TriggerMythicMobDeath when MythicMobs is installed and TriggerMobDeath when it isn't. They look and behave the same in the editor, but only one of them exists on any given server. A dungeon saved on a server without MythicMobs will fail to load on a server with it, and the other way around: the whole dungeon fails to initialise while its functions.yml is being parsed, not just the one function. The only fix is to edit the trigger's ==: line in that dungeon's functions.yml by hand.

Note: TriggerConditionHolder may show up in a dungeon's functions.yml or in a load error. It is not a real trigger and never appears in the trigger browser; it is the container that stores the IF conditions of the Conditional Function (Meta category).