FAQ   Rechercher   Membres   Groupes   S’enregistrer   Profil   Connexion 
Se connecter pour vérifier ses messages privés

REGLE GAME BATTLE

 
Poster un nouveau sujet   Répondre au sujet    TEAM KALASH SEARCH & DESTROY Index du Forum -> SECTION CALL OF DUTY 4 -> GAME BATTLE
Sujet précédent :: Sujet suivant  
Auteur Message
KaLasH DarKness
Administrateur

Hors ligne

Inscrit le: 18 Juil 2008
Messages: 79
Localisation: TECHILAND
gamertag:

MessagePosté le: Jeu 4 Sep - 01:46 (2008)    Sujet du message: REGLE GAME BATTLE Répondre en citant

  1.

      It is the responsibility of all the users of this ladder to know and understand the rules.
   2. Rules are subject to change at any time, so please check them often.
   3.

      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 with Match Finder.
   4.

      Our goal here at GameBattles 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 with an unsportsmanlike attitude and such violators will be dealt with accordingly.
   5.

      GameBattles prohibits members from creating or managing more than one team on a ladder from the same household as well as competing against each other. In addition players cannot have more than one managing role (anything other than a member) on a team from the same household.
   6.

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

      Verbally abusing other teams and/or players is unacceptable. This includes but is 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 member, you and/or your team risk penalties.
   8.

      Team names are not able to be changed by the team members. Please submit a ticket to request a team name change. Staff will decide if the requested name is appropriate.
   9.

      Team names, blast messages, logos, avatars, and website link are subject to the Forum Rules.
  10. All MLG/GameBattles accounts are property of Major League Gaming Inc.  Any advertising of, or attempts to buy, sell, trade, or exchange an account by any means is strictly prohibited.  Violators will be banned from all MLG/GameBattles websites and all related accounts terminated.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
Rosters

   1.

      It is both teams responsibility to verify the eligibility of all players playing in the match prior to starting or continuing any match play. Do NOT start play, or the team with the ineligible player will face forfeiture of the match. Any team found abusing this rule to attempt to avoid a loss will be subject to additional penalties. Before submitting your claim of an ineligible player, you must have allowed the required 15 minutes from match start time, or the required time between rounds/maps.
   2.

      The following outlines our policies on eligible rostered players:
          *

            Users are permitted to be listed on only one team on each ladder at any given time. Users are only permitted one gamertag per ladder.
          *

            All roster spots must be comprised of only one valid gamertag. 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.
          * Players must have a green eligibility icon next to their name to participate in seasonal play.

          * All gamertags on a team's roster must be valid. A team that has invalid gamertags is subject to penalties.

   3. If an ineligible player is participating in the match at any time, the following actions should be taken:

          * First, please try to contact an available staff member to resolve the issue.

          * If none are available, please take adequate proof the ineligible player, and submit this in a ticket immediately. Tickets submitted after the match are not valid.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
Challenges

   1.

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

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

      A team cannot play the same team more than once within a 12 hour period.
   4. 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 match details, these default rules will be followed.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
No-Shows

   1.

      Failure to show for an accepted match will result in a forfeit.
   2.

      A team has 15 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.
   3.

      To receive a no-show win, you must submit a ticket within 45 minutes of the scheduled match time. You must also report the match as a win for your team.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
Reporting

   1.

      Both teams are responsible for reporting the match within 30 minutes of its completion. If teams do not report matching results, a ‘dispute’ will be created in our support system automatically. Both teams are then required to submit a ticket regarding the dispute and include any proof they have. If a ticket is not submitted by a team, that team is subject to a warning level increase.
   2.

      If a team is found to have multiple disputes or fails to report matches, they will be subject to penalties.
   3. Matches that go unreported by one team will be reported automatically. Matches that go unreported by both teams will be disputed automatically, and a ticket is required to resolve the dispute.

   4. Any team found to report as the winning team before the match is played or before the match is completed will be subject to penalties.

   5. * All matches need to be reported accurately by both teams. If there is an issue with a match, the match must first be reported accurately and then a ticket containing your 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.

   6. * 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.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
Crown

   1.

      Crown holders must play at least 2 matches every week. If 2 matches are not played in a week then the crown will be reverted to the previous crown holder, or GameBattles.
   2.

      Crown holders must report their loss prior to playing any other matches to make sure the crown is granted to the correct team.
   3.

      If the crown holder is caught giving a win to another team before reporting to a team that rightfully won the crown, they are subject to penalties.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
