Season 2 Rules


  • The RHL season will be split into two distinct entities, Single-Day Events, and Competitive League Play.
  • Entrant sizes will be 3-5 players, with PC and PS4 players allowed to compete.

Administration and Announcements

  • Official announcements as well as statements of RHL Commissioners may overrule or alter any of the following rules. In case of contradicting declarations, the most recent announcement or statement will be enforced.


  • By competing, participants acknowledge without limitation to comply with the rules and regulations, official announcements, and with the statements and decisions made by the RHL Commissioners.
  • Every participant acknowledges the right of RHL Commissioners to modify the rules and regulations at any time without notice.
  • Every participant must show respect towards admins and other participants. Disrespectful behavior towards anyone will not be tolerated.
  • Every participant must always have the newest version of Steam and Rocket League installed and is responsible to check for updates in time before each match. Unless an update comes out right before a match, patching is not a valid reason for delay.
  • Every Entrant and participant has to try to win every game at every stage of the competition. Purposefully losing for any reason will not be tolerated.
  • Any use or abuse of rules intended to undermine the spirit of competition will not be tolerated.

League Play Registration

  • Captains must register by filling out the google doc Registration Form.
  • Each player registered must have a steam profile link (PC) or a PSN ID (PS4) included in their information.
  • Entrant captains must include an email address.
  • Entrant names, player names, and logos must be original. If you feel your name is already well established, and another Entrant in the league has a conflicting name, you may contact the Commissioners to have them assess the situation and resolve it positively for those involved.

Entrants & Players

  • An Entrant has to consist of at least (3) three member players, and no more than (5) five. Those persons will be called “members” or “players” of the Entrant in the following.
  • Entrants will designate a “captain” and (optionally) an “assistant captain”. Either the captain, assistant captain, or an acting captain must be present for all RHL games. A team’s captain or assistant captain must notify the opposing team in advance if they plan to use an acting captain.
  • Any duties designated to the team captain may be fulfilled by the assistant or acting captain.
  • Rosters will be locked for each Period. Roster changes will only be allowed during two week Intermissions between period.


  • All formal communication in between participants and RHL administrators has to be in English language.
  • Team captains and assistant captains are responsible for communication within their team, with other teams, and with the administration.
  • Captains may communicate on any platform of their choosing for the purposes of scheduling.

Seasonal Format

Single-Day Events Registration

  • The RHL Single-Day Events are detailed in the RHL Single-Day Events Document.
  • RHL Single-Day Events will be broadcast on the RHL Twitch with full commentary and graphics, and will allow players immense fluidity and team options, as any combination of players may enter in groups of 3-5.
  • You may play in the same formations as League-Play, but are under no obligation to do so.
  • Players from different League-Play entrants are welcome to compete as teammates in Single-Day, etc.
  • Players who aren’t playing in League-Play are free to participate as well.
  • Registration for Single-Day Events will be announced well in advance of any scheduled event, with details forthcoming.

Match Protocol

  • Before the match, captains will communicate to establish team colors, server locations, and server name/password.
  • Challenging team chooses their desired color and server location for Game 1, Game 3,  and Game 5 (if needed) (every odd numbered game).
  • Accepting team chooses their desired color (stay/switch) and server location for Game 2 and Game 4 (if needed) (every even numbered game).
  • Challenging team creates the server and starts matches using standard server info — the two teams acronyms combined, with home team first, for both server name and password. (Example TOBO challenges FINE and therefore sets-up the match, with server name TOBOFINE and password TOBOFINE.)

Server Settings

  • Snow day mutators (ball type puck, ball bounciness low). NOTE: Options must be changed in the mutators sub­menu. Changing the “game type” on
  • the server selection screen does not apply all of the snow day mutators.
  • Unless another standard map is agreed upon by both teams, the default snow day map (DFH Stadium Snowy) will be used.
  • Non­-standard maps are not currently allowed.
  • 3 v 3
  • Server/password, no party servers.
  • Default for all other game settings.
  • Before joining a side at the start of a game, players must wait until everyone involved in the match has joined the server.
  • At the end of a match, a Team Captain must post screenshots and replays to the designated Discord channel on the RHL Discord: #league-play-match-results. Failure to provide replays will result in the match not counting and any personal stats for the match will not be collected.
  • Only screenshots and replays are to be posted to this channel.
  • Replays and end game screenshots of the scoreboard are required to be submitted or your match will not count for Points, and your stats will not be accumulated for end-of-season glory!

Match Rules

  • Only 3 (three) players per team are allowed on the server at any time. Coaching while using a spectator slot is not allowed.

Re-games (or re-starting games) required for the following reasons:

  • The game is hosted in the wrong server region or with the wrong settings.
  • An Entrant has more than 3 players on the server at the same time during a game, for more than 10 seconds on the game clock.
  • A player joins a match before all players have connected (triggers game start countdown).
  • Server Reroll – Entrants may ask for a reroll once per match, before 10 seconds have passed on the game clock, and before the first goal. This is to mitigate server issues and/or unusual latency. The re-game is played in the same region.
  • Server crash ­- If a game is interrupted by a Steam or Psyonix server crash, the first recourse is utilizing the Match Admin feature to reset the new server to the last known score and time remaining. If the Entrants cannot agree on these variables, and no review is able to determine the settings, the game must be re-gamed to count toward a match result.
  • If a server crash occurs during overtime, the regame must be played as a first to 1 goal.
  • Re-games are allowed for other reasons only at the agreement of both Entrants, unless ruled otherwise by an admin.
  • Re-games are to be played in their entirety, aside from the overtime regame rule, UNLESS the Match Admin tool is used to recreate the conditions at the time of the crash, in which case the game shall be played to its natural conclusion.
  • Communication between teams during a game should remain in-­game when possible.

Substitutions and Disconnects

  • Entrants are allowed to substitute one member for another, between games.
  • If a player disconnects, emergency substitutions are allowed, in lieu of that player reconnecting.
  • Players subbing in are not allowed to join the game prior to another teammate disconnecting.


  • A game is finished at the end of the default 5 minutes if an Entrant scored more goals than the opposite; after Overtime if the game is tied at the end of regulation; when the majority of an Entrant’s players leave intentionally, or when the administration decides on it.
  • Stats will be maintained and curated for all submitted matches and players. If no replay is submitted for your match, that performance will not be reflected in official stats.


  • If any game­ breaking bugs occur, the game has to be quit and re-­played. If an Entrant objects to a rematch, a video recording of the bug is strongly recommended. The Commissioners will then decide the outcome.
  • Abusing a bug is forbidden.
  • Pinching (pressing the puck between two surfaces to launch it) is not considered a bug.
  • Deadstops (where the puck changes speed or direction unpredictably while only interacting with map geometry), though extremely rare, will not be considered game­ breaking except in extreme circumstances (causing or stopping a goal in very close games), after review by Commissioners.

Tools and Hacks

  • The use of any Rocket League tool that alters gameplay or provides an unfair advantage during a match is strictly forbidden.

Rule Violations and Punishments

  • Rule enforcement and punishment is at the discretion of RHL Commissioners. The possibilities for punishment include game forfeits, match forfeits, player/entrant suspension, and player/entrant banning.