Character cards, personas and desktop pets compared

Roleplay plugins split into three kinds: character cards, persona companions and status pets. All sound like "chat companions," but they solve different problems; the wrong pick produces "why does it not remember me" or "why does nothing show up."

Three forms

Start with the object and how it persists.

Cards are about content, companions about relationship, pets about visualization. Cards solve "how do I bring my setting in," suiting people with existing cards and worlds (source). Companions solve "how does it remember and speak first," suiting long-term use (source). Pets turn agent state into an image, suiting progress and mood feedback (source).

dsh-tavern: SillyTavern compatible

Its value is reusing existing roleplay assets.

1. Import a character card and enter RP mode.
2. Import world books and presets to keep the narrative consistent.
3. Reply in character instead of as an assistant.
4. Manage sessions and switch characters.
5. Keep a safety boundary, so out-of-scope content may be refused.

Importing beats writing by hand, and the world book decides consistency. People with cards can use them immediately; without one, a short setting still runs. Without background, a character drifts; a lorebook reduces that drift.

dsh-assist: persona and memory

It turns a character into a package you can keep.

1. Portable character packs with version numbers.
2. Long-term notes shared per character.
3. Short-term checkpoints isolated per session.
4. Proactive chat limited by cooldown, quiet hours and unanswered caps.
5. Persona, memory and switches restored after a restart.

Memory is the real difference, and proactive chat needs boundaries. The setting can be lost; the memory is not, which separates it from a card. Cooldowns and quiet hours exist to prevent interruption; misconfigured, they become noise.

dsh-dafeiyu: status pet

It makes agent state visible.

1. A separate window shows current state.
2. It handles priority when several sessions run.
3. Display and platform settings are configurable.
4. It carries no persona or memory.
5. It can pair with a persona plugin but serves a different role.

It is a display, not a brain, and multi-session priority needs a rule. Use it to watch state; use a persona plugin to be remembered. With several tasks at once, the pet needs a rule for which one to show, or it jumps around.

Choosing

Decide by existing assets, memory needs and whether you want an image.

Combine without duplicating, and get one working first. Two plugins that both manage memory interfere; choose one primary memory and let the rest display. Get cards importing and chatting before adding memory and visuals.

Memory and retention

The roleplay experience depends heavily on memory.

1. Confirm where memory lives: local files, a database, or the plugin directory.
2. Confirm what is stored: settings, preferences, dialogue summaries.
3. Confirm retention: whether it decays and whether it can be cleared.
4. Export regularly: back up important personas and settings separately.
5. Confirm before cleaning: deleting memory can give a character amnesia.

Stronger memory raises privacy risk, and migration needs the whole pack. Long-term companionship stores a lot of dialogue, so periodic export and cleanup matter. When pack, memory and configuration live apart, migration misses pieces; export the full pack as documented.

Risk boundaries

Three risk classes apply to roleplay plugins.

1. Content: a persona can steer toward unsuitable material; plugins set boundaries but do not catch everything.
2. Retention: long-term memory stores sensitive dialogue, which needs a cleanup policy.
3. Dependency: cards and world books come from third parties and may contain injected instructions; read before importing.

Review third-party cards and write boundaries into configuration. A card is essentially a prompt and may include out-of-scope instructions; read it fully rather than trusting it. Set quiet hours, content limits and retention together, which beats fixing problems afterward.

Troubleshooting

Four failure classes cover most roleplay issues.

1. Out of character: the setting is thin, the lorebook is missing, or the prompt was compacted.
2. No memory: memory is off, the namespace is wrong, or the write failed.
3. Too much proactive chat: cooldown and quiet hours are unset; tune frequency and silent periods.
4. Pet invisible: switch off, off-screen position, or an unsupported platform; check config and logs.

The order is setting, memory, frequency, display, and short sessions prove it fastest. Confirm the setting first, then memory and frequency. Long sessions introduce compaction and memory interference; a short one shows quickly whether the persona works.

Next steps

Pick the form, configure memory, then set boundaries. For SillyTavern compatibility, read What dsh-tavern is. For pet forms, read How to set up a DeepSeek desktop pet. For memory plugins, read Memory plugins round two.

Sources: dsh-tavern plugin page, dsh-assist plugin page, dsh-dafeiyu plugin page