EventShell:More Rice than Anneka
Synopsis
More Rice than Anneka leads teams around the Jade Archipelago on a specifically-designed treasure hunt for prizes!
Full Description
More details on the rules can be found at this website. Essentially, teams were to be led around a select few islands, visiting shops and solving problems via the use of cryptic questions. They had to team up with a partner, go to Ajax's Estate for registration, and go out and return within 90 minutes, sending an email with answers to questions. Questions were mostly observation-based, and required a little thinking! Bonus 'stunts' such as buying bandanas or bring something else back in time were also included.
Materials
- Event host with infinite patience and omnipotence
- Crew
- House
- A set of questions which are thoroughly checked.
- 'Sniper' [optional stunt]
- 'Lost pirate' [optional stunt]
Prize Precedents
- Two golden tickets for the winners
- Two grey/grey (silver) ribbons for the runners-up
- Two tan/tan (bronze) ribbons for third place
- Two more golden tickets for a random team out of those that completed at least 3 of the 5 stunts.
Strong Points
- A very challenging, cerebral event.
- Encompasses general knowledge, trivia, common sense, clever thinking and that against-the-clock pressure right up until the last minute.
Sadly, that's where the pluses end.
Weak Points
- An organisational nightmare:
- Jobbing 100 people into a crew is fairly difficult. Organising them into pairs, making them form teams, getting them to register ONCE ONCE ONCE!, getting them to stay patient and not confuse the ones using macs to open an Excel spreadsheet is stepping into the Herculean realms. Timing was also hard to keep too; the event started late
- The damned questions:
- It is impossible to predict what people will answer; some of the more crazy things they say might even be correct! Either thoroughly research this beforehand (NOT recommended) or research on-the-fly to make sure that questions devised are correct.
- For example, there is more than one Shakespearian quote involving a skull, both from the play Hamlet:
- Alas poor Yorrick, I knew him well,
- To be or not to be; that is the question
- For example, there is more than one Shakespearian quote involving a skull, both from the play Hamlet:
- The questions must be dry-ran before-hand AND on the day to try and catch out as many errors as possible.
- It is impossible to predict what people will answer; some of the more crazy things they say might even be correct! Either thoroughly research this beforehand (NOT recommended) or research on-the-fly to make sure that questions devised are correct.
- Logistics
- My run involved getting bid tickets at the end and answering an observation question at the end. Already exhausted, I had to log back on twice to answer them. I ended up cancelling the bid ticket one because it just wasn't fair to not let people who I willingly allowed to log off take part. As it happened, that team would not have won, but still, imperfection is bad.
- Contestants
- Be ready for your contestants to challenge every word. Stick to your guns!
Links to Precedents
Status
Nobooty is not willing to run this event again without severe reconstruction. He would be willing to assist in and/or partipate in other versions of such an event.
If you are thinking of running this event, and are a perfectionist - don't, just don't. If you can deal with it being a subjective and imperfect event, go ahead.
| Event comments
| |
| Bootlicker on the Cobalt Ocean says: | |
| I thought the event was a lot of fun, despite the difficulties at the start and end. Running any event that doesn't rely heavily on in-game mechanics is away a challenge. The best advice I have for making an event like this run more smoothly is to get more help. This means more people to help with registration and score checking. For example, checking all the bonuses was too much work for a single person, but having a group of helpers, each responsible for checking one particular bonus, would have made things better. More help also means using various tools (wiki, webpages, forums) to automate some of the process, leaving less work for the event organizers. For example, require people to register on the website or wiki, and only job the teams who have registered properly. Web-based submission of answers, instead of e-mail, might also speed things along. | 
|
| Shell comments give everyone a chance to give critique on this event. If you would like to add your own, see the usage notes at Template:Shellcomment | |