Tickets

   1.

      Do not contact staff inquiring about the status of a ticket or your team risks being subject to penalties. We receive many tickets from our users, and they are handled in the order they are received.
   2.

      When submitting a ticket, fill out all applicable fields. Submitting an incomplete or incorrect ticket will simply be closed without being processed.
   3. 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 argumentative and you risk your team being subject to penalties.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
Cheating

   1.

      The use of any communications other than what is provided within the game is prohibited.
   2.

      We have a zero tolerance policy for cheating, and teams are subject to penalties if they are found cheating.
   3.

      "Glitching" and abusing the In-Game mechanics in any way is not tolerated. We do not allow cheaters to compete on GameBattles.
   4.

      If your team receives a win that was not earned or played, submit a ticket to have it removed. Failure to do so may result in your team being subject to penalties.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches
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 the referees first as this is their job. Only contact an admin if unable to get a response from any referees.
   2.

      If referees are called into a match for any reason, all players must comply with the referee's instructions. Failure to do so may result in penalties.
   3.

      Verbally abusing the referee while in game will not be tolerated. The individual user and/or team violating this rule will be subject to penalties. 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.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Proof

   1.

      You need to show proof of winning each map/game in a match to be given the win for it. All proof must contain the in game full scoreboard (showing clearly) during the completion of that map/game, showing both team's players to be considered valid.
   2.

      We recommend all video proof should be uploaded to the GB Game Room.
   3.

      For all glitch and cheating claims, the burden of proof is on the accuser. To submit a glitch and/or cheating claim, you must submit a ticket and include the proof.
   4.

      All conversations between users are not considered proof.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

General Ladder

   1. All players participating in a match must be on the roster for at least 12 hours and can not be updated within the past 12 hours prior to the match start time indicated in the accepted match details.
   2. This ladder is limited to 24 players per team.
   3. Every team is required to have a minimum of 3 players on their roster prior to accepting a match.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Settings

   1. 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 match details, these default rules will be followed.
          * The following settings apply to all GameBattles matches, regardless of the Game Mode.
               1. Spectator : Disabled (Does not apply for Search and Destroy)
               2. Friendly Fire : Enabled
               3. Forced Respawns : Enabled
               4. Wave Spawn Delay : None
               5. ReSpawn Delay: None (Does not apply to Sabotage)
               6. Radar Always On : Challenge Option
               7. Max Health :  Normal
               8. Health Regeneration : Normal
               9. Allow Kill Cam : Challenge Option
              10. Allow Sprint : Enabled
              11. Headshots Only : Disabled
              12. Allow Perks : Challenge Option
              13. Allow Air Support : Challenge Option
              14. Number of Lives : Unlimited (Does not apply to Search and Destroy.)
              15. Join in Progress : Not Allowed
              16. Old School Mode : Disabled
              17. Hardcore Mode : Challenge Option
          * The following settings are specific to each Game Mode, so please read them carefully before setting up the server.
               1. Team Deathmatch
                      o Points to Win : Challenge Option
                      o Round Timer : 10 Minutes
               2. Search and Destroy
                      o Round Length : 3 Minutes
                      o Bomb Timer : 45 Seconds
                      o Number of lives: 1 Life
                      o Plant Time : 7.5 Seconds
                      o Defuse Time : 7.5 Seconds
                      o Multi Bomb : Disabled
                      o Score Limit : 4 Points
                      o Round Switch : Every Round
                      o Spectator: Team Only
               3. Sabotage
                      o Time Limit : 10 Minutes
                      o Bomb Timer : 30 Seconds
                      o Plant Time : 5 Seconds
                      o Respawn Delay: 7.5
                      o Defuse Time : 5 Seconds
                      o Shared Bomb Timer : No
                      o Score Limit : 1
                      o Round Switch : Never
               4. Domination
                      o Time Limit : 10 Minutes
                      o Score Limit : Unlimited
                      o Respawn Delay : 5 Seconds
   2. If any of the above settings are incorrect, the hosting team forfeits that map. The team hosting is responsible to ensure all setting are correct prior to beginning any map. If the settings are incorrect, the map needs to end and the next map needs to be played. The team that was not hosting is responsible for obtaining valid proof to show that the hosting team did not have the settings correct. A ticket with valid proof must be submitted immediately after the match has been completed.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Matches

1.   All matches must be played in their entirety unless both teams agree to postpone or cancel the match. Teams can play a best of 3 (first team to win 2 maps wins the match) or a best of 5 (first team to win 3 maps wins the match). If no selection is made, a Standard Ladder Match will be played best of 3 maps.

2.   Randomized maps MUST be used. Users cannot pick maps or change options selected in the challenge details. The staff will support no other agreements, (i.e. verbal, AIM, email). Unless specified otherwise in the challenge details, these default rules will be followed.

