Group Chat
Run scenes with multiple characters, choose who speaks next, and control room dynamics.
Group chat turns Abolitus from a one-on-one roleplay tool into a room-level scene tool.
Instead of one character replying forever, you can manage a shared scene with multiple participants and decide how speaking turns should move.
When to Use Group Chat
Use group chat when:
- You want multi-character banter.
- You want a narrator, guide, or moderator inside the room.
- You want scenes where several characters can react to the same event.
- You want party dynamics instead of one isolated relationship.
Core Controls
Group chat includes several orchestration choices.
Speaker policy
You can choose how the active speaker should be determined.
Available policies include:
- Manual.
- Round robin.
- Random.
- Targeted.
Auto-cycle speaker
Use this if you want the room to advance through speakers more automatically instead of manually nudging every turn.
Observer mode
Use this when you want to watch or direct the scene without participating as a normal speaker.
Auto-turn count
Use this to decide how many automatic turns should be taken in a row before control returns to you.
Practical Speaker Policy Advice
Manual
Best when you want precise scene direction.
Round robin
Best when you want predictable turn flow and equal airtime.
Random
Best when you want spontaneity and looser room energy.
Targeted
Best when replies should focus on a selected character or room target.
Slash Command Support
Group chat works especially well with command-based scene control.
Typical examples include:
- Advancing to the next speaker.
- Targeting the room instead of one character.
- Targeting a specific participant when you want the next response shaped around them.
Cost and Context Reality
Group scenes are powerful, but they are not free in context terms.
Why:
- More participants means more possible state.
- More identity and relationship context may need to stay visible.
- The scene can grow noisy faster than one-on-one chat.
If a room starts feeling unstable, do not immediately blame the model. First check whether the scene has simply become too crowded for the current route and context budget.
Best Practices
Keep each participant distinct
Group chat works best when each participant has a clear voice, motive, or role.
Use targeted turns for important beats
If one reply really needs to come from one character, use targeting rather than hoping the room picks correctly.
Use observer mode for scene management
Observer mode is useful when you want to direct tone and pacing without constantly inserting your own in-scene voice.
Expect heavier prompt pressure than direct chat
If a group room becomes dense, consider a stronger model route, lighter wrappers, or tighter lorebook discipline.