2. Game Format

2. Game Format

2.1 Main Info

Tourney Style: Round Robin
Gamemode: Firefight
Team Size: 5v5
Max Roster: 8
Round Time: 2.5 Minutes
Win Limit: 11 Rounds
Team Switch: Every 5 Rounds
Max Rounds: 21
Theater file: pgl_comp_0012.theater (Downloadable)
Main Config: server.cfg
FF Config: server_firefight.cfg
Version: Current Live Build

2.2 Additional Info

Starting side is picked by playing a knife round. NO equipment, grenades, or weapons can be used during this time. For the main part of the game, all weapons and attachments are controlled by the theater file. If a weapon/item is displayed, it can be used, unless there is an obvious issue with your clients theater file and it can be determined that you have not properly connected to the server.

2.3 Round Robin Info

This even will be a Regional, Divisional Round Robin. Each team will compete with every other team in their Division, with the top team from each Div, going through to finals. If the number or registered teams are high enough, it may be announced (before the Season starts) that the top TWO teams will go to finals.

The following is the list, in order, of ranking criteria for finalists selection;

1. Points (3 for Win, 1 for Loss, 0 for Forfeit/DQ)
2. Total Win-Loss
3. Difference in Rounds For-Against
4. Least Forfeit Wins
5. 1 Round (Sudden Death) Decider Match

One game will be played by every team, each week, unless they are on a bye. In the current theater, a game will be played until one team reaches a score of 11, and will be tied at 10:10. Tie breakers are handled by the theater and plugin, but for your understanding, the match format is detailed below.

At 10 rounds, the halves will switch. In case of a tie (10:10 after 20 rounds played), overtime will have to be played. The overtime is played first to 4, 3 round halves. Teams will continue from where they left off with the score being 10:10 (last round).

The teams will start on the side they began the game on (the side they picked after the knife round). After 3 rounds played, teams switch sides. If a team wins in overtime, the reported score will be what the score was from OT (4-2 as an example). If Overtime ends in a tie, Overtime will be repeated.

These weekly match-ups will be generated by our website and crosschecked by Season Admins, 3 days before the event begins. All Teams will know their match-ups for every coming week, excluding finals.

It is the responsibilty of all Team Captains, to ensure their matches are played each week, by contacting the opposing TL via their prefered means. The date and time for each game, is to be agreed upon by the Team Captains of both sides. It is suggested that players offer flexibility and agree on a time slot a few days before it is meant to be played, wherever possible. Later Rounds for example, allow for several weeks of negotiating, whereas Round 1 may only offer 3 days notice for a Monday game.

One key reason for our regulations on public Steam profiles, is to allow a default contact method for scheduling games in events like this. Other methods, such as utilising our Discord for the Text Channels or Direct Messaging, are also recommended, as an addition to Steam. Since all Team Captains are required to be present in the Discord during matches, this makes for another excellent method.

Any issues regarding match-ups and scheduling must be directed to a Season Admin, ASAP. Unfortunately, some regional reps won't have the ability to solve your issues if you are from another region, so wherever possible, approach an Admin from your region.

3. Registration

3. Registration

3.1 Player Registration

Players wishing to take part, must complete their Play! profile, which is generated for you when you register for PGL, but is a seperate profile than the one you are redirected to on login. Simply login and join a team which is registered for the Season. For detailed instructions, visit Get Started. Players must make their Steam profile public, in order to compete. If you wish to keep a private profile, you may be allowed to return it to private, after an Admin has inspected it. Players looking for a team (LFT) should contact Team Captains or apply for the Mercanaries team, to be placed in one, or remain an emergency extra.

3.2 Team Registration

Team Captains must create a new team, or register and existing one, in order for players to join. For instructions, visit Get Started. Once your team is registered, simply add players manually, or approve/reject those requesting to join your team. Teams looking for players (LFP) should utilise our forum. 

4. Members

4. Members

4.1 Sportsmanship

