An Apology, an Alarm, and Small Talk All Qualify. Which Comes First? A Table for Checking Priority Conflicts

When an apology, an alarm, and small talk all meet their eligibility conditions, writing “alarm before apology before small talk” is not enough: the explanation may already have played, or the person receiving the apology may have left. First identify candidates, exclude blocked ones, compare priorities, and then handle ties or gaps.

The Yarn Spinner documentation explains that saliency strategies select content from eligible lines or node groups. Read the documentation. The review table below is an original design suggestion. It does not imply that DramaFork uses this algorithm or describe implemented product features.

Start by fixing one scene, one selection moment, and one display slot. Content that can appear simultaneously in different slots need not compete. Whether dialogue already underway can be interrupted requires a separate rule.

The following is a fictional teaching example, not a real user case, and has not been validated through actual play. In an orbital station’s duty room, Lin Yao wants to apologize to Zhou Lan, an alarm lights up on the console, and the two have also started discussing old photographs. Lin Yao stays in the duty room throughout this example. Both the apology and the photo conversation require Zhou Lan to be present. Only one segment appears per round, followed by another check once it ends.

Here, “handled” means that emergency operations are complete and conversation may resume. “Cleared” means that verification is complete and this alarm has ended. These are recorded separately: an alarm can be handled without being cleared. Any outstanding explanation plays only while the alarm remains uncleared.

There are three priority levels, with level 1 first. The photo conversation must wait until the apology is complete and the misunderstanding is resolved. Even if another event resolves the misunderstanding early, the apology cannot be skipped. “Apology accepted” is not an additional condition: acceptance or rejection cannot substitute for checking whether the misunderstanding has been resolved.

Eligibility does not guarantee availability: blocking conditions have veto power. Raising the apology’s priority cannot make someone who has left hear it. The fallback does not participate in ranking. Check its own conditions only when all ordinary candidates are confirmed unavailable.

The table header should identify the scene, check time, state version, and authorial intent. Update the version only when relevant facts change, such as a character leaving, alarm handling finishing, or an ordinary segment ending. Advancing the round or recording that a waiting line has played does not update the version. When checking the waiting line, compare against its recorded version so the act of recording it does not trigger a replay.

Round one: Zhou Lan is present; the misunderstanding occurred and remains unresolved; the apology is incomplete; the photo topic has been opened, but the photo conversation segment has not played. This alarm has occurred but has neither been handled nor cleared; its explanation has not played, and neither has the waiting line in the current version. All three ordinary segments meet their eligibility conditions, but the apology and photo conversation are blocked, so the alarm explanation appears. This checks blocking only: removing the priority numbers would produce the same result.

Set up a separate comparison to check ranking: retain all other round-one states, changing only the alarm to handled but not cleared. Operations are complete, but verification is unfinished, and the explanation still has not played. Both the explanation and apology are available; the photo conversation remains blocked. The level-1 explanation wins. This is what tests priority.

Return to the original example. When the explanation ends, update only its played record and the state version. Do not also mark the alarm as handled. In the next round, the explanation is excluded, while the apology and photo conversation remain blocked. Display “Lin Yao looks toward the console, waiting for Zhou Lan to finish the operation,” and record that it played and in which version. Another check within the same version also excludes the waiting line. No new segment appears; the story waits for an event to advance it.

Only after the story explicitly depicts the handling operation being completed should the alarm state and version be updated, making the apology available. Delivering the apology in full records only that it has been made; it does not automatically resolve the misunderstanding. If the misunderstanding remains unresolved, the photo conversation stays blocked. If another event has already resolved it, the photo conversation can play after the full apology, even if the apology was not accepted, provided all other table conditions are met. If the misunderstanding is resolved early but the apology is incomplete, the photo conversation must still wait. This is consistent with the apology’s eligibility condition that a misunderstanding “occurred.”

A record might read: “Round two: explanation played, alarm unhandled; all ordinary candidates blocked; waiting line first displayed and logged in version two; rechecking the same version displays nothing; progress depends on the handling operation.” For each round, retain the candidates, reasons for exclusion, result, and any missing information.

First, create a tie: add a level-1 “hatch notice” and make it available at the same time as the explanation. Specify a fixed order, combine the segments, or add distinguishing conditions. Without a tie-breaking rule, mark the selection as “not uniquely determined.” Do not silently use table row order to decide.

Next, create repetition: leave the alarm state unchanged after the explanation plays. If the explanation appears again, check whether its already-played blocking condition or playback record was incorrectly cleared. If an old record blocks a new alarm, scope the explanation record to the specific event. For the waiting line, check both replay within the same version and whether round changes have been mistaken for state changes.

The third case is prolonged deferral of lower-priority content. If new level-1 segments keep arriving, the apology may never get a turn. Continue the walkthrough until a character leaves and check opportunities to resume: a dedicated conversation slot could be scheduled after the alarm is handled. If you decide the apology is missed, write its consequences. Do not treat an undisplayed segment as completed. The photo conversation will also be blocked in this example and must be tracked alongside it.

Finally, check gaps and unknowns. When Zhou Lan leaves, both the apology and photo conversation are blocked. If the alarm has also been cleared, the line about waiting for the operation no longer meets its conditions. Write a separate departure transition with explicit conditions. If Zhou Lan’s presence is unknown, mark that state as missing. Do not treat it as “absent,” or conclude from it that all ordinary candidates are unavailable. A valid gap can contain no new segment. A fallback cannot supply unknown facts.

To preserve the apology’s emotional momentum, move the alarm before the apology begins. To convey the regret of an interruption, write a separate brief interjection and retain the record that the apology is incomplete. When two pieces of information need to be understood together, combine them into one segment. These changes affect timing, interruption behavior, and content organization respectively; raising a number alone cannot achieve them.

The table suits competition between discrete segments at a defined moment. For continuous performance, simultaneous speakers, or players deciding whom to hear first, determine the display and interaction model first. If players choose, also specify whether unchosen segments are deferred, become unavailable, or can be revisited.

Before submitting the draft, ask another reviewer to recalculate each round’s candidates, blocks, result, and state changes using only the state record and table. If the answers differ, identify missing conditions or tie-breaking rules. The record should explain why the alarm plays first, when the apology returns, whether the photo conversation meets conditions including a completed apology and a resolved misunderstanding, and when displaying no new segment is allowed.