Insurgency: Sandstorm (5v5) OC Season #1



Competitive Insurgency: Sandstorm in a 5v5 Firefight format.
PacificGL hosts Oceanic competitive Sandstorm and has supported the game since early Alpha, after founding Insurgency ANZ in 2015-2016, to host Insurgency 2.
To get involved, simply register an account and create or join a team.
Need help? Visit Get Started


Rank Teams Won Lost Played For - Against Difference Points Last 5
1 Enigma 0 0 0 - 0 0 ?????
2 I Didn't Spawn 0 0 0 - 0 0 ?????
3 GGEZ 0 0 0 - 0 0 ?????
4 REDACTED 0 0 0 - 0 0 ?????
5 Rusty Scrubs 0 0 0 - 0 0 ?????

Event Starts 4th of Feb 2019

After years of hosting Insurgency 2014 we announced that we would stop with OC Season #6 and wait for Sandstorm. Well it's here and it's reached a point that allows us to present to you, the first Insurgency: Sandstorm Oceanic Season, hosted right here at Pacific Gaming League. This season is proudly sponsored by, our Insurgency server provider. To get your own server, either Insurgency: Sandstorm or a range of other games, check out their website and get a nifty 10% off, by using the code: PACIFICGL.

We are happy to confirm that Insurgency: Sandstorm OC Season #1 will begin 4th of Feb, but registrations are now open! Originally announced as 14th Jan, it was delayed to allow people to return from holidays, allow the development to progress further and provide more time to develop new Discord Bot technology that will help us setup and run the season. Whether you play Coop or PVP and whether you are new or experienced, be sure to take part in this event, set to be a blast! We already have 4 extremely eager teams whom expressed interest, comprised of some veterans, new bloods, or a combination.

To participate, simply register an account with our website, complete your Play! profile, then join an existing team, or create one and register it for the event. For detailed instructions, check out Get Started. For this event, all players are also required to join our Discord. Most players with an average ping of 150ms or less to a Sydney, Australian sever, will be able to take part in this season. For full eligibility and other info, read the Rules. Some weekly games will be broadcast at, along with all of Finals. Register ASAP, as teams will lock @ 11PM on Friday 1st of Feb 2019. Remember, as rules and information gets updated, you can find it first at our Discord. Our websites Insurgency: Sandstorm section will continue to post updates of important events.

Registration End Date: 1st Feb '19
Event Start Date:  4th Feb '19
Comp Format: Round Robin (with Divisions if enough teams)
Version: Live Steam Build
Mode: 5v5 Firefight
Team Size: Max 8 players (5 Core, 3 Subs)
Round Time: 2.5 Minutes
Round Win Limit: 11 Rounds
Max Rounds: 20 + Overtime
Game Win Limit: Best of 1 (BO1)
Finals: Best of 3 (BO3)
GameMode Ruleset: CompetitiveFirefight
Other: No Mods, No Third Person Spectate, Otherwise Vanilla


Registrations Close 1st of Feb @ 11pm AEDT

Need help or wish to take part in our nightly PUGs and scrims? Come and speak to our staff and PUG Helpers at Good luck, have fun!


Rules, Eligibility & Config



1. Config

1.1 Config Summary






Point Control (3 Objectives)

Team Size


No Spectators

Max Roster


5 Core, 3 Subs

Round Time

2.5 Minutes

150 Seconds

Win Limit

11 Rounds

Team Switch Every 10

Max Rounds

20 + OT

Comp Ruleset



Current Live Build

We update as NWI update


1st Person & Team Only

No One in Spectator Mode

Friendly Fire



2. Game Format

2.1 Main Info

Registration End Date: 1st Feb '19
Event Start Date:  4th Feb '19
Comp Format: Round Robin (with Divisions if enough teams)
Version: Live Steam Build
Mode: 5v5 Firefight
Team Size: Max 8 players (5 Core, 3 Subs)
Round Time: 2.5 Minutes
Round Win Limit: 11 Rounds
Max Rounds: 20 + Overtime
Game Win Limit: Best of 1 (BO1)
Finals: Best of 3 (BO3)
GameMode Ruleset: CompetitiveFirefight
Other: No Mods, No Third Person Spectate, Otherwise Vanilla