All members are required to uphold and observe a universal level of sportsmanship. Any unsportsmanlike action which can include, but is not limited to racism, profanity, rude/vulgar acts, abusive remarks, and disrespect of an official are not tolerated. Users who engage in unsportsmanlike conduct may be subject to suspension, match forfeits, or any other punishment at Admin discretion.
Participants must treat other participants with basic respect and decency. Seeking to cause significant distress to other participants is unacceptable and may result in round or match forfeit, or greater sanctions if warranted. Intentionally engaging in behavior that would reasonably cause significant distress to other participants may be punished even if no complaint is raised or harm can be shown. This includes taunting, insulting, flaming, or any negative comments over voice and text chat. Anyone witnessing or experiencing uncivil conduct by a participant should record evidence and report it to an Admin. Teams must attempt to win each game to the best of their ability. Actions taken for the benefit of any team except your own are strictly forbidden. Collusion between teams is not allowed and bannable.

4.2 Member Names

Member name handles containing any of the following will not be tolerated: profanity, racism, sexism, drug use, or general vulgarity. Players found with offensive names may be contacted by an official and asked to change their name to something more appropriate. Refusing to do so may result in termination from the Season. No one is permitted to include "Admin", "Mod" or anything deemed as false or an imitation. Offenders will be subject to punishment at Admin discretion.

4.3 Season Admins & Staff

Season Admins are responsible for managing and moderating the event, as opposed to Team Captains, who are responsible for their own individual members. All Admins will be easily identified in Discord for any support, however Pacific Gaming League hosts many other games, so not all Moderators and Admins are Insurgency Representatives. "Insurgency Rep" is what to look for once you see an Admin/Mod tag. Any PacificGL staff member may be able to assist with questions or grievances, so don't be afraid to use the @Mods mention in the #support channel of Discord. However only select staff are Season Admins, capable of making rulings on disputes, for this event.

The Season Admins are;

• Dr. Ace Misanthrope (Organiser)
• Masser (Organiser & EU Rep)
• HighHeedYin (EU Rep)
• Solusvod (OCE & EU Rep)
• Piggymonster (OCE Rep)
• Jazza (OCE Rep)

5. Teams

5. Teams

5.1 Captains

Team Captains are in control of every aspect of the team. Team Captains have the right to edit team information, add or remove members on the team, schedule matches, report scores, and file disputes. Every team is required to have a Team Captain. Team Captains WILL be held accountable for the actions of their players and disciplinary action may be taken on the Captain, in addition to the guilty player, whenever appropriate.

Team Captains should be the only person to submit a complaint or dispute on behalf of the team. Team members may submit inquiries, providing the Captain is not already doing so. Multiple submissions from a single team will result in them being ignored and only the Captains, if submitted, will be reviewed.

It is the responsibilty of all Team Captains, to ensure their matches are played each week, by contacting the opposing TL via their prefered means. Any issues regarding this responsibility should be brought to the attention of a Season Admin in your region, ASAP. For more information, see 2.3 Round Robin Info.

Team Captains MUST be in the Pacific Gaming League Discord for the duration of ALL official matches. Players may utilise the Discord and/or TeamSpeak at their own discretion, however Captains are required to be easily contacted in Discord during their games, so this rule may result in a penalty round to the offending team if violated. Players must not message the opposing team during games, unless done so in-game, within sportsmanship guidelines, or they are directed to do so by Season Admins.

Upon the completion of each game, once screenshots are taken and players have disconnected, the Captains must report their scores. For more information, see 6.6 Match Results.

5.2 Team Names

Team name changes are allowed, however other Team Captains and Admins are to be informed and the team name changed in all places it is identified. Team names must be distinguishable from eachother, but may be similar and are under the same regulations as player names. See 4.2 Member Names for more.

5.3 Rosters

A team is the actual collection of players on a roster together. A common name, group of origin, community, affiliation, or sponsor does not join two teams, a team is treated as an independent group. If a group has two different teams with different rosters, they are treated as independent teams and players cannot be freely swapped between the two teams.

The roster may consist of up to 8 players (Lineup: 5 | Subs: 3). Team rosters may change at any point in a Season and rosters are never locked, however recently acquired players MAY NOT play a tournament game within 1 week of joining a team UNLESS permission is given by the opposing Team Captain AND Season Admins.

5.4 Team Captain Changes

Changes to the member designated as Team Captain are permitted if the Team Captain would like to relinquish the leadership to another member on the team, has been terminated from the event by an official, would like to leave the team, or has been mutinied by the other members of the team.

5.5 Ringers, Substitutes, and Alternate Teams

If a team is met with the situation of having less than the required players from their roster, available for a given match, there may be some options;

1. Forfeit
   • This will count as a 0-11 loss
   • Teams with only 1-3 players available must forfeit
