I’ve been asked a few times about starting up Shooting Game Tournament 2008.
Edge and I have discussed it. He has some new responsibilities in real life that he must devote his full time to, and I just moved in with my girl and I initiated my accounting career that I do not intend to fuck up, breaking my free time into unpredictable inconsistent very short periods.
Therefore, both of us regretfully must decline our roles as primary organizers of the annual tournament for 2008.
You, the internet, have 2 choices:
A. Put the tournament on ice for 2008 and revisit the possibility for a 2009 tournament when the time comes.
B. Divide up the tournament tasks to all who are willing and they construct STGT 2008.
Since this is the third year of it, many users who have participated sorta know the drill by now. Edge and I tried to smooth out rules and other details as best we could so the [integrity of tournament] drama could be minimized. What that means to the volunteers who take this task over is to just copy the format we’ve been doing the past 2 years.
The tasks are:
Code: Select all
1. The Registration ThreadThis thread will be the first thing opened to initiate the tournament. It will be opened alongside the Week Themes Selection thread. The volunteer will add players, move players, and construct teams as requested by all players wishing to participate. The registration period should run 3 weeks to a month with a formal deadline to close all player registration known well in advance. We created a player registration form for willing participants to post so sorting the players out will be slightly easier. After the registration thread, it is recommended the volunteer assist or guide the other volunteers in any way possible, especially during questions asked in the scoring week threads.
Requirements: The volunteer should be available to update the team rosters and player requests to post 1 on a daily or near-daily basis for the duration of the registration period. Must work well with others and have the whole “sense of leadership” thing.
---------------------------
Volunteers:
sikraiken
Code: Select all
2. The Week Themes Selection ThreadThis thread will open alongside the Registration Thread. As you know, the STGT is based on 5 playing weeks voting on 5 game choices with all 5 choices revolving around a set theme. During the registration period, this thread will be used for group discussion of what 5 game themes the STGT should have. The volunteer can decide the final 5 choices however he/she wants as long as popular opinion is taken into reasonable account. After that decision is made, a schedule should be made (coordinating with the Registration thread deadline) as to what weeks will feature which game voting theme. Remember every theme week is a 2 week period, the first week is a formal voting period and the second week is spent playing the decided game.
After the registration period ends, the thread will be used for discussion of what games should be picked for upcoming themed weeks, including what games should be eliminated because of known scoring bugs, exploits, infinites, poor emulation, etc. The volunteer will update post 1 with a summary of popular game choices for MAME testing.
Requirements: The volunteer should be available to answer questions and maintain his/her method of assessing week theme choices a few times a week. During each playing week, the volunteer must keep post 1 up to date on summarizing popular game picks and invalid games so the volunteer in charge of game testing will have a good time period to actually test the games so the next voting week can be constructed. Basically, common sense, an understanding of calendars, and observing what people want is required. Must work well with others.
----------------------------
Volunteers:
mikwuyma
Code: Select all
3. The Shortlist GuyRequirements:
The volunteer must:
-Make sure the game works in MAME and any quirks about getting the ROM to run are easily communicatable to 90+ people.
-Figure out a reasonable autofire setting where needed. Too fast can break the game, too slow can make the game not fun if the player can tap the button consistently faster than your setting.
-During EVERY boss or midboss area where the scrolling stops until the enemy(s) is defeated, make sure:
--The player cannot accumulate points DURING that fight
--If the player CAN accumulate points during the fight, the fight must time-out.
--If the player can accumulate points and the fight does not time out, then verify if the fight becomes progressively harder as time passes and DOES NOT LEVEL OFF.
-Check scoring threads, strategy threads, and google for known scoring exploits, easy counter stops, and bugs that will mess up the scoring week.
-Snap and upload screenshots of each game for use by the Voting Week volunteer.
-----------------------------
Volunteers:
Twiddle
Code: Select all
4. The Voting Week ThreadsThe actual STGT is a 10 week period. A voting week, then a playing week, repeated 5 times. This volunteer will construct a voting thread with a known ending deadline based on that week’s gaming theme (the forum Poll function is not required). This will be constructed using the 5 shortlist game picks of the Shortlist Guy, and the banner created by The Banner Art Guy (if available), along with providing a short description of each game. Because we want voting to be limited to all players actually in the tournament, all votes are taken from players posting their choice in the voting thread, in addition to the Private Vote which gives players the option to send their vote to username "STGT" to be counted. Immediately after the voting thread deadline has been reached, the volunteer must announce the thread is closed and be able to tally up the results of all who have voted at that time via the thread and the PM inbox of user "STGT". A [cropped] screenshot should be taken, uploaded, and hotlinked into the post 1 as proof of private votes. Furthermore, the results of the vote would be added to post 1 and the game chosen for that themed week would be formally announced.
Requirements:
To sift through many thread pages and spot the formal vote posted by each player, being aware of users who may illegally edit their vote or other users who will still post votes while not registered for the tournament.
The volunteer should know how to take screenshots and post the pic in a thread.
Most importantly, this volunteer must be able to set this voting deadline between Sunday afternoon and Monday morning and BE THERE when it ends long enough to formally announce the end of the voting period, count the votes, and post the results so the Scoring Week volunteer can begin the next step.
------------------------------------
Volunteers:
sikraiken
Code: Select all
5. The Scoring Weeks ThreadsImmediately after every scoring week, this volunteer will put up a scoring thread in the hi-score subforum. This is run pretty much like any other scoreboard, requiring to post the game defaults, settings, etc., but the frequency of posts will be much higher than most threads, so the volunteer will not only have to keep the thread up to date throughout the week with a neatly formatted table, but he/she may have to answer extra questions that were previously unforeseen until players download the game, such as MAME to console version differences, modes, and other settings. All volunteers who have played the game already should be able to communicate with each other and settle these questions relatively quickly before most players can 1CC or hit their scoring peaks. The scoring thread will have a known and posted deadline by which the volunteer will be able to close the thread and fully update the scoreboard so the Final Results volunteer can take on the next step.
Requirements:
Must be available daily during the scoring weeks to upkeep and maintain the scoring thread. Must be able to research and resolve player questions quickly and politely, even going as far as to teach players how to run the game if necessary. Must be available to formally close each scoring thread at the deadline and update the scoreboard right down to the final post.
--------------------
Volunteers:
mikwuyma
Code: Select all
6. The Final Results ThreadThis volunteer will maintain and post the final results to every scoring week. This requires maintenance of 4 scoreboards:
-Team Rankings
-Breakdown of Each Team’s Top 3
-Single Player Rankings (this game)
-Single Player Rankings
While this is a team-based tournament involving taking the top 3 scores from every team and dividing up ranking points evenly by placement, single player statistics were maintained through a different system of ranking points. These are probably the toughest threads to create unless firestorm(STG)’s ranking application is utilized. Half the nightmare is calculating the points while the other half is formatting all the posted numbers. It is possible to make this a two-person task.
Requirements:
I recommend players who have played in past tournaments volunteer for this since they are familiar with how ranking points are distributed.
The volunteer will have to calculate how the team points and individual points are distributed according to placement in the scoring weeks, add them together accordingly, then append and format each of the 4 scoring tables.
-----------------------
Volunteers:
Davey
Enhasa
(I nominate firestorm(STG) & mikwuyma. Up to them to accept)
Code: Select all
7. The Banner Art GuySee how every voting week thread and main registration & theme thread had a banner made for them. You would be making those. Just PM your delivery to the Vote Thread volunteer so he/she can add that to the thread. This task is optional, but having somebody to do these is nice and makes everything look all “formal” or something…
Requrements:
Having and not sucking at Photoshop,GIMP, etc.
Webspace to upload to and display hotlinked pics.
-------------------
Volunteers:
JoshF
Zebra Airforce
Anybody intending to help with organization can take on multiple roles like Edge and I did. Just don’t stretch yourself too thin. This tourney requires 2 people at least, and even that is pushing it…
(or he can do it himself).
.
