>>538047930
the redpill is that roleplay is just cooperative novelism and you're writing the book with someone else

>>719785316
>op thinks its only going to be $1000

for your sillytavern-specific lorebook/char creator assistant needs
>lorebook robot that creates lorebook robots
i love the future


### **[Lorebook Entry: SillyTavern Context Protocol]**

* **Keywords:** `SillyTavern`, `lorebook`, `context`, `insertion`, `UI`, `position`, `strategy`
* **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.

The following is an example character sheet and should be the baseline for suggestions in the future.
***
**Meta-Instructions:**
* **Objective:** Generate a token-efficient, LLM-readable character profile.
* **Directive:** Prioritize concise keywords and short, descriptive phrases.
* **AVOID:** Purple prose, long paragraphs, redundant adjectives, and information not immediately relevant to the character's core identity and function. Every token must serve a purpose.
***

[Character Name]

A concise, three-sentence summary defining the character's core concept, their primary role in the world, and their immediate situation.

Physical Profile:

Species:
Gender:
Age:
Height:
Measurements:
Attire: [Signature or typical outfit]
Appearance: [Defining physical features]
Affiliations & Motivations:

Affiliation(s): [Group, Faction, or Organization]
Goal: [Primary driving objective]
Motivation: [The 'why' behind their goal]
Personality & Dialogue:

Traits: [Keyword, Keyword, Keyword, Keyword, Keyword]
Demeanor: [How they act and present themselves]
Example Dialogue: "[A single, representative line of dialogue.]"

>>718684785
i'm not into it so anything that curbs junk data and gets people on board to make more art of women with big titties and mommy hips are good for me

>>513477543
Top fucking kek. Ohio in Beit hanun?

At least try next time

>>718317175
>>718317317
nta but those examples have extremely prominent chins and jawlines which is typically offputting for a lot of people
i personally like it cause that means they'll birth handsome sons but everything about 2025 is soft and gay and people want women that birth chinlets now

>>508779883
my value is not measured by the approval of inferiors