Change Teams & Death Management Commands Documentation

Overview

These two moderator commands manage the live state of players during a game:

• /changeteams - Move a player from one team to another
• /deathmanagement - Mark a player as dead or resurrect them

Both commands require the server's configured moderator role and must be run in the role server.

/changeteams Command

Move a player to a different team. Updates channel permissions and records the change in the game log.

Moderator only: This command requires the server's configured moderator role.

Required Arguments

┌────────────┬────────┬────────────────────────────────────────────────────────┐
│ Argument   │ Type   │ Description                                            │
├────────────┼────────┼────────────────────────────────────────────────────────┤
│ player     │ User   │ The player to move to a new team                       │
│ teamname   │ String │ The exact name of the team to move the player to       │
└────────────┴────────┴────────────────────────────────────────────────────────┘

Optional Arguments

┌───────────────────────┬────────┬────────────────────────────────────────────────┬─────────┐
│ Argument              │ Type   │ Description                                    │ Default │
├───────────────────────┼────────┼────────────────────────────────────────────────┼─────────┤
│ removefrompreviousteam│ Boolean│ Remove player from their previous team channels│ True    │
│ comment               │ String │ Optional note to add context to the change     │ None    │
└───────────────────────┴────────┴────────────────────────────────────────────────┴─────────┘

Prerequisites

• Active game: A game must be configured with team channels set up.
• Valid team name: The teamname argument must exactly match one of the team names configured in the game's teamChannelsList.
• Player in game: The target player must be registered in the current game.
• Bot permissions: The bot needs ManageChannels and ViewChannel permissions in the role server.

Restrictions

• Can only be run in the role server (not the chat server)
• teamname is case-sensitive and must exactly match an existing team name
• If no teams are configured in the game, the command will fail

Examples

Move a player to a new team:

/changeteams player:@Alice teamname:Werewolves

Move a player without removing old team access:

/changeteams player:@Alice teamname:Werewolves removefrompreviousteam:False

Move a player with a reason:

/changeteams player:@Alice teamname:Clowns comment:Converted by Mystic Honk ability

What Happens When You Run /changeteams

1. Player and team are validated — the bot checks that the player is in the game and that the specified team name exists.
2. Old team channel permissions are removed (if removefrompreviousteam is true) — the player's permission overrides are deleted from each of their current team's channels.
3. New team channel permissions are granted — the player is given ViewChannel, SendMessages, ReadMessageHistory, and PinMessages in each of the new team's channels.
4. Private channel is moved to the new team category (if teamCategoriesList is configured) — the player's personal channel is re-parented into the new team's category without locking inherited permissions.
5. Game info is updated — the player's teamChannels and teamName are saved to the game-info sub-config.
6. A log entry is posted — an embed is posted to the game log channel summarising what changed, who made the change, and any optional comment. The comment is only visible by moderators.
7. A confirmation is returned — the command responds with a private summary of all permission changes and any warnings.

Note: The response is only visible to the moderator who ran the command (ephemeral).

/deathmanagement Command

Mark a player as dead or resurrect them. Adjusts channel permissions, Discord roles, and game action tracking to reflect their new status.

Moderator only: This command requires the server's configured moderator role.

Required Arguments

┌──────────┬─────────┬────────────────────────────────────────────────────────┐
│ Argument │ Type    │ Description                                            │
├──────────┼─────────┼────────────────────────────────────────────────────────┤
│ player   │ User    │ The player whose alive/dead status is being changed    │
│ isalive  │ Boolean │ True to mark alive (resurrect); False to mark as dead  │
└──────────┴─────────┴────────────────────────────────────────────────────────┘

Optional Arguments

┌──────────┬────────┬────────────────────────────────────────────┬─────────┐
│ Argument │ Type   │ Description                                │ Default │
├──────────┼────────┼────────────────────────────────────────────┼─────────┤
│ comment  │ String │ Optional note to add context to this change│ None    │
└──────────┴────────┴────────────────────────────────────────────┴─────────┘

Prerequisites

• Active game: A game must be configured with player info.
• Player in game: The target player must be registered in the current game.
• Bot permissions: The bot needs ManageRoles and ViewChannel permissions.
• Role hierarchy: For role changes to succeed, the bot's highest role must be positioned above the active and dead player roles in the server settings.

Restrictions

• Can only be run in the role server (not the chat server)
• If the player is already in the requested state (e.g., already dead), the command does nothing and reports the current status
• Role changes on the chat server will silently skip if the player is not a member of the chat server

Examples

Mark a player as dead:

/deathmanagement player:@Alice isalive:False

Resurrect a player:

/deathmanagement player:@Alice isalive:True

