General- Rules are subject to change at any time, so please check them often.
- It is the responsibility of all the users of this ladder to know and understand the rules.
- 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. This includes posting or accepting challenges on the
Match Finder.
- Our goal here at Socom Leagues is to
provide gamers with a place to find fair and competitive matches. In
order to accomplish this goal, we will not tolerate players or teams
that cause problems or attempt to. This includes teams that cheat,
dispute on purpose, or repeatedly abuse players. Violators will be
dealt with accordingly. As with all accusations, valid proof must be
provided. Please see the proof section below.
- Socom
Leagues prohibits members from creating or managing more than one team
on a ladder from the same household as well as competing against each
other. Multiple people from the same household may compete on Socom
Leagues; however, only one username can be in a management position on
a team. For example, only one username can be a Co-Leader or Leader on
a team. All other usernames from the same household cannot be anything
higher than member on any team.
- Abuse of our volunteer
Staff will not be tolerated in any form. This includes written messages
or verbal comments. Violators will be banned from Socom Leagues.
- Team
members are not able to change the name of their team. Only the leader
of the team can submit a ticket to request a team name change. Names
must be appropriate and cannot be taken by another team on the same
ladder.
Rosters - It
is both teams responsibility to verify the eligibility of all players
playing in the match prior to starting or continuing any match play. A
team playing with an ineligible player will forfeit the match.
- If
the opponent team has an ineligible player present, ask the team to
replace that player. You must have given the team the required 5
minutes from match start time to substitute their ineligible players.
If the ineligible player shows up between maps/rounds, you must give
the team the required 5 to replace their ineligible player. If the team
does not substitute their ineligible player and allows that player to
compete in the match, follow these steps:
- Immediately
submit a ticket stating an ineligible player was present. This ticket
must be submitted before starting or continuing to play the match.
- When
the match is completed, you must go back to your ticket and submit the
URL link containing valid proof showing the ineligible player playing
in the match. Without valid proof, no win can be awarded.
- Tickets submitted after the match is completed are not valid. You must submit a ticket immediately when the issue arises.
- All members socom name on a team’s roster must be valid.
- The rules below outline our policies on rostered players. Please see rule number 2 if the following rules are broken:
- Users are permitted to be listed on only one team on each ladder at any given time.
- All
roster spots must be comprised of only one valid clan tag. Spelling and
spaces must be exact, but does not need to be case sensitive.
- Gamertags may not contain foul language, disparaging remarks, hateful or racist names.
- PPlayers must have a green eligibility icon
next to their name to participate in matches.
Challenges - Should
a team need to cancel an already accepted match, they must submit a
ticket requesting to do so at least 12 hours before the scheduled start
time of the match. The match can also be removed at any time if both
teams submit tickets agreeing to have it removed. Both teams are also
recommended to post feedback stating they wish to cancel the match. If
both teams do not agree to have the match removed, both teams are
required to play the match.
- A team cannot play the same team more than once within a 6 hour period.
- The
default settings specified in these rules can be changed, but only if
an option is available in the challenge. The staff will support no
other agreements, (i.e. verbal, messenger, email). Unless specified
otherwise in the match details, these default rules will be followed.
No-Shows - A
team has 5 minutes to show-up with the number of eligible players
indicated in the match details, and be ready to start the match.
Failure to do so will result in a forfeit. Teams are responsible for
all scheduled matches.
- To receive a no-show win, you
must submit a ticket within 30 minutes of the scheduled match time. You
must also report the match as a win for your team.
Reporting - Both
teams are responsible for reporting the match within 30 minutes of its
completion. If teams do not report matching results, the match will
result in a ‘dispute’. Both teams are then required to submit a ticket
regarding the dispute and include any valid proof they have. Teams can
also resolve their own disputes by changing the scores they reported
for the match. To do this, teams must go into the match report screen
for the disputed match and change the scores within 24 hours of the
scheduled start time.
- Matches that go unreported by
one team will be reported automatically for the team that did report.
Matches that go unreported by both teams will be deleted automatically.
- Any team found to report as the winning team before the match is played or completed will be subject to penalties.
- All
matches need to be reported correctly by both teams. If there is an
issue with a match, the match must first be reported accurately and
then a ticket containing your valid proof can be submitted afterwards.
Do not dispute the match on purpose. Please see the proof section below
for more information. If your claims are found to be valid with proof,
an Admin has the ability to revert the match.
- Disputing a match on purpose will result in penalties for your team.
- The
first time a team disputes on purpose without valid proof, the team is
locked for 6 days and the team warning level is increased to level 1.
- The
second time a team disputes on purpose without valid proof, the team is
disbanded and the member that disputed is banned as well as the leader
of the team.
Tickets - Do
not contact staff inquiring about the status of a ticket. We receive
many tickets from our users, and they are handled in the order they are
received.
- When submitting a ticket, fill out all
applicable fields. Submitting an incomplete or incorrect ticket will be
closed without being processed. You are required to select your team
name from the drop-down. If you are submitting a ticket about a match,
you must also fill out the match ID or your ticket will not be
processed.
- All admin decisions are final. If you
would like your case looked into again due to new evidence, feel free
to submit a new ticket. Submitting a ticket without additional evidence
is argumentative and you risk your team being locked.
Cheating - The
use of any communications other than what is provided within the game
is prohibited. For example, the use of Skype or private chatting during
a match is not allowed.
- We have a zero tolerance policy for cheating. Teams caught cheating, “glitching”, or abusing in-game mechanics in any way will be removed from Socom Leagues.
- If
your team receives a win that was not earned or played, you must submit
a ticket to have it removed. Failure to do so will result in your team
being removed from Socom Leagues.
Referees - If
you have any problems during a match, you may contact a Staff member
over Live Support to answer any questions you may have. Please contact
the Referees first as this is their job. To find the list of Staff
members, click on the “Staff” tab located within each ladder. Please
use this link to get to Live Support: http://socomleagues.com/staff.php
- If
a Staff member is called into a match for any reason, all players must
comply with the Staff member’s instructions. Failure to do so will
result in penalties for your team.
- Verbally abusing
Staff members called into a match will not be tolerated. The individual
user and/or team violating this rule will be subject to being locked.
All team leaders are responsible for the conduct of the players on the
team while interacting with staff and are subject to penalties for
abusive team players.
Proof - You
need to show proof of winning each map/game in a match to be given the
win for it. All proof must be clearly visible and show the in-game full
scoreboard during the completion of that map/game. The proof must all
clearly show both team's players to be considered valid.
- We recommend all video proof should be uploaded to the GotVidz. Picture proof can be uploaded to your profile. The URL link to the individual pictures/proof must be placed in a ticket.
- For
all glitching and cheating claims, the burden of proof is on the
accuser. To submit a glitching or cheating claim, you must submit a
ticket and include the URL link containing valid proof.
- Unlike
the other ladders we do take in consideration talks on messengers. If
any member speaks of cheating or glitching to another team on any
messenger we will look into that. Note the messenger must be on the
teams profile.
General Ladder
All
players participating in a match must be on the roster for at least 2
hours and can not be updated within the past 12 hours prior to the
match start time indicated in the accepted match details. - This ladder is limited to 4 players per team.
- Every team is required to have a minimum of 4 players on their roster prior to accepting a match.
Settings
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. - ALL MAPS MUST BE SMALL DEMO
-
Round count: 11 Rounds
Round time: 4 Minutes Friendly fire: On Vehicles: Teams Decide All weapons must be set to: On - All rooms set to: Unranked Room
- The
following are regulations for matches that must be followed. If they
are not, the match or map will not count for the match, and must be
replayed correctly.
- Map as specified in the Challenge.
- Game Mode as specified in the Challenge.
- Time of Day as specified in the Challenge.
Spectator
mode must be turned off unless a staff member is spectating. If
spectator mode is turned on, and a staff member did not make the room,
that map must be replayed. All accepted challenges that
declare the match to be played in a ranked server must be played as
such. If you have a clan member who has an unverified account and
cannot join the server, the room will not be remade to accommodate that
player. All rooms must be made an extra 2 player slots
larger than what is stated in the challenge, in order to accommodate
the possibility of a staff member entering the match. This setting will
be pursuant to rule 1 under this section, and the map will count if
both teams green up.
MatchesAll
matches must be played in their entirety unless both teams agree to
postpone the match or remove the challenge. If agreed, both teams must
submit a ticket requesting the postponement or challenge removal. A
referee can be contacted to witness the agreement details. - The
default settings specified in these rules can be changed, but only if
an option is available in the Challenge. The staff will support no
other agreements, (i.e. verbal, AIM, email). So unless specified
otherwise in the challenge details, these default rules will be
followed. In a best of 3, the team with the higher rank
picks sides on the first map, the other team chooses their side on the
second map. In both cases, whichever team won the most overall rounds
gets to pick their side for the final map. If both teams have won the
same amount of overall rounds, the team ranked closest to #1 gets to
pick there side. If neither team is ranked, the team with the id
closest to 1 will be considered the higher ranked. Rank is determined
at the scheduled time of the battle 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. Quads: 2 players from each side or 3 players from one team If only one team loses players in the boot, that team will forfeit the round they were booted.
- The
use of any restricted item or weapon (i.e. M203 or Ghillie Suit: as
specified in the challenge), which results in one team receiving a
positive kill, will result in a forfeit of that map for the offending
team. |