Make your own free website on Tripod.com

dfo.gif

Socom 3 rules

Home
Members
SOCOM 3 Tournaments
Socom 3 rules
Page Title
Page Title

Clan Ladder Rules
Last Updated April 25, 2006

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
General

1.

It is the responsibility of all users of this ladder to know and understand the rules before accepting a challenge or playing in a match.
2.

By sending or accepting a challenge in the challenge system, you acknowledge that you have read, understand, and agree to abide by the rules posted here.
3.

Do not contact the staff inquiring about the status of a ticket / application or risk your team losing XP.
4.

All admin decisions are final. If you would like your case looked into again due to new evidence, feel free to submit another ticket, but doing so without additional evidence is just argumentative and you risk losing XP.
5.

Our goal here at GameBattles is to provide gamers with a place to find fun and competitive matches. In order to accomplish this goal, we will not tolerate players or teams with an unsportsmanlike demeanor attempting to destroy the friendly atmosphere we are trying to create. Violators of this rule will be dealt with accordingly.
6.

This ladder is limited to 40 players per team.
7.

No win / XP will be awarded for playing a team 10 levels above or below the level of your team.
8.

Staff abuse will not be tolerated in any form, be it messaging, forums, or tickets. Situations such as this will be handled on a case-by-case basis.
9.

Verbally abusing other teams and or players is unacceptable. This includes but not limited to the use of foul or degrading language on this ladder. If you are unable to be respectful to any player, team or GameBattles staff, you and or your team risk warnings up to removal from this ladder.
10.

Clan names are not able to be changed by the clan members. Please submit a ticket to request your clan name be changed.
11. If your team has not played a match in 7 days and you are ranked above level 7 you will lose 100XP. 7 days later your team will be checked again for activity and forfeit another 100XP if you have still not played.

12. All top 10 teams must play at least one top 25 team once a week.

13. Crown Holders must play at least one match per week. If a match isn’t played within a week (7 Days), the Crown will revert back to the previous holder. Crown holders must report their loss prior to playing any other matches to make sure the crown is granted to the correct team.

14. Rules are subject to change at any time, so please check them often.

15. Gamebattles prohibits members from creating or managing more than one active clan on a ladder from the same household.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Rosters

1. Socom 3 is NOT case sensitive; the capital letters on your roster and on SOCOM 3 do not need to match exactly.

2. Only one player name is allowed per line on a team roster.

3. All players participating in a match must be on the roster for at least 24 hours and can't be updated within the past 24 hours prior to the match start time indicated in the accepted challenge. Please note: the Gamebattles timezone is GMT -5.

4. Ringers: (Names that are not on the roster). Ringers are defined as a ineligible player. If a staff member finds a player as being a ringer/ineligible, the clan will forfeit the match.
* Names that are spelled differently.
* Names that are not listed on your Gamebattles roster.
* Names that have been updated in the past 24 hours.

5. If a team greens up to a player at ANY point during a match they are legal for the entire match, all maps/rounds before and after the green up. If a ringer is brought in mid-map and is greened up to at a later time then that player becomes legal for the entire war, all parts before and after.

6. The rule stated above applies only to physical roster problems, such as a player not on a roster, or spelt wrong. If a player is on a roster legally and is at a later time found to be a ringer name, then if valid proof is presented that the ringer name was in the match then the match can be voided. This will have to be reported within 48 hours after the scheduled match start, by sending a ticket.

7. Users are permitted to be listed on only one team on each ladder at any given time. Players or teams breaking this rule will be dealt with accordingly.

8. If your team is found to have a ringer problem before the match starts, you must bench the player. Warnings can be given out to teams for ignoring the rules, and will be decided on a case-to-case basis.

9. If a team is proven to have brought in a ringer mid-match, they will automatically lose the match and be given a warning.

10. If a team is caught using ringer names the account is subjected to deletion or warning and loss of XP. All ringer names will be looked and handled on a case-to-case basis. If you are found to have played under a ringer name while in another clan you will be subject to suspension from the Socom 3 (EU) arena.

11. It is each teams responsibility to make sure there are no roster issues with either clan. By accepting the challenge and entering the room, you will be liable for any roster issues with your clan, so please check before sending or accepting a challenge.

12. Team or Player names will not contain foul language, disparaging remarks, hateful or racist names.

13. Blast messages will be subject to forum rules.

14. Clan logos may be no larger than 620 x 200.

15. Clan tags are limited to no more than 3 characters long. If anyone in your clan has a long clan tag they are considered a ringer and cannot play in the match. Clan tags consisting of rank images are also considered illegal and cannot be used in ladder play.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Challenges

