MNVL Spring Club Rules

Please read the general rules below. Check back soon for the game-specific rulesets!

 
 

  • Important Dates

    Registration Period: March 16th – April 1st

    • Teams need to be created and signed up for their respective seasons on the league platform by this date. MNVL will allow late registrations for Club leagues by admin request.

    Preseason Dates: April 6th – April 10th

    Regular Season Dates: April 13th – May 22nd

    Club Finals:  May 18th – May 22nd

    General Rules

    The spirit of MNVL is to always play if you can and never take a forfeit win unless you absolutely must. Although not a rule, this is a standard we hope all our teams and players try to live up to!

    1. Default Game Times

    The regular season will consist of one weekly game, as outlined below. 

    *Titles are subject to change pending team numbers

    Monday 

    • 5:00 PM CT - Super Smash Bros Ultimate 3v3 Crew Battles

    • 5:00 PM CT - Rainbow 6 Siege 

    • 6:00 PM CT - Minecraft 2v2 

    • 6:00 PM CT- 2XKO 2v2

    Tuesday 

    • 5:00 PM CT - League of Legends 3v3 Aram

    • 5:00 PM CT - Magic the Gathering Arena 1v1

    • 6:00 PM CT - Marvel Rivals 6v6

    Wednesday:

    • No Matches

    Thursday 

    • 5:00 PM CT - Rocket League 1v1

    • 6:00 PM CT - Mario Kart 4v4

    • 6:00 PM CT - Blitz Chess

    Friday

    • 5:00 PM CT - VALORANT   

    • 6:00 PM CT - Fortnite Battle Royale Zero Build Squads (4 player)

    • 6:00 PM CT - Pokémon Unite


    2. Season Structure:

    League Structure - Club

    A. Teams

    Schools are allowed to field unlimited Club teams.

    B. Divisions

    There are no divisions in Club. All teams compete in the same pool.

    C. Season

    Club league seasons will have a one-week preseason followed by a five-week regular season. It will end with an online Club Finals Tournament. The dates and times for Club finals will be announced each season on the Fenworks platform, league Discord, calendar, and other channels.

    D.  Format

    Club leagues use the following formats:

    a.  Swiss (queue)

    E. Club Finals Qualification

    The top teams from the club league make it to the online Club Finals. The number of teams qualifying for the finals is found in Section 3, but may be adjusted after registration closes. Club leagues do not include a LAN finals; finals are all online.

    Teams will advance to the Club Finals based on the tiebreakers in section 3.3 of General Rules. The second tiebreaker, average game differential, will be calculated with one additional point awarded for each match played during the regular season.

    For example:

    • Team A: 1-4 record = +5 (net -3 with additional 8 points for matches played)

    • Team B: 2-0 record = +4 (net +2 with additional 2 points for matches played)

    Club tournament winners will receive a special role in the League Discord server with Gif posting permissions.

    2.1 Regular Season League formats

    • Queue System Swiss

    What is a Swiss: This is a format where teams always play against another team with the same record (e.g. a 2-0 team will play against another 2-0 team).  Our queue system leagues also follow the Swiss format. Learn more about our queue system here

    2.2 Preseason
    Preseason matches will function like a regular season match, in that players will still need to check-in and connect with their opponent on the league platform and report their scores. Results of preseason matches do NOT count towards your regular season record and do not affect qualification for the club finals. Due to the nature of queue system leagues, teams that miss their preseason matches for our club seasons will not be dropped.

    3. Club Finals Tournament
    Below you will find information on how Fenworks runs the Club Finals Tournament. All information below is subject to change, pending time, and the number of teams competing in each game title. Any changes will be confirmed once registration closes, and if no changes are communicated then the current process will stand.

    The Club Finals will be executed as a single elimination tournament in the last week of the season. It will be fully online and administered through our league platform. There will be an all-team meeting 15 minutes before the start of the tournament for all competing teams. This meeting will occur either in Microsoft Teams or Discord, depending on the league. Information on this meeting will be communicated with teams several weeks before it occurs. After the meeting, the tournament will commence. Most Club Finals tournaments are expected to last up to four hours.

    SPRING CLUB

    • Super Smash Brothers 3v3 Crew Battles: Top 8 Teams

    • Minecraft Bedwars 2v2: Top 8 Teams

    • Marvel Rivals: Top 8 Teams

    • Fortnite Battle Royale: Top 25 Teams

    • VALORANT: Top 8 Teams

    • Rocket League 1v1: Top 16 Players

    • Mario Kart 8 4v4: Top 16 Teams

    • League of Legends 3v3: Top 8 Teams

    • Blitz Chess: Top 16 Players

    • Magic the Gathering Arena: Top 8 Players

    • 2XKO 2v2: Top 8 Teams

    • Rainbow 6 Siege: Top 8 Teams

    • Pokémon Unite: Top 8 Teams

    (*The number of teams/players entered are subject to change based on needs or considerations by the league admin)

    3.3 Tiebreakers
    Teams/Players making the finals will be based on seeding, which considers standings score first, then average game/round differential, then head to head (if applicable), and difficulty of schedule.

    Standings Score will be calculated with the following values:

    • Win by Play: 4 points

    • Forfeit Win: 4 points (not counted in game differential)

    • Bye Win: 4 points (not counted in game differential)

    • Tie: 2 points

    • Loss by Play: 1 points

    • Loss by Forfeit: 0 points


    4.  Checking In and Reporting Scores

    A team captain or GM should check in all participating players for that match on the Fenworks Platform match page before starting their match. If a team decides to play with a reduced player count, the platform still requires you to check in a full roster. In this scenario, a team should declare in the match chat which players are missing before checking them in.

    If both teams fail to check in to their match on the league platform at the default time, both will receive a forfeit loss for the match. If one team is checked in and the other is not after the check-in time has expired, the team present is expected to wait 15 minutes after the start time of their match for their opponent. Once 15 minutes have expired, the absent team will receive a forfeit loss automatically on the platform.

    Scores will be reported using the platform score reporting tool

    • Both teams are responsible for reporting scores and saving replays/screenshots that prove their claim

    • All reported matches must have a screenshot attached

    • Procedures on how to report scores can be found in each title’s separate rules section

    All scores must be reported directly following the match, or it will be considered a loss for both teams. Fenworks staff have the right to adjust the score if evidence is presented that the match was played.

    5. Rescheduling Matches

    Matches are NOT able to be rescheduled due to the nature of a queue system league. The queue will occur during the same day and time each week, and teams will be matched with others that join the queue. Thus, reschedules are not able to take place during club seasons for any reason.

    6.  Home/Away

    The team shown on the left on the league platform match page is the home team, and the team shown on the right is the away team for that match. This is not in effect for playoffs, where teams gain home advantage based on seeding. Refer to the game title for specific rulesets on how home and away affect pick/ban processes.

    7.   Player Eligibility

    A player is any participant who plays in an official match. All players:

    • Must be enrolled in the school they are representing

      • Homeschooled players may participate with a school if they live within the defined district lines for the school district in question and have received approval from the school district to participate.

    • Must be 13 years or older, in 7th – 12th grade, and be 21 years old or younger.

      • A player may play for only one high school in the same school district.

      • Players who are 12 years of age or younger are not eligible to compete in all club titles. However, if a player turns 13 in the middle of the season, they are eligible to compete on and after the day of their 13th birthday.

    • The following are the only titles a player under the age of 13 is eligible to compete in for club seasons:

                                                                  i.      Chess

                                                                 ii.      Super Smash Brothers Ultimate

                                                               iii.      Minecraft

                                                               iv.      Mario Kart 8

    • Must meet and maintain the district’s eligibility requirements for GPA and attendance to be eligible to play. School Administrators and GMs are responsible for following and enforcing this policy and their school policy. The league suggests a 2.0 GPA or higher to participate.

    • Can only be on one roster per game title

      • A player can only be rostered to one team and play in one weekly match per title. If a player plays in more than one match of the same title, those games will be forfeited. Players can, however, play in multiple titles in a season.

        • For example, Student A cannot compete or be rostered on two Rocket League teams but can compete on one Rocket League team and one Minecraft team.

      • There is no restriction on the number of teams or players that can compete from each school.

    *Eligibility is subject to change at the League’s discretion but must be communicated to all schools before any changes take effect.

    7.1.Roster Changes and Substitutions

    Any changes to rosters must be done at least 24 hours before the roster’s next scheduled match. Players cannot be added to a roster if their next match is within the 24-hour time period. In this case, coaches must wait until after the roster’s next scheduled match to add another player to the roster.

    Substitutions are allowed if all players involved have been on the roster for 24 hours before the match. Substitutions can be made between games in a series but not during a game currently in play. Teams should never substitute during an individual game (I.e., passing their controller off).

    Substitute players are not allowed for individual game titles (1v1s). If one of those students cannot play their match in a week, should not join the queue. Their record will not change unless they join the queue.

    8. Spectators

    Only the players from the two teams competing in the official match are allowed in the game lobby. The one exception is if a spectator is joining to stream their team's point of view (POV) for their official school stream and the opposition is made aware. The spectator must have an open mic for the entirety of the stream to prove they are not in contact with either team.

    Players competing in the match may stream their own POV. Stream malfunctions do not qualify as a reason for pausing a match.

    • Valorant: When streaming Valorant, the spectator MUST choose the coach position in the lobby for their team only. The spectator in this situation must not have communication with their team or they will forfeit the match. 

    • League of Legends: Spectator Delay is set to “Add Delay”

    Any team caught breaking these rules are subject to penalties listed in section 12.

    9. Names/Usernames

    A player’s name in-game must match the name that they have registered for that game on their Fenworks profile. All participants names or profiles are prohibited from including:

    • Gang Affiliation

    • Drugs (including alcohol and tobacco)

    • Sexual Material

    • Offensive Material

    • Politically Charged Symbols/Images

    • Homophobic or Racially Insensitive Material

    This includes our Discord community.

    10.Cheating

    Any manipulation of gameplay including, but not limited to, scripts, wallhacks, aimbot, 3rd party applications, sound changes, or having another person play on an official player’s account during match time will be considered cheating. Players must also follow the Code of Conduct. Any team or player caught cheating will be subject to the items outlined in section 12.

    11. Harassment

    Players and coaches must always abide by the Fenworks Code of Conduct.  Failure to do so will result in disciplinary action, as outlined in the following section.

    12.Disciplinary Action

    If Fenworks decides that a Player has violated any of the Rules, Fenworks may take the following disciplinary actions (as applicable). More information can also be found in the Code of Conduct:

    • Verbal Warning

    • Game and/or Match forfeiture

    • Issuance of Public warning (Verbal or written) to the Player

    • Disqualification of the Player from participating in one or more Matches of the Tournament.

    • Stoppage of the Player from participating in one or more future competitions

    • Stoppage of the School from participating in one or more future competitions

    If a Player is suspended/banned by a Fenworks Representative, they will be notified via email and/or Discord. Within 30 days of the initial penalty, an appeal can be sent by the coach or program coordinator representing the Player. Please send all appeals via email to esports@fenworks.com

    13. Spirit of the Rules

    Finality of Decisions

    All decisions regarding the interpretation of these rules, player eligibility, scheduling and staging of the Tournaments, and penalties for misconduct lie solely with Fenworks Officials, and their decisions are final. This includes the exclusive right to make definitive rulings on matters not specified within the rules and handbook.

    Amendments

    Fenworks may update, revise, change, or modify these Rules at any time to ensure fair play and the league's integrity. Each Player’s participation in Fenworks after any update, revision, change, or modification to these Rules will be deemed as acceptance by such Player of these Rules as updated, revised, changed, or modified.