O.2.O -|-
2 MEMBERS:
| Servers Rulez |
|
1) No abbusive behaviour towards members or opposing clans in any way. 2) No cheating anywhere, on own or others servers. 3) DMW must be operational on your computer. 4) You must be in possession of a working microphone. 5) TeamSpeak needs to be operational on your computer. 6) Activity in game and on msn is needed. Please take the time to read through our global rules before you start playing in this ladder. These rules not only apply to MoH:AA Deathmatch Realism but all ladders within O.2.O. Knowing the global ladder rules will avoid conflicts and will increase your chances of winning conflicts. Pay particular attention to our rules on freelancing, linking your accounts and the 24-hour rule, reporting a no-show and the match conflict rules. The General rules section covers the default punishment for breaking the rules, our right to broadcast matches, the complaints system and what counts as official match rules. The rating system is explained in detail, and provides information about the number one spot. A list of defined ladder terms can be found here. 2. Match rules A match is played over two maps, one picked by each team in the challenge form. On every map, both clans will play each side once, so a match will be 4 rounds in total. Rounds are played with a timelimit of 10, 15 or 20 minutes, depending on which option you selected in the challenge form. The total frags of both maps will decide who is the winner of the match. The match will begin with a massbash (all players involved), or a 1on1 bash. The winning team decides which map & side to start with. In rifle/sniper only ladders rifle/sniper must be used. Between maps a break of max 5 minutes can be taken. All matches played with an incorrect team size will be cancelled. 3. Optional rules Anti-cheat: the selected anti-cheat must be used and players must have the corresponding GUID added in CB (check GUID's chapter). None Demo-only (record with mohaa.exe) - default UAC3 + demo By default the shotgun and the rocketlauncher are not allowed. It is also allowed to have other weapon limitations. The challenger puts them into the challenge notes and they will be accepted by the opponent when he accepts the challenge. For example: 2 shotgun max 2 snipers max (This rule does not apply to the sniper and rifle only ladders) The use of anticheat not supported by ClanBase is allowed if it is put in the challenge notes. The challenger puts it into the challenge notes and it will be accepted by the opponent when he accepts the challenge. FriendlyFire is enabled by default (set g_teamdamage 1). It is possible to choose FriendlyFire to be disabled in the challenge options (set g_teamdamage 0). 4. Maplist The maplist for MoH:AA Deathmatch Realism is: Southern France Destroyed Village Remagen Crossroads Snowy Park Stalingrad Algiers 5. Client settings The "Force models" and "Smoothclients" commands are allowed. All the standard skins are allowed. Everyone should have the health bar and team sign shown when playing the game. This is set by a cvar, ui_hud 1 (standard setting). Not having this setting will result in a forfeit loss of the match and it will be considered as a trace of cheat. Nobody should have 'g_subtitle' cvar different than g_subtitle 0 (0 is the standard value). Having another value will result in a forfeit loss of the match and it will be considered as a trace of cheat. When the UAC3 option is chosen as anti-cheat, the UAC3 client has to be turned ON. Each player is responsible for making sure they are running it during the entire match and have to make sure they input the correct war-id before starting any match. In case a player entered an incorrect war id, then he must mention the correct war id in the match comments within 48 hours after the original match time. If he fails to do so, then his clan will loose by forfeit. Also, please pay special attention to the following lines: If a player logged out from UAC3 during a match, that player's clan will receive a forfeit loss of that match. If a player times out (or crashes) during a match and consequently logged out from UAC3, the score will stand, if he or a new player joins the server within 5 minutes (starting from the moment he logged out) with UAC3 enabled. If they fail to do so, they will lose by forfeit. If a new player joins the server, he must be allowed to play according to the 24 hours rule and his last change or registration of a UAC3 guid must have occured more than 24 hours before the official match time. If he does not meet these terms, then he is considered to be a freelancer and his clan will lose the match by forfeit. Screenshots must be uploaded after each match ( even if they are black). If a player or a clan fails to upload his or their screenshots within 48 hours after the official match time, the concerned clan will lose by forfeit. For the record, there is no required minimal amount of screenshots made by UAC3. It is allowed to play with the setting 'FPS 1', but only your FPS may be visible (as this mohaa.exe will do for you). Any player caught using the 'FPS 1' setting with the wt, wv and other numbers still showing, will cause his clan to forfeit the match. Modifying your soundfiles in your MoH:AA folder is only allowed if you remove or rename your plane and watersounds (including the cinematicmod and changing pak3 files from water and plain sounds from the extension .wav into .xxx) 6. Server settings All matches must be played on servers that have the ClanBase standard settings, custom/altered settings are not allowed. It is not allowed to change any server setting after the match has started, doing so will result in a forfeit loss. Match servers must have this mapfix installed. The CKR mod 1.1 has to be installed on the server. The Nadefix mod has to be installed on the server. Download the mod here!. set fraglimit 0 set g_inactivespectate 0 set g_allowjointime 2 set g_forcerespawn 10 7. Demos and screenshots All players must record demos from the whole match in 2 parts (or 3 in case 3 maps are played). This means that you have to record a new demo on each map. This is due to the fact that admins or players can't rewind or fast forward their demo's. The exception to this rule is any match played in the TDM mod, in which players need to have 4 parts, one for each side (axis/allies) on each map. Demos can be requested by the supervisors and must be kept until one week after the result has been accepted on ClanBase. If your demo is not divided in 2 (or 3 or 4 in the specific cases mentioned above) parts you will lose by forfeit! If a clan suspects their opponent of cheating, they may request in eye demos from the other clan, but the following is required or the request will be invalid: The clan must immediately state the exact demos they want; players and maps (example: Upload demos - Player X, The Hunt; Player Y, V2). The amount of in eye demos that can be requested are: 1on1: all, 2on2: all, 3on3: 2 per map, 4on4: 3 per map, 5on5: 4 per map, 6on6: 5 per map etc. 1 demo is a 1 complete map demo of one player. This request can only be made during the first 48 hours after the actual match time. A clan can only request demos once, other requests apart from the first one will be ignored. Requested demos must be uploaded to ClanBase by using the ClanBase Demo Upload tool. Demos that are uploaded on any other site will be disregarded and ignored by ClanBase admins. Failure to upload requested demos (correctly) or uploading demos that are broken or incomplete within 48 hours after the request has been made will lead into a forfeit loss. If a conflict is created because a player did not upload the demo within the first 48 hours after the request was made, then this player still has 72 hours (as of the moment the conflict was created) to upload the requested demo(s). Failure to do so will result in a forfeit loss. A demo is considered to be incomplete if it's missing 3 or more rounds. If a clan is manipulating the demo recording process (e.g. by stopping it in a live match on purpose), all the points gained in that period will be awarded to the opponent. If the opponent uploaded the requested demo(s), you should make a match conflict to have it investigated by the ClanBase MoH:AA DemoCrew. In such a case you must always provide a link to the concerned player's profile ([hl]2763111,example[/hl]), a link to the specific match in which you believe cheating occured (example) and the link to the demo you wish to have investigated (example. With this information, you also need to provide timestamps (example: V2 Axis - round 5 - 3:25: strange prefire when he kills player x). Clans who repeatedly fail to upload demos will be suspended from the ladder(s). Players who repeatedly fail to upload demos can be suspended from playing according to the C&A policy. Screenshots of the scoreboards should always be taken by each clan and kept until one week after the match result has been confirmed. Only screenshots can be accepted as proof when there is a dispute about the score. Screenshots can be requested by supervisors at any time. When the UAC3 option is chosen as anti-cheat, all screenshots made by UAC3 must be uploaded within 48 hours after each match. These screenshots can be used to check if the GUID is corresponding to the GUID entered on ClanBase. The rcon status screenshot must be taken in every match and sent to your opponent if requested. The request can only be made inside the server and can't be done later than 3 rounds before the end of a match. However ClanBase Admins reserve the right to ask for a rcon status after the end of a match. A clan may request new/extra status screenshot(s) when: The opposing clan makes changes to their original match line-up. Someone of the opponents clan leaves & joins again, even if it's the same player. These extra screenshots must be requested also inside the server. Failure to upload rcon status screenshot(s) will result in a forfeit loss. These screens will be used if foul play is suspected and can be used to trace IP's to countries. 8. Regional ladder rules In order to participate in a regional ladder a clan/player must reside in that region or in a region that includes it. For example: East Europe includes Hungary. Any clan or player not from a ladder's region will be removed from that ladder. Depending on the kind of violation, the clan/player might face suspensions from a forfeit loss to a 3-month suspension from all regional ladders for that game. All matches MUST be played on servers within that region. Once a match has started then the server's settings and region is accepted, so clans/players will not be punished if the match is played. When neither clan/player can provide a server from that region and they refuse to play, the match should be cancelled. If a clan/player does have a server from that region and the opponent doesn't, the match must be played on the server from that region. In this case, the opponent may not refuse the server with the correct region and if they do, then the clan/player (with the correct server) should report the match as a no-show in the ladder channel. During matches a certain number of players must be from the ladder's region. The values are as follows: In a 2v2 : both players must be from that region In a 3v3 : 2 players must be from that region In a 4v4 : 3 players must be from that region In a 5v5 & 6v6 : 4 players must be from that region In a 7v7 : 5 players must be from that region In a 8v8 : 6 players must be from that region In a 9v9 & 10v10 : 7 players must be from that region Anything above this must have a minimum of 8 players and must be a minimum of 70% of the team Violating this rule will result in a forfeit loss. In addition, you will be suspended for a period of time depending on the type of violation as stated in the ladder punishments table. If the players are faking nationalities, more harsh punishments may be used. It is a clan's responsibility to make sure its clan & player flags are correct for when clans are checked for regional status. IPs can be traced to a country by using IP trace tools such as 'Network Tools' and 'Geektools'. Any clan found guilty of abusing the regional ladder rules by faking nationality will be punished, depending on the violation, with a forfeit loss or more harsh measures. Players who continually rejoin ladders they were removed from despite warnings will have their responsible clans suspended. 9. GUID's GUID's are unique identifiers used in games to recognise players. Examples: SteamID, PB guid, CoD2 guid, UT2004 guid, ETpro guid, DMW client nr and Xbox Live Gamertag. Every player must register his 'UAC User ID' on the GUID page. Click here to find out how to retrieve and register your 'UAC User ID'. Please note that missing the corresponding GUID will lead into a forfeit loss which is considered as freelancing. The last change of a GUID can not be done later than 24 hours before a match. Players who did not register the correct GUID more than 24 hours before a match will be considered freelancers. Only the last entered GUID (the one you can see on your account's page) in the changelog will be considered as valid to play with. 10. Miscellaneous rules At least half the line-up used in every match (not 1on1) should be different from those used by any other clan in the same ladder. This does not apply to 2on2 ladders (unless it happens too regularly - both clans use the same line-up in 4 or more occasions) or matches older than 14 days. The following list shows what is not allowed, based on the line-up of two matches, one for each clan: - 3on3 ladder: two players are the same - 4on4 ladder: three players are the same - 5on5 ladder: three players are the same - 6on6 ladder: four players are the same - 7on7 ladder: four players are the same - And so on Violating clans will receive a forfeit loss for all of the matches in which they are violating the shared line-up rule. Two or more violations of this rule will also result in suspensions. Spectating during an official match is not allowed. If a player leaves the server for any kind of reason and joins again he needs to choose sides immediately. Substitutions can only be made at half time. The only exception to this rule is when a player is having severe connection problems, and is unable to continue playing. Lag is not an example of this. In these cases you can change to a new player after the next round has started without pause. Play will only stop if both clans agree, or if the end of a quarter is reached. Teams officially have 2 minutes between team changing (unless granted more by the other team) and an official 5 minute break between map changing It is NOT allowed to kick any player during play. The ONLY exception to this is when a player has timed out, and is waiting to re-enter the server. Permission must first be obtained from the opposing team, and wait for the opposing team to ask for a player to be kicked if it is one of their players. 11. Cheating and abuse The cheating and abuse policy applies to all ClanBase ladders. Any cheating or excessive abusive behaviour during a match will result in a forfeit loss. Cheating and/or using suspended players in matches results also in different kind of ladder suspensions. If both clans cheated and/or used a suspended player in the match, both clans get a forfeit loss. Ladders are moderated by four methods: join applications, score changes, suspensions and deletions: Join applications are dealt with by the ladder/mod supervisors to stop fake clans, members with fake GUIDs and countries from the wrong region from entering the ladder. Matches may be edited to a cancellation, no-show, forfeit loss or a win for the opponent - depending on the ladder rules and severity of the problem. A forfeit loss is the standard punishment for all violations unless the punishment is otherwise stated in the rules. Suspensions are used to punish abuse of the ladder system and range from short-term to long-term/permanent suspensions, from one ladder only to all ladders. Suspensions are added by the ladder chiefs and assistants. Punishments are summarised in a table, found here. Clans that are suspended from a ladder may not form the same clan elsewhere to play that ladder, this includes new clans or altered existing clans. The guidelines for determining if a clan with an active suspension has rejoined with a new clan will not be given out so don't ask for them. If a clan is suspended from a ladder the suspension can be viewed by using the clan's matches page. Appeals to the suspension reporter will only be acknowledged if the accusation against the clan can be proven false. Provide all necessary proof immediately on the war summary page. Members may only contact the ladder assistants/chiefs if the reporter is not mentioned. Clans or accounts may be deleted without warning as described in the ladder punishments table. It is strictly forbidden to use accounts of other users, even if the users are in your clan. Such cases will always be considered abuse and subject to temporary bans. This does not apply to players who are forced to share GUID's. It is not allowed to take advantage of or abuse bugs. Any kind of bug abuse is considered cheating and will lead to a forfeit loss, unless otherwise mentioned specifically in the game-related rules. Examples of above rule are: grenades through closed doors and 16 bit that causes shadows/complete characters to show through a wall. All programs or files, either changed game files or new files, that change the game or add to its functionality, or which interact with the game in any way, are strictly forbidden unless other rules specify otherwise. Modified versions of the game's resource files are always forbidden, regardless of what they do. The use of any forbidden program or file by any clan member during a match, leads to a forfeit loss, and could lead to a removal and ban from ClanBase in major cases. The only exceptions to the rule above are clientside applications for anti-cheat, the mohaa.exe record no-CD crack and all the ClanBase approved custom maps plus its accompanied maps folder. ClanBase approved maps are maps which are allowed on ClanBase ladders/cups. Programs that do not interact with the game in any way are allowed, even if they can be used and operated simultaneously with the game. Voice communication programs are examples of such programs. Any place on the map that you can reach by yourself, without altering server settings, is allowed. It is also allowed to stack players on top of each other to look and shoot over buildings and walls. However, it is not allowed to: Jump on rooftops or walls with help of other players, when you could not have reached that place on your own. Go out of the map. Abuse any map bugs. It is allowed to block doors and to bash through doors. Clans abusing the ladder system in any way in order to gain an advantage or just to be a nuisance will be deleted or suspended from ladder(s). Further punishment may include deletion of the accounts of the person responsible for the abuse, in extreme circumstances. Abusing any clear loopholes in the rules is forbidden, Chiefs of Ladders can punish clans/players for abuse not described in these rules.
Posted by michaeljacksongr
0 Comments
Aug 07, 2013 11:43 AM
|
GAME SERVERS
| There are no servers assigned to this clan. |
CALENDAR
| November | December 2025 | January |
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |
GAME RANKING
World Rank
6731st out of 142104
| Game | Rank |
Medal of Honor Allied Assault
|
12 |
Call of Duty 2
|
24 |
Counter Strike 1.6
|
184 |
|
GAMETRACKER
Servers Teams Profiles Games |
QUICK LINKS
Members Area Search Report a Bug Forums |
SPONSORS
Cheap Ventrilo Hosting Rent Game Servers |
LEGAL
Terms of Service | Privacy Policy Use Policy | Anti-spam Policy Cookie Policy | GDPR Privacy Notice |
|
© Copyright GameTracker.com - Game Server Stats, Online Server List, Multiplayer Server Rank, FPS Server Banners.
|
||||