Mark a player dead with a reason:

/deathmanagement player:@Alice isalive:False comment:Eliminated by wolf attack Night 2

What Happens When You Mark a Player Dead (isalive:False)

1. Channel is renamed — 💀- is prepended to the player's private channel name (e.g., alice becomes 💀-alice).
2. Role server roles are updated — the active player role (from game-info) is removed; the dead player role is assigned.
3. Chat server roles are updated — the active player role is removed; the dead player role is assigned.
4. Team channel access is removed — the player's permission overrides are deleted from all of their current team's channels.
5. Ghost channel access is granted (if configured) — the player receives ViewChannel, SendMessages, ReadMessageHistory, and PinMessages in the ghost channel.
6. Game action embeds are removed (if game actions are enabled) — the player's embed is deleted from each configured category thread, the category count message is updated, and all pending or confirmed action data is cleared.
7. Game info is updated — the player's alive status is saved to the game-info sub-config.
8. A log entry is posted — an embed is posted to the game log channel with the status change, who made it, and any optional comment. The comment is only visible by moderators.
9. A confirmation is returned — the command responds with a private summary of all changes and any warnings.

What Happens When You Resurrect a Player (isalive:True)

1. Channel is renamed — the 💀- prefix is removed from the player's private channel name.
2. Role server roles are updated — the active player role (from game-info) is re-assigned; the dead player role is removed.
3. Chat server roles are updated — the active player role is re-assigned; the dead player role is removed.
4. Team channel access is restored — the player regains ViewChannel, SendMessages, ReadMessageHistory, and PinMessages in all of their current team's channels.
5. Ghost channel access is removed (if configured) — the player's permission override in the ghost channel is deleted.
6. Game action embeds are created (if game actions are enabled) — a "No Action" embed is posted to each configured category thread, the category count message is updated, and the new message IDs are recorded.
7. Game info is updated — the player's alive status is saved to the game-info sub-config.
8. A log entry is posted — an embed is posted to the game log channel with the status change, who made it, and any optional comment. The comment is only visible by moderators.
9. A confirmation is returned — the command responds with a private summary of all changes and any warnings.

Note: The response is only visible to the moderator who ran the command (ephemeral).

Role Configuration

Both commands interact with player roles configured across two servers (if configured): the role server (where the game channels live) and the chat server (where players chat during the game).

Role Server Roles (from game-info)

These are configured when setting up the game and are stored in the game-info sub-config:

• Active players role (activePlayersRoleId) — assigned to all living players
• Dead players role (deadPlayersRoleId) — assigned to eliminated players

Chat Server Roles (from server config)

These are configured in the server settings (for games which use a separate chat server):

• Active player role (chatServerActivePlayerRole) — the chat server counterpart to the role server active role
• Dead player role (chatServerDeadPlayerRole) — the chat server counterpart to the role server dead role

Note: If either role in a pair is not configured, role changes for that pair are skipped. The command still proceeds with channel permission changes.

Game Log

Both commands post an embed to the game log channel when they succeed. The embed includes:

• The player affected and their new status or team
• The moderator who ran the command
• A summary of all permission changes made
• Any optional comment provided

If the game log channel does not yet exist, the bot will create it automatically. If it cannot be created or written to, the command still completes — the log failure does not block the status change.

Tips and Best Practices

Team Names

• Team names in /changeteams are case-sensitive and must match exactly what was configured when the game was set up
• If the command fails with "Team not found", the response includes a list of all valid team names

Removing from Previous Team

• By default (removefrompreviousteam:True), the player loses access to their old team channels when moving teams
• Set removefrompreviousteam:False if you need a player to temporarily observe both teams (e.g., during a mid-game setup phase) before fully cutting over

Ghost Channel

• The ghost channel is optional but strongly recommended — without it, dead players have no shared space
• If no ghost channel is configured, /deathmanagement still runs but will warn you that no ghost channel was found

Role Hierarchy

• If the bot's role is not positioned above the active/dead player roles in the server settings, role assignment will fail silently with a warning
• Check the warnings section of the command response and adjust role order in Server Settings → Roles if needed

Game Actions

• Action embed management during death and resurrection only applies if the Player Action System was enabled when the game was set up (via /assignroles → Game Setup page)
• When a player dies, their action embed is permanently deleted and all pending or confirmed actions are cleared
• When a player is resurrected, a fresh "No Action" embed is created for each configured category

Using Comments

• Use the comment argument to leave an in-Discord record of why a change was made
• Comments appear in the game log embed and are visible to any moderator who can see the log channel
• Examples: Night 2 wolf kill, Turned by alpha, Moderator error - reverted