Notes and Events

A calendar note is a journal entry page attached to a date. Notes hold rich text content, an icon, a recurrence pattern, categories, and an optional macro trigger.

Note storage

Notes are stored as journal entries inside a per-calendar folder, nested under a top-level Calendar Notes folder in the Journal sidebar. Neither folder can be deleted: the delete is refused and a warning is posted instead. Access notes through the calendar UI or the Note Viewer.

Creating a note

1. Click a date on the calendar grid
2. Click Add Note
3. Pick one or more categories in the preset dialog, or confirm without one
4. Set the title, icon, dates, times, and content
5. Close the window to save

The preset dialog accepts more than one category. Ticking Always use this selection with a single category chosen stores that category as your default and skips the dialog on later notes; reset it from the Notes tab of the Settings Panel. Cancelling the dialog abandons the note instead of creating an uncategorized one.

A new note is discarded when you close it while it still carries the default name and has empty content. To keep it, give the note a title or type something into the content editor.

Editing and deleting

Edit a note

1. Click the note to open it in view mode
2. Click the edit icon in the header to switch to edit mode
3. Make changes
4. Switch to view mode or close the window; changes save automatically

Delete a note

1. Open the note in edit mode
2. Click the trash icon in the header
3. Confirm deletion

---

Note sheet

The note editor has three tabs: Content, Schedule, and Settings. Field edits save as you make them. The content editor commits when you leave edit mode or close the sheet.

Content tab

• Title: Note name
• Emblem: FontAwesome class or image file (right-click to switch modes)
• Color: Note color via color picker
• Subjects: Documents the note is about. Drag a document onto the subject drop zone to add it. Each subject shows as a chip; click the chip name to open that document, click the x to remove it.
• Content: Rich text editor for the note body

Festival notes display an info banner on each tab. For a GM the banner links to the calendar editor; players see the banner without the link.

Schedule tab

The Schedule Mode toggle at the top of the tab switches between One-time Event and Recurring Event. The controls below it change with the mode.

Switching from Recurring to One-time prompts for confirmation, because it clears the condition tree.

One-time mode

• Start Date / End Date: Click to open a date picker. The two pickers sit side by side and set the event’s span directly.
• Time: Hour and minute inputs for start and end time
• All Day: Checkbox that disables the time inputs

Recurring mode

• Anchor Date: Click to open a date picker for the base date the recurrence pattern is anchored to
• Repeats Until: Optional date picker that caps the recurrence. Click the x button to clear.
• Time: Hour and minute inputs
• All Day: Checkbox that disables the time inputs
• Duration: Number of days each occurrence spans (minimum 1)
• Condition Presets: A select that reflects your calendar’s weekdays, months, seasons, and moon phases. Interval presets count days from the anchor date. Occurrences keep their spacing across month and year boundaries.
• Edit in Builder: Opens the visual condition builder with the note’s current conditions loaded
• Condition Summary: Displays the note’s recurrence rules as pills. Right-click a pill to delete it.
• Max Occurrences: Limit how many times a recurring note appears. Leave blank for unlimited.
• Occurrence Preview: Read-only list of the next upcoming dates

Choosing a preset on a note that already has conditions opens a confirmation dialog with a merge checkbox, which merges the preset into the existing conditions instead of replacing them. On a note with no conditions the preset applies straight away.

The same dropdown holds a Clear All Conditions entry. It strips the note’s recurrence rules after a confirmation, leaving the note on its anchor date alone.

Show Bookends lives on the Settings tab under Display Style.

Settings tab

Display

• Visibility: Visible, Hidden, or Secret. A note owner can choose Visible or Hidden. Secret is offered to GMs only.
• Silent: Suppress reminders and event announcements
• Display Style: Icon, pip, or banner
• Show Bookends: Start/end markers on the first and last days. Enabled only when the event spans more than one day.
• Macro: Select a macro to execute when the event triggers

The Macro field only appears when at least one macro is visible to you. When a player assigns a macro they cannot execute, the assignment is dropped on save. A macro is also skipped at trigger time if the note’s author has since lost permission to run it.

Reminders

