Last Updated Tuesday, September 13, 2011 6:56 am
This rule applies to ladder matches only.
In order to cancel a match, both opponents must post their acceptance of the cancellation in matchcoms. This will result in the complete removal of a match; no win, loss, or forfeit is recorded.
A match can not be canceled once it has begun or after a no-show report has been submitted.
League and Tournament matches can not be cancelled.
(See ?Change Agreements")
Last Updated Saturday, September 10, 2011 4:19 am
To allow for flexibility, certain rules can be changed so long as both opponents agree to the change prior to the match.
Any such rule change applies equally to both opponents throughout the entire match.
All change agreements must be recorded in matchcoms prior to the match for the purposes of resolving potential disputes that may arise from any such agreement.
The list below shows these rules by type of competition.
Leagues and Tournaments
Last Updated Friday, January 30, 2009 7:24 pm
Any attempt to gain an unfair advantage is cheating. This includes: modifying game files, running memory resident cheats, utilizing exploits/glitches, or anything else beyond the normal scope of the game.
Anyone caught cheating in a GWL match may be suspended or banned from all competition.
Contact an admin if you have any doubts, questions, or concerns about something that could possibly be considered a bug, exploit, or cheat.
It is your responsibility to ensure that your computer system is free from cheats prior to playing any online game.
We do not conduct investigations into alleged cheating violations unless credible evidence is presented.
Last Updated Friday, January 30, 2009 5:40 am
Sportsmanship
All players competing on this site are required to conduct themselves with the highest standards of sportsmanship. Members are encouraged to work together and attempt to settle disagreements without admin intervention.
Fair play
Winning is without true value if it was achieved unfairly or dishonestly. Cheating is easy, but it will bring you no pleasure. Playing fair requires personal courage and strong character. Fair play is rewarding even when the match is lost. It earns you respect, while cheating and cheaters are detested by all.
Last Updated Friday, January 30, 2009 10:45 pm
All match coordination must be recorded in the match communications (matchcoms). Matchcoms are available once a challenge has been initiated. Matchcoms should include, but are not limited to:
Last Updated Friday, January 30, 2009 5:51 am
Disputes must be filed no later than 12 hours after the match is completed. (Intent to file a dispute must be posted in matchcoms no later than 1 hour after the match.) Disputes must be filed before the match is reported; once the match has been reported, the result will not be changed. Players must use matchcoms to file a dispute. Do not post any match disputes publicly. A dispute should contain as much information as possible and should include any supporting evidence. Accusations without evidence will be thrown out. Investigations may take up to 96 hours to complete. All Globalwarfighter decisions are final.
Report Format
Last Updated Saturday, September 10, 2011 4:14 am
Leagues
All matches must be completed prior to finals.
Tournaments
Not applicable
Ladders
Players or teams who are inactive on a ladder for more than a month will be removed from that competition. If you plan to be gone for longer than a month, you should withdraw from all ladder competition.
Last Updated Friday, January 30, 2009 5:52 am
Loss Reports
Loss reports must be submitted by the losing party no later than 1 hour after the match has been completed.
In the event of a dispute, the disputing party must file their intent before the 1 hour deadline. (See Disputes)
If the losing team/player does not report within the 1 hour deadline, an admin will report the loss. An admin reported loss is considered a penalty; the losing party will not be awarded skill points and will be given a 48 hour lock from challenging.
Forfeits
Teams/players must forfeit if they cannot meet all match requirements prior to the match. Team/players can not forfeit once a match has started.
An Automatic Forfeit occurs when the defender fails to respond to (accept) a challenge prior to the ladder Response Time setting.
No-Shows
A no-show occurs when an opponent fails to meet at the agreed upon link up point within 10 minutes of the scheduled match time. A no-show must be reported in matchcoms no later than 30 minutes after the initial match time, but no earlier than 10 minutes after.
Once a no-show report has been submitted, the accused will have 20 minutes to counter with a reply in matchcoms. If the accused fails to counter within this time limit, the match will be marked as a no-show and an admin will report the loss.
(See "Ladder Rules / Match Description - Scoring and Reporting Format")
Last Updated Saturday, February 11, 2012 10:59 pm
Shoutcasting
We reserve the right to record and/or broadcast any match or event hosted by Global Warfighter.
Spectating
Spectating by players is not allowed for GWL matches (excepting for the purpose of shoutcasting in matches as reserved above).
Last Updated Wednesday, December 14, 2011 1:55 am
Team Member Listing (Open Roster)
The team member listing, also know has the open roster, is used to view all of the members of a team. When a player joins a team, he or she is automatically added to this listing. Players may join as many open rosters as they like, but they are not allowed to be on more than one competition roster for the same competition.
Competition Rosters
Each competition a team joins will have an individual roster. These rosters are called competition rosters. Members who are on a competition roster are considered the primary competitors for that competition, and will receive skill points whenever their team competes in that competition. The number of members who can join a competition roster is determined by the size of the competition. Normally, the minimum would be one less, and the maximum one half larger than (or 1.5) the competition size rounded up. (Example: 5v5 has a Minimum of 4 [1 less] and a Maximum of 8 [2.5 rounded up to 3])
(See "Eligibility")
Location
The default location for this array is World.
System Required
The required system type for this array is PC.
Skill
There are no skill points required to join this array.
Response Time
Defenders must respond to a challenge within 36 hours or receive an automatic forfeit.
Auto Drop
Teams with 3 consecutive forfeits will be automatically removed from this ladder.
Map Selection
The map will be randomly generated.
Authorized Team Sizes
Teams must have 2 members
to be considerd eligible for a match on this ladder. Responding to challenges before meeting the team minimum requirement
will result in forfeit. Teams may have no more than 6 members on this ladder.
GUID Required
Players are required to have a valid Name GUID on record.
Staff
Last Updated Wednesday, October 27, 2010 7:56 am
Matches will be played on the latest official release of Star Wars Battlefront 2.
Currently: SWBF2 Ver 1.10
Any modification made to the game client will not be allowed. This includes any change of player skins or 3rd party software that changes the game client in any way or 3rd party software that runs in conjunction with SWBF2 to give a player an advantage in gameplay.
Running Game Profilers (IE: Pinnacle Game Profiler) for controller configurations that allow repeatable button programming and mapped button configurations are not allowed for competition. Controllers are programmable through the SWBF2 game without 3rd party software and will operate in the SWBF2 game with the appropriate drivers installed for the controller.
Any team caught violating this rule will lose their match and will be subject to further disciplinary actions. The game is to be played as is from the original installation and updated in accordance with official patch releases.
You are NOT allowed to use a NO-CD crack as this will conflict with MD5-checksums if you have the 1.0 version of the game on disk. If you have the 1.1 version on disk or DVD, the game will run without the CD in the drive via the Xfire Launch or a launch shortcut created on your desktop.
Last Updated Friday, July 10, 2009 11:48 pm
Players should test their connectivity during the initial setup round. GWL is not responsible for players who experience hardware, software, or connectivity problems with the game. Due to the nature of computers and the internet, it is possible for players to be disconnected from their provider or dropped from a server. Should this happen, the dropped player may rejoin the server. Upon joining the server, the player must rejoin their team?s side immediately. If the player who dropped is unable to rejoin the server, you may immediately substitute in an eligible player to fill the spot.
Server Crashes
If the server crashes before the end of a round has been reached, the round will be replayed from the start. In the event of a third server crash, an alternate server should be used to complete the match. If an alternate server can not be found within 10 minutes, the game may be rescheduled or canceled. Both teams must report and agree in matchcoms on their intent to reschedule or cancel the match. If rounds were completed prior to the crash, the rescheduled match will allow for the remaining rounds to be played. Completed round results must be posted in matchcoms.
Last Updated Saturday, July 11, 2009 5:51 pm
In order to be eligible for any GWL SWBF2 competition match, a player must have a valid SWBF2 "NAME GUID" on file at GWL. "Valid"... meaning "current". This is the name you will appear as on the battlefield (clan tag included if there is one) in any GWL SWBF2 competition match. This is done in an effort to identify a player online when compared to a known CD hash for that player. If you change your name you play under in a GWL SWBF2 match.. your SWBF2 Name GUID at GWL must match. Multiple accounts (smurfing) is not allowed and is grounds for a permanent ban. (see GWL Site Rules "Accounts")
Multiple SWBF2 players from the same IP address must be verified by GWL SWBF2 Staff.
Last Updated Saturday, July 11, 2009 12:07 am
All players that are playing in the match must be in the match server by at least 10 minutes after the scheduled match time or play men down... OR receive a "no show" loss for singles matches. A score of 0-0 is reported with the opponent that showed for the match receiving a "win" and will take ladder position of the "no show" opponent... or remain in defending position on the ladder with an additional "win" stat.
All match coordination MUST take place in Matchcoms via a player's/Team's Profile page. Xfire or some other communication like TeamSpeak is fine for coordinating a match, provided that the conversation is confirmed in matchcoms (IE:"We agreed over Xfire to do the match Tuesday 6:00 PM EST"). In the event of a dispute, the posted matchcoms are what the admins rely upon for match coordination so update them accordingly.
Last Updated Saturday, July 11, 2009 6:27 pm
Disputes must be filed before the match loss is reported; once the match has been reported, the result will not be changed. Players must use matchcoms to file a dispute. Do not post any match disputes publicly. A dispute should contain as much information as possible and should include any supporting evidence. Accusations without evidence will be thrown out. Investigations may take up to 96 hours to complete. All Global Warfighter decisions are final.
This rule is to be followed by ALL players in the community. If a GWL admin is playing in a match.. the admin is a player like everyone else and subject to the same rules as the other players regarding the match.
Players/teams are required to have evidence for a dispute. Take screenshots... have your Xfire "Chat log enabled", and Video Demo your matches with Fraps or Xfire. Server chat logs or CSV stats files from the servers are also helpful evidence. (See GWL "Disputes")
Last Updated Saturday, July 11, 2009 12:22 am
A screenshot is captured view of what you currently see on your monitor.
Screenshots are to be taken of, but not limited to the following:
Last Updated Monday, July 5, 2010 10:04 pm
The following are moves banned in GWL SWBF2 competition:
Det Glitching
Det glitch throwing speed presents an issue of a player using an exploit/glitch within the game to gain an advantage.
Det throwing is not Det glitching. Normal det tosses are perfectly acceptable in competition. It is the det glitch throw that presents a speed you can't react to.. and presents a distance you can never throw with a normal toss.
Infinite Stamina
Utilizing any move in competition matches that provides for infinite stamina is considered a glitch and is not allowed in GWL matches. Including: Infinite Sprint, Infinite Choke, Infinite Block, and Infinite Bothan.
Last Updated Wednesday, October 27, 2010 7:59 am
All players are required to run the GWL Launcher for SWBF2 matches. This is non-negotiable.
The launcher is available for download HERE. The GWL SWBF2 Launcher verifies that your originally installed SWBF2 files haven't been modified.
A "Fail" result from the GWL SWBF2 launcher will result in a loss for that player (in a singles match) or that player's team (in a team match). If a player does not run the GWL SWBF2 Launcher for their match it will equal a "Fail" result.
SWBF2 Game Version Verification results from recent matches can be viewed HERE.
Last Updated Saturday, July 11, 2009 6:30 pm
Separate mod or expansion map packs may of course be installed, provided they do nothing when playing the original game itself and don't change originally installed SWBF2 game files when installed. Map Packs that don't change originally installed Star Wars Battlefront 2 game files are usually just a 3 letter folder that is deposited in the Star Wars Battlefront 2 Addon folder.
Use of certain Mod Maps for SWBF2 has been approved for competition at GWL and are currently available in the GWL SWBF2 Resource section HERE. Mod maps have been added to certain ladders and may be selected by the GWL Random Map Generator.
Approved GWL Star Wars Battlefront 2 Mod Map Packs:
Last Updated Friday, July 10, 2009 6:40 am
Two teams of 3 each compete against each other in the conquest mode of SWBF2 using the Sniper unit exclusively.
Last Updated Friday, July 10, 2009 6:32 am
One map will be randomly generated by the GWL random map generator for all challenges on this ladder. Maps from the +123 Mod v2.2 have been added in for selection. (see SWBF2 "Use of Mod Maps")
Last Updated Friday, July 10, 2009 6:33 am
This match is played as a standard conquest match would be played, (capturing command posts for a win/defeat of a map).
The DEFENDING team will choose which faction they will play as for the first round. The one map will be played a minimum of two times. Each team will play both factions once. If one team wins both maps then that team is the winner of the match. If each team wins one map then the same map will be played a 3rd time. (see Tie Breaker Rules)
Last Updated Saturday, July 11, 2009 1:18 am
When submitting a loss, the defeated team will enter the score as total rounds won for both teams in the match, including tie breaker round if played (IE: 2-0 or 2-1).
Last Updated Saturday, July 11, 2009 1:00 am
Each team shall assign one player to act as a team Captain for the match. This is the only person allowed to coordinate the match (talk) through in game global chat. Teams are asked to keep the match organized and professional. Once both Captains have announced their team's readiness, the match may begin.
Only the sniper unit can be used in competition for this ladder. Use of any other unit will result in a loss for the match.
Each team will field a team of 3. If they are not able to field a team of 3 by 5 minutes after the scheduled match time, then they must play the match with fewer people or take a loss for the scheduled match.
Last Updated Friday, July 10, 2009 6:33 am
In the event that each team wins one round of the two required, then the same map will be played a third time to decide the winner. The team that won the most tickets will choose what faction they will play as for the final round. In the event of a tie of tickets won from the previous 2 rounds, the DEFENDING team will then choose what faction they play as for the final round.
Last Updated Friday, July 10, 2009 6:33 am
NO VEHICLES! Vehicles are not permitted for use of any kind in this ladder. Using them to shuttle quickly across the battlefield, moving from the original spawn position or using them to kill the enemy is NOT ALLOWED. Vehicles will be left untouched in their original spawn placement. If you are caught using a vehicle in any way during a match you will receive a loss.
Last Updated Monday, November 23, 2009 3:00 am
Match server is defender's choice. The defender's choice must be a "GWL Approved" SWBF2 server.
GWL Approved SWBF2 servers listed HERE
If the defender does not have a GWL approved server then he can request a GWL game server in matchcoms and then hitting the "Admin Request" button. (24 hour notice required). Players may come to an agreement to play on another SWBF2 server that is not GWL approved (but not recommended). This agreement should be supported in matchcoms or xfire chat log.
After each map a buffer (stock) map must be present. This buffer map is to be a different map than the map being played. The purpose of this is to allow teams to substitute players in/out. The buffer map should last no longer than 5 minutes.
If playing against a team in another region or if two teams have a ping difference of more than 100. It's recommended to use the the "in game" admin command /waitlate. This command will force the server to even out the lag between both teams by waiting for network late moves from players (lag). If teams decide the lag was more tolerable without the command, they can use the "in game" admin command /nowaitlate to return the server to game default "wait" settings.
If this doesn't help the network connection, then a 100 ping difference between team averages is grounds to find another server.
Autoaim is not allowed, AI set to elite will eliminate autoaim. (/noaim in the command line for the server configuration)
Server must be set to a host simulation rate of 30 (/tps 30 in the command line for the server configuration)
TICKET COUNT: 97 (If using BBO Remote Manager, Con Reinforcements should be set to 65 to give you the correct ticket count of 97)
MIN/MAX PLAYERS TO START: 6 MIN, 8 MAX
TEAM DAMAGE: ON
AI (bots): NONE AND AI set to ELITE
HEROES: OFF
TIMER: OFF
AWARDS: OFF
PLAYER NAMES: On
SPAWN INVINCIBILITY: 0 SEC