Rounds and key publication
Enter and publish round keys in the Discord operator channel. See Setup to create the channel. Discord buttons use the Japanese labels shown below.
A round is one stage of play. An entry size of one produces one match per round; an entry size of three produces matches 1–3 played simultaneously in every round.
1. Set up round 1
Press 第1試合を設定 (Set up round 1) in the operator channel and complete the form.
| Field | What to enter |
|---|---|
| Custom keys | Keys prepared by the organizers for each match |
| 開催案内 (Announcement) | An editable, multiline template for the start time and participation instructions, at the bottom of the form |
For one match, enter one key for all recipients. For two to four matches, enter each key in its match’s field. For five or more matches, enter one key per line, starting with match 1.
Use a different key for every match. Each key must contain 1–64 characters, with no spaces or backticks.
Checking recipients
Saving round 1 uses the current entries to set the participants and their matches. Check the Register Now entry list before saving.
| If saving fails | What to check |
|---|---|
| No entries | Has registration completed in Register Now? |
| Incorrect participant count | Does every entry contain the configured number of members? |
| Duplicate participants | Is the same person in more than one entry? |
| Team role unavailable | Were any team roles or categories created by Register Now removed or changed? |
The saved settings appear as a preview in the operator channel. Participants cannot see the keys yet.
The operator panel also displays the recipient count. To apply later changes, follow Changing participants. Updating recipients cancels a scheduled publication if the roster changes.
Publication adds a new announcement and key button to the selected channel.
2. Review and publish
Check each match’s key and the announcement. Press 設定内容を編集 (Edit settings) to make corrections.
| Button | Action |
|---|---|
| 公開 (Publish) | Make keys available to participants immediately |
| 公開予約 (Schedule publication) | Publish keys at a specified time |
| 予約変更 (Change schedule) | Change the scheduled publication time |
| 予約取消 (Cancel schedule) | Cancel automatic publication and return to a draft |
Use 5分後に公開, 10分後に公開, or 30分後に公開 to schedule publication 5, 10, or 30 minutes later without typing.
For a specific time, open 公開予約 and enter 21:00 (today), 明日 21:00 (tomorrow), or 10分後 (in 10 minutes). A full date such as 2030-01-01 21:00 is also accepted. All times use Japan time. A time written in the announcement does not schedule publication.
Keys and the announcement remain editable while scheduled. The latest saved settings are published when the scheduled time arrives. If the BOT was offline when publication was due, publication takes place after it restarts.
3. Participants check their keys
Participants press カスタムキーを表示 (Show custom key) in the selected key distribution channel. Their assigned match and custom key appear in a reply visible only to the person who pressed the button.
| Message | What to do |
|---|---|
| 現在公開中のカスタムキーはありません (No published key) | Wait for the organizer to publish the round |
| Router Key参加者として登録されていません (Not registered as a participant) | Ask the organizer whether you are included in the currently published round |
4. Set up the next round
Press 次の試合を設定 (Set up the next round), enter new keys, and review and publish them as for round 1.
While the next round is being prepared, participants can still check the currently published round’s keys. Publishing the next round adds a new announcement. Previous announcements remain, but their buttons no longer provide keys. There is no need to decide the total number of rounds in advance.
Operation logs
The log channel records who configured keys and announcements, published or scheduled rounds, updated participants, changed the distribution channel, and archived a distribution. When a participant receives a key using the button, the log records their name, round number, and match number. Custom key values are never included in logs.
During bursts of activity, several log entries are posted together. Key replies are handled separately, so log messages may arrive a little later.