Rules Submenu     Select a section of the rules you wish to go to.       Please read these rules carefully before you play on BF 2142. 1.4 Units 1.1 Game Rules1.2 Post Match1.3 Penalities    1.4 Units Unit Specifications Each unit in BF2142 must have at least 1 valid leader and 2 valid players for a total of 3 valid/active players and not more then 32 active players per unit. All unit members must have a valid email address and a valid callsign. Player that is locked is not included in active unit head count. If unit falls under 3 active members for more then 2 weeks the unit will be then deleted.    1.1 Game Rules Callsigns Callsigns if possible should match at all times. If you can not match exactly what your callsign is please make a callsign very similar to the one you have. Example your callsign is Liquidice you should have something like liquidice007 or something similar to your main callsign. E-mail addresses should always be up to date. Please do everything you can to make the Admins job easier. If at anytime you need help with your callsign, or having Unit problems please contact one of our admins. Music on BF 2142 Unit Page Under no circumstances shall music play when entering a BF 2142 unit's page, and no drastic changes to html as this will slow down the BF 2142 site and we do not want that so please keep it simple. If repeated incidence occurs the unit in question will dealt with by any game admin. Your unit maybe fined points and or be removed from the league. Unit Limit All units will be limited to 32 players per unit, there are and will be no exceptions to this rule. Pre-Match When looking for a match we encourage everyone to use the BF2142 league forums or e-mailing a unit leader. If challenged, you do have a choice to whether or not you wish to accept. Once a challenge has been accepted, and once the size of the match has been agreed upon by both teams, you can decide what match type to play (see details below (Match Types)). The team who was challenged will have to decide on where to play the match. If the connection is unsatisfactory, then both unit s will need to decide on a new server to play the match. all games are a standard of maps Match Types Unit Battles (5v5 min max 32v32) If more than one member in your unit is going to participate in a match, this is known as a Unit Battle. Both units must have the same amount of players. I.e. If unit A has 3 players wanting to play in a match, then unit B must find 3 players from their own unit to participate. However, if a unit wanted to play under-manned (less players), then this is acceptable. Match Categories TITAN MODE Titan mode challenges gamers to destroy the opposing army's Titan - a massive, heavily armored, flying warship - while defending their own. To defeat a Titan, gamers must first take down its shields, board the craft and fight to its inner core before detonating it from the inside. CONQUEST MODEHGO (Hand Guns Only) Armies from both sides must capture and hold specific spawn points on the map. Doing so will reduce the tickets on the opposing team. Killing enemies will also reduce their tickets. The game is won when the enemy's tickets are reduced to zero. Match Start Lag Test Before a match can begin; a lag test must take place. A lag test is mandatory, to ensure that the lag is to a satisfactory level. The lag test may take place on any map, which agreed upon by both teams. Shooting glass and opening doors can determine how good the level of lag is, the longer it takes the glass to break or door to open the higher the latency level is. It is also recommended that you repeat a lag test at least once, as the first load of a server can cause latency. A player can ask for as many lag tests as he/she wants. This is to ensure that every player is satisfied with their amount of lag. Once everyone is happy the match may begin. If you are re-connecting mid game and if you prefer not to wait for another lag test, you may call a load-abort, wherein the host will launch a game then immediately abort. ABORT must be called in order to take effect. Maps After a lag test has been successfully completed, the match can start. The team or unit that is not hosting may have the first choice of map (If the match consists of a neutral host, the team that was challenged will choose the first map). Any map can be played. Map Format All match categories and match types will be played in 3/5 format. This means that it is "best of 5", the first team or unit to win three (3) rounds on one map wins that map and the first team or unit to win 3 maps wins the match. Teams After a map has been chosen, teams must be assign to each unit. The team or unit, who did not pick the map, may choose which color they wish to have (either Blue or Gold). No exceptions may apply. Uniforms Uniforms is the last option that has to be assigned. The team or unit that picked the map may decide which uniform they want for that map first. All uniforms apply to BF2142 matches. Time Limit Depending on what match category is being played, the time limit must be set to correct amount. During a Match Crashes/Drops (Players) If a player drops whilst the game is in progress, and at least 1 minute has gone, the team who lost the player will have to continue under-manned. If a player drops within one (1) minute of when the game started, the team who lost the player have the opportunity to call for an abort (using the global chat), making sure that the host can see it (It is the hosts job to make sure the game gets aborted) or they may wish to continue under-manned. If, however, a player has been killed, on either team, the game must continue, no exception. If a player disconnects whilst the game is loading, the host must abort straight away if the dropped player's team call for an abort. The dropped player then has five (5) minutes to return. If a player drops during the weapon selection screen, the host must abort the countdown, if necessary, and players may sit and chat amongst each other while the dropped player returns. The disconnected player has approximately 5 minutes in which to return. If, after 5 minutes, the disconnected player has not returned, a substitute may be found. Further details about substitutes can be found below. If a player drops three (3) times whilst the game is in progress, he/she must be substituted, if no substitute can be found, the team or unit must continue under-manned. Crashes/Drops (Host) If the host disconnects whilst the game is in progress for the first time, the game must be continued with the same host. The match must be continued from when the host crashes, using the correct map, time limit, format and insertions points and the host must tk him/herself. If the host crashes three (3) times, the non-hosting team or unit may have the opportunity to host. If the non-hosting unit can not produce a host, a neutral host may be brought it (The team or unit has approximately 5 mines to find a neutral host). If a neutral host can not be found, the original host must be used, despite whether he/she crashes a lot. Substitutes Substitutes must be from the same unit. A maximum of two (2) substitutes may be used in any one match (except for single's match's, where no substitutes can be used). The substitute may inherit the amount of kills the disconnected player had, if he/she wishes. Screenshots BF2142 recommends that player's take screenshots at important events, such as results screens, suspicions of glitching/cheating or of profane or foul language. This is hard evidence and will help in any investigations BF2142 may have to carry out. Please take a screenshot of the final results screen. If a player does not confirm a match, this screenshot is proof that the match existed and was completed. Screenshot of final score must be saved for 3 days. Please make sure you take a screenshot after each match.    1.2 Post Match Post-Match Reporting/Confirming The winner of the match must report the match by filling in the correct details on the BF 2142 site. The loser then has to confirm the match. It is recommended that the winner informs the confirmed of the battle number to avoid any confusion. The losing player or unit has one (1) hour to confirm the match. If after an hour the match has not been confirmed, the winning player or unit may approach an administrator with evidence of the match. BF 2142 will not tolerate unconfirmed matches. The winning player or unit will then have the option to enforce a penalty to the losing player or unit. If a player fills out the report form incorrectly, but is unaware of it, the losing player or unit should inform the reporter of his/her mistakes, then it may be re-reported. All battles must be reported right as soon as they have ended. Waiting to report a match and just play a rematch and maybe more, then report them all. Could give admins the impression that something is fishy. Battles reported in a row can be voided by admins without evidence that the game took place. Therefore matches then report then continue matching Reporting a Forfeit A forfeit is a game that never ended. If you play a 1v1 and the other player disconnect, and is not back in 10 mins. A forfeit is reported. Forfeits are reported as if all players were actually in the game but losing teams kills are set to zero and the winning team reports their kills as normal. in a forfeit you must have a ss and report this to a BF 2142 admin if a admin is not on E-Mail all ss's and tell the Admin why this was a forfeit. Reporting Substitutes The player who has substituted, has the choice whether he/she wishes to be included in the final match report, whether win or loss. If the substitute chooses to be excluded from the final report, the dropped player must be reported with all the kills that he/she got, plus all the kills that the substitute got, if any. BF 2142 recommends that the substitute should be informed of the match situation before he/she participates. Sportsmanship And General Behavior And Profanity BF 2142 enforces fair play for everyone and wouldn't want anyone to suffer from unacceptable behavior from other BF 2142 members. Any forms of profanity, bad language or racism or Any accusations made towards any BF 2142 member, without hard evidence, will not be tolerated. Anyone found doing this with in BF 2142 matches, on the BF 2142 site or forums or any gaming platform BF 2142 matches are played on will be dealt with severely. As part of our fair play scheme, players should acknowledge fair play and always abide by the rules. Everyone has more fun when players are good sportsman. Complaining and whining is a sign of bad sportsmanship and just creates a negative atmosphere, which is what we do not want on the BF 2142 network. See Profane Language for Penalties. Breaching of Rules Glitching Glitching is a form of cheating, it is a way to gain an unfair advantage and BF 2142 will not tolerate it. Anyone found glitching will be punished accordingly. If, however, a player glitches due to misfortune, i.e. warped or fell into a glitch, it is up to the other player's in the match to recognize this and redo that game. False Reporting Reporting battles that didn't take place is another form of cheating. If found reporting false battles, a punishment will be forced upon. Adding extra kills whilst in game or in the report is classified as false reporting and the same punishment will apply. Multiple Callsigns As a BF 2142 member you are entitled to one (1) and only one callsign. We understand that you may have other members in the household that play as well, but these members must be on same unit. Failure to comply with the above will result in all callsigns involved being locked. Imitation of BF 2142 Members Imitating another member of BF 2142 or a BF 2142 admin is an offense and a punishment will be enforced if a player is found doing so. Confirmation of Battles If after an hour of when the match was reported, the match still isn't confirmed, an admin may be approached and a punishment will be applied by choice. If you have a comment or a suggestion about these rules, please send an e-mail to us with your feedback. Thank you for participating in Battlefield 2142 League!    1.3 Penalities 1. Accusations of Cheating Any accusation of cheating on a member of BF 2142 without proof of cheating will be enforced with a 48 hour lock, and will be fined 1000 personal points. Multiple offenses will have increase the period of the lock and fine, and could result in a permanent lock. This is based on the discretion of a BF 2142: CO Lead Admin. 2. Glitching/Cheating Glitching and Cheating is frowned upon within BF 2142. If there is proof of either or in a BF 2142 match, the player's callsign/IP will be banned for life. If upon launch you insert into a glitch, it is your duty to ask for an abort. If you do not ask for the abort, and continue play, this will be considered cheating as well. 3. Owning 2 or more callsigns and reporting against them BF 2142 will only acknowledge the use of one callsign per player. If a player has multiple callsigns, and starts to report false battles against each of them, then both callsigns will be banned as will the IP of the callsigns. 4. Profane Language: We must all be aware that not everyone playing this game is old. Obsessive use of profane language/cussing after being asked to stop by any member in the room can lead to a 72 hour lock and a 2000 point fine to the player or players caught doing so, along with a 5000 point deduction to the unit the offender(s) belong to. To be released from the lock a written apology must be written to the clan you were competing against. All apologies must be posted on the BF 2142 public forum. http://www.wgleague.com/forums/ Screenshots must be provided from the clan with the complaint. The screenshots must include them asking the clan to watch their language, and screenshots of when the clan failed to do so. 5. Imitation Imitating administration from BF 2142 is not looked upon lightly. If you are caught doing so, a permanent lock can be enforced. 6. Admin Abuse: Administration abuse is something that all leagues must deal with. However, BF 2142 will not tolerate excessive abuse of its staff. All administrative abuse reports will be handled by the lead of that league. Screenshots of the abuse must be available for both the player and the lead. After fully reviewing the case, the lead will determine the duration of the penalty. 7. Confirming Battles: Battlefield 2142 Admins will use a progressive system towards punishment of non-confirmers. The system is as follows: " First non-confirmation violations will be warned via a written warning, by email or chat. " Second offenses are warned again; however this time a fine may be imposed. (Fines are determined by each individual league). " Third time offenders are dealt with strictly. A mandatory fine is imposed, as well as a lock with duration of no longer than 3 days, which may be imposed as well. " Fourth time offenders are mandatory locked fined. Locks will last the extent of 7 days. All lifetime locks will have the IP of the callsign banned as well. All additional penalties and fines defined on a per league basis.