More actions
Esca Sinak (talk | contribs) No edit summary |
Salartarium (talk | contribs) m Replaced a page with a filled out template |
||
| Line 1: | Line 1: | ||
Trivia events can be run alongside lesser attention-demanding events like mining shared cans | {{EVEUniEvent | ||
| name = Trivia events | |||
| description = Trivia events can be run alongside lesser attention-demanding events like mining shared cans or as standalone events. | |||
=== Before the event === | === Before the event === | ||
* Collect a list of | * Collect a list of EVE-related trivia. You can follow a theme if you want: lore-related, faction-related, ships-related, etc. | ||
* Decide on a point system if you're planning on awarding prizes. | * Decide on a point system if you're planning on awarding prizes. | ||
* If there are enough participants, you can split them into teams. Set things up for a team event beforehand (Mumble comms, a different point system, prizes). | * If there are enough participants, you can split them into teams. Set things up for a team event beforehand (Mumble comms, a different point system, prizes). | ||
| Line 8: | Line 10: | ||
=== Communications === | === Communications === | ||
* For Mumble: if there are teams, it's a good idea to use one of the fleets channels so that each team can use the subchannels for private comms. If not, make an on-demand Mumble channel that you can customise. | * For Mumble: if there are teams, it's a good idea to use one of the fleets channels so that each team can use the subchannels for private comms. If not, make an on-demand Mumble channel that you can customise. | ||
* For chat: the Events (EVE Uni) is open to use for events like this. Teams can also use group chats to talk | * For chat: the Events (EVE Uni) is open to use for events like this. Teams can also use group chats to talk among team members. | ||
=== During the event === | === During the event === | ||
* Set up teams if you're planning on organising the event that way. Ensure that each team has | * Set up teams if you're planning on organising the event that way. Ensure that each team has its communications set up. | ||
* Teams should also decide on an order in which to take questions: | * Teams should also decide on an order in which to take questions: Pilot A goes first, Pilot B goes second, and so on. | ||
* Before you ask each question, ensure that the player is not AFK and can respond. You can do this by asking them to verbally confirm their presence on Mumble, or x-up in chat. | * Before you ask each question, ensure that the player is not AFK and can respond. You can do this by asking them to verbally confirm their presence on Mumble, or x-up in chat. | ||
* You can use a buzzer system if there are teams: the first player to x-up in fleet chat after a question has been asked gets to answer it. | * You can use a buzzer system if there are teams: the first player to x-up in fleet chat after a question has been asked gets to answer it. | ||
[[ | | scheduling = | ||
*(Day, Date, Month) | |||
*(Time, Plus Event Duration Estimate) | |||
*(Form up Location) | |||
| requirements = | |||
*[[Mumble]] | |||
*Be in (Form Up Location) at the start of the operation. | |||
| recommendations = | |||
| fitting = | |||
| warnings = | |||
| additional information = | |||
PLEASE POST IF YOU WISH TO ATTEND, SO WE KNOW WHAT NUMBERS TO EXPECT. | |||
}} | |||