Chaos's Winter Carnival
2023 Winter Tournament
Rules & Guidance
Welcome to the 2023 Winter Tournament, Chaos's Winter Carnival. Previously called the Spring Tournament, our newly rechristened Winter event is our big tournament for the year, pitting players in 1v1 matches to determine this year's FFR server champion. The event this year will be a three-week series of pod matches followed by a traditional bracket, all so players can take their shot at being the top of the heap.
About the Tournament
This year's Winter Tournament will follow a two-part structure. The first part will be pods, with six players assigned to a pod. Players in those pods will then play their matches, get their win/loss score and then, from there, seed into brackets. Brackets will then follow play out in a single-elimination, best-of-three (Bo3) format, except for the championships which will be best-of-five (Bo5).
Note that the flags this year will evolve, from pods through the lower and upper halves of brackets, getting progressively more difficult as the tournament goes on.
All races will be conducted on the Winter Tournament 2023 leaderboard on Racetime.gg. Players will need to have a Racetime account, as well as a Twitch stream to broadcast to, if they wish to participate in the tournament.
Important Dates:
Tournament Structure:
Pods
The first phase of the tournament will be pods. Please note there will be no qualifiers leading into pods, nor is there a leaderboard we'll be seeding from. Thus, all pods, from the very first “seed” into the pods to the very last, will be random. On the weekend before we start the tournament team will air a reveal stream, and part of that stream will be seeding all the players, one at a time, into the pods via the magic of a spinning wheel. Come one, come all, and spin that wheel for a chance at victory in the Carnival!
Pods will be comprised of six players in a (not at all) patented “Clown Car” format. Each player in the pod will play three matches against a specific selection of other players. How this works is:
Because everyone is seeded in randomly the “player positions” are meaningless in the context of this seeding and does not imply anyone is actually a higher or lower “seed” until after pods have been played. The clown car format also helps to add further randomness to the seeding this potentially mitigating a “death pod” that is comprised only of good players. You might have three or four “good players” in your pod but there's no guarantee that, based on your position, you'll actually race them. It's all up to the luck of the draw!
Please note that we have a scoring sheet that clearly shows who you'll have to race so you don't need to memorize any of this. Reference the sheet, once everyone is seeded, and you'll be able to see your matches, your win/loss record, and your current pods score.
Once you have your assigned pods you will have three weeks to get all your pod matches done, but you can do them any time during that period as is convenient. We do ask, however, that players avoid scheduling matches on days that already have a lot of matches scheduled. Anything you can do to ease scheduling and make games easier to staff is appreciated. Also note that not all pod matches will be staffed and broadcast. We'll try to get as many streamed as we can, but with limited tournament and broadcast staff available, some matches simply won't be on stream especially on busier days.
Once everyone has played through their assigned pods matches, their pods score will be tabulated and players will be organized into official seeds. Position in the seeding will be determined from their pods score, their race time differential average (with a cap of +/- 20 minutes per race), and then, if all else fails and there still exist ties, a further spin of the wheel to break ties.
Play-in Races
In the likely event that there isn't an even number of players to seed from pods into brackets (say a bracket of 16 and only 15 players make the cut-off naturally), final chance play-in races will be held. One race will be for all 1-2 racers. A second, “Last Chance Qualifier” race will be for all 1-2s (who don't make it into brackets from the previous play-in) and 0-3s. The exact number of players seeded in from each of the race will be determined once we know the number of 3-0s and 2-1s seeded into brackets.
Brackets
With everyone scored and seeded, play will then progress to brackets. Depending on the number of players, brackets may be anywhere from 24 players or more (we have brackets setup to handle 24, 32, 48, and 64 player variations, depending on players). We will seed at least half of all players from pods out into brackets, with the cut-off based on pods score (if there are more 3-0s and 2-1s than we have slots in, say, a 24-player bracket then a 32-player bracket will be used, and so on). Size of the brackets will be announced during the pod seeding reveal stream, once total number of players for the tournament is known.
At this point, then, bracket play begins. Brackets will be single elimination, with all matches being best-of-three (Bo3), except for finals, which will be best-of-five (Bo5). Each round of the brackets will have one week to play out, although once players know who their opponent is in the next leg of the bracket they can schedule their matches as soon as they are ready. Again, we do ask that players avoid scheduling matches on already busy scheduling days to ease the burden on our schedule and broadcasting staff. And, especially during the early legs of the brackets, we cannot guarantee that all races will be restreamed. We will try to broadcast all game 2s (and game 3s, as needed), but game 1s in the early legs are likely to be played without broadcast to easy the burden on restreaming needs.
Note that the flags during brackets will evolve, with the lower bracket (round of 8 and larger) using one version of the flags while Semi-Finals and Finals will use the final iteration.
In the Event of Ties
While unlikely, ties are possible. In the Final Fantasy Randomizer community, a race will be retimed if both players finish within three (3) seconds or less of each other. If this occurs, a tournament staffer will retime the race off the Twitch streams from both players. If the final time is within 1 second between the players, the race will be considered a tie. If this occurs during Pods that race will need to be re-run. If it occurs during brackets, another race will be added to the Bo3 (or Bo5) series. Ties do not count to the final score for a player and are considered a “voided” race (even if they are cool to see).
The Flags
The flagset this year will evolve. Players will see a standard flagset that will remain consistent except for one specific change: the requierd orbs will change from 2 Orbs Any to 3 Orbs Any, and then 3 Orbs Specific as the tournament progresses.
Important things to note for all players:
Drafting and Other Allowances:
Although the party selection is set by the seed, players are allowed to agree to a specific party, as they like, before the seed is rolled. This can be any combination of characters and nones, or even just random four forced (4orced). Party changes (forcing) must be done before the seed is rolled and must be agreed to by both players.
Players may also choose to modify the flags with the below set of approved changes (and only this approved changes):
The Winter Tournament staffer gatekeeping the race room will confirm all changes agreed upon before they roll the seed.
Sign-Ups:
Please sign up using the Winter Tournament Participant Form. ALL ENTRANTS MUST BE A MEMBER OF THE FFR DISCORD SERVER.
By signing up, you agree to be held to the Final Fantasy Randomizer Discord’s Code of Conduct while engaged as a participant of this event. Violations of the Code of Conduct may result in consequences ranging from a warning to bans from the discord, the tournament, all further events; these consequences may extend to other communities as well.
Broadcasting and Restreaming:
If you are being restreamed, the following Quality of Life flags will be required:
This request is to accommodate spectators who may be photosensitive. If you fail to make this accommodation, you will not be featured on future restreams unless you enable these features in your next race.
Stream Requirements:
Custom Sprites:
Players may use their fun graphical hacks for their game. That is, of course, with the caveat that the rom must pass the “Tournament Safe” flag, so players will really only be able to edit their hero sprites.
If the sprites are not recognizable as the traditional heroes of the game, the players must name their characters after the classes being used (i.e., FI, TH, BB, RM, BM, WM). As an example, using FF3 versions of the sprites is fine and does not require players to adjust the character names, but using Ranma 1/2 sprites, or Breath of Fire sprites, or Castlevania sprites, etc.. isn’t as easy to understand and would require conformed, basic names for the characters. And, of course, character names, and hero sprites, must conform to the above standards listed (so no swear words for character names, and no offensive or NSFW sprites of any kind, etc.). Questionable sprites should be sent to a Tournament Organizer for review/approval.
The Use of Trackers:
Throughout the Winter Tournament 2023 runners will be able to use trackers to help track key items and locations checked. However, the tracker must not be automated. Trackers which update entrances based on user input are allowed.
Conduct:
While on stream, and in interviews afterwards, players are expected to behave professionally and act to the expected standards for on-air behavior. This includes, but is not limited to: no inappropriate language, no rants about the other player, no rants about the tournament, no rants about the format, no rants about the streaming service, etc. This extends not only to the on-air portion of the event but to Twitch chat and public-facing Discords as well. Anyone that acts in a manner counter to the professional attitude and bearing we expect from our players at this event will be disqualified from the tournament.
Dropping/No Show Rules:
Player Drops:
Game Rules:
All games will be run using Racetime.gg. You will be asked if you have an account when entering into the tournament; please make sure you do so. You may use a console or approved emulator to play. All races are blind.
The winner will be determined by the Racetime's timer, unless external technical difficulties are in place, or if the race is decided by 3 seconds or less. In either case, the runners may agree upon a race retime. If they do not, a Tournament Organizer will retime the runs by hand and determine the winner.
Accidental Forfeits:
If you accidentally forfeit, please re-enter within 60 seconds of the forfeit. If the 60 seconds elapse, or you forfeit three (3) times in a race, the forfeit will be official. If you accidentally “.done” during the race before completing the race, let the tournament staff in the race know that it was an accident and re-enter the race as soon as possible.
Forfeits Due to Technical Issues:
If somebody has a technical issue that results in a forfeit (e.g. power loss, internet outage, hardware malfunction, software issues, etc.), please notify tournament staff as soon as possible! If you are unaware of the issue that caused the forfeit (e.g. LiveSplit integration betrayed you), a tournament staff will contact you as soon as possible via Discord and tell you of the issue.
Anti-Cheating Policy:
Cheating is not tolerated in community races. This includes, but is not limited to: using any external programs to analyze a ROM, looking at your competitor’s stream or chat, looking at the restream or the restream chat, or hacking the ROM to give yourself any sort of advantage. Any cheating discovered will result in penalties ranging from a forfeit of the race or instant disqualification from the tournament. Additionally, bans on participation in future FFR events or events organized by other communities may be sanctioned depending on the nature of the offense.
We require that all entrants keep their stream on emote only mode during official races.