2. Use a "ringer"
   • May be used by each team, TWICE per Season
   • The team must have at least 4 players from their own roster, available
   • The team may call upon a SINGLE ringer to be their the 5th/6th player.
   • This ringer must be a REGISTERED and ELIGIBLE player, residing within the MERC team, meaning they have have been registered for at least 7 days prior to the match.
   • Each MERC player, may only play ONE game for each team, per Season
3. Play Short
   • Play 1 or 2 players down (4/6 or 5/6 only)
   • Teams with only 1-3 players available must forfeit

The MERC team is a group of players, dubbed Mercenaries, whom reside within a non-competing team. This team is a collection of players, unable or unwilling to join a competing team and are available for teams to select from in emergencies. Teams needing a Mercenary may directly contact one when required.  We expect both teams to operate with professionalism and sportsmanship in the event of a needed MERC.

6. Matches

6. Matches

6.1 Game settings

ALL official matches, must be played on offical servers listed below;

• Asia/Oceania: PacificGL ANZ Offiical Server
• Europe/Africa: The Gym EU Offiical Server
  
• North/South America: The Gym NA Offiical Server

For details on configurations, see 1. Game Format.

6.2 Maps

The Official International Season maps are;

• Verticality
• District
• Heights
• Market
• Ministry
• Siege
• Station

Each week, Team Captains will knock off 1 map each until the last remains, which will be played, starting with the HIGHER RANKED team.

In the case of play offs, which will be a best of three (BO3) elimination, the same process will be used, with the higher ranked team banning first, until 3 maps remain. The order of which they are played will be determined by the Season Admins.

6.3 Picking sides

A knife round must be used to pick sides, with the winner electing to stay or swap. No grenades, equipment or weapons of ANY type, other than knives, are to be used. Doing so will result in the team forfeiting the knife round and the opposing team choosing the side. To swap teams, a vote should be passed, rather than players manually swapping sides.

6.4 No Show

If your opponent is not present 15 minutes after the agreed upon time you have the right to open a protest, to request a default win. Please try and be accommodating and sportsmanlike.

6.5 Server Crash

If the server crashes before the first round has been completed the server must be restarted and the score will be reset to 0-0. If the server crashes after the first round, a screenshot must be made showing the current score (you should have time to do this). The server should then be restarted and play will resume with the previous score-line.

If no screenshot was taken, captains may agree on a score to be played from. If there is no record of the score (e.g. screenshot, demo review, etc.) and there is no agreement upon a score to play from, the match will be restarted at 0-0. (REFER TO SPORTSMANSHIP!)

If an Admin is observing the game and no record of the score is kept by the captains the Admin may elect to intercede with regards to the score.

6.6 Match Results

Both of the teams are required to take screenshots of the final scoreboard. This should clearly show all the players involved and whether or not the team won or lost the game. In order to assure this is carried out, all players are asked to wait on the server for around 1 minute after the games completion. Disconnecting immediately after the final rounds completion is considered unsportsmanlike and makes the Captain's jobs harder. Please be considerate.

Upon completion of the match, each Team Captain (whom should both be in the PacificGL Discord) are required to post in the "#scores" Text Channel in the format "HomeTeam Score:Score AwayTeam". Eg. "TeamX 11:5 TeamY". If a team forfeits (eg. TeamX), they must both post "TeamX FF:11 TeamY". All scores will be updated by Season Admins to be displayed on the event's Standings page and through the site, as soon as possible. 

6.7 Match Aborts

If a team aborts a match before it is finished, a win may be granted to the remaining team if the match advanced to a point where the end result can be determined. If your opponent should deliberately leave the match, you must submit a report to the Season Admins. You are not allowed to enter a result yourself. This can be penalized as a fake result.

6.8 Substitutions

Substitutions may occur after a round is complete not in the middle of a round. 4 substitutions may be performed per game. A substitution is counted for ANY reason one player leaves and another joins. This includes disconnects, crashes, etc. only if a different player joins.

6.9 Pauses