2.2 Additional Info

Starting side is picked by playing a pistol round. NO equipment, grenades, or other items can be used during this time. For the main part of the game, all weapons and attachments are controlled by the server configuration. If a weapon/item is displayed, it can be used, unless it can be determined that you have not properly connected to the server.

2.3 Event Format Info

This event will be a Round Robin. 24 hours before the start of the event, all weekly matchups, except Finals, will be announced. The Qualifiers Round begins and each team will compete with every other team, with the top 2-4, going through to Finals, based on number of competing teams. Each team will receive points, based on the outcome of the game.

The following is the list of points rewarded for match outcomes;

  • Winning team receives 3 points in all cases
  • Losing team receieve 1 point for a loss
  • Losing team recieves 1 additional point for a loss in Overtime (2 total)
  • Lose team receieves 0 points for a forfeit / disqualification

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

  1. Points
  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 each week, by every team, unless they are on a bye. With current settings, a game will be played until one team reaches a score of 11. If they tied at 10:10, they will go into Overtime. OT is First to 4 (BO7) with 3 round teamswap. Teams will continue from where they left off with the score being 10:10 (last round). OT is repeated if it hits 3:3 with another First to 4. The teams will start on the side they began the game on (the side they picked after the pistol round). If a team wins in Overtime, the reported score will be 11:10 with a comment providing the final OT score and number of OT's played.

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, well in advance. 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 a couple of days notice for a Monday game.

Any issues regarding match-ups and scheduling must be directed to an event Admin, ASAP.


3. Registration

3.1 Team Member Registration

Exisiting Players: Existing players wishing to take part, must login and either create a team and register it for the event, or join one via the event standings. From there, visit a teams page and click "Join Team", then wait to be accepted by the Team Captain. To create your own team, read 3.2 Team Captain Registration, below.

New Players: New players wishing to take part, must register for our website, then login. Upon logging in, you must add your Discord tag and Steam Profile URL, to your Play! profile. This is a separate profile that was created with some basic info that you provided for the website account. Now you can visit the event standings to join a team. From there, visit a teams page and click "Join Team", then wait to be accepted by the Team Captain. To create your own team, read 3.2 Team Captain Registration, below.

All players must make their Steam profile public, in order to compete, as well as provide the link and your Discord tag in your Play! profile. All players are also required to join our Discord. If you wish to keep a private Steam profile, you may be allowed to return it to private, after an Admin has inspected it. Players looking for a team (LFT) or teams looking for players (LFP) should make use of our Discord.

3.2 Team Captain Registration

Team Captains must login, and then create a new team or register an existing one, in order for players to join. If you create a new team, be sure to register it for the event, for it to show in standings and allow your team members to join. When they apply, be sure to add them to your roster. The rosters will lock @ 11pm Friday 1st Feb '19 and only those players added to the team roster, will be eligible to play in weekly matches.


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

Members must play their official matches, with their registered Play! display name. 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 event. 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 Event Admin & 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 not all Pacific Gaming League staff are Insurgency Admins. If you aren't sure who to speak to, mention @staff in the #support channel of our Discord.

The Admins for this event are;

  • Dr. Ace Misanthrope (PacificGL Staff)
  • Solusvod (PacificGL Staff)
  • Svenare (PacificGL Staff)
  • Piggymonster (PacificGL Staff)
  • Rad (Event Staff)


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 an event Admin, ASAP. For more information, see 2.3 Knockout Info.

Team Captains MUST be online on Discord, for the duration of ALL official matches. Players may utilise the Discord at their own discretion, however all must be a member of the official Discord for the purpose of easy contact. 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 event Admins.

Upon the completion of each game, screenshots must be taken before any player disconnects, and then the Captains report their scores. For more information, see 6.6 Match Results.

5.2 Team Names

Team name changes are allowed within 48 hours of the registrations locking, however other Team Captains and Admins are to be informed. The name is to be changed in all places it is mentioned. Team names may be similar but must be distinguishable from eachother, 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 multiple teams with different rosters, they are treated as independent teams and players cannot be freely swapped between them.

The roster may consist of up to 8 players (Lineup: 5 | Subs: 3). Unless permission is given by event Admins, no roster changes are allowed after registrations lock. Only the 5-8 members in your roster at the beginning, are allowed to play in any official matches.

