# Master Categories

A master category is like a label on a file folder - it tells you what's inside before you open it.

## **Basic Structure**

{% code overflow="wrap" %}

```js
[Master Category:
Cat1: detail1(desc1, desc2), detail2(desc3, desc4)
Cat2: detail3(desc5, desc6, desc7)
...]
```

{% endcode %}

{% code overflow="wrap" %}

```js
[Environmental Triggers:
Office: entering building(professional mode(straightens posture, checks schedule)), meeting room(alert state(prepares notes, observes attendees)), break room(casual mode(relaxes shoulders, engages in small talk));
Public: crowds(heightened awareness(scans exits, stays alert)), quiet spaces(relaxation(deeper breathing, thoughtful responses)), social venues(sociable mode(initiates conversations, shows interest));
Private: home office(focus mode(organizes space, minimizes distractions)), personal room(decompression(releases tension, processes day)), quiet corners(recharge mode(takes breaks, practices self-care))]
```

{% endcode %}

## **Examples**

<figure><img src="/files/i83s3RlLzdlJI6YBe47F" alt=""><figcaption></figcaption></figure>

1. Single Character:

{% code overflow="wrap" %}

```js
[Alex Reed:
Occupation: tech expert;
Personality: individualistic(unempathetic, asocial, introverted)]
```

{% endcode %}

2. Group Information:

{% code overflow="wrap" %}

```js
[Party Info:
Members: Tom, Sarah, {{user}};
Tom: fighter(sword expert);
Sarah: wizard(spell master)]
```

{% endcode %}

3. Scene Setting:

{% code overflow="wrap" %}

```js
[Crime Scene:
Location: warehouse;
Evidence: footprints, broken glass;
Present: guard, witness]
```

{% endcode %}

4. Tracking Game Status

{% code overflow="wrap" %}

```js
[Combat:
Round: 3;
Next Up: Tom, then Sarah;
Special: dark room(hard to see)]
```

{% endcode %}

5. Showing Relationships

<pre class="language-js" data-overflow="wrap"><code class="lang-js">[Team:
Leader: Alex(de facto, assumed role);
<strong>Friends: Tom and Sarah(synergetic, compensatory strengths and flaws);
</strong>Conflicts: James and Mira(difficult communication, clashing beliefs)]
</code></pre>

## **When to Use Them**

* Managing several characters
* Organizing group info
* Setting up scenes
* Showing connections

<figure><img src="/files/Cj97oKh1CzrCY98oeif2" alt=""><figcaption></figcaption></figure>

## Troubleshooting

| Issue            | Error                              | Correction                   | Why/Solution                                      |
| ---------------- | ---------------------------------- | ---------------------------- | ------------------------------------------------- |
| Nested confusion | `Team Alpha[`                      | `[Team: Alpha:...; Beta:...` | Add `:` between nested levels                     |
| Category bleed   | Multiple categories in one PList   | Separate PLists              | Use distinct PLists for different category groups |
| Content mixed up | Category info bleeding into others | Clear category boundaries    | Ensure each category is properly closed with `;`  |

## When to Start Fresh

* More than 3 nested levels
* Very similar categories
* Mixed information
* Unclear boundaries

***

![](/files/iadwt1BvQjiz0K1C4cEt)\ <sub>© 2024 by SopakcoSauce. Except as otherwise noted, the content of this page is licensed under</sub> [<sub>CC BY-NC-SA 4.0</sub>](https://creativecommons.org/licenses/by-nc-sa/4.0/)&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sopakcosauce.gitbook.io/sopakcosauce-docs/master-categories.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
