The information given here is helpful and can be used as a guide or a reminder when conducting any kind of training.
As you have some creative flexibility when hosting, the information below is not technically necessary, but it does act as a checklist for you to go through.
Have your attendees gather in the room where the event is being held after announcing using #event_announcements. You may say hello to them, inform them of your start time, etc. As soon as you get going, introduce yourself and/or your co-host, if they are there, and inform your audience of the following:
[REQUIRED] The "Permission to speak?" or "PTS?" command is in effect (spelling out the whole phrase is recommended to encourage discipline in attendants).
[RECOMMENDED] Recognize the agenda. Tell attendees what you'll be speaking about, including relevant subjects for the event and more. You should then start your event from there.
If there are Temple Guards online, it is highly recommended that you ask them to guard your training. Only do this if the temple is not being overrun by raiders and there are sufficient guards to protect both the temple and the training. At least 2-4 guards are enough for guarding trainings.
If the temple is being overrun by raiders or if there are no guards online then use the barrier commands to close your training (:spawn/:mats/:library).
Everyone taking part in your event must be aware of the time they can depart (be dismissed) and whether your event has ended or not.
If any of the remaining participants have any questions on an issue, you should ask them about it. You can set them (the questions) aside for just after the event, or during.
When logging, be sure to:
Take a screenshot of the attendees who left your event (as you will use that to provide proof of your event). If you ran the event on a private server, be sure to take a screenshot of any admin commands you used during the event.
[HIGHLY RECOMMENDED] Include the date of the event.
Be sure to verify whether any attendants have complied with any requirements (specifically FS to Initiate). Make sure to log them in under #promotions if they have (follow the format for the channel as usual).
Have a logging message and event announcement message prepared. The amount of typing might sometimes make hosting difficult. The best way to fix this is to have messages that are already formatted to your preferences so that the next time you announce an event, all you have to do is press CTRL + C and then CTRL + V into #event_announcements.
If you notice a member of the staff team hosting improperly, using suspicious admin commands during the training or teaching the wrong content. You are to report to a Jedi Master+ immediately, only Jedi Master+ are allowed to intervene in trainings to assist the host. You are not to intervene in the training yourself unless you are a Master+ in the main group.
Usually the job of the Master would be to make minor corrections to help the host out in the event. If the host for example explains AC wrong, it’s not the Master’s job to shame them in public but rather help the host so that the attendees don’t get robbed of their education and the host can continue the event smoothly.
In very rare cases a host is conducting suspicious activity like admin abuse or you encounter a scenario which a regular Master cannot handle, report to a member of the Jedi Council with evidence.