Triggers
Where to find it
A Trigger is one of the four kinds of block you can put inside a Chapter, alongside paragraphs, Headers and media. You insert it like any other block. It shows up as a dashed box with the Trigger's name, or "Trigger" if it has no name. The box also holds one line saying what it checks and does, and an Edit button (Set up while it is still empty). Pressing anywhere on the box opens its settings.
What your Reader sees
Nothing. A Trigger is invisible to your Reader, and their reading does not pause for it. The moment their reading passes the spot where you placed it, the Trigger checks its conditions and runs its results. What they see is the effect: a part of the story they can now reach, a mention they can now open, or a window over the page.
- It runs once. Once a Trigger has run for a Reader it does not run again on the same read-through, however often they scroll back past it. In Reading Simulation you can rewind to it from the Triggers tab and play it again.
- A Trigger whose conditions fail does nothing at all, and your Reader is not told a check happened. If you want them to feel the door that stayed shut, the prose after the Trigger has to say so.
- A window it opens holds the page. A Decision Template, a conversation, a combat or a shop opens over the story. Your Reader deals with it before reading on. They can minimize it, but they cannot read past the spot until it is done. A dice roll opens the same way and closes once the die has landed.
At the bottom of the Trigger window, What your Reader gets reads the whole rule back in your Reader's order. It changes as you pick, and reads like this: Your Reader never sees this Trigger itself, only what it changes. When they reach this point, if Ishmael's Coins is more than 1, reveal The Ship. A check with nothing in it shows as your checks pass, or as one check you have not filled in yet beside a finished one.
The modals
The settings window is one form. A Name box sits at the top. It is optional, and only you see it. A box below it says what a Trigger is. Then comes the rule itself, in one card with two named halves: When lists the checks, and Then lists the changes. With a second check, the heading grows into When all of these are true. The checks join with "and", never with "or". With the switch on Always, the When half goes, leaving one Always half. An empty Trigger offers four starting points above the rule. Decision Templates and Dialogue Templates use the same form, so once you've built a Trigger you can build those too.
A newly placed Trigger. Four starting points sit above the empty rows. The one that reveals a later part offers only The Ship and The Quarter-Deck as Chapters, because they come after this one.
What goes into a Trigger
- Name: optional, up to 50 characters. Readers never see it. A name makes the Trigger easy to find on the Story Canvas and in the Chapter's block list.
- Conditions: up to 10 checks the Trigger runs before it does anything. All of them must be true.
- Results: up to 10 things that happen when the conditions are met. If there are no conditions, they happen every time.
Reading a row
Every condition and every result is one row of boxes, and each box narrows the one before it. The first asks what kind of thing the row is about, and the next asks which one. The rest ask what to check or change about it. The boxes fill from left to right, and a box only appears once the one before it has an answer. A line under the row reads the whole thing back as a sentence while you build it.
The words in the boxes change with what you picked:
- A Numeric Fact offers is exactly, is more than and is less than.
- A Text Fact offers is exactly, is anything but, has the words and does not have the words.
- A bag offers holds and does not hold.
- A list offers includes and does not include.
- A Yes-No Fact keeps a bare is, because its value box already offers True or False.
When a thing has only one sensible part to talk about, the box is filled in for you.
Conditions
The When half
A condition is a question the Trigger asks before it runs: Has your Reader been here yet? Does this character know the protagonist's name? Did they pick up the lantern? Each condition names a target and what to check about it. You can ask:
- About a Chapter: has the Reader passed it, or a specific Header inside it? Chapters that come after the Trigger are greyed out here (see the forward-only rule below).
- About a Glossary Item: has it been revealed, does one of its Facts match a value, does it carry a Tag? You can target a specific Glossary Item, or Reader, which stands for whichever character your Reader is playing as. Reader only means something once a Character has Playable switched on in its Character and Creature settings. Reader can only be picked once a Character has it on.
If the Glossary Item you pick has no Facts yet, there is nothing to point at. The row says so, and the rule is about the whole item. It offers to open that item in a new tab, and to look again once you have added a Fact. That way you do not lose the Trigger you were part-way through.
The comparisons offered depend on what you picked. A Fact offers the words that fit its type, as listed under Reading a row above. A number gets is exactly, is more than and is less than. A bag gets holds and does not hold. A Glossary Item itself offers Is revealed, Has any of, Has all of and Has none of its Tags. Reader offers is playing as. Options that don't fit the target are not shown.
Results
The results section
Results are what the Trigger does when its conditions are met. Building one works like a condition: pick a target, pick an action. The difference is that the action changes something instead of reading it.
- Chapter: reveals a Chapter or a specific Header so your Reader can reach it, or hides one again. Chapters that come before the Trigger are greyed out here (forward-only rule). A reveal opens the path, but your Reader still reads their way there. The Story Flow page explains how.
- Glossary Item: Reveal or hide the item itself. On one of its Facts: Set to, Add, Subtract, Raise by %, Lower by %, or Reset to its starting value. Put in or Take out of a bag or a list. One Put in on a bag can name up to 200 Items, each with its own amount. A Take out of one Item takes the amount it names. Of several, it takes all of each. Add Tags or Remove Tags. The same results work on Reader, for whoever they play as.
- Many at once: applies one change, in one step, to every Glossary Item, Chapter, Header or Fact Card Section of one kind. It can take all of them, or only the ones with a Tag. The row asks Every... which kind, then All of them or Only the ones with a Tag, then the Tag. It suits a moment that every enemy in the room needs to react to.
- Dynamic Component: opens a Decision Template, a Dice Template, a Dialogue Template, a Combat Template, a Trade Screen, or raises a Background. The Trigger opens it for your Reader the moment it runs, one per Trigger.
Results run in the order you list them, and you can mix the types. One Trigger can change two Facts, reveal a character, reveal a later Chapter, and open a Dialogue Template.
Always, or only when
A two-way switch at the top of the rows chooses between Always and Only when...:
- Always: no conditions. The Trigger runs the moment your Reader reaches it. It is for something that should always happen at that point in the Chapter.
- Only when...: at least one condition. It checks them when your Reader arrives, and the results run only if every condition is true.
The forward-only rule
Look back, act forward
A Trigger can only check what your Reader has already read, and it can only open up what lies ahead of where it sits.
- Conditions can only ask about things before the Trigger: earlier Chapters, or earlier Headers in the same Chapter.
- Results can only act on things after the Trigger: later Chapters, or later Headers in the same Chapter.
The dropdowns enforce this. A Chapter on the wrong side of the Trigger stays in the list greyed out, with the reason under the row. Headers inside the Trigger's own Chapter are only offered on the side the row may use: above the Trigger for a check, below it for a change.
The box at the top of the window names the two sides in your own titles, for the Trigger you have open. A check can look back at lists what is behind it. A change can reach forward to lists what is ahead. A Trigger at the very start of the book has nothing behind it. The line then says so, which explains an empty dropdown.
Nesting under a Header
A Trigger placed between two Headers belongs to the Header above it. The editor draws a thin line down the left of everything under a Header, one line per level, so a Trigger inside a part sits beside that part's line. It matters in two places:
- On the Story Canvas, a Trigger sits under its Header, indented, inside its Chapter's band.
- A reveal that targets a Header treats the Trigger as inside that Header. That is useful when a Trigger should run only after your Reader has entered a specific sub-section.
Validation
A Trigger can become invalid in three ways, and a fourth problem blocks publishing even though the Trigger itself looks fine. The editor and the publish check won't let any of these through until they're fixed.
- Something it points at no longer exists: a Chapter, a Header, a Glossary Item, a Fact, a Tag, or a Dynamic Component you deleted. In the Trigger, the row that pointed at it has an empty box where it was. A replacement in that box fixes it, and so does removing the row.
- The forward-only rule got broken: usually because something moved after you set it up. Promoting a Subheader to the top level, reordering Chapters, or dragging a Header past the Trigger can all do it. Each can put a referenced spot on the wrong side, and the Trigger gets the warning mark. In the Trigger, the row that pointed there comes back with its boxes emptied. The Chapter and Header lists offer only what the Trigger can still reach from where it sits now. A new target fixes it, and so does moving the Trigger itself. The demo above shows one.
- A Dynamic Component it opens reveals something at or before the Trigger: this one can surprise you. Editing a Dialogue Template or a Decision Template elsewhere in the book can put the warning mark on a Trigger you haven't touched in weeks. Your Trigger opens that template, so the template's reveal actions count as part of your Trigger's results. They must respect your Trigger's position too. The template stays valid for anyone else using it. Only this Trigger's use of it is broken. The fix is to change what the template reveals, or to open it from a Trigger later in the story.
- The Dynamic Component itself is invalid for another reason: the Trigger pointing at it won't get the mark on its own. The Trigger only checks that the template exists, not that it is currently valid. You still can't publish. The publish check refuses any book with an invalid Dynamic Component. The broken template appears on the publish page as its own row to fix.
Deleting a Trigger removes its block from the Chapter and can leave orphaned references elsewhere. The editor warns you before it lets you delete.
Questions writers ask
The same questions and answers sit behind the "?" in the Trigger settings window.
How this fits your story
What is the difference between a condition and a result?
A condition, under "When", is a question about what your Reader has already done. A result, under "Then", is a change that happens once the answer is yes.
"Has the Reader seen The Ship?" is a condition. "Reveal The Ship" is a result. The same thing can appear on either side, which makes them easy to mix up. One asks about it, and the other changes it.
Both are built the same way, in the same order, everywhere in Verhaler. First comes what the row is about, then what to ask or what to do.
If I add several conditions, do all of them have to be true?
All of them. Rows are only ever joined with And. There is no "Or" anywhere in the builder.
"Either of these" takes two separate Triggers, each with one condition and the same result.
Up to 10 conditions in one group.
What is the first box in a row, the one that asks what should be checked or changed?
It picks what the row is about.
In a condition, that is a Chapter or a Glossary Item. The dice roll and an Emotion are offered too, where the window you are in allows it.
In a result, it is the thing you want to change: a Chapter, a Glossary Item, or many of them at once ("Many at once"). Where the window you are in allows it, it can also be a Dynamic Component to open.
The boxes after it narrow down what you picked, so they only make sense once the first one is filled.
Can one result put several Items in a bag, or take them out?
Yes. A "Put in" on a Container Fact can name up to 200 Items, each with its own amount.
A "Take out" of one Item takes the amount it names. A "Take out" of several takes all of each.
What is the difference between "The whole Chapter" and one of its Headers, or "The item itself" and one of its Facts?
The whole thing, not one of its parts.
The Ship with "The whole Chapter" means the Chapter itself. A Header instead means only that part. On a Glossary Item, "The item itself" means the item, as against one of its Facts or one section of its page. When the row is about the Reader, the same choice reads "The Reader themselves".
When there is nothing inside to choose from, that box is not shown at all. The whole thing is the only answer, so it is taken for you.
Why did my result disappear after I saved?
A set whose result row was never filled in is not saved. Under Always, a Trigger says "Nothing to save yet. Pick at least one result first". It says "A few of these are still empty, so nothing was saved yet" under Only when... instead. Elsewhere, the empty set is quietly dropped when you save the window. That is the usual reason a result seems to vanish after saving.
What do "Always" and "Only when..." mean?
They decide whether the results need conditions at all.
Always: the results happen every time, and there is no "When" block to fill. Only when...: they happen only when every condition under "When" is true. The one that is pressed in is the one you are in.
What does revealing or hiding something do to my Reader?
Chapters, Headers and Glossary Items can start out hidden, and stay out of your Reader's reach until something reveals them.
A reveal result on The Ship lets them get to it. A hide takes it away again. The condition "is revealed" asks about that same state. That is how one part of your story can depend on another having happened.
How do I open a Dice roll, a Dialogue or a Combat from here?
Through a result: Dynamic Component in the first dropdown, then the kind, then the one you built under Dynamic Components in the sidebar.
It has to exist first. An empty list means nothing of that kind is built yet.
One Trigger can open only one Dynamic Component. Once it is used, the option is greyed out on the other rows, with the reason on it.
This window's own settings
Why are some Chapters greyed out in the list?
Because of the forward-only rule.
A condition can only look backwards, at what your Reader has already passed. A result can only reach forwards, at what they have not got to yet.
A Chapter on the wrong side stays in the list greyed out, with the reason under the row. So if The Ship is greyed out in a result, it sits before this Trigger. Your Reader has already been past it. Headers inside this Trigger's own Chapter are not offered on the wrong side at all. The next answer covers that.
So where you put a Trigger decides what it can do. Moving it earlier gives its results more to reach, and its conditions less to check.
It says every Header sits on the wrong side of this Trigger.
The same forward-only rule, inside this Trigger's own Chapter. Results can only reveal Headers that sit below it. Conditions can only check ones above it.
If the list is empty, there is nothing on that side yet. Moving the Trigger up the chapter fixes that, and so does a new Header below it.
What will my Reader get from this?
The line at the bottom of this window, under What your Reader gets, says it. It tells the whole rule in the order your Reader meets it, and it changes as you pick.
Your Reader never sees the Trigger itself, only what it changes. So the sentence starts from the moment they reach the spot, and says what happens next.
A rule you have not finished reads as unfinished. A check with nothing in it shows as your checks pass. A rule with no change yet says nothing happens yet. Neither is left out, so the line never reads as finished while a row is still empty.
Above and below what, exactly?
The two lines in the box at the top of this window say it. They name the two sides in your own titles, for this Trigger where it sits now:
A check can look back at is everything behind it: the Chapters before this one, and the Headers above it in this Chapter. A change can reach forward to is everything ahead of it.
If one of them says there is nothing, that explains the empty dropdown underneath. A Trigger at the very start of the book has nothing to check. One at the very end has nothing to reach. Moving it changes both lists.
Should I give it a name?
It helps you, never the Reader, who never sees a Trigger at all.
The name shows on the block in your chapter, on the Story Canvas, and in the Reading Simulation's Trigger Log. Without one, you are left working out which of two "Unnamed Trigger in Chapter 3" was the one about the lantern.
Names start to matter once you have more than about three.
When something looks wrong
"Add another" has stopped doing anything. Why?
You have reached a cap. One group holds up to 10 conditions, and one Trigger holds up to 10 results.
A second Trigger can carry more, with its own conditions and results.
How do I check that any of this works?
In a Reading Simulation, by reading past the point where it should happen.
The sidebar's Trigger Log lists every Trigger you passed. "What it checked and changed", under a Trigger in the log, shows each condition marked Passed or Failed, and each result Applied or Skipped. That tells you whether the problem is your condition or your result.
The Glossary Item I picked has no parts to choose from.
Then it has no Facts yet. There is nothing on it to point at, so the row is about the whole item.
The row says which item it is and offers to open it in a new tab. Once a Fact is added there, I added one, look again in this tab picks it up. This Trigger stays open and keeps everything you have already picked.
A Fact is something your story remembers and changes, such as a number, a yes or no, or a bag. A rule about the item as a whole is already right as it is. Whether it has been revealed, or carries a Tag, is that kind of rule.
"This one cannot open from here"
The Dynamic Component you picked reveals or hides a part of the book that sits above this Trigger. Your Reader would already be past whatever it changes. It is the forward-only rule again, one step removed.
There are three ways out. A different one can be picked. That component can reveal or hide something later instead. Or this Trigger can move earlier in the story.
When a Trigger above already opens the same one, this one is a repeat, and the warning names it. A second roll after a fail needs its own Dice Template, with results that open parts below this Trigger.
Left as it is, it saves, and the Trigger is marked with a warning. Until it is fixed, a Reading Simulation cannot start and the book cannot be published.
My Trigger turned red with a warning icon.
Something it points at is gone, or has moved to the wrong side of it. Deleting a Chapter does this, and so does dragging a Header from below the Trigger to above it.
One of its Chapter or Header rows pointed at the deleted or moved target. That row comes back with its boxes empty, and the lists offer only what the Trigger can reach from where it sits. A new target fixes it, and so does deleting the row. Moving the Trigger back, so its targets are on the right side of it, works too. Until then, a Reading Simulation cannot start and the book cannot be published.