Messages to teams: codes, announcements, restarts and warnings
During the evening the bot talks to the teams for you: the code of every game, a break notice, a lobby to redo, a warning. Everything starts from a single dashboard page, **Messages**, and for every send you see how many teams actually received it.
From the dashboard
Open the dashboard, pick the tournament in the selector at the top and go to Messages: on a phone it is in the bottom bar. The page has five tabs: Lobby code, Announcements, Lobby restart, Warnings and History. In wager tournaments there are only Announcements, Warnings and History, because there are no lobby codes there.
1. Sending the lobby code
Every game needs the private match code. Instead of pasting it into every ticket by hand, you type it once and the bot takes it to the ticket of every team in the lobby.
- 1In the Lobby code tab pick the Lobby, or All lobbies.
- 2Leave Game on Auto (next game): the bot already knows which one is next.
- 3Type the Code (letters turn to capitals on their own).
- 4Press Send code. After sending, the game menu goes back to Auto, ready for the next one.
Heads up
Pick a game number only to fix a wrong code. If that game was already sent, the dashboard asks you first (Game N already sent): with Yes, correct it the bot and the players treat it as the same game with a new code, not a new game. If you wanted the next game instead, cancel and leave Auto.
Sent codes: who received it
Next to the form, Sent codes lists every game with the time and how many teams received the code (for example 14/15). If someone is missing, the team name and the reason are shown underneath, and the Resend button sends the saved code only to whoever did not receive it, without changing the game count.
- The team ticket is gone: recreate it from the Teams page, then resend the code.
- Discord did not accept the message: give the NEMIX role the Send Messages permission in the team ticket, then resend the code.
- The next game has already started: the team is already playing the next one, no need to resend it.
Note
The same send is also in the Control room, in the Lobby code box, so you do not have to switch pages during the evening. If the connection drops right while you send a code, the dashboard does not resend it on its own: it checks for a few seconds whether it went out and tells you what it finds.
!codicelobby<lobby> <codice> [partita]StaffThe same send from Discord: sends the match code to every team in a lobby.
Aliases: !lobbycode
2. Announcements
A break, a time change, a reminder about the rules: in the Announcements tab pick To, write the Message and press Send announcement. The bot sends it as a tournament message, and shortly after the dashboard tells you how many teams received it.
| To | Where it lands |
|---|---|
| All teams | In the ticket of every registered team (in wagers also in the tickets of running matches) |
| Captains only | In a private message to each captain |
| Lobby N | In the tickets of the teams in that lobby (not in wagers) |
Note
The announcement goes out without a confirmation window, like the code: read it again before pressing. The lobbies in the list are the real ones of the tournament.
!annuncio<lobby> <messaggio>StaffFrom Discord: sends a free-form message to every team in a lobby.
Aliases: !announce
3. Restarting a lobby
When a match has to be replayed (a crash, a code that ended up in the wrong hands) the captains have to know straight away, before joining. In the Lobby restart tab pick the Lobby to restart and press Request the restart: after you confirm, every captain in the lobby gets a highlighted private message telling them not to join and to wait for the new code.
- The captain confirms with the â Visto button: the confirmation lands in the tournament commands channel, with how long they took to answer.
- The dashboard tells you how many captains out of how many received the message.
- Then you send the new code from the Lobby code tab, picking that game number: for the bot it is a correction of the same game.
4. Warnings
A warning is an official notice to a team, with the reason written by you. In the Warnings tab pick the Team, the Player involved if needed, write the Reason (what happened, which rule was broken, what the consequences are) and press Send the warning.
- After you confirm, the warning reaches the captain in private and the team ticket, and it stays on record.
- Here too the captain has the â Visto button, and the confirmation lands in the tournament commands channel.
- If it reaches neither the private messages nor the ticket, the dashboard tells you: the warning shows as not delivered.
Note
The list holds every team in the tournament, withdrawn ones included. A warning does not take points away: for a bonus or a penalty there is Matches â Bonus / penalty.
5. The history
The History tab collects everything sent in the tournament, even after you closed the page: codes (and resent codes) with how many teams received them, announcements with the recipients, restarts with the captains reached, warnings delivered or not, and the result reminders sent from the Control room. Every entry shows day and time.
Note
The history keeps who received what and when, not the text of the messages: that stays on Discord, in the tickets and private messages.
Frequently asked questions
Do I have to pick the game number myself?
No. With Auto the bot sends the code of the next game. The number is only for fixing a code already sent, and in that case the dashboard asks you to confirm.
A team says it did not get the code: what do I do?
Check Sent codes: if the team is missing, the reason is there along with the Resend button, which sends the code only to whoever did not get it. If it shows as delivered, it is in the team ticket.
Can I send an announcement to captains only?
Yes: under To pick Captains only, and the message reaches each of them in private.
Do messages work after the tournament is over?
Yes, the page stays available: for example for an announcement about the prize-giving. The only thing that disappears is the Resend button for codes.