GoW Battle Rules

[hasds]

for the people who are going to be on the se7ensins clan and participate in clan matches on this website as well as battle other clans on other sites, then here are the rules from game battles

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 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 battles. 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. Intentional abuse of a rule to use any rule against another clan to secure a win will warrant action from GB staff.
6.

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

Gamebattles prohibits members from creating or managing more than one active clan on a ladder from the same household.
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.

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

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

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
Rosters

1.

All players participating in a match must be on the roster for at least 12 hours and can't be updated within the past 12 hours prior to the match start time indicated in the match scheduler.
2.

It is both teams responsibility to verify the rosters prior to starting the match. If a staff member finds a player as being ineligible, the clan will forfeit the battle. If any clan is found to abuse this rule to avoid a loss, your clan will be subject to penalties.
3.

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.
4.

All roster spots must be comprised of only one valid Xbox Live gamertag. Spelling and spaces must be exact, but is not case sensitive.
5.

This ladder is limited to 16 players per team.
6.

Guests are not permitted to participate in clan matches. Any clans found using guests in a match forfeit any right to submit a ticket for any roster problems.
7.

Before adding a player to the roster, verify they aren't on another clan's roster. Violators of this rule will be dealt with accordingly.
8.

Every team is required to have a minimum of 4 players on their roster prior to accepting a clan match.
9.

Team or Player names will not contain foul language, disparaging remarks, hateful or racists names.
10.

Blast messages will be subject to forum rules.
11.

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

Teams can substitute eligible rostered players as often as they need in between rounds. Each team will have ONE 10-minute grace period to arrange for a substitute before playing short handed.

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
Challenges

1.

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

If there is no response to a challenge (accept or decline), we ask that the challenging team submit a ticket notifying us of a possibly inactive team on the ladder. We will then attempt to contact the inactive team to see what the problem is. We obviously don’t want inactive teams on the ladder, so if we determine a clan is inactive, they will be removed.
3.

Should a team need to cancel a match already accepted in the match scheduler, they must do so at least 24 hours before the scheduled start time of the accepted match by submitting a ticket. The accepted challenge can also be removed at any time if both teams agree, and both teams must submit a ticket requesting the challenge be removed.
4.

A team can’t play the same team more than once in a 12 hour 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
Settings

Settings / Game Mode War Zone /
Assassination
Selected Map Custom Cycle
Rounds 3 or 5
Bleed Out Duration 20
Round Duration 5 Minutes
Friendly Fire On
Private Slots 7
Weapons Swapped No

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
Battles

1.

All 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.
2.

A clan match will consist of at least 3 no more then 4 players on each team.
3.

*Hosting a clan match. The lower ranked team at the time of battle, will host the first two maps. The Higher ranked team will host the remaining maps including the tiebreaker if it is needed.(NOTE: This is for a Best of 5 maps.) If the challenge is best of 3 maps, Lower ranked team will host 1st map, Higher ranked gets to host remainder of the match.
4.

The lower-ranked team at match time chooses first map, The higher ranked team picks Cog or Locust. These choices will alternate with each new map.(When using the map generator to select maps being played, the lower ranked team will choose Cog or Locust first)
5.

Any map may be selected by both teams during the course of the battle. However, the same team may not select the same map twice in a match. Tie breaker maps are selected by the challenge system are not taken into consideration for map selection.
6.

A standard ladder match will be first to selected number of rounds per map and the best of selected number of maps in the challenge.(First to win the number of rounds specified in the challenge wins map). The team to win the best of number of maps selected in the challenge wins the match.
7.

If the map generator is used, teams will play the selected maps in the challenge.If the map generator is not used Both teams will have to select there maps after the challenge is accepted and set up the server accordingly.
8.

In the event a tie breaker map is needed, the last map on the generated maps list of the challenge notes will be played as the tie breaker map.
9.

The default settings specified in these rules can be changed only if both teams agree, and the changes are specified in the challenge notes. 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.
10.

A "Lag Test" must be completed prior to starting the battle. This is a test round that doesn't count and uses the standard game settings that will be used during the match. If the host lags during this test, both teams should attempt to locate another host. If an acceptable host can’t be found by either team, the options are as follows:
*

Both teams submit a ticket requesting a postponement so that an acceptable host can be found. Include in the tickets the date and time of when the match will resume.
*

Both teams submit a ticket requesting the challenge be removed.
11. Time Limit (Between Rounds) - The in between round time limit is game specific. The maximum hold up time will be 5 minutes. A team can have a referee come in and authorize the rounds be started in less then 5 min. between rounds. If starting the round means the team plays short handed, so be it. Repeated abuse of this grace period can lead to warnings up to and including forfeits.
12.

If a member of either team drops during the initial launch of the game, the round will be replayed. Each player will kill themselves and not respawn, and the host will abort the mission so that it can be restarted.
13.

If a player drops mid-round, the round will continue and it's the responsibility of the team that lost the player to invite the dropped player back to the battle.
14.

If the host drops or disconnects, that round will be replayed. If the host doesn't come back online or drops a second time, choose one of the options in rule 8 (Lag Test) above.

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
No-Shows

1.

Failure to show for a scheduled and accepted match will result in a forfeit. Forfeits will only be awarded to teams who have a scheduled and accepted match in the match scheduler. Once both teams have agreed on a date and time and the challenge has been accepted, only then can a forfeit be awarded to a team for the no-show of an opposing team.
2.

A team has 30 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 submit a ticket within 3 hours of the scheduled match start time, and an admin will evaluate the situation.
4. Any challenge accepted after the scheduled match time will not be awarded a no-show win.

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
Reporting

1.

*The losing team is responsible for reporting the loss within 30 minutes of the completed battle. Failure to report a loss within the time period or submiting a ticket explaining why it wasn’t reported will result in a warning increase on the clan. Any clan reaching the warning level of three (3) is subject to deletion and banning.
2.

Please don't submit a ticket about the other team not reporting their loss unless the 30 minute time limit has expired, or you had problems in the match justifying a ticket.
3. *Any clan who did not repspond to an Admin email regarding the non-reported battle or reporting the loss before the specified time limit in the email, will be deleted from the ladder and the leader is subject to a 2 year site ban.

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
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.

When submitting a ticket to have challenges removed, list all challenge ID#s that need to be removed in one ticket. Please don’t send a ticket for each challenge when requesting multiple challenges to be removed, put all the information in one ticket.

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
Cheating

1.

The use of any communications other than what is provided within the Xbox game is prohibited.
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.

General · Rosters · Challenges · Settings · Battles
No-Shows · Reporting · Tickets · Cheating · Referees
Referees

1.

If you have any problems during a match, you may contact a Referee on AIM 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.
3.

If referees are called into a battle for any reason, all players will keep the referees un-muted at all times. The referee's may mute players at their discretion. Referee's may call out a players name at any time and the player must respond within a reasonable time in order to verify they do not have the referee muted. This is done as a way to battle 3rd party communications.