Q&A

Up to 50 people (including the organizer). The recruitment capacity input is 1-50, and the actual limit is "input value + organizer" (capped at 50).

Currently, editing recruitment details after creation is not supported. If changes are needed, cancel the recruitment and create a new one.

• Full Join: Counts towards the recruitment capacity. The recruitment completes when full.
• Tentative Join: Does not count towards capacity. It's a "maybe" status (you may receive a DM when the group is nearly full). Tentative join does not reserve a spot.

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

A Plus plan subscription ($5/month) is required. After subscribing, you can create custom matches using the /custom command.

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. Server admins can change the server-wide timezone with /config setting:timezone value:+9 (UTC offset).

Yes. Auto Rooms are created in the same category as the trigger channel.

Server admins can add game types with /config setting:add_game_type value:<game_name>.

Each recruitment is assigned a random 12-character ID used for identification.

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.

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: Category is not configured

Solution:

/config setting:vc_category_id value:<category_id>

Cause 2: Insufficient Bot permissions

Solution: Grant the Bot "Manage Channels" permission

Cause: Not subscribed to the Plus plan

Solution: Subscribe to the Plus plan from the Monvoke Web Dashboard

Cause: Participant count hasn't reached the maximum

Explanation: Scheduled recruitments complete when the start time has passed AND the participant 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:

/config setting:autoroom_trigger_channel_id value:<channel_id>

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