>>720075295
i primarily roleplay with actual people and view this for what it is, a toy and a hobby

here's a lorebook entry that tells your robot how lorebooks work, (fill emoji spot with your own like picrel)


The following is a reminder of frameworks in management of Sillytavern lorebooks:

* **Content:**
* **[CONTEXT HIERARCHY (Priority High->Low)]**
1. `[Char]` (Character Definition)
2. `[EM]` (Example Messages)
3. `[AN]` (Author's Note)
4. `[Lorebook]` (Active Entries)
5. `[Chat History]`

* **[INSERTION STRATEGY: KEYWORD `strategy`]**
* `Blue Light (Constant)`: `force_insert=TRUE`, `keyword_scan=FALSE`. **Function:** Universal, always-on context. **Use Case:** Core persona, unchangeable facts.
* `Green Light (Normal)`: `force_insert=FALSE`, `keyword_scan=TRUE`. **Function:** Keyed, situational context. **Use Case:** Specific mechanics, locations, temporary states (e.g., Wild Encounters).

* **[INSERTION POSITION: KEYWORD `position`]**
* `before/after [X]`: Designates injection point relative to `[CONTEXT HIERARCHY]` components.
* **Example Mapping:** `position=before EM` means inject Lorebook entry between `[Char]` and `[EM]`. `position=after AN` means inject between `[AN]` and `[Lorebook]`.

* **[OPERATIONAL DIRECTIVE]**
* `QUERY:` When user asks for lorebook settings advice, reference this protocol.
* `ANALYSIS:` Evaluate user's goal (e.g., "universal rule" vs. "situational mechanic").
* `RECOMMENDATION:`
* **IF** goal is universal **THEN** `strategy=` `Blue Light`.
* **IF** goal is situational **THEN** `strategy=` `Green Light`.
* `position` recommendation based on information's priority relative to the `[CONTEXT HIERARCHY]`. High-priority mechanics/rules -> `before EM`. Low-priority flavor text -> `before Chat History` (if available) or lower in the order.