Raincloud/MixerTwitch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

development: just a few more tags

Browse Source
This commit is contained in:
Raincloud
2026-06-07 19:26:12 -06:00
parent f6015be3fc
commit c0e4e39c66
3 changed files with 32 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
marker-context.md
+8 -5
View File
@@ -72,9 +72,11 @@ Premiere keeps the raw stamp names; chapters use friendlier labels at the **same
---
## Deliverable content markers (red / descriptive)
## Deliverable content markers (descriptive)
Added during tagging (MCP or manual). Short labels: locations, bosses, setup beats, tangents worth skipping or revisiting.
Short labels: locations, bosses, setup beats, tangents worth skipping or revisiting. May be yours (live/post) or agent-added during visual tagging.
**Red is only for agentic stamps** — markers the agent adds during MCP/visual passes (`Underworks`, `Wisp Thicket`, etc.). Agent `INT:` / `LORE:` → **white**. Your own descriptive stamps → **orange** (same family as `SEG`). Do **not** recolor your existing markers to red; leave pipeline/FUNI/bookend colors alone.
### Gameplay & exploration
Examples: `Bellhart`, `far fields arena`, `goo beast defeated`, `first sinner fight`.
@@ -93,6 +95,7 @@ Both bounds are deliverable chapter candidates. Do **not** use `gamign` or `env`
- Chapters in `editDesc/*.txt` are **semi-manual** (JSyntax Workflows + cursor edit prompt).
- Agent tagging work targets **Premiere markers**; do not auto-fill `editDesc` with `INT:`, `FUNI`/`funi`, or pipeline stamps.
- Agent adds **red** markers only for its own new deliverable location/activity stamps; set **white** on agent-added `INT:` / `LORE:` only. Your descriptive stamps stay **orange**. Never bulk-recolor the user's markers.
- Transcription aids live in **`editDesc/prtranscript/`** (per year): `*_prtranscript.txt`, `*_visual_tags.txt`, marker JSON snapshots, probe frames (`_gap_probe/`), etc. — not mixed with deliverable chapter `.txt` files.
- `prompts.txt` rules still apply: remove `FUNI`, `INT`, `LORE`, `gamign`, and `env` lines (treat lowercase `funi` the same as `FUNI`); normalize YouTube timestamps.
@@ -103,12 +106,12 @@ Both bounds are deliverable chapter candidates. Do **not** use `gamign` or `env`
| Marker family | Color | `setColorByIndex` |
|---------------|-------|-------------------|
| Start | Green (default) | 0 |
| Deliverable tags (locations, tag in/out, bosses) | Red | 1 |
| Agent-added deliverable tags (locations, tag in/out, bosses) | Red | 1 |
| gamign, env | Purple | 2 |
| SEG | Orange | 3 |
| SEG; your manual descriptive stamps | Orange | 3 |
| BEGIN, END, AFK, UNAFK | Yellow/tan | 4 |
| INT: | White | 5 |
| FUNI, FUNI(INT) | Blue | 6 |
| funi | Aquamarine / turquoise | 7 |
When adding markers via MCP: red = 1, white (`INT:`) = 5. Hard tags share the same yellow/tan as each other, not white.
When adding markers via MCP: **new agent stamps** → red = 1; agent `INT:` / `LORE:` → white = 5. Do not change colors on markers you did not add.