A team will be allowed up to 10 minutes of Time Out, over the course of the game (in increments adding up to 10 minutes). To prevent the timer hitting 00:00 and causing complications, it is VERY IMPORTANT that a RESTART ROUND vote is called after 3 minutes of pausing. If longer is needed, pass the vote and specify CLEARLY that the game is still paused. During a pause, both teams MUST stay in their spawn. We encourage every team to communicate properly if an emergency arises. It is also encouraged to always have a substitute player on hand should a real life emergency occur.
A pause should be called either during the previous round in text, in global/all chat, e.g. “pause next round”, or during the countdown time between rounds. ONLY the team that has called the pause may unpause the game. This is done by passing a RESTART ROUND vote and typing in all chat Live on Restart or LOR.

If a team goes over the allocated pause time (10 minutes total, not just over the 3 minutes of a round), a restart round vote is to be passed and play resumed, regardless of whether the paused team is ready or not. If this restart round vote IS NOT passed, then the team that did not call the pause is awarded 1 round. The cooldown timer for the vote is to be waited out, then another restart round vote should be called. If this too is not passed then another round is awarded. If the 3rd restart round vote is not passed then the pausing team will forfeit the match.

Pausing can sometimes cause complications and disrupt the flow of the match. It is encouraged not to use pauses for reasons other than subbing or quick, urgent breaks, such as rushing to the toilet, however teams ARE allocated up to 10 minutes per match. Please be considerate.

7. Misc. Rules

7. Miscellaneous Rules

7.1 Spectating

Spectating matches in-game is not permitted unless it is for official business (i.e. casting). Spectators/players found to have breached these rules and interfered with the game, in any way (not including official referee-type actions) will be punished. An Admin is permitted at any time to spectate a match. If any team member has an issue and intends to complain, it is the responsibility of the CAPTAIN to do so. Refer to 5.1 Captains.

7.2 Connection Issues

If players cannot connect to the Official Match Server, contact a Server Admin. If both teams agree to delay their game, they may do so, provided a new date and time is organised within the same week. If at least 4 players from each team can connect to the server, the game must be played.

If a player disconnects unintentionally for any reason during a match, play continues! This includes during the pre-round timer. It is the job of the team with the disconnect, to call a pause if they wish to replace the person or wait for them to reconnect, instead of continuing the play. If you choose to pause at all, it will count towards the 4 sub limit and your 10 minute pause cap.

This particular event is open to all (excluding hackers/cheaters and those with a perpetual ban from PGL events). People with high ping on servers in their own region may fall under the sportsmanship rulings, meaning they are expected to be substitued wherever possible. However unless a player is found to be intentionally raising their ping or effecting the servers performance, they are welcome to play.

7.3 Invalid/Illegal Rounds/matches

Examples when a ROUND is deemed invalid and the offending team forfeits that ROUND;
> An unauthorised player is spectating
> A team leaves spawn during pause (subject to Admin discretion if dispute arises)

Examples when a MATCH is deemed invalid and the offending team forfeits that MATCH;
> Team member(s) cheating/hacking (includes walling, aimbots etc.)
> Team member(s) using macros (All macros are illegal in this tournament)
> Team subs more than 4 times in one game.
> Team manages to use invalid weapons (bypass theater)

7.4 Cheating/Hacking

To be eligible to compete in this season, all players must use a clean Steam account and link it to your PGL Play! profile. The Steam profile MUST be public, allowing Admins to check for additional information, as per the registration requirements. Cheating/Hacking/Smurfing is not allowed and will result in a removal/ban from the Season.

Cheating and/or Hacking includes any unauthorised manipulation of: server configurations and server variables, client configurations and client variables, models, skins, entities, textures, weapon, sounds, or anything else that subverts the PGL rules. Hacking includes but is not limited to: wall hacks, aim bots/auto aimers, speed hacks, ESP, or any other third party program which alters the game in a way that the game developer did not intend for.

Smurfing is the act of intentionally deceiving teams and Administrators involved in the competition, whereby a team plays a non-rostered or ineligible player on a) an account not belonging to them, or b) on another player's account.

8. Player Settings

8. Player Settings

8.1 Overlays and Audio Alerts

Overlays and Audio Alerts conveying otherwise-concealed game information are prohibited.

8.2 Custom Files

You may not modify critical game files, i.e. texture or sound replacement circumventing consistency checks and pure settings. Console commands, launch options, and autoexec.cfg settings are permissible to tweak, as long as nothing clearly exploitative is done. ANY evidence suggesting a player is modifying their game to gain an advantage WILL result in a ban from all PGL events.

8.3 Application Tampering

