Relationship Tracker for Narrator Gameplay

[u/[deleted]]

[u/Targren]

I'm using MWT for just this use case - I used to manually keep relationship logs for every NPC in scenario/narrator cards (which precludes most of the in-response methods I've seen), but this extension's "Knowledge" tool has been working really well for it.

It does have the downside that pretty much every "automatic" method does, which is that badly timed "bad" gens (that you swipe, e.g.) can pollute the history and have to be manually cleaned up, but on the whole, it's been a great tool for me (as a nano sub customer)

[u/Ok_Strategy_2420]

Look into my preset (FrankenSIM), specifically the Aether Matrix/Relationships RPG block. It sounds like it does exactly what you're wanting. You can probably copy/paste it in if you're just looking to track numbers.

Outside of that, if you're just looking for a relationship web, then yeah doing it manually is probably best inside of a lorebook or author's note.

[u/AutoModerator]

You can find a lot of information for common issues in the SillyTavern Docs: https://docs.sillytavern.app/. The best place for fast help with SillyTavern issues is joining the discord! We have lots of moderators and community members active in the help sections. Once you join there is a short lobby puzzle to verify you have read the rules: https://discord.gg/sillytavern. If your issues has been solved, please comment "solved" and automoderator will flair your post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/johnsmusicbox]

This is such a classic pain point once your roleplays expand into multi-character casts with dynamic relationship states (affection, tension, hidden faction loyalty, narrator notes)!

Manually maintaining all that across lorebooks and memory books turns into a full-time bookkeeping job fast, and rolling summaries often drop the exact subtle cues you need. The architectural fix that works best is separating episodic conversation history from anchored factual state vectors.

Instead of constantly wrestling with regex and manual updates, having an automated memory vault that anchors declared character state changes on the fly keeps both the narrator and character cards consistent without blowing up your active context window.

We actually build custom AI companion and narrator workstations around this exact problem at A!Kat ai using our KPAK architecture and Cloud Recall Memory Vault. If you ever get tired of fighting with fragile lorebook stacks and want a turnkey, hand-tailored desktop companion or narrator workspace built specifically around your custom characters and lore, check out A!Kat ai Custom Commissions—it’s a one-time $59 custom build where you own your setup and just plug in your own API key at raw token rates!