Dungeon Meshi–style lorebook in SillyTavern (JSON sketch)

Fans searching dungeon meshi lorebook sillytavern json usually want a practical pattern: short keyword → snippet rows that fire when the chat mentions monsters, cooking, or camp logistics—without pasting a novel into scenario.

This article is an educational layout for original roleplay inspired by a dungeon-crawl cooking tone. It is not official media content; it only shows how character_book entries are shaped in Character Card JSON.

What “Dungeon Meshi” RP needs from a lorebook

For this kind of setting, lorebook-style entries often cover:

• Fauna / flora — edible vs dangerous, short behavioral notes.
• Camp rules — fire, tools, who cooks what.
• Tone — light panic vs pragmatic problem-solving.

In SillyTavern, that usually maps to character_book.entries: each row has keys (triggers) and content (text inserted when triggered). Budget and ordering are controlled by fields like token_budget, insertion_order, and priority on the book and entries.

Canonical JSON reference (use this page)

Do not treat a blog sketch as the spec. The full SillyTavern / Character Card lorebook JSON structure — outer book fields, entries, and per-entry keys — is documented here:

• (4/5) Lorebook: character_book and entries

That guide includes a minimal JSON example you can compare to your export.

Minimal pattern (illustrative only)

Below is a fictional three-entry fragment showing shape only (names and facts are generic originals, not excerpts from any work):

"character_book": {
  "name": "Camp lore",
  "scan_depth": 50,
  "token_budget": 400,
  "recursive_scanning": false,
  "extensions": {},
  "entries": [
    {
      "keys": ["mushroom", "forage"],
      "content": "Party rule: unknown fungi get a smell check before the pot—when in doubt, skip.",
      "enabled": true,
      "insertion_order": 100,
      "case_sensitive": false,
      "selective": false,
      "secondary_keys": [],
      "constant": false,
      "position": "before_char",
      "extensions": {}
    },
    {
      "keys": ["fire", "embers"],
      "content": "The cook keeps embers banked; sudden flare-ups scorch stew and tempers.",
      "enabled": true,
      "insertion_order": 110,
      "case_sensitive": false,
      "selective": false,
      "secondary_keys": [],
      "constant": false,
      "position": "after_char",
      "extensions": {}
    },
    {
      "keys": ["inventory", "rations"],
      "content": "Rations are counted nightly; swapping items without telling the quartermaster causes drama.",
      "enabled": true,
      "insertion_order": 120,
      "selective": true,
      "secondary_keys": ["theft"],
      "case_sensitive": false,
      "constant": false,
      "position": "before_char",
      "extensions": {}
    }
  ]
}

Tune keys to phrases your chat actually uses; selective / secondary_keys are for two-part triggers (see the field table in the linked article).

Strong internal links (same topic cluster)

• SillyTavern Lorebook vs Character Card — what belongs in the card body vs lore entries.
• World Info & lorebook JSON structure example — terminology and pointers for World Info vs character_book.
• Chub.ai: system prompt and character book — exports and UI vs JSON keys.

---

Series index: Blog · Silly Tavern character card fields

Preview and edit embedded JSON in PNGs on Mac with Sillycard.