SemethWikiSearch
Adventure Engine logoAdventure EngineBassSanctum logoBassSanctumCataclysm DeDust logoCataclysm DeDustEpicQuest Dungeoning logoEpicQuest DungeoningEpicQuest Hub logoEpicQuest HubEventMaker logoEventMakerLeylines logoLeylinesSpell Codex logoSpell CodexSpell Codex Ars Compat logoSpell Codex Ars CompatSpellActionbar logoSpellActionbarStructure Encyclopedia logoStructure EncyclopediaTikFiniTok logoTikFiniTokSC Final Adventure logoSC Final AdventureSC Final Adventure - Arcana logoSC Final Adventure - ArcanaSC Final Adventure - Machines logoSC Final Adventure - MachinesSC Final Adventure - Mechanical Genesis logoSC Final Adventure - Mechanical GenesisUpdatesAbout

EventMaker

Getting started

EventMaker is for pack authors. Players should never see a block. They walk through a doorway and something happens.

The short version:

  1. Place an Event Trigger (or inject a trigger id onto a normal block).
  2. Optionally place an Event Location with the same id. That is the spot commands should run from, not the player’s feet.
  3. Write a poll in data/<namespace>/command_poll/.
  4. Write an event in data/<namespace>/event_trigger/ that points at that poll.
  5. Pick whether commands run on the player or at the location.

Inside an EpicQuest Dungeoning piece this is how you open a door, drop a chest, or extract the party. Dungeoning 3.0 also has its own event markers. Use those for “player walked near this spot in this generate.” Use EventMaker when the trigger has to live in the overworld, the hub, or a structure that is not a dungeon instance.