• Notification Type: None, Toast, Chat, or Dialog
• Notify: Everyone, GM Only, Author Only, Note Viewers, or Specific Users
• Reminder Offset (labeled “Notify Before”): How far before the event to fire the reminder, in the unit set by Increment. 0 fires at event start.
• Increment: Hours, Days, Weeks, Months, or Years, applied to the Reminder Offset value.
• Reminder Users: User list, shown only when Notify is set to Specific Users
• Save as To-Do: Mirrors the fired reminder into each notified user’s Don’t Forget list. Shown only when Don’t Forget is active. See Reminders.

Categories

• Select from existing categories
• Add new categories inline
• Categories with the player-usable flag disabled are hidden from non-GM users unless already assigned to the note
• The Default preset does not appear as a selectable category. It acts as a fallback for uncategorized notes and is hidden from category pickers and badge displays.

Ownership

Per-user permission dropdowns. Each user can be set to None, Observer, or Owner. The GM and the note author are fixed at Owner.

Per-user grants layer on top of the visibility default and are editable in every visibility mode. To add a player alongside the GM and author on a Hidden note, grant them Observer. Setting a player to None removes their explicit grant and returns them to the visibility default. Flipping visibility updates the default tier: Visible raises it to Observer, Hidden and Secret drop it to None; existing per-user grants are untouched.

Only GMs can manage note permissions. Non-GM users see a disabled ownership fieldset with a tooltip explaining the restriction.

---

Condition engine

Conditions check date, weekday, season, moon phase, and more to decide whether a note shows on a given day.

Condition fields

• Date fields: year, month, day, day of year, full date comparison, and more. Month and day can also be tested against another registered calendar; those fields appear only when more than one calendar is registered.
• Weekday fields: weekday, week number in month, inverse week number. When the calendar uses a week cycle, week-number fields count cycle rows instead of fixed-length weeks.
• Season fields: current season, percentage through the season, season day, solstices, equinoxes
• Moon fields: moon phase, named phase (New, Full, and so on), sub-phase (Rising, True, Fading), phase occurrence counts
• Cycle and Era fields: current cycle entry and era, when the calendar defines them
• Other fields: intercalary days, leap years, weather, eclipses, random values, event references, computed dates

See API Reference for the complete field list.

Condition operators

• Comparison: equals, not equals, greater than, less than, greater or equal, less or equal
• Modulo: repeating intervals like “every 4th year”. The interval counts from the note’s anchor date. An optional offset shifts the pattern by that many units. A note never appears before its anchor date, whatever the cadence would otherwise match.
• Event-relative: days ago, days from now, within the last N days, within the next N days

See API Reference for the complete operator list.

Condition groups

Each group has a Match dropdown:

• All: every condition must pass
• Any: at least one condition must pass
• Not All: at least one condition must fail
• Exactly One: only one condition may pass
• At Least N: a minimum number of conditions must pass, set by the Threshold field that appears next to the dropdown

Groups nest inside other groups, five levels deep at most. The Add Group button disappears from a group that has reached the limit.

To build “every 3rd Tuesday in winter during a full moon”, put conditions for weekday, week number, season, and moon phase in one group set to All.

Event-based conditions

A note’s schedule can depend on another note’s occurrences, such as “3 days after Festival X” or “within 5 days of Event Y”.

• Select the target note using the note picker in the condition builder
• Use event-relative operators: days ago, days from now, within last, within next
• Circular references are prevented

Computed dates

The Computed Date field resolves one date per year from a chain of steps. Select the field in the condition builder, then click the configure button to open the computed date builder.

A chain starts from an anchor step. Anchors include equinoxes, solstices, season starts and ends, a fixed month and day, and another note’s occurrence. Later steps refine the anchor:

• First After: Advances to the next date matching a moon phase or weekday. An on-or-after toggle also accepts the anchor date itself.
• Days After: Shifts the date by a day count. Negative counts shift backward.
• Weekday On or After: Advances to the next matching weekday.

The builder previews the resolved date for upcoming years and marks years where the chain does not resolve. Year overrides pin the result to a fixed month and day for a chosen year. The year on each override row is editable.

Condition builder

1. Open a note in edit mode
2. Go to the Schedule tab
3. Click Edit in Builder

In the builder:

