vcod.gg - CoD:UO Rifles Only Rules
Here you will find the rules for our upcoming competition. Please bear in mind, that although we are not new to hosting competitions, there may be a rule that is missing or a rule that is not clear. You can contact us on our contact page if you find any issues.
1.1 – Punishment
1.1.1 – Players who violate any of the vcod.gg rules are subject to punishment.
1.1.2 – Punishment will result in receiving a card and in more serious cases, a temporary or permanent ban from all vcod.gg competitions.
1.1.3 – A player and/or clan can be given two types of card:
- 1.1.31 – Yellow card: This card is given out for small rule violations and will usually be given out as a warning. However, a yellow card can still end in the result of a match being amended. A second yellow card is equivalent to a red card.
- 1.1.32 – Red card: This card is given for more serious offences and will in most cases lead to a forfeit loss and punishment of the player and/or clan in question. Receiving a red card may also lead to a temporary or permanent ban from all vcod.gg competitions.
1.1.4 – A player and/or clan can be given more than one card in a match. In case of several violations, only the most severe card will be issued. However, all extra punishments for each rule that was violated will still be applied.
1.1.5 – Abusive behaviour towards a vcod.gg Admin, Supervisor, Referee or opponent, at any time during the competition is not acceptable. If the abusive behaviour is severe, then a vcod.gg Admin has the right to punish with a temporary or permanent ban from the competition.
1.1.6 – The Clan Leader is responsible for his/her own members to know, understand and follow the rules.
1.1.7 – If a player is banned by PunkBuster during a match, the match will end immediately, and the opposing team will receive a forfeit win; please take a screenshot for evidence.
1.2 – Spectating
1.2.1 – vcod.gg reserves the right to broadcast every match.
1.2.2 – Spectating during an official match is not allowed unless you are an official vcod.gg Admin, Supervisor, Referee or Streamer. Should any spectator join who is not allowed, the game should be immediately paused whilst the spectator is removed from the server.
1.2.3 – The vcod.gg Admin has the right to TeamView any player during the match.
1.3 – Arranging Matches – Cups
1.3.1 – Matches can be played from Monday through to the following Monday, 22:00 CET. If you cannot find an agreement with the enemy team, the match will be automatically set for the Sunday at 20:00 CET.
1.4 – Arranging Matches – Division Series
1.4.1 – Matches will be played from Friday, 13:00 CET through to Monday 23:00 CET. If you cannot find an agreement with the enemy team, the match will be automatically set on the tournament page.
1.5 – Arranging Matches – General
1.5.1 – Matches should be arranged by sending a personal message on Discord to a Clan's Admin.
1.5.2 – When both clans agree not to play a match, it can be cancelled for any reason after the scheduled starting time, only if the match can still be completed in the scheduled game week or weekend.
1.6 – Before the Match
1.6.1 – To find your opponent before a match, you should look on the website and add them on Discord.
1.6.2 – If you have still not managed to get in touch with your opponent 15 minutes after the scheduled starting time of the match, you can fill in a no-show.
1.6.3 – Matches can only start if a vcod.gg Referee is present (unless both teams agree to play without).
1.6.4 – Players listed with an EYE will be teamviewed upon entering the game. Anyone refusing to be teamviewed will not be allowed to participate.
1.6.5 – A vcod.gg Admin, Supervisor or Referee should TeamView EYE players upon entering the game. In case the vcod.gg Admin, Supervisors or Referees are unavailable, the opposing Clan's Admin will be allowed to TeamView their opponent's EYE players onto the server.
1.6.6 – Before each game can start, the vcod.gg Referee should always ensure that both teams are ready. If one member of a team says that his team is ready, he is considered to speak for the whole team, regardless of his status in the clan.
1.7 – After the Match
1.7.1 – Either clan can post the result of a match, unless the other has already done so. Your result should be posted in the #vcod_cup board on Discord.
1.7.2 – Clans are expected to have proof of their match being played for 48 hours after the score has been confirmed.
1.8 – Leaving
1.8.1 – Clans which leave the competition or are removed for 2 no-shows/forfeits are likely to be excluded from future competitions.
1.8.2 – Reconnecting during the match without any valid reason is not allowed and will result in a yellow card and forfeit of the round.
1.8.3 – If a player drops connection because of a technical error, the match must be paused. You can call a time out by typing “/matchtimeout” in the console. A pause can only be made when a round has started or finished.
1.8.4 – The maximum time you can pause for is 5 minutes. After this time, the match will resume. The maximum total pause time is 5 minutes per map, per team. You do not need a reason to call a time-out.
1.8.5 – In extreme cases, it can be agreed for teams to have an extra 5 minutes to resolve issues.
1.9 – vCoD.gg Organisation
1.9.1 – vcod.gg Admin
- 1.9.11 – razRR-raRR#9282 (49d5ce5c)
1.9.2 – vcod.gg Supervisors
- 1.9.21 – dream-mrd#7168 (821129fd)
- 1.9.22 – HanNiBaL-K33NB34N#3227 (37740bfa)
- 1.9.23 – xa1ruZ-xa1ruZ#6662 (98ae2a96)
- 1.9.24 – prm-prm#2642 (3ac7ce54)
1.9.3 – vcod.gg Conflict Team
- 1.9.31 – nana-steve#0802 (60a8a8ee)
- 1.9.32 – fe@r-dragounet#9647 (********)
- 1.9.33 – Fantasy-Fantasy?#1116 (********)
1.9.4 – vcod.gg Referees:
- 1.9.41 – opfii1ee-supatroopa#8123 (28997e1d)
- 1.9.42 – nana-steve#0802 (60a8a8ee)
1.9.5 – Only a vcod.gg Referee from this list can be an official spectator. Anyone who falsely pretends to be a vcod.gg Referee will receive a temporary ban from vcod.gg competitions.
1.9.6 – A vcod.gg referee should ensure the match is played according to the rules.
1.9.7 – Clans have the right to refuse a vcod.gg Referee, but must state a specific reason why. The vcod.gg Admin and Supervisors cannot be refused.
1.9.8 – If you think a vcod.gg Referee has made an incorrect decision, then contact the vcod.gg Admin or Supervisors.
1.9.9 – In case of no vcod.gg Referee being available, ensure screenshots are kept of any rule breaking or violations; if you have a conflict, post a ticket via Discord.
2. Server Rules
2.1 – Server Settings
2.1.1 – All matches hosted by vcod.gg will be played on the original Call of Duty: United Offensive 1.51 patch.
2.1.2 – All matches need to be played on a server that has PunkBuster enabled.
2.1.3 – All players will need the latest PunkBuster folder, which can be downloaded at: https://www.sendspace.com/file/6t8otf.
2.1.4 – All matches must be played on the latest vcod.gg PAM, which can be downloaded at: LINK COMING. Teams can refuse to play on a server if the vcod.gg ruleset has been edited.
2.1.5 – To properly configure vcod.gg PAM for competition settings, use the following command: “/rcon pam_mode vcodgg_match” (default mode for all competition matches) and “/rcon pammode vcodgg_night” (default mode for all weekend competitions).
2.1.6 – All server must have the latest vcod.gg cvarlist file, which can be downloaded at: LINK COMING.
2.1.7 – All server must have the latest vcod.gg pbsv file, which can be downloaded at: LINK COMING.
2.1.8 – All server must have the latest vcod.gg pbsvuser file, which can be downloaded at: LINK COMING.
2.1.9 – Default servers have been provided for the competition. These should be used if teams cannot agree on a server or if there are any ping issues:
3. Client Rules
3.1 – Client Registration
3.1.1 – Each player in your clan must have the last 8 characters of their GUID registered on the website to be eligible. GUIDs are unique identifiers used in game to recognise players. Join a PunkBuster enabled server, open your console and type: “/pb_myguid” to find your GUID.
3.1.2 – The last change of a GUID cannot be done later than 24 hours before a match (unless agreed by the opposition). Players who did not register the correct GUID before a match will be considered freelancers.
3.1.3 – A clan can only use players during a match who are registered to their team. Using a player who is not allowed to play will result in a red card and forfeit of the match.
3.1.4 – A clan can only register new players throughout the group stage as long as they have not signed up for another team. Swapping clans throughout the tournament is not allowed.
3.1.5 – Players always have to be easily identifiable to the vcod.gg Admin, Supervisors, Referees and opponents. Therefore, players must use the nicknames registered on the website or nicks which are very similar.
3.1.6 – Clans have the right to refuse a player from participating if the GUID does not match what is registered on the website. In cases where the there is a slight mistake in the registered GUID, vcod.gg the Admin will decide on next steps to avoid conflicts.
3.1.7 – All players will need to install the Call of Duty: United Offensive map pack, which can be downloaded at: https://www.sendspace.com/file/czbsdu. If the installation does not work, you can download the uomappack00.pk3 at: https://www.sendspace.com/file/66trw6.
3.1.8 – To show the GUIDs of all players in a match, open your console and type: “/pb_plist” or “/pb_power”.
3.2 – Client Settings
3.2.1 – In all competition matches, MOSS Anti-Cheat will be mandatory and must be turned on for the entire match. You can download MOSS at: https://www.sendspace.com/file/cqory2.
3.2.2 – Each player is responsible for making sure they are running MOSS during the match.
3.2.3 – If a player closes MOSS during the match, the player will receive a yellow card and the clan will forfeit the match. In cases where the player experiences an unknown bug, the vcod.gg Admin, Supervisors and Conflict Team will decide on the next steps.
3.2.4 – If a player crashes during the match, he must re-join MOSS immediately. Clans can use the following command: “/matchtimeout” at the start of the round to allow players to reconnect to MOSS.
3.2.5 – Screenshots from ALL players must be uploaded after each match. Screenshots not uploaded 48 hours after a match will result in the player receiving a yellow card and the clan forfeiting the match. In cases where the player experiences an unknown bug, the vcod.gg Admin, Supervisors and Conflict Team will decide on the next steps.
4. Competition Rules
4.1 – Match Rules - Cups
4.1.1 – A match is played over two maps; each clan will play one time as defenders and one time as attackers on both maps.
4.1.2 – Each map has a round limit of 20, in which both clans will play 10 rounds as defenders and 10 rounds as attackers.
4.1.3 – Rounds are set at 2 minutes and 30 seconds.
4.1.4 – The first team to reach 21 rounds will be determined the winner.
4.1.5 – The map pool for the competition is: Arnhem, Bocage, Brecourt, Carentan, Cassino, Dawnville, Depot, Harbor, Hurtgen, Neuville, Pavlov, Peaks, Powcamp, Railyard, Rocket, Sicily, Stalingrad, Streets, Tigertown, UO Carentan, UO Dawnville, UO Depot, UO Harbor, UO Hurtgen, UO Powcamp, UO Stanjel.
4.1.6 – During the group stage, the maps will be pre-chosen and will be played in the order listed on the website. Bash for side will take place before each map begins, with the winner deciding which side to start on.
4.1.7 – During the knockout stage, teams must state their map before bash takes place. The winner of bash will then choose whose map will be played first. Bash for side will take place at the start of each map to determine sides. Clans can only choose a map once until the Grand Final, where maps will be reset.
4.1.8 – In the event of a draw (20 - 20) during the knockout stage, a golden map will be played. Bash for side will take place with the winner starting a veto of maps. The final map left from the veto will be played as a third map. Bash for side will take place to determine sides. The first team to reach 11 rounds will be determined the winner.
4.1.9 – In the event of a draw (10 - 10) during the golden map, the second last map banned during the veto will be played. Bash for side will take place to determine sides. The first team to reach 11 rounds will be determined the winner.
4.2.0 – All maps from the map pool are eligible to be played as a golden map, even if a team has already played it during the knockout stage.
4.2.1 – In the Grand Final, the Upper Bracket team holds the advantage; if the Upper Bracket team reaches 21 rounds, they will be determined the winner. However, if the Lower Bracket team reaches 21 rounds first, a golden map will be played. The first team to reach 11 rounds will be determined the winner.
4.2.2 –The default team size for clan matches is 5 vs 5, but you can specify a different team size if needed. The minimum team size is 4 vs 4 and the maximum team size is 6 vs 6.
4.2.3 – Substituting a player during the match is only allowed between sides and map change, or in case of extreme connection problems, during the game. If the new player has not showed up after 5 minutes, the match will resume.
4.2.4 – At side or map change, clans can take a maximum of 5 minutes for a break, the match is to resume after that time. When the 5 minutes are up, spectators can be removed freely. Staying in spectator will lead to the automatic loss of the round.
4.2.5 – If a clan does not ready up in time after side or map change, it will lead to forfeiting rounds and eventually a forfeit loss for the violating clan.
4.2.6 – In total, all 8 teams will progress into the knockout stage.
4.3 – Match Rules - Division Series
4.3.1 – A match is played over one map; each clan will play one time as defenders and one time as attackers on both maps.
4.3.2 – Each map has a round limit of 26, in which both clans will play 13 rounds as defenders and 13 rounds as attackers.
4.3.3 – Rounds are set at 2 minutes and 30 seconds.
4.3.4 – The first team to reach 14 rounds will be determined the winner.
4.3.5 – The map pool for the competition is: Arnhem, Bocage, Brecourt, Carentan, Cassino, Dawnville, Depot, Harbor, Hurtgen, Neuville, Pavlov, Peaks, Powcamp, Railyard, Rocket, Sicily, Stalingrad, Streets, Tigertown, UO Carentan, UO Dawnville, UO Depot, UO Harbor, UO Hurtgen, UO Powcamp, UO Stanjel.
4.3.6 – The maps will be pre-chosen and will be played in the order listed on the website. Bash for side will take place before each map begins, with the winner deciding which side to start on.
4.3.7 –The default team size for clan matches is 5 vs 5, but you can specify a different team size if needed. The minimum team size is 4 vs 4 and the maximum team size is 6 vs 6.
4.3.8 – Substituting a player during the match is only allowed between sides, or in case of extreme connection problems, during the game. If the new player has not showed up after 5 minutes, the match will resume.
4.3.9 – At side change, clans can take a maximum of 5 minutes for a break, the match is to resume after that time. When the 5 minutes are up, spectators can be removed freely. Staying in spectator will lead to the automatic loss of the round.
4.4.0 – If a clan does not ready up in time after side change, it will lead to forfeiting rounds and eventually a forfeit loss for the violating clan.
5. Demos and Screenshots
5.1 – Demos
5.1.1 – All players must record demos from the entire match. Demos can be requested as long as there is a valid reason and must be kept until the result has been accepted. Demos can be requested before a conflict is made.
5.1.2 – If you have an EYE, your demo must be uploaded after each match. Demos not uploaded 48 hours after a match will result in the player receiving a yellow card and the clan forfeiting the match.
5.1.3 – In case of a conflict the following is required, or the conflict will be discarded:
- 5.1.31 – The clan must explain their reason(s) for their demo request.
- 5.1.32 – The clan must state round number(s) and time(s) within the round.
5.1.4 – Failure to upload requested demos or uploading demos that are broken or incomplete will result in the player receiving a yellow card and the clan forfeiting the match.
5.1.5 – A demo is considered to be incomplete if it is missing 3 or more rounds. If a clan is manipulating the demo 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.
5.1.6 – A demo that is missing more than 10 rounds will result in the player receiving a yellow card and the clan forfeiting the match.
5.2 – Screenshots
5.2.1 – Screenshots of the scoreboards should always be taken by each clan and posted in the #vcod_cup board on Discord.
5.2.2 – Only screenshots can be accepted as proof when there is a dispute about the score.
5.2.3 – Screenshots or demos can be requested by the vcod.gg Admin, Supervisors or Referees at any time.
6. Cheating and Bug Abuse
6.1 – Cheating
6.1.1 – If a player is caught cheating during an official match, they will receive a red card and a permanent ban from all vcod.gg competitions. The clan will also forfeit the match.
6.1.2 – If both clans cheated and/or used a suspended player, the match result will be void. Players will receive a red card and a permanent ban from all vcod.gg competitions.
6.1.2 – All programs or files, be they changed game files or new files, that change or edit the game or add to its functionality, or that interact with the game in any way, are strictly forbidden. The use of any forbidden programs or file by any clan member leads to a forfeit loss and could lead to a removal and ban from the competition in major cases.
6.1.3 – 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 the competition in major cases.
6.1.4 – Config settings that give a distinct advantage over the opponent may be deemed config abuse and can lead to the player receiving a yellow card and forfeit of the match.
6.1.5 – When providing timestamps for demos, remember to state which player's demo and what map you are referring to. The round indication should be clear for everyone to be able to follow. If the match was interrupted by a map restart (for example because of a pause) or similar and the round ordering has changed, be sure to mark those to make everything clear. Every timestamp must be exact, saying “watch demo” or “whole round” are unacceptable and will not be taken into consideration while watching the demo.
6.2 – Bug Abuse
6.2.1 – It is not allowed to take advantage of or abuse bugs. Any kind of bug abuse is considered cheating and will result in forfeiting the round where the bug was abused, unless otherwise mentioned specifically in the rules. Bug abuse consists of:
- 6.2.11 – Aim glitching (includes the short aim glitch after reloading).
- 6.2.12 – Fast reloading (includes the fast weapon switch).
- 6.2.13 – Shooting players through walls (includes hands of players clipping).
- 6.2.14 – Using map exploits (includes crouch jumping to get stuck in buildings and see through them).
- 6.2.15 – Abusing player model speed (includes A+D spam).
- 6.2.16 – Using prone to head glitch and become unhittable.
6.2.2 – Any types of scripts proven to give a real advantage or are part of the not allowed binds/scripts below, will not be tolerated and will result in the player receiving a yellow card and the clan forfeiting the match. Disallowed binds and scripts are:
- 6.2.21 – Any ‘exec’ or ‘vstr’ bind (this does not include anything related to demos or demo players).
- 6.2.22 – Any ‘cmdcur’ bind.
- 6.2.23 – Any script including ‘lookdown’.
- 6.2.24 – Any bind including ‘rate’ cannot have a value outside 25000.
- 6.2.25 – Any bind including ‘com_maxfps’ cannot have a value below 40 or above 250.
- 6.2.26 – Any bind including ‘attack’ cannot be combined with any other command.
- 6.2.27 – Any bind including ‘stand’ or ‘crouch’ cannot be combined with other command.
- 6.2.28 – Any bind including ‘left’ or ‘right’ cannot be combined with other commands.
6.2.3 – All binds/scripts that are not covered above will be reviewed on a case-by-case basis to see if they do give an advantage.
6.2.4 – Any abuse of the two monitor bug will be reviewed case-by-case by the cup vcod.gg Admin, Supervisors and Conflict Team. You should avoid using this bug at all costs, as it may result in the player receiving a yellow card and the clan forfeiting the match.
6.3 – Match Conflicts
6.3.1 – The match conflict system functions as a court room with vcod.gg Admin, Supervisors and Conflict Team acting as judges. A match conflict can be made on Discord when the result entered by one clan is not accepted by the other.
6.3.2 – In the conflict, both sides must explain the problem in a short but clear and complete way. Both sides should state the match result they claim, and only relevant and proven facts may be mentioned.
6.3.3 – All proof and information on the match should be written within the ticket posted in the #vcod_conflicts board on Discord.
6.3.4 – Examples of valid proof are: demos, in-game screenshots and server logs that were obtained from a neutral party. If a demo is used as proof of cheating or other malicious actions, you must specify the exact moment(s) (down to the exact minute and second) where the cheating occurred, or you will get a conflict loss. The vcod.gg Admin, Supervisors and the Conflict Team will not look at entire demos.
6.3.5 – If a clan does not give any new relevant information within 48 hours since the last reply, it will be considered they have nothing more to add.
7. Disallowed Jumps and Exploits
7.1 – Jumps and Exploits Abuse
7.1.1 – Arnhem
- 7.1.1 – Jump to church.
- 7.1.2 – Glitching behind the buildings in the allies spawn.
7.1.2 – Brecourt
- 7.1.21 – Shooting through spawn corner bush to kill mid bunker.
- 7.1.22 – Shooting over any bush that separates the centre of the map.
- 7.1.23 – Shooting through the B bomb to small ruins where you cannot be hit.
7.1.3 – Carentan
- 7.1.31 – Jumping onto the roof in the back of MG garden.
- 7.1.32 – Jumping onto the top roof of sniper house.
7.1.4 – Cassino
- 7.1.41 – Planting on top of the lanterns on the B bomb.
- 7.1.42 – Glitching and shooting through the closed windows in mid house.
- 7.1.43 – Going to the roofs in west ruins and spawn buildings.
7.1.5 – Dawnville
- 7.1.51 – Jumping onto the stick outside of orphanage to see back grave.
- 7.1.52 – Jumping onto the German FPS roof.
- 7.1.53 – Jumping onto the B building roofs.
- 7.1.54 – Jumping onto the archway near white house.
- 7.1.55 – Jumping onto the sign next to the allies tank is allowed, the ruins is not.
- 7.1.56 – Shooting through the orphanage bush.
- 7.1.57 – Abusing the bush in grave to see into orphanage.
- 7.1.58 – Abusing the window in back sniper to see through walls.
7.1.6 – Harbor
- 7.1.61 – Jumping out of the map.
- 7.1.62 – Abusing a bug bottom police to become unhittable.
- 7.1.63 – Using prone on the Russian ramp into ramproom to become unhittable.
7.1.7 – Hurtgen
- 7.1.71 – Using prone on the rock above A bunker to become unhittable.
7.1.8 – Neuville
- 7.1.81 – Jumping onto the outer ledge of jumphouse.
- 7.1.82 – Jumping onto the bookstore roof.
- 7.1.83 – Jumping onto the American spawn house roof.
- 7.1.84 – Jumping out of the map.
- 7.1.85 – Jumping on top of A mg.
- 7.1.86 – Jumping onto the ledge outside of butchers.
- 7.1.87 – Jumping onto mayors roof.
- 7.1.88 – Jumping onto the roof of red house.
- 7.1.89 – Planting inside the B bomb.
7.1.9 – Peaks
- 7.1.91 – Glitching to top barn.
- 7.1.92 – Jumping on top of the snow hill near B bomb.
- 7.1.93 – Jumping on top of the fences near B bomb.
- 7.1.94 – Jumping on top of dog house near B bomb.
- 7.1.95 – Headglitch in burned house.
- 7.1.96 – Proning in the window frame at MG.
- 7.1.97 – Jumping to burned from A flak cannon.
7.2.0 – Powcamp
- 7.2.01 – Jumping onto the German north roof.
- 7.2.02 – Jumping onto the Russian south roof from the boxes.
- 7.2.03 – Jumping onto the German spawn hut roof.
- 7.2.04 – Jumping from the mid tower to the roof next to B bomb.
7.2.1 – Railyard
- 7.2.11 – Jumping onto the ruins roof.
- 7.2.12 – Jumping onto the ledge besides the trains at B.
- 7.2.13 – Jumping onto the B south hut roof from the ledge (hotel jump is allowed).
- 7.2.14 – Hiding behind the spawn hut where your model becomes invisible.
- 7.2.15 – Shooting through the A tank.
7.2.2 – Sicily
- 7.2.21 – Jumping to the roofs.
- 7.2.22 – Glitching under the map.
- 7.2.23 – Jumping over the wall in the village to get behind the houses.
- 7.2.24 – Jumping into the trees on A bomb.
- 7.2.25 – Jumping out of the map.
- 7.2.26 – Jumping on the rocks outside B on water side.
- 7.2.27 – Proning on top of the rocks to head glitch.
7.2.3 – Stalingrad
- 7.2.31 – Jumping into the glitch room.
- 7.2.32 – Shooting through the A barrels.
- 7.2.33 – Using prone behind the little boxes in mid tunnel to go underground.
7.2.4 – Stanjel
- 7.2.41 – Jumping out of the map.
- 7.2.42 – Glitching under the map.
- 7.2.43 – Jumping to other roofs from the balcony.
- 7.2.44 – Jumping on top of the green house from the bush.
- 7.2.45 – Jumping into the big tree on east defence spawn.
7.2.5 – Streets
- 7.2.51 – Jumping to the roofs from balcony house.
7.2.6 – Tigertown
- 7.2.61 – Jumping onto the ledge in A alley.
- 7.2.62 – Jumping into the bathroom in top hotel.
- 7.2.63 – Using the glitch box near the B bomb to become unhittable.
8. Changes and Expectations
8.1 – Changes and expectations
8.1.1 – These rules are subject to change at any time. All clans are expected to know the rules; not knowing them is no valid excuse for not following them.
8.1.2 – Any issue that affects a vCoD.gg Admin, Supervisor or referee's clan may not be handled by that person.