3.   Teams can select to use a custom mapset, which will generate random maps of the game mode that was selected. The variety mapset will include all maps as well as the maps present from the variety map pack. Selecting this mapset will not guarantee that a map from the variety map pack will be generated.

4.   The higher ranked team at match time will host the first map. The higher ranked team is the team ranked closer to “1” on the ladder. If there is a tie in rank (i.e. both are unranked), the Team ID closest to 0 will host first. The lower ranked team at match time will host the second map. This will alternate for each map until/if a tie breaker map is needed. If a tie breaker map is needed, the lower ranked team will host the final map.

5.   The team that is not hosting will pick which side to play on.

6.   A "Lag Test" must be completed prior to starting the match. This is a test round that does not count and uses the standard game settings that will be used during the match. For the lag test, a map that is not scheduled for play must be used. If the game lags during this test, a new host must be chosen. If both teams cannot find or agree upon an acceptable host, the match needs to be removed. To have the match removed, both teams need to submit tickets asking that the match be canceled.

7.   Teams may not delay the match for more than 5 minutes between each map. If a team delays the start for longer than 5 minutes between maps, they will forfeit that map. The team that did not delay must submit a ticket with valid proof showing that this delay did occur. First, the match must be completed and the scores must be reported correctly. Do not dispute the match on purpose. After the match is complete, submit a ticket containing the URL link of the proof.

8.    If a player/host disconnects during the initial launch of a map, the map will be restarted. The initial launch is defined as within the first 30 seconds or before the first kill. If both teams disagree over when the disconnection took place, video proof must be provided. First, the match must be completed and the scores must be reported correctly. The URL link of the proof must be submitted in a ticket once the match is completed.

9.    If the host disconnects after the map has started, the host's team forfeits that map. After the map has started is after 30 seconds or after the first kill. If both teams disagree over when the disconnection took place, video proof must be provided. First, the match must be completed and the scores must be reported correctly. The URL link of the proof must be submitted in a ticket once the match is completed.

10.  If a player disconnects after the game has started, the game will continue and a player may be re-invited. The re-invited player may be the player that dropped or a new eligible player. The only exception to this rule is for a "Kill Dependent Game Mode". Please see rule 11 below.

11.  A "Kill Dependent Game Mode," often referred to as Deathmatch, Sharpshooter or Slayer, is a game mode whose winner is decided by the overall number of kills, or points gained from kills. Because this mode relies on the number of players present, a team can never play shorthanded when playing this mode. A Team that loses a player during this game mode, after the first kill has occurred, forfeits that map.

12.   If a team loses players during a map, they must find eligible substitutes prior to beginning the next map. A team is not allowed to start a map shorthanded. For a “Kill Dependent Game Mode”, a team can never play shorthanded as stated in rule number 11. Teams are allowed a 5 minute grace period to find eligible substitutes between maps as per rule number 7. Please follow the steps in rule number 7 if the match is delayed longer than 5 minutes between maps.

13.  We highly recommend that all players appear offline at all times during their match. Users are not to dispute a match on purpose if the other team did not appear offline. If random players enter the room, ask them to leave. If they leave immediately without disrupting the match, the match can continue. If the player disrupts the match, the match is to resume from the score at which the player(s) entered.

14.  If a map results in a tie, the map will be replayed with the same sides and settings.

15.   Deliberately team-killing or committing suicide on purpose during Team Deathmatch will  result in a forfeit of the map. If a team is accused of violating this rule, the accuser must provide valid video proof. First, the match must be completed and the scores must be reported correctly. The URL link of the proof must be submitted in a ticket once the match is completed. An Admin has the ability to overturn the match if valid proof is provided.

Qui veux la paix prépare la guerre


Revenir en haut
Publicité






MessagePosté le: Jeu 4 Sep - 01:46 (2008)    Sujet du message: Publicité

PublicitéSupprimer les publicités ?
Revenir en haut
Montrer les messages depuis:   
Poster un nouveau sujet   Répondre au sujet    TEAM KALASH SEARCH & DESTROY Index du Forum -> SECTION CALL OF DUTY 4 -> GAME BATTLE Toutes les heures sont au format GMT + 2 Heures
Page 1 sur 1

 
Sauter vers:  

Portail | Index | Panneau d’administration | créer forum gratuit | Forum gratuit d’entraide | Annuaire des forums gratuits | Signaler une violation | Conditions générales d'utilisation
Powered by phpBB © 2001, 2005 phpBB Group
Traduction par : phpBB-fr.com
Theme xand created by spleen.