1.

When you challenge a team, make sure you fill out all the needed fields.
2. Adding match notes is not allowed. You may only use the by the challenge system provided abilities to ban things (such as maps and weapons).

3. For a match to be official, the challenge must be accepted in the match scheduler.

4. Any challenge accepted after the scheduled match time will not be awarded a no-show win. The challenge can be removed after you have submitted a ticket.

5. Upon accepting the challenge, three or five random maps with modes will be displayed. All wars are default best of three maps, unless stated otherwise in the challenge.

6. For small map wars, all maps will be suppression. In addition, Storm Front does not have a small version, which means that map will be played in its normal size but as suppression.

7. A team can’t play the same team more than once in a 2-day period. This rule is here to prevent teams from getting multiple wins from the same team within a short period of time.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Settings

1.

The following are regulations for matches that must be followed. If both clans green up, the match or map will not be voided later on.
1.

Round count: 11
2.

Round time: 4 Minutes, 5 Minutes, or 6 Minutes
3.

Friendly fire: On
4.

Vehicles: On
5.

All weapons must be set to: On
6. All rooms set to: Unranked Room

2. Spectator mode must be turned off unless a staff member is spectating. If you wish to have a staff member to spectating your match, this staff member is to make the room and set a spectator password that only he knows. If another player made the room, a new one will be made. To request a referee, please check the referee section to find out how to get one.

3. Both teams are reponsible for making sure the map, mode, and time settings are correct.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Battles

1.

All matches must be played in their entirety unless both teams agree remove the challenge. If agreed, both teams must submit a ticket requesting the challenge removal.
2.

The higher ranked team chooses sides on the first map, the lower ranked chooses sides on the second map and the team with most rounds won gets to choose sides on the last map
* If both teams have won the same amount of rounds, the higher ranked team chooses.
* If both teams are unranked, team with lower ID chooses first.
* Teams are allowed to play first map twice, once on both sides, and 2nd as decider when both agree in the challenge.

3. In the event of a mass boot, the match will resume from where it left off with the same score and sides. If there is an odd number of players, half is considered the lower number.
* Singles: Either player
* Doubles: One player from each side or two players from one team
* Squads: Half
* Clan: Half
We advise you to take a screenshot before the start of every map, showing the number of players participating so the administrator knows how many people have actually played on each side.

4. Number of players allowed for matches:
Singles Ladder 1 player
Doubles Ladder 2 players
Squad Ladder 3 - 7 players
Clan Ladder 8 - 16 players

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
No-Shows

1.

Failure to show for a scheduled and accepted match will result in a forfeit. Forfeits will only be awarded if you have an accepted challenge.
2.

A team has 20 minutes to show-up with the proper number of players, and be ready to start the match.
3.

To receive a no-show win, you must contact a referee and have them verify the no-show. Please send in a ticket to get the no-show awarded.
4.

Any challenge accepted after the scheduled match time will not be awarded a no-show win. The challenge can be removed after you have submitted a ticket.
5. A match is considered a no show if a team does not turn up at all or if they have less than the following amount of players:

Singles Match At least 1 player per team.
Doubles Match At least 2 players per team.
Squad Match At least 3 players per team.
Clan Match Challenged for 8-9 players Min. 8 players
Challenged for 10-12 players Min. 10 players
Challenged for 13-16 players Min. 13 players

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Reporting

1.

The losing team is responsible for reporting the loss within 3 hours. Failure to report a loss within this time period or submit a ticket explaining why it wasn’t reported will result in a warning for the offending team and a deduction of XP. If a team breaks this rule repeatedly, they may be removed from the ladder.
2.

Please don't submit a ticket about the other team not reporting their loss unless the 3-hour time limit has expired, or you had problems in the match justifying a ticket.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Tickets

1.

Do not IM the staff inquiring about the status of a ticket or risk your team losing XP. We receive many tickets from our users, and they are handled in the order they are received. Admins decisions are final.
2.

When submitting a ticket, fill out all applicable fields. Submitting an incomplete or incorrect ticket will simply be closed without being processed.
3.

Tickets that are submitted that prove to have false information are subject to clan deletion and removal from the ladder. Lengths of bans will be determined on a case by case basis.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Cheating/Glitching

1.

The use of any outside communication other than the PS2 headset is NOT allowed. However, you may communicate with your team ONLY if they are dead, or alive with you. Communication from dead players to alive players, or alive players to dead players is STRICLY prohibited. Anyone caught cheating in this form will be deleted and banned from the ladder.
2.