5.4 Team Captain Changes

Changes to the designated 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 Admin, 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 < 4 players available MUST forfeit
  2. Use a "ringer"
    • May only 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, unless Season Admin permission is given, and the opposing captain, consulted.
  3. Play Short
    • Play 1 player down
    • Teams with < 4 players available MUST forfeit


6. Matches

6.1 Game settings

ALL official matches MUST be played on the servers listed below;

  • [ANZ] #3 MATCH | PES  -  connect; password pacific

For details on configurations, see 1. Config and 2. Game Format.

6.2 Maps

The Official maps for Qualifiers are;

  • Scenario_Crossing_Firefight_West
  • Scenario_Farmhouse_Firefight_East
  • Scenario_Farmhouse_Firefight_West
  • Scenario_Summit_Firefight_East
  • Scenario_Summit_Firefight_West
  • Scenario_Refinery_Firefight_West
  • Scenario_Precinct_Firefight_East
  • Scenario_Precinct_Firefight_West
  • Scenario_Hideout_Firefight_East
  • Scenario_Hideout_Firefight_West

Each week a specific map will be set, which must be played for all games. Week #1 could be Precinct East, Week #2 could be Hideout West, etc. The weekly map will be set with the release of matchups for the season, so players will have time to practice these maps and avoid surprises.

In the case of Finals, which will be a Best of 3 (BO3), the same process will be used, until 3 maps remain. The order of which they are played will be determined by the Season Admins.

6.3 Picking sides

A pistol 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 pistols and pistol attachments, are to be used. Doing so will result in the team forfeiting the pistol round and the opposing team choosing the side. If BOTH Team Captains agree, '-coin' toss can be used in Discord to decide who picks sides, forgoing the pistol round.

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 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 Staff & Captain's jobs harder. Please be considerate.

Immediately after completion of the match, one of the Team Captains is required to post in the #oc-season-captains channel of Discord using the following format;

  • HomeTeam vs AwayTeam < HomeScore - AwayScore > Map - DD/MM hh:mm timezone - Comments
    • Eg. Team A vs Team B <11:10> Precinct East - 05/02 18:30 AEDT - 4:2 with 2 OTs

It is up to the Team Captains to decide who will post the scores. All scores will be updated by event Admins to be displayed on the event standings page and throughout 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 event 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. FOUR substitutions may be performed per game. A substitution is counted for ANY reason one player leaves and another joins. This includes disconnects, crashes, etc., 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 3 minute increments. 3 minutes is the maximum pause allowed between rounds. A pause should be called either during the previous round in text, in 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. Before doing so, they MUST type "live on restart" or "lor" for the other team.

If a team goes over the allocated pause time (10 minutes total, not just over the 3 minutes of a round), the game will be live on restart, regardless of whether the paused team is ready or not. If the pausing team refuses to continue play without their member, then that team concedes 1 round and another 3 minute pause timer, begins. If this occurs twice, that team forfeits 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. Miscellaneous Rules

7.1 Spectating

Spectating matches in-game is not permitted unless it is for official business (ie. 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, providing there is no conflict of interest. If any team member has an issue and intends to complain, it is the responsibility of the Team Captain, to do so. Refer to 5.1 Captains.

7.2 Connection Issues

If players cannot connect to the Official Match Servers, contact a Server Admin ASAP. If both teams agree to delay their game, they may do so. 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 players with 150ms ping or less, when connected to a Sydney, Australia server (excluding hackers/cheaters and those with a perpetual ban from PGL events).

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 config)

7.4 Cheating/Hacking

To be eligible to compete in this event, 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 event. All players must also provide their Discord tag (Example#1010) in their Play! profile.

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.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, ie. 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 also forbidden. An exception is where players must kill themselves to avoid a bug or other similar, justifiable uses.

8.7 Demos


8.8 Streaming, Recording & Casting

No player may stream a match (this includes private streams). If a player streams the match, the opposing team may dispute the match results and a decision for punishment will be determined by event 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 event 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.1 VAC Ban Policy

The PGL prohibits players with any VAC bans from competing in PGL seasons, tournaments and events. 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 event.

* 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.