You may not tamper with the game application in a way that causes unnatural functioning. Console commands, launch options, and autoexec.cfg settings are permissible to tweak, as long as nothing clearly exploitative is done. ANY evidence suggesting a player is modifying their game to gain an advantage WILL result in a ban from all PGL events.

8.4 Connection Tampering

You may not interfere with your connection quality or connection settings aside from rare tweaking if there are issues during a match. This rule includes automated tampering systems. This rule includes all systems between you and the server, not just your game client.

8.5 Macro-Like Systems

Anything similar to hotkeys, macros, automated programs, scripts, and/or other systems for executing the equivalent of multiple keystrokes/inputs with a single keystroke is banned in PGL events, including matches and contests. (This includes console inputs. Chat macros and Admin/casting tools used legitimately by an Admin/caster are the only exceptions.) Any hotkey, macro, script, keybind, and/or automated program that artificially alters the fire rate (such as a fire macro that turns the m16 into an automatic rifle), causes unnatural aim adjustment or movement compensation, or causes other unnatural actions, are against our rules. Field of View Changing Macros are banned. Scroll wheel firing or macros used to fire a weapon are banned. One keystroke per “trigger pull”.

8.6 Player Suicide

Using the kill command during a match is prohibited. Intentionally killing oneself through game actions is forbidden, unless an opponent is legitimately and very feasibly targeted as part of the act. An exception is where a restart round vote has not been called and the time has reached 0:00 during a match requiring 1 team to win a round. In this situation the LOSING (team with the lowest score) must all type “ kill ” into console so as to restart the round. It must then be noted that they have an extra round win on the scoreboard that must be discounted.

8.7 Demos

It is mandatory for all players to record point-of-view (POV) demos for the full duration of all matches without exceptions. The knife round has to be recorded also. As long as one of the players/teams is able to upload the knife round on Admin request there will be no consequences for a missing the knife round. In case no player/team can upload the demo on request the player/team may result in a round or match forfeit. Protests regarding missing the knife rounds are not valid. The main part of the game must be recorded by ALL players from start to finish. Failure to do say may result in match forfeit. The purpose of this is to be able to provide a demo in case of disputes or at Admins request. This source recorder uses minimal resources and creates a tiny file, unlike other video recorders. All demos must be made through this method.

To record a demo, follow these instructions;
1) Open up the in-game console using Tild (~)
2) Type “record” followed by a space and then a name for your file. (Eg. “record CFvAURmarket)
3) Hit Enter and you should get some feedback that you are now recording.

To stop a recording, open up the console and type “stop”, then press Enter.

Additional rules that apply to Demo Recordings are as follows;

• Demos and any other required recordings of matches should be retained at least until 14 days after the end of the relevant Season, Tournament, or event.
• The original match demo file must be the file uploaded.
• Original match demos may not be edited.
• In general, dysfunctional or manipulated demos will be treated as missing demos, although the final decision is up to the Admin. If the demo is incomplete, the Admin will decide whether or not it will be treated as a missing demo.

8.8 Streaming, Recording & Casting

No player may stream a match (this includes private stream). If a player streams the match, the opposing team may dispute the match results and a decision for punishment will be determined by Season Admins. It is in the interest of Pacific Gaming League, to broadbast as many events as possible. Therefore, interested Streamers & Casters are encouraged to approach Season Admins for approval to stream matches, however no Live Stream is permitted for a player participating in the aforementioned match. All streamed matches must have a delay of 2 minutes or more. See 7.1 Spectating for more info.

9. VAC Bans

9. VAC Bans

9.1 VAC Ban Policy

The PGL prohibits players with any VAC bans from competing in PGL events, Seasons, and tournaments. Players caught cheating in any game, will be barred from all PGL competitive play. Any player found with a VAC ban on their current or previous accounts*, will be barred from PGL play at Admin discretion. Any player who receives a VAC ban for ANY game, during a PGL Season/event, may find their team disqualified from the current Season.

* If a player with a VAC ban on a previous account wishes to compete in a PGL event, they MAY be considered at Admin discretion. For the player to be allowed to compete, they must demonstrate their case, that the VAC ban was a false positive or for a game that PGL is not involved in. PGL always strives to ensure a safe and friendly environment for its players, so we take bans seriously. If players with bans on their CURRENT account wish to compete, the ban must be over 1 year old and they may still be asked to purchase the game on a clean account. Approval of banned accounts is entirely up to the Admins and undergoes a strict check.