We have a ZERO tolerance policy for cheating here at GameBattles. Greedy teams who come here to cheat the ladder system in ANY way will be IMMEDIATELY removed from the ladder and banned from the website.
3.

"Glitching" and abusing the In-Game mechanics in ANY way is not tolerated. Our goal is to give the online gaming community a place to compete with others and we will not allow cheaters to get in the way of that goal.
4.

If your team receives a win that wasn’t earned or played, submit a ticket to have it removed. Failure to do so may result in your team being deleted and/or banned.
5.

If you give out free wins to other teams you are subject to have your account deleted and/or banned.
6. Glitching:
* Looking through or passing through any solid object with any part of the body of the player (e.g. walls, the ground, floors, windows, railings).
* Using soft spots. Any parts of objects that should be solid and impossible to hide in with any part of the player’s body are considered soft spots.
* The use of claymores to blast yourself to otherwise inaccessible places.
* Other aspects that shouldn't be possible are also considered as glitches (e.g. the use of double mines).
* A List of some of the common/misunderstood glitches is available here. Please note that even if the glitch isn't on this list, it can still be classed as a glitch, the list is just to give examples.

7. If a team is found to be glitching or cheating in a clan match they will lose the match, have their account deleted and be possibly banned from the gamebattles.com website. Bans will be decided on a case-to-case basis.

8. If you think a team is abusing the rules, you must provide valid proof or contact a referee to come and witness their abuse. Administrators will then look into the case and determine the punishment on a case-to-case basis. Accusations with no proof will not be tolerated and may result in handing out warnings.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Referees

1.

If you have any problems during a match, you may contact a referee by IM'ing him to answer any questions you may have. Please contact a referee first as this is their job. Only contact an Admin if unable to get a response from any Referees.
2.

If you anticipate referees will be needed for a clan match, you must request them 48 hours in advance of a scheduled and accepted match in the match scheduler. Only request a referee if you have had issues with a team in the past, and only if you truly believe there will be a problem in the match that would require the referee's assistance. If this is the case, submit a ticket under the "Referee Problem" heading. In the ticket, please include a short description of why you think the referee will be needed, and the accepted challenge ID #. After we receive your ticket, we will respond to it with the contact information of the referees assigned to your match. Referees in a match will have sole authority over how disputes are handled. The referee will be making the room to ensure no outside users are able to join the spectators.
3. When contacting a referee, please assign only one member per issue to do so. Having multiple users from one clan contact a referee about the same issue may result in the loss of XP.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues

Punishments

1. Warnings are given out per incident, for the reasons listed above. Warning consequences are as follows:

* First Warning - Deduction of 50xp.
* Second Warning - Deduction of 100xp.
* Third Warning – Suspension/deletion of account and deduction of 150xp.

1. Failure to report a loss, and not responding to a 24 hour no report email, or sending a valid ticket explaining why you didn’t report: 1 month ban and loss of account.

2. Lying to an admin about the outcome of a match: month ban and loss of account.

3. Glitching – This is determined on a case-to-case basis and can range from a verbal warning to a lifetime ban.

4. Ringers – Depending on incident and circumstance either warnings or loss of account/ban. Bans will be determined on a case-to-case basis.

5. Using a weapon that is banned in the challenge is not allowed. When using a banned weapon AND damaging/killing someone with it, you will automaticly lose the map where this weapon was used.

6. Staff abuse – This will NOT be tolerated, any form of staff abuse; on any messaging service, IRC, IM, the forums, or in tickets will not be tolerated. Anyone caught abusing staff is subject to a ban of any length, depending on the situation which will be handled on a case-to-case basis

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues
Tournaments

1. All tournament matches count for the bracket and the ladder unless stated in the tournament rules.

General ˇ Rosters ˇ Challenges ˇ Settings ˇ Battles
No-Shows ˇ Reporting ˇ Tickets ˇ Cheating ˇ Refereesˇ Punishments ˇ Tournaments ˇ Leagues

Leagues

1. All matches for the leagues will count for the ladder.

2. Matches are expected to be played and reported by the given date.

3. All maps will be generated randomly; teams will play the first map twice, once on both sides. The deciding map for that weeks fixture can be found on the schedule screen above the opponent for that week.

4. Teams will receive no support from the staff if they choose to change their maps by mutual agreement.

5. Teams do not win based on rounds won. Matches are to be played best of three.

6. We suggest you just keep sending challenges. The more you show you really want to play them, the better chance you have of advancing (tournament match) or receiving a win (league match) when a team does not respond to a challenge

Enter supporting content here