Secondary's Scheduled Events TI
Technically the summary AI is supposed to keep track of upcoming events on its own, but I found that it would often forget it or forget when it was so I decided to make a more stable way to do it via tracked items
JSON[edit]
{
"id": [REPLACE],
"name": "Scheduled Events",
"positionInList": [REPLACE],
"dataType": "yaml",
"visibility": "everyone",
"description": "A list of scheduled events and when they are supposed to happen",
"updateInstructions": "Whenever something comes up where something will or should happen at a specific time in the future record it here. If the time it will happen changes, change it here. Remove an event only when I either show up, see it happen, I am specifically told it happened or I get told I missed it",
"formatExample": "- event:\n location: London\n description: A bomb will go off\n time: \"5:35 on Tuesday, November 25th, 2025\"\n- event:\n location: Home\n description: A zoom meeting\n time: \"Noon on the 5th\"",
"enforceFormat": false,
"formatSchema": "",
"initialValue": "",
"initialValueBasedOnPC": "same",
"autoUpdate": true,
"variableName": "scheduled_events",
"driftAcknowledgedForName": null
}
Plaintext[edit]
Data Type[edit]
YAML
Description[edit]
A list of scheduled events and when they are supposed to happen
Update[edit]
Whenever something comes up where something will or should happen at a specific time in the future record it here. If the time it will happen changes, change it here. Remove an event only when I either show up, see it happen, I am specifically told it happened or I get told I missed it
Layout Example[edit]
- event: location: London description: A bomb will go off time: "5:35 on Tuesday, November 25th, 2025" - event: location: Home description: A zoom meeting time: "Noon on the 5th"
Explanation[edit]
Its a pretty basic system, the idea is that its a basic YAML layout where its a list of events and each event has a date and time, a location, and a description. This is just enough information for the AI to reconstruct an event if its been lost to the summary or to realize it needs to reference something stored in summary. The goal is not to be verbose and explicit, but simply be a nudge and a thing to check when it generates a turn.
Caveats[edit]
This tracked item really only works if you either print whereWhen somewhere in the turn itself or if you have a whereWhen replacement TI.
The tracked item specifically tries to be lax with removing things from the list to prevent the story from moving past important events but this can sometimes cause it to keep items on the list for too long.
Since I wanted to use this lots of places, the instructions for when to add an item are vague and it often misses when it should do so.