• Select a field, grouped by category
• Choose an operator for the field type
• Enter a value using the field-specific input
• Add conditions and nested groups with the Add Condition and Add Group buttons
• Remove a condition or group by clicking its X icon

Removing a group that still contains conditions asks you to confirm first, but removing a single condition does not.

The builder has no reorder controls and only edits the condition tree. The preset dropdown and merge option live on the Schedule tab, next to the Edit in Builder button. Its optgroups are Basic, Weekly, Monthly, Yearly, Every Nth, Seasons, Moons, and Eclipses. Right-click-to-delete applies to the condition-summary pills on the Schedule tab, not to the builder.

---

Categories

Every world starts with built-in presets, and you can create your own. Open the Note Preset Editor from the Settings Panel to create, edit, delete, and reorder presets.

Defaults

Categories define defaults that fill in fields on a new note. Adding a category to an existing note prompts to apply the category’s styling and defaults.

Player-usable flag

Each category has a player-usable flag. When it is disabled, non-GM users do not see that category when creating or editing notes.

---

Subjects

A note can name the documents it is about. To link one, drag a document onto the subject drop zone on the Content tab. Subjects appear as a metadata row when you read the note in view mode, and each one opens the linked document. The Chronicle filters entries by subject.

---

Visibility

Level	Icon	Who Can See
Visible	(none)	All users with journal permissions
Hidden	Eye-slash	GM, the note’s author, and users granted Observer
Secret	Lock	GM only, and only when Show Secret Notes is enabled

• A note’s owner can switch it between Visible and Hidden. Only GMs can mark a note Secret.
• Secret notes are hidden from everyone by default, including GMs. Enable Show Secret Notes in the Settings Panel to see them.
• The Silent flag suppresses reminders and announcements independently of visibility.
• Non-GM users need at least Observer permission on the parent journal entry to see a visible note.

---

Duration and display styles

Duration

Duration is a number-of-days field. Whether it appears on the Schedule tab depends on the Schedule Mode:

• One-time: the Start Date / End Date pickers control the span directly. Duration is derived on save from the date range.
• Recurring: Duration is the primary control for per-occurrence length.

Multi-day events render as continuous bars across calendar days in BigCal. Show Bookends adds start and end markers on the first and last days, and is configured on the Settings tab.

Display styles

Style	Description
Icon	Default inline icon next to the note name
Pip	Dot indicator
Banner	Full-width bar spanning the event’s duration across days

In a BigCal day cell, notes sort banner first, then icon, then pip, with ties broken by name. Festival notes are not part of that list; a festival draws as an icon beside the day number. The MiniCal notes panel uses a different order: festivals first, then all-day notes, then start time.

---

Festival notes

Calendar festivals are created as journal notes using the condition engine. Festivals are templates that produce independent notes.

• After creation, festival notes are independent. Editing a festival note does not change the template.
• An info banner on the note editor links to the calendar editor for a GM; players see the banner without the link
• Festivals support leap-year-only scheduling via the Is Leap Year condition field
• Non-GM users cannot delete festival notes
• GMs can re-sync festival notes from Settings Panel > Notes tab
• Festival notes and the calendar note folder are created by the primary GM’s client

The Festivals tab of the calendar editor lists the festival notes themselves. Renaming a festival note, or changing its icon, color, or schedule, changes what that tab shows and what a calendar export carries.

---

Player permissions

Players create and edit notes based on Calendaria permissions, combined with Foundry document permissions.

Note

Players with the “Add Notes” permission but without Foundry’s core Journal Create permission can still create notes as long as a GM is present. The request is relayed to a connected GM.

What players can do

• Create notes using the Add Note button
• Edit notes they created
• Edit another user’s note when granted Foundry Owner permission on it
• Delete notes they created
• View notes with appropriate permissions

What players cannot do

• View secret notes, or hidden notes they did not author and hold no grant on
• Delete others’ notes or festival notes
• Modify time, date, or weather

There is no Edit Notes Calendaria permission. Editing another user’s note requires Foundry Owner permission on that note, set through the note’s visibility tier or a per-user Ownership grant. Edit mode in the note sheet is gated on document ownership. Calendaria’s note permissions are limited to Add Notes for creation and Delete Notes for bulk deletion.

---

For developers

See API Reference and Hooks.