Q&A

• Normal Recruitment: 1-99 members (up to 100 including the host). Leave the number of members field empty for unlimited
• Custom Match: Up to 9 players (10 total including the host)

The host can open Recruitment Settings from the gear icon button on the recruitment message and change the following:

• Title and description
• Adding or kicking participants
• Adding roles and groups

Number of members, scheduled start time, and mention targets cannot be changed after creation, and roles or groups you have already added cannot be removed. To change those, cancel the recruitment and create a new one. Note that for custom matches the gear icon disappears once the recruitment is full, so it cannot be edited after teams are formed.

• Full Join: Counts towards the number of members. The recruitment completes when full.
• Maybe: Does not count towards the number of members. You may receive a DM when the group is nearly full. Maybe does not reserve a spot.

Manual deletion is possible, but dedicated VCs are automatically deleted when all members leave.

Ratings are updated when match results are reported, considering the relative rating difference between opponents. Winning against stronger opponents yields more rating points.

By default, JST (Japan Standard Time) is used for Japanese clients, and UTC for others. A member with the Administrator permission can run /config, choose Timezone, and enter a UTC offset (+9 for Japan) to change the server-wide timezone.

Yes. Autorooms are created in the same category as the trigger channel. You can configure multiple trigger channels (Free plan: 1 / Plus plan: up to 20), each in different categories.

A member with the Administrator permission can run /config and choose Rating Type to add one from the modal.

When the Bot is kicked/banned from a server, all Bot-side data for that server (recruitments, ratings, settings, etc.) is automatically deleted. However, Monvoke website server registration and Plus subscription data are retained, so web settings carry over when re-invited.

This message comes from Discord, not Monvoke. Your Discord account requires verification (email or phone verification). Complete the verification on the Discord website or app, then try logging into Monvoke again.

Members with the Administrator permission on the server. They can run /config to change server-wide settings.

Cause: The role is set to not mentionable (the Bot only shows mentionable roles as suggestions)

Solution:

1. Go to Server Settings → Roles
2. Select the relevant role
3. Enable "Allow anyone to @mention this role"

Cause 1: Insufficient Bot permissions

Solution: Grant the Bot "Manage Channels" permission

Cause 2: Want to specify the VC creation category

Solution: Run /config, choose Category for creating dedicated VCs, and enter the category ID

* If not set, VCs are created in the recruitment channel's category.

Cause: The number of members hasn't reached the actual limit

Explanation: Scheduled recruitments complete when the start time has passed AND the member count reaches the maximum.

Cause 1: Invalid URL format

Solution:

• Ensure the URL starts with https://
• File extension must be one of: .jpg, .jpeg, .png, .gif, .webp

Cause 2: Image access permissions

Solution: Use images uploaded to Discord CDN

Cause 1: Trigger channel is not configured

Solution: Run /config, choose Add Autoroom, and register the voice channel to use as the trigger

Cause 2: Insufficient Bot permissions

Solution: Grant the Bot "Manage Channels" and "Move Members" permissions

Cause: The viewer's Discord client hasn't fetched the target user's information yet

Explanation: In recruitment messages or leaderboard displays, usernames may appear as <@123456789> ID format. This is not a Bot issue but rather the viewing user's Discord client not yet fetching the target user's data.

Solutions:

1. Reload the page: Refresh the browser page (F5)
2. Restart the app: Restart the desktop/mobile Discord app
3. Add as friend: Adding the user as a friend makes their info easier to fetch
4. Wait: The issue often resolves itself over time