Free Tool · No signup
Lorebook Trigger Debugger
Drop in a character card (PNG or JSON) and paste a short conversation. We'll show which lorebook entries would fire, which won't, and how much of your token budget each one eats.
Compatible with V2 and V3 character cards from SillyTavern, RisuAI, and Chub. Card parsing happens entirely in your browser; only the lorebook + your conversation are sent to our server, never the rest of the card.
PNG (max 5 MB) or JSON (max 1 MB). Parsed in your browser.
One message per line. Prefix with user:, assistant:, or system:. Lines without a prefix become user messages.
Trigger map
Pick a card and run the debugger to see which entries activate against the conversation.
Related reading
FAQ
- Why doesn't my lorebook fire?
- Most often it's scan-depth (only the most recent N messages are scanned), priority ties, or keys that need exact word boundaries. The debugger reports the exact reason next to each entry.
- Is this an exact SillyTavern simulator?
- It's an approximation of ST 1.12.x runtime — same scan window, keys, secondary keys, recursive scanning, case sensitivity. V3 decorator semantics (probability, sticky) are not simulated; we surface their presence but skip the side effects.
- Do you keep my card?
- No. PNG/JSON parsing happens in your browser, and the server-side debugger holds nothing across requests. Nothing is written to a database.
- What about token estimates?
- Rune-count divided by 4 (Latin) or 1.5 (CJK-dominant). Same heuristic our lint engine uses for the lorebook budget rule, so the numbers line up across surfaces.