Source Toggles and Monster Filtering

Dice Monster uses source-aware queries so players only see content from allowed owners.

How Sources Work

A source is an owner identity for content (for example, a specific user or system content).

Source identity stays stable as the source owner id, and UI metadata is layered on top:

displayName: label shown in source pickers and toggles
abbreviation: short label for chips/badges
toggleKey: stable key used to persist on/off source toggle state

Book metadata is stored in the database (content_source_metadata) so labels can be managed without app code changes.

Naming rules:

book/system sources use their configured book metadata (for example WotC SRD, TOB3)
user sources use the pattern UserName's Homebrew and abbreviation H

Allowed sources are combined from:

your own account
explicitly granted access entries
system content sources

These source filters are applied server-side when searching monsters, spells, powers, and other compendium content.

Source Controls in Practice

In admin and management screens, source controls are exposed as owner/user filters.

selecting a source narrows results to that owner
clearing the source shows all content allowed for your account

Monster Filtering

Monster browsing supports both source filtering and attribute filters.

Available monster filters include:

name search
CR range
HP range
AC range
creature type
creature size
alignment
role
special flags (for example legendary/lair/villain/mythic markers)

Access Management

Admin access management can grant or revoke source visibility between users.

This directly affects what appears in filtered queries for monsters and compendium content.

Persistence Notes

Source filtering behavior is enforced in query logic, and source toggles are keyed by toggleKey so saved preferences do not break when labels change.

Long-term per-account/per-campaign toggle persistence is still being expanded.