BROGGUA Tournament Regulations
Edition 1.1 · in force from 5 October 2026
1General provisions
1.1These regulations apply to all BROGGUA tournaments. By submitting an entry, a team and each of its players confirm that they have read and accept them.
1.2An individual tournament may set additional conditions. They are published on its page before registration opens and prevail over these regulations in the part they concern.
1.3Entry fee. Participation is free of charge. The exception is tournaments for which a fee is stated explicitly in the announcement and on the tournament page before registration opens. If such a tournament is cancelled (Art. 1.8), fees are refunded.
1.4Administration. The administration is the organiser and the tournament referees appointed by them. Decisions on match results, sanctions and protests are taken by the head referee of the tournament; their name or nickname is announced on the tournament page before the start.
1.5These regulations are applied by their meaning, not by their letter. An act not described here expressly, but aimed at gaining an advantage by circumventing the regulations or at exploiting an imprecise wording, is a violation to the same extent as one expressly prohibited.
1.6Decisions of the administration are binding during the tournament. Disagreement is handled under Section 10, not during a match.
1.7These regulations may change between tournaments. The edition in force at the moment registration for a tournament opens applies to that tournament.
1.8Force majeure. If a tournament or part of it cannot be held for reasons beyond the control of the parties — a power outage, an air raid alert, a failure of the game servers or of the platform — the administration reschedules or cancels the affected matches. Stages already played remain valid. The order of prize payment in the event of cancellation is announced separately and cannot be worse than proportional to the stages played.
2Eligibility and roster
2.1Age. Persons aged 16 and over are eligible. A player under 18 participates with the consent of a parent or guardian; the same consent is required for the payment of prize money.
2.2Participation requires an account on broggua.com, a submitted and confirmed entry, and a valid PUBG account for every player.
2.3The entry states the PUBG in-game nickname, Discord and country of every player.
2.4The main roster is 4 players (1 for solo tournaments, 2 for duo).
2.5Substitutes are registered in addition to the main roster before the tournament starts. Only a person listed on the roster may play a match.
2.6Roster during the tournament. The registered roster applies for the whole tournament, including between stages. A roster change after the tournament has started is possible only with the agreement of the administration and is announced before the team's next match.
2.7A player on the list of banned persons does not pass onto a roster; an entry containing their nickname is rejected.
2.8Participation by a person banned from BROGGUA tournaments under another account or another nickname results in disqualification of the team from the current tournament and annulment of its results. A ban from future tournaments is applied under the rule of Art. 9.4.
2.9The captain ensures the team's presence in the organiser's Discord for the duration of the tournament.
3Format and schedule
3.1The tournament mode — FPP or TPP, in squad, duo or solo — is stated on the tournament page.
3.2The maps, the number of matches and the stage structure are announced before the tournament starts.
3.3A team is assigned a slot number; it is the same in the lobby and on the broadcast.
3.4Start times are given in Kyiv time (EET/EEST, UTC+2, UTC+3 in summer) — exactly as the tournament page displays them.
3.5A team must be in the lobby 15 minutes before the match starts. Arriving after that deadline but before the match begins is not a no-show.
3.6No-show. A no-show is the absence of the entire roster of a team from the lobby at the moment the match starts.
3.7Consequences of a no-show. A first no-show means a match result of 0 points. A second no-show means removal of the team from the tournament. A no-show without notifying the administration (Art. 3.9) means removal from the tournament immediately.
3.8Incomplete roster. A team may play with an incomplete roster. Players who did not join do not take part in the match; the match counts for the team.
3.9The captain informs the administration of a delay, a substitution or an inability to play before the match starts.
4Scoring
4.1Unless stated otherwise, the SUPER 22 system applies.
| Place | Points | Place | Points |
|---|---|---|---|
| 1 | 10 | 5 | 3 |
| 2 | 6 | 6 | 2 |
| 3 | 5 | 7 | 1 |
| 4 | 4 | 8 | 1 |
4.2Each kill gives 1 point. Places 9th and below give no placement points; kills count regardless of place.
4.3A team's result in a stage is the sum of its points across all matches of that stage.
4.4Other scoring systems (WINS ONLY — points for a match win only, kills do not count; WWCD — a bonus for a win, with kills making the main difference) apply only if stated on the tournament page.
4.5Penalty points imposed under Section 9 are deducted from the result of the stage in which the violation occurred.
4.6Tied points. Teams with an equal points total are separated by the first criterion that distinguishes them. The higher place goes to the team with:
- more placement points across the whole stage;
- more points in the last match played;
- a better place in the last match played;
- more match wins;
- more kills.
This is the SUPER Global Point Rule — the PUBG Esports standard. It applies with any scoring system, including SUPER 22.
The official standard has damage dealt in fourth position. We do not store it, so match wins and kills take its place.
4.6.1A different order may apply in an individual stage if it is announced on the tournament page before that stage begins.
4.6.2A decision of the administration on a specific tie prevails over these criteria and is announced with its grounds.
4.7Finality of results. The results of a stage are deemed final 48 hours after it ends. Until that deadline the administration corrects any accounting errors found; afterwards only on newly discovered circumstances under Section 10.
5Match conduct
5.1The lobby password is not passed to anyone outside the registered roster.
5.2A player joins the lobby under the nickname stated in the entry.
5.3Only the administration calls a pause. A pause request is made through Discord, not in the in-game chat.
5.4A match is not replayed. The only exceptions are: the whole lobby dropped; a technical failure made holding the match impossible; the wrong mode or the wrong map was selected; the failure or mistake was caused by the organiser — in particular a wrong password, address or lobby setting.
5.5Players failing to join the lobby, an individual disconnect, lag or a game failure of a single player are not grounds for a restart — regardless of how many players are affected, as long as the cause is not on the organiser's side.
5.6Decisions on a pause and on a replay are taken by the administration.
6Fair play
6.1Third-party software. Any programs, scripts and game modifications that confer an advantage are prohibited.
6.1.1Macros. Macros of any kind are prohibited — in particular recoil compensation, automatic or accelerated fire, and a sequence of actions on a single keypress. The prohibition does not depend on whether the macro conferred an advantage in a particular match.
6.2Collusion with an opponent (teaming). Agreements not to open fire, to divide the zone, to surrender positions or to play for another team's result are prohibited. Both teams bear responsibility.
6.3Use of a broadcast (stream sniping). Using any broadcast to obtain information about opponents during a match is prohibited.
6.4Use of game bugs. Knowingly exploiting defects of the game is prohibited. A player who discovers a defect is obliged to report it to the administration.
6.5Account sharing. Playing from an account not listed on the roster, including playing on behalf of another player, is prohibited.
6.6Verification by recording. Where there is reasonable suspicion, the administration has the right to demand a full game recording (POV / demo) from a player or a team at any moment of the tournament. Failure to provide a recording without good reason is a separate violation (see Section 9), not automatically a violation of Art. 6.1.
6.7Real-time verification. During the tournament an administrator has the right to join the team's voice channel and demand a share of the entire screen — not of a single window or of the game. The team provides access to the channel and complies without delay.
6.8Limits of verification. Verification lasts only as long as necessary and is confined to the duration of the tournament. What is seen during verification is not disclosed.
6.8.1Recording of verification. The administration may record the screen share, having given notice before the verification begins. Without notice no recording is made. Refusing verification after such notice is treated as refusing verification as such.
6.8.2A recording is kept until the case within which it was made is concluded and is not published. After the case is concluded it is deleted, unless it is evidence in an ongoing case.
7Conduct and language
7.1Respect for opponents, the administration and viewers is mandatory, regardless of the result.
7.2Insults, threats, harassment and hate speech are prohibited — in the game, in Discord, in comments on the site and on the broadcast.
7.3Conduct incompatible with the principles of sportsmanship and fair play is prohibited, even where it is not named expressly in these regulations. The administration determines its gravity, taking intent and repetition into account.
7.4Disrespect towards the administration. Insulting or pressuring an administrator, contesting their decisions in the lobby or in general channels instead of under Section 10, and acts obstructing the conduct of a match are prohibited. Disagreement with a decision is not a ground for failing to comply with it during the tournament.
7.5The language of in-game text chats is any language except Russian.
7.6In-game All Talk is switched off. Team communication is not restricted.
7.7The language of broadcasts is Ukrainian; English where an English-speaking caster is available. Official announcements are published in a language understood by the tournament's field of participants.
7.8Team name, tag and logo. A team's name, tag and logo appear in the lobby, the standings, the broadcast and announcements, so they must be fit for publication. Joke ("troll") names, offensive or obscene names, tags and logos are prohibited, as are those containing hate speech, political or commercial advertising, or impersonating another team or organisation. The administration may require a change; until it is made, the team competes under a technical name and without a logo.
8Restrictions related to the aggressor state
8.1Ineligibility. Citizens and permanent residents of Russia and Belarus are not eligible to participate. The administration may extend this restriction to other states, giving notice before registration for a tournament opens.
8.2Confirmation of country. The country is stated in the entry separately for each player. Stating a false country results in disqualification of the team from the current tournament and annulment of its results; a ban from future tournaments is applied under the rule of Art. 9.4.
8.3Systematic and knowing joint play with players from Russia, as well as playing on Russian servers and taking part in Russian tournaments, is prohibited.
8.4What counts as systematic. Systematic means repeated play, not an isolated random match. The assessment is made by the administration on the basis of evidence, taking into account the number of matches and whether the player could have been unaware of the opponents' composition or of the tournament's origin.
8.5Facts established under Art. 8.3–8.4 within the last 3 months result in disqualification of the player and annulment of their results.
8.6Concealing a region. Concealing a country or region by technical means (VPN, proxy) in order to circumvent the restrictions of this Section is prohibited.
8.7Verification procedure. Verification is carried out manually — from a player's profile, a message or other evidence. There is no automated control: our data covers only matches of our own tournaments.
9Sanctions
9.1Violations are sanctioned according to the table below. The decision to apply a sanction and, where the table gives a range, the specific measure are taken by the administration, taking into account intent, consequences and repetition.
| Violation | Sanction |
|---|---|
| Russian in text chat (Art. 7.5) | −2 points |
| All Talk voice communication (Art. 7.6) | −2 points |
| Insults, threats, hate speech (Art. 7.2) | from −2 points to disqualification from the tournament |
| Disrespect towards the administration (Art. 7.4) | from −2 points to disqualification from the tournament |
| Unfit name, tag or logo (7.8) | change required; until then a technical name without a logo; on refusal the application is rejected |
| Collusion with an opponent (Art. 6.2) | disqualification from the tournament for both teams |
| Refusal of verification (Art. 6.6, 6.7) | −5 points; on a repeated refusal — disqualification from the tournament |
| Third-party software (Art. 6.1), account sharing (Art. 6.5) | player — indefinite ban; team — disqualification from the tournament and annulment of results |
| Circumventing a ban (Art. 2.8) | disqualification of the team from the tournament, annulment of results |
| False country in the entry (Art. 8.2) | disqualification of the team from the tournament, annulment of results |
| Concealing a region (Art. 8.6) | disqualification of the player, annulment of their results |
| Failure by a captain to pay out prize money to the roster (Art. 12.4) | ban of the captain from future tournaments |
9.2In case of repetition and aggravating circumstances the administration applies the next measure up in severity.
9.3Whom it concerns. A sanction is applied to the player who committed the violation, or to the team — in accordance with the table in Art. 9.1. Where the table does not determine this, the administration determines the addressee of the sanction.
9.3.1A team is disqualified from the current tournament with annulment of its results where the violation affected its result. The ground here is not collective guilt but the impossibility of separating the offender's contribution from the team's result.
9.3.2Recalculation of places. The places of the other teams in matches in which a disqualified team took part are recalculated as if it had not played in them: every team that finished below it moves up by the corresponding number of positions, and placement points are awarded from the new rank.
9.4Ban from future tournaments. A ban from future tournaments is applied to the offending player. It is applied to the other players of the team only where they knew or ought to have known of the violation. This rule applies to all sanctions of these regulations, in particular those of Art. 2.8 and 8.2.
9.5Recording. Every sanction is recorded with its grounds and a reference to the clause of these regulations, and the reason is communicated to the team.
10Protests and appeals
10.1A protest is filed by the captain through the organiser's Discord within 24 hours after the match ends.
10.2Evidence is attached to the protest: a recording, a clip, a screenshot or a match number. A protest without evidence is not considered.
10.3Time for consideration. The administration considers a protest before the next match of the stage begins, or, where the stage has ended, within 48 hours of filing.
10.4A decision of the administration on a protest is final. A review is possible only on newly discovered circumstances.
10.5A disqualification under Art. 6.1 is not subject to appeal.
11Broadcast, imagery and data
11.1Matches are broadcast with a delay. The size of the delay is a protection against violations of Art. 6.3 and is not reduced at the request of teams. A player running their own broadcast of a match is obliged to keep a delay of at least 5 minutes.
11.2Participation in a tournament constitutes consent to the use of gameplay, nickname, team name, tag and logo in broadcasts, on the organiser's site and in its social media.
11.3Personal data. The organiser processes the data stated in the entry — in-game nickname, Discord, country, and for the payment of prize money also payment details — solely for holding tournaments, keeping statistics and making payments. The data is not transferred to third parties except in cases provided for by law.
11.4A player has the right to obtain information about their data, to correct it or to demand its deletion by contacting the organiser. Deletion does not extend to published match results and final standings — they are the history of the competition.
12Prize money
12.1The prize pool and the order of its distribution are announced before the tournament starts. Payment is made within one calendar month after the tournament ends.
12.2Prize money is transferred to the team captain, who submits the payment details. Where the captain is under 18, the details are submitted by their father, mother or guardian.
12.3Where the captain is personally disqualified, the prize money is transferred to another player of the roster named to the administration by the team.
12.4Further distribution among the players is the captain's responsibility. Failure to share the prize money with the roster is a violation of these regulations.
12.5Where details are not submitted. Payment details are submitted within 14 days after the tournament ends. If the captain has not submitted them, the administration approaches the other players of the roster. Prize money not claimed within 3 months goes to the prize pool of future tournaments.
12.6A team disqualified from a tournament receives no prize money.