Testament Cup v2.0 · Counter-Strike 2
Rules and Regulations
Organised by Proving Grounds. Please review the complete rules before registering or approving a player’s participation.
Jump to a section
- 1. GAME VERSION
- 2. TOURNAMENT STRUCTURE
- 3. MATCH FORMAT AND WIN CONDITIONS
- 4. MAP POOL
- 5. MAP VETO AND SIDE SELECTION
- 6. PLAYER ELIGIBILITY
- 7. PARTICIPANTS UNDER 16
- 8. TEAM REGISTRATION
- 9. TEAM ROSTERS
- 10. TEAM CAPTAIN AND VICE-CAPTAIN
- 11. ONLINE MATCH REPORTING
- 12. LAN SETUP
- 13. MATCH READINESS AND LATENESS
- 14. PLAYER COMMUNICATION
- 15. PUBLIC CHAT
- 16. SCRIPTS, MACROS, SOFTWARE AND CONFIGURATIONS
- 17. CHEATING AND COMPETITIVE INTEGRITY
- 18. PLAYER DISCONNECTIONS
- 19. TECHNICAL PAUSES
- 20. TACTICAL PAUSES
- 21. SERVER AND TECHNICAL FAILURES
- 22. BUGS, GLITCHES AND EXPLOITS
- 23. CODE OF CONDUCT
- 24. ONLINE CONDUCT
- 25. MATCH DISPUTES
- 26. EVIDENCE AND INVESTIGATIONS
- 27. INFRACTION SYSTEM
- 28. MAJOR INFRACTIONS
- 29. PENALTIES
- 30. SUSPENSIONS AND BANS
- 31. MATCH RESULTS
- 32. PLAYER WITHDRAWAL AND MATCH ABANDONMENT
- 33. PRIZES
- 34. PHOTOGRAPHY, RECORDING AND BROADCASTING
- 35. PERSONAL DATA
- 36. CONFIDENTIAL INFORMATION
- 37. VENUE AND EQUIPMENT CONDUCT
- 38. HEALTH AND SAFETY
- 39. FORCE MAJEURE AND EVENTS OUTSIDE THE ORGANISER’S CONTROL
- 40. RULE CHANGES
- 41. UNFORESEEN CIRCUMSTANCES
- 42. TOURNAMENT ADMINISTRATOR DECISIONS
- 43. GOVERNING LAW
- 44. SEVERABILITY
- 45. ACCEPTANCE OF THE RULES
- TOURNAMENT CONTACT
Organised by Proving Grounds
Game: Counter-Strike 2
Rules Version: 2.0
These Rules & Regulations (“Rules”) govern participation in Testament Cup v2.0 (“Tournament”), organised by Proving Grounds (“Organiser”).
By registering for or participating in the Tournament, each player, substitute, coach, manager and team representative (“Participant”) confirms that they have read, understood and agreed to comply with these Rules.
The Tournament Committee and authorised Proving Grounds administrators (“Tournament Administrators”) are responsible for interpreting and enforcing these Rules.
1. GAME VERSION
The Tournament will be played using the latest stable official version of Counter-Strike 2 available at the time of the Tournament, unless otherwise announced by the Tournament Committee.
If a Counter-Strike 2 update occurs shortly before or during the Tournament, the Tournament Committee may:
- continue using the existing Tournament version where technically possible;
- adopt the updated version;
- temporarily prohibit a newly introduced feature, weapon, map or mechanic;
- modify relevant server or game settings; or
- take other reasonable measures necessary to maintain competitive integrity.
Material changes will be communicated to affected teams where reasonably practicable.
2. TOURNAMENT STRUCTURE
Testament Cup v2.0 will be conducted as a two-stage Tournament.
Group Stage
Teams will be divided into:
2 groups of 8 teams
The Group Stage will use a:
Best-of-One (BO1) Double-Elimination format
The top four teams from each group will qualify for the Playoffs.
Playoffs
The eight qualifying teams will progress to a:
Best-of-One (BO1) Single-Elimination bracket
unless otherwise announced by the Tournament Committee.
Third-Place Match
Best-of-Three (BO3)
Grand Final
Best-of-Three (BO3)
The Tournament Committee may adjust the Tournament structure where reasonably required because of:
- team withdrawals;
- disqualifications;
- technical failures;
- venue restrictions;
- scheduling constraints;
- changes in the number of participating teams;
- circumstances outside the Organiser’s reasonable control; or
- other matters materially affecting Tournament operations.
Where practicable, affected teams will be informed before the relevant stage begins.
3. MATCH FORMAT AND WIN CONDITIONS
Counter-Strike 2 competitive match rules will apply.
Unless otherwise announced:
- Regulation consists of 24 rounds.
- Teams play 12 rounds on each side.
- The first team to reach 13 rounds wins the map in regulation.
If the score reaches 12–12, overtime will be played.
Overtime
Unless otherwise announced:
- each overtime set consists of 6 rounds;
- teams play 3 rounds on each side;
- overtime starting money is $10,000; and
- additional overtime sets will be played until a winner is determined.
Server configuration will follow the Tournament’s approved competitive Counter-Strike 2 configuration.
The Tournament Committee may update technical server settings where necessary to remain compatible with the current version of Counter-Strike 2.
4. MAP POOL
The Tournament will use the Counter-Strike 2 Active Duty competitive map pool applicable to Testament Cup v2.0.
At the time of publication, the map pool is:
- Ancient
- Anubis
- Cache
- Dust II
- Inferno
- Mirage
- Nuke
If Valve changes the Active Duty map pool before the Tournament begins, the Tournament Committee may update this list.
Once the Tournament has begun, the map pool will normally remain unchanged for the remainder of the Tournament unless a serious technical or competitive issue requires otherwise.
5. MAP VETO AND SIDE SELECTION
Map vetoes will be conducted through the official Proving Grounds Tournament communication channel or on-site for LAN matches.
Only the nominated Team Captain, Vice-Captain or an approved team representative may conduct the veto.
Teams must attend and complete their veto when instructed.
Failure to attend a scheduled veto may result in the opposing team receiving veto priority or the Tournament Administrator completing the veto administratively.
Once a veto has been completed and confirmed, it may not be changed except to correct an administrative error or with Tournament Administrator approval.
BO1 Veto
Unless otherwise announced:
- Team A bans one map.
- Team B bans one map.
- Team A bans one map.
- Team B bans one map.
- Random Draw from 3 leftovers Maps
Side selection will be determined by a knife round, unless otherwise announced.
The winner of the knife round may select its starting side.
BO3 Veto
Unless otherwise announced:
- Team A bans one map.
- Team B bans one map.
- Team A picks Map 1.
- Team B selects its starting side on Map 1.
- Team B picks Map 2.
- Team A selects its starting side on Map 2.
- Random Draw from 3 leftover Maps
Side selection for Map 3 will be determined by a knife round unless otherwise announced.
6. PLAYER ELIGIBILITY
All Participants must satisfy the Tournament’s published eligibility requirements.
Participants must:
- use their own valid Steam account;
- provide accurate registration information;
- provide the requested Steam ID 64;
- meet any applicable age requirements;
- comply with Valve’s applicable rules and Terms of Service; and
- not be subject to a relevant competitive ban that makes them ineligible to participate.
A Steam ID 64 submitted during registration must consist of the required 17 digits.
The Organiser may request reasonable evidence to verify:
- identity;
- age;
- nationality;
- ownership of a registered Steam account;
- team membership; or
- another eligibility requirement.
Providing false information or competing under another person’s identity or Steam account may constitute a Major Infraction.
7. PARTICIPANTS UNDER 16
Participants under 16 years of age must obtain permission from a parent or legal guardian before participating.
The Organiser may require the parent or guardian to complete a consent form or provide confirmation of consent.
Where required, the consent may cover matters including:
- participation in the Tournament;
- participation in online and/or LAN matches;
- photography and video recording;
- livestreaming and Tournament broadcasts;
- reasonable use of the Participant’s gamer tag, image and likeness in Tournament coverage; and
- emergency contact information.
A minor may not participate where required parental or guardian consent has not been received.
The Organiser may require additional consent or documentation where reasonably necessary.
8. TEAM REGISTRATION
All team members must be registered through the official Testament Cup registration process.
A Tournament roster may consist of:
- 5 starting players; and
- up to 2 optional reserve players.
Teams must nominate:
- one Team Captain; and
- one Vice-Captain.
The Captain and Vice-Captain must provide valid contact details and remain contactable through the official Tournament communication channel.
Only registered and approved Participants may compete.
Registration does not guarantee acceptance into the Tournament until confirmed by the Organiser.
9. TEAM ROSTERS
A player may only represent one team during Testament Cup v2.0.
A player who has participated in a Tournament match for one team may not subsequently compete for another team in the same Tournament.
Registered reserve players may substitute for starting players subject to these Rules.
Teams wishing to make a substitution should notify a Tournament Administrator at least 10 minutes before the scheduled match, wherever reasonably possible.
Emergency roster changes outside the registered roster may only be made with prior approval from the Tournament Committee.
Approval is not guaranteed.
For teams that qualify for the Playoffs, at least three members of the starting roster that qualified the team must participate in the Playoffs.
A player who qualifies for the Playoffs with one team may not play for another team.
Tournament Administrators may conduct identity and Steam account verification at any stage.
10. TEAM CAPTAIN AND VICE-CAPTAIN
The Team Captain is the primary point of contact between the team and Tournament Administrators.
The Vice-Captain will act as the alternative point of contact where the Captain is unavailable.
The Captain or Vice-Captain is responsible for:
- receiving Tournament communications;
- attending map vetoes;
- confirming team readiness;
- communicating technical issues;
- submitting disputes;
- participating in coin tosses or selection procedures;
- providing requested team information; and
- attending reasonable Tournament interviews where required.
Official Tournament communications sent to the Captain or Vice-Captain will be treated as having been communicated to the team.
It is the team’s responsibility to monitor official Tournament channels.
11. ONLINE MATCH REPORTING
For online matches, Team Captains or Vice-Captains must report to the designated Proving Grounds Discord channel at least 20 minutes before the scheduled match.
This period may be used for:
- check-in;
- map veto;
- server assignment;
- administrative checks; and
- technical preparation.
Players must:
- ensure Counter-Strike 2 is updated;
- ensure Steam is operational;
- ensure required anti-cheat software is operating where applicable;
- join the assigned server promptly; and
- be ready to compete at the scheduled start time.
Teams should not wait until the scheduled match time to begin troubleshooting.
12. LAN SETUP
For LAN matches, players will normally receive up to 15 minutes to:
- connect peripherals;
- configure permitted settings;
- install approved drivers where necessary; and
- confirm equipment functionality.
Players are responsible for ensuring that personal equipment is functional and compatible.
Where reasonably available, the Organiser may provide replacement equipment where a Participant’s peripheral proves incompatible or fails.
An identical replacement is not guaranteed.
Participants may not:
- install unauthorised software;
- connect unauthorised storage devices;
- change Tournament-controlled network settings;
- interfere with another Participant’s equipment;
- modify Tournament-controlled system settings without permission; or
- attempt to bypass Tournament security measures.
13. MATCH READINESS AND LATENESS
Teams must be ready to compete at their scheduled match time.
A team that is not ready may receive a Minor Infraction.
Unless otherwise authorised, a team that remains unable to begin 15 minutes after its scheduled match time may receive a match forfeit.
Tournament Administrators may waive or extend this period where a delay is caused by:
- Tournament equipment;
- Tournament servers;
- Tournament networks;
- Tournament administration;
- venue operations;
- a widespread Steam or Counter-Strike 2 service issue; or
- another circumstance outside the team’s reasonable control.
Deliberately causing or prolonging a match delay may result in additional penalties.
14. PLAYER COMMUNICATION
During a live match, players may only receive communication permitted under the Tournament rules.
Players may communicate with:
- active teammates;
- an authorised coach during approved periods, where coaches are permitted; and
- Tournament Administrators.
Participants must not obtain tactical information from:
- spectators;
- livestreams;
- observer feeds;
- eliminated or unauthorised players;
- external messaging applications; or
- other sources not normally available during competitive play.
For LAN matches, Tournament Administrators may require Participants to disable Steam communications or other external communication tools.
15. PUBLIC CHAT
During live matches, public in-game chat should primarily be used for legitimate match communication.
Where a technical or administrative issue occurs, the Captain or Vice-Captain should communicate with the Tournament Administrator.
Participants must not use public chat to:
- harass opponents;
- spam excessively;
- disclose a server password;
- promote unauthorised websites, products or services;
- impersonate Tournament staff; or
- deliberately interfere with Tournament operations.
16. SCRIPTS, MACROS, SOFTWARE AND CONFIGURATIONS
Scripts, macros, software, hardware modifications or configurations that provide an unfair competitive advantage are prohibited.
Ordinary Counter-Strike 2 binds and configurations are permitted unless they:
- automate gameplay in a prohibited manner;
- execute multiple competitive actions in a manner not normally available to a player;
- exploit a game vulnerability; or
- have otherwise been prohibited by Valve or the Tournament Committee.
Prohibited tools include, but are not limited to:
- aimbots;
- wallhacks;
- trigger bots;
- radar hacks;
- unauthorised automation;
- information-revealing software;
- game-file manipulation intended to provide an unfair advantage; and
- other software or hardware designed to compromise competitive integrity.
Tournament Administrators may inspect Tournament-controlled equipment, software, configurations, running processes and relevant game files when reasonably necessary to investigate suspected cheating.
Where Participants use their own equipment, reasonable inspection requirements may also be imposed as a condition of participation.
Refusing to cooperate with a legitimate competitive-integrity investigation may result in disciplinary action.
17. CHEATING AND COMPETITIVE INTEGRITY
All Participants must compete fairly.
The following are considered serious competitive-integrity offences.
Cheating
Using unauthorised software, hardware, scripts, exploits or other methods to obtain an unfair competitive advantage.
Ghosting
Providing, receiving or attempting to obtain information about an opponent’s position, strategy or game state through information that should not be available during normal competitive play.
Stream Sniping
Watching, receiving or acting upon information from a Tournament broadcast, livestream or observer feed during the affected match.
Account Sharing or Impersonation
Allowing another person to compete using a registered Participant’s account or identity.
Collusion
Cooperating with another Participant or team to manipulate a match, bracket, ranking or Tournament result.
Match-Fixing
Deliberately losing, underperforming, manipulating scores or agreeing to predetermine an outcome.
Bribery
Offering, requesting or accepting money, gifts, benefits or other consideration in exchange for influencing a Tournament result.
Betting
Participants may not place or facilitate bets on matches in which they participate or where they possess confidential competitive information.
Unauthorised Assistance
Receiving tactical or competitive assistance from a person who is not permitted to communicate with the team at that time.
Attempting to commit a competitive-integrity offence may be penalised even where the attempt is unsuccessful.
Serious competitive-integrity offences may result in immediate disqualification without a prior warning.
18. PLAYER DISCONNECTIONS
If a player disconnects, the affected team must notify a Tournament Administrator promptly.
Where supported by the Tournament server, the match may be paused during the freeze time of the next available round.
The disconnected player must attempt to reconnect promptly.
Players must not deliberately disconnect to obtain:
- a pause;
- tactical discussion time;
- a rollback; or
- another competitive advantage.
The Tournament Administrator will determine whether:
- play continues;
- a pause is permitted;
- a backup is restored;
- a round is replayed;
- a map is restarted; or
- another remedy is appropriate.
A rollback will not normally be granted after meaningful player-versus-player damage has occurred during the affected round.
The Tournament Administrator may make an exception where a serious Tournament-controlled technical failure makes this necessary for competitive fairness.
19. TECHNICAL PAUSES
Technical pauses may only be requested for legitimate technical issues, including:
- disconnections;
- game crashes;
- equipment failure;
- server failure; or
- network problems.
The affected team must provide the reason for the pause when requested.
Unless otherwise authorised, a technical pause may last for up to 10 minutes.
A Tournament Administrator may extend the period where:
- active troubleshooting is taking place;
- Tournament equipment caused the problem;
- a Tournament server or network caused the problem;
- an external service outage is involved; or
- competitive fairness reasonably requires additional time.
Abuse of a technical pause may result in an infraction.
20. TACTICAL PAUSES
Each team may use up to two tactical pauses of 45 seconds during regulation, unless otherwise announced.
Tactical pauses must be initiated through the Tournament-approved procedure.
They may not be used to:
- deliberately waste time;
- disrupt an opponent;
- obtain additional unauthorised communication;
- conceal a technical issue; or
- circumvent the permitted pause allocation.
Misuse may result in a Minor Infraction.
21. SERVER AND TECHNICAL FAILURES
If a Tournament server, network, Tournament PC or other Tournament-controlled system experiences a significant failure, a Tournament Administrator may:
- pause the match;
- restore an available backup;
- replay a round;
- restart a map;
- relocate players to another server;
- reschedule the match; or
- take another reasonable action necessary to restore competitive fairness.
Teams must not independently restart, abandon, replay or agree to alter the result of a Tournament match without Tournament Administrator approval.
22. BUGS, GLITCHES AND EXPLOITS
Knowingly abusing bugs, glitches, errors or unintended game mechanics to obtain an unfair competitive advantage is prohibited.
Players who identify a potentially serious exploit should report it privately to a Tournament Administrator.
Visible map-loading or rendering issues should be reported before the match begins where reasonably possible.
If both teams knowingly begin a match without reporting a visible issue, the Tournament Administrator may determine that the match should continue.
However, the Tournament Administrator retains the right to intervene where the issue materially compromises competitive integrity.
The Tournament Committee may prohibit a particular exploit, location, mechanic or interaction at any time.
23. CODE OF CONDUCT
Participants must behave respectfully towards:
- opponents;
- teammates;
- Tournament Administrators;
- production personnel;
- volunteers;
- venue staff;
- partners;
- sponsors;
- spectators; and
- members of the public.
Prohibited conduct includes:
- harassment;
- bullying;
- discriminatory or racist remarks;
- hateful conduct;
- threats;
- intimidation;
- targeted personal abuse;
- sexual harassment;
- physical aggression;
- deliberate disruption;
- vandalism;
- deliberate damage to equipment; and
- behaviour that creates a material safety concern.
Competitive banter is not automatically prohibited.
However, Tournament Administrators may intervene where conduct becomes abusive, discriminatory, threatening, excessive or materially disruptive.
Participants must comply with reasonable instructions from Tournament Administrators, security personnel and venue staff.
24. ONLINE CONDUCT
These standards also apply to Tournament-related activity through:
- Discord;
- game chat;
- livestream chat;
- social media;
- messaging platforms; and
- official Tournament channels.
Participants must not:
- threaten other Participants or Tournament staff;
- intentionally disclose another person’s private personal information;
- impersonate a Tournament Administrator;
- fabricate an official Tournament announcement;
- encourage harassment of another Participant; or
- deliberately interfere with Tournament administration.
Participants are free to criticise Tournament decisions.
Criticism does not permit threats, harassment, discriminatory conduct or deliberate misinformation presented as an official Tournament communication.
25. MATCH DISPUTES
A match-related dispute must normally be submitted within 10 minutes of the conclusion of the affected match.
The Team Captain or Vice-Captain should provide:
- the match concerned;
- a description of the incident;
- the rule believed to have been breached;
- the requested remedy; and
- any available supporting evidence.
Evidence may include:
- demo files;
- screenshots;
- recordings;
- clips;
- server information; or
- other relevant material.
Teams are responsible for preserving relevant evidence.
Unsupported accusations do not automatically justify a penalty, replay or match reversal.
The 10-minute deadline does not prevent the Tournament Committee from subsequently investigating serious allegations involving:
- cheating;
- match-fixing;
- collusion;
- bribery;
- harassment;
- threats;
- account impersonation; or
- other serious integrity or safety matters.
26. EVIDENCE AND INVESTIGATIONS
Tournament Administrators may consider reasonably reliable evidence including:
- server logs;
- demo or GOTV recordings;
- anti-cheat records;
- screenshots;
- video recordings;
- livestream footage;
- game chat;
- Discord communications;
- Tournament platform records;
- administrator observations;
- witness accounts; and
- relevant technical information.
Participants must reasonably cooperate with legitimate Tournament investigations.
Knowingly:
- submitting falsified evidence;
- deleting or concealing evidence after being instructed to preserve it;
- misleading an Administrator; or
- interfering with an investigation
may itself result in disciplinary action.
An accusation alone does not establish that an offence occurred.
27. INFRACTION SYSTEM
Infractions may be issued for minor or moderate rule breaches and carry throughout Testament Cup v2.0.
The Tournament Committee will consider the seriousness, frequency, intent and competitive effect of a breach when determining penalties.
Minor Infractions
Examples may include:
- excessive vulgarities;
- administrative tardiness;
- unnecessary match delays;
- deliberate time-wasting;
- incorrect team assignment caused by Participant error;
- unauthorised advertising;
- unauthorised URLs;
- failure to comply with required LAN communication settings;
- careless disclosure of a server password;
- misuse of a pause;
- failure to attend a veto on time; or
- repeated failure to follow administrative procedures.
A Minor Infraction may result in:
- a formal warning;
- loss of veto priority;
- loss of side-selection priority;
- an administrative penalty; or
- escalation for repeated breaches.
Repeated Minor Infractions
Three Minor Infractions accumulated by a team may result in a competitive penalty.
Depending on the circumstances, this may include:
- round penalty;
- map penalty; or
- match forfeit.
Three minor administrative offences do not automatically result in a multi-year player suspension.
Where multiple Minor Infractions demonstrate deliberate abuse of the rules rather than ordinary mistakes, the Tournament Committee may treat the conduct more seriously.
28. MAJOR INFRACTIONS
Major Infractions include, but are not limited to:
- cheating or hacking;
- intentional ghosting;
- deliberate stream sniping;
- match-fixing;
- collusion;
- account impersonation;
- bribery;
- serious harassment;
- credible threats;
- deliberate tampering with Tournament servers or equipment;
- deliberate attempts to compromise competitive integrity; and
- repeated serious misconduct after previous disciplinary action.
A Major Infraction may result in immediate disqualification.
No previous warning or Minor Infraction is required before a Major Infraction penalty is imposed.
29. PENALTIES
Available Tournament penalties include:
- informal instruction or correction;
- formal warning;
- Minor Infraction;
- loss of veto priority;
- loss of side-selection priority;
- round penalty;
- map penalty;
- match forfeit;
- removal of a player;
- Tournament disqualification;
- prize forfeiture;
- suspension from future Proving Grounds competitions; or
- referral to Valve or another relevant authority.
Penalties do not need to be issued in the order above.
The Tournament Committee may consider:
- seriousness of the offence;
- whether the conduct was deliberate;
- competitive advantage gained;
- harm caused;
- previous disciplinary history;
- cooperation with an investigation;
- attempted concealment; and
- impact on Tournament integrity.
Where misconduct by an individual materially benefits the team, a team penalty may also be imposed.
30. SUSPENSIONS AND BANS
Serious misconduct may result in suspension from future Proving Grounds competitions.
Depending on the circumstances, a suspension may be:
- for the remainder of the Tournament;
- for a specified number of future events;
- for a specified period;
- for up to three years for serious competitive-integrity violations; or
- permanent in exceptional circumstances involving repeated or particularly serious misconduct.
The Tournament Committee will consider proportionality when determining the length of a suspension.
A suspension imposed by Proving Grounds applies to Proving Grounds-organised events.
A permanent ban applies to the individual Participant found responsible; it does not automatically extend to their teammates.
Application of that suspension to independently organised affiliated or partner tournaments will depend on the applicable rules and arrangements of those events.
31. MATCH RESULTS
Results confirmed by Tournament Administrators are the official Tournament results.
Teams should verify their recorded result promptly.
Administrative or scoring errors may be corrected where reliable evidence establishes that an error occurred.
Once:
- the applicable protest period has expired; and
- subsequent Tournament matches have progressed to a point where reversing a result would materially affect other teams,
the result will normally be treated as final.
Serious competitive-integrity investigations may still be conducted after this point.
32. PLAYER WITHDRAWAL AND MATCH ABANDONMENT
Teams wishing to withdraw should notify the Tournament Committee as soon as possible.
A team that abandons a match without Tournament Administrator approval may be treated as having forfeited that match.
A Participant must not persuade or coordinate with another team to withdraw, abandon or manipulate a match for competitive advantage.
The Tournament Committee will determine how previous results are treated where a team withdraws or is disqualified.
33. PRIZES
Where prizes are awarded, eligibility remains subject to compliance with these Rules.
Prize winners may be required to provide reasonable information for:
- identity verification;
- payment administration; and
- applicable legal or financial requirements.
Unless otherwise agreed, a team prize may be paid to the nominated team representative, who will be responsible for distribution among team members.
Proving Grounds is not responsible for private disputes between team members regarding the distribution of team prize money.
Participants are responsible for their own tax or reporting obligations relating to prizes.
Where a player or team is subsequently found to have committed a serious competitive-integrity violation, unpaid prizes may be withheld or revoked.
34. PHOTOGRAPHY, RECORDING AND BROADCASTING
Testament Cup may be:
- photographed;
- filmed;
- livestreamed;
- recorded;
- broadcast; and
- documented for editorial, promotional and archival purposes.
Tournament footage may include:
- Participants;
- gamer tags;
- team names;
- gameplay;
- voice recordings;
- interviews; and
- reactions.
By participating, Participants acknowledge that Tournament-related photographs and recordings may be used by Proving Grounds in connection with:
- Tournament coverage;
- livestreams;
- highlight videos;
- social media;
- Proving Grounds websites;
- promotion of Testament Cup;
- promotion of future Proving Grounds events;
- sponsor or partner reporting;
- news and editorial coverage; and
- Proving Grounds’ portfolio and corporate communications.
Where additional consent is legally required, including for minors where applicable, it will be obtained separately.
35. PERSONAL DATA
Proving Grounds may collect information reasonably necessary to administer the Tournament.
This may include:
- full name;
- gamer tag;
- email address;
- nationality;
- age or date-of-birth information;
- Steam ID 64;
- team information;
- Tournament results;
- photographs and recordings;
- parent or guardian information where applicable;
- emergency contact information where applicable; and
- payment details for prize administration.
Such information may be used to:
- process Tournament registrations;
- verify Participant eligibility;
- communicate with teams;
- administer matches;
- manage Tournament operations;
- investigate rule breaches;
- administer prizes;
- produce Tournament coverage; and
- maintain Tournament records.
Personal information will be handled in accordance with applicable Singapore data-protection requirements and Proving Grounds’ applicable privacy practices.
Registration consent for marketing communications should be obtained separately from consent required to administer participation in the Tournament.
Participants should therefore be provided with a clear option during registration regarding whether they agree to receive future Proving Grounds marketing communications.
36. CONFIDENTIAL INFORMATION
Participants may receive Tournament information that has not yet been made public.
Where information is clearly identified as confidential, embargoed or not for public release, Participants must not deliberately disclose it without permission.
This does not prevent a Participant from appropriately reporting:
- unlawful conduct;
- safety concerns;
- serious misconduct; or
- suspected competitive-integrity violations.
37. VENUE AND EQUIPMENT CONDUCT
At LAN events, Participants must comply with venue rules and reasonable staff instructions.
Participants may be responsible for deliberate or negligent damage to:
- Tournament computers;
- monitors;
- peripherals;
- furniture;
- networking equipment; or
- venue property.
Unauthorised access to restricted Tournament, production, server or administration areas is prohibited.
The Organiser may remove an individual from the venue where their conduct presents a genuine safety, security or operational concern.
38. HEALTH AND SAFETY
Participants are responsible for determining whether they are able to participate safely.
A Participant who becomes unwell or experiences an emergency should inform Tournament staff.
Tournament Administrators may pause or stop play where reasonably required because of a health or safety issue.
In an emergency, Proving Grounds may contact:
- emergency services;
- venue security; or
- a Participant’s nominated emergency contact
where reasonably appropriate.
39. FORCE MAJEURE AND EVENTS OUTSIDE THE ORGANISER’S CONTROL
The Tournament Committee may postpone, relocate, modify, suspend or cancel all or part of the Tournament where reasonably required because of circumstances outside Proving Grounds’ reasonable control.
Examples include:
- severe weather;
- venue closure;
- public-health restrictions;
- government restrictions;
- major power failure;
- internet or network failure;
- Steam or Counter-Strike 2 service outages;
- cyberattacks;
- security threats;
- transport disruption;
- game publisher decisions; or
- failure of critical third-party services.
Where possible, Proving Grounds will communicate material changes to affected Participants.
The Tournament Committee may modify the schedule or format where reasonably necessary to complete the Tournament fairly following such disruption.
40. RULE CHANGES
The Tournament Committee may amend these Rules where reasonably required to:
- respond to Counter-Strike 2 updates;
- reflect map-pool changes;
- correct an administrative error;
- clarify ambiguous wording;
- respond to an unforeseen circumstance;
- address a newly identified exploit;
- protect competitive integrity;
- comply with venue requirements; or
- comply with applicable legal requirements.
Material rule changes will be communicated through an official Tournament channel where reasonably practicable.
Participants and Team Captains are responsible for monitoring official Tournament communications.
Changes will not normally be applied retrospectively to penalise conduct that was permitted when it occurred.
41. UNFORESEEN CIRCUMSTANCES
No Tournament rulebook can anticipate every possible situation.
Where an issue is not expressly covered by these Rules, the Tournament Committee may make a reasonable ruling based on:
- competitive fairness;
- consistency;
- Tournament integrity;
- Counter-Strike 2’s intended competitive mechanics;
- Participant safety;
- available evidence; and
- the practical requirements of running the Tournament.
A ruling made for a particular situation does not automatically establish a permanent rule for future circumstances.
42. TOURNAMENT ADMINISTRATOR DECISIONS
Tournament Administrators are responsible for administering these Rules and may make immediate decisions where required for a match or Tournament to continue.
Decisions will be based on:
- these Rules;
- available evidence;
- relevant Counter-Strike 2 rules and mechanics;
- competitive fairness;
- consistency;
- safety; and
- Tournament integrity.
Where reliable new evidence subsequently demonstrates that a material administrative error occurred, the Tournament Committee may correct the decision where reasonably practicable.
This provision does not guarantee a replay or reversal where subsequent Tournament stages have already progressed and doing so would materially prejudice other Participants.
43. GOVERNING LAW
These Rules and participation in Testament Cup v2.0 are governed by the laws of Singapore.
Participants should first raise Tournament-related disputes through the Tournament dispute procedure described in these Rules.
Nothing in these Rules excludes or limits any right or liability that cannot lawfully be excluded under Singapore law.
44. SEVERABILITY
If any provision of these Rules is found to be invalid or unenforceable, the remaining provisions will continue to apply to the extent permitted by law.
45. ACCEPTANCE OF THE RULES
By registering for or participating in Testament Cup v2.0, each Participant confirms that they:
- have read and understood these Rules;
- have provided accurate registration information;
- agree to comply with reasonable Tournament Administrator instructions;
- agree to compete fairly;
- understand that rule breaches may result in penalties;
- understand the Tournament’s photography, recording and broadcast arrangements;
- consent to the collection and use of information reasonably required to administer their participation; and
- where they are a minor, have obtained the required parent or legal guardian consent.
Team Captains are responsible for ensuring that team members are aware of these Rules.
TOURNAMENT CONTACT
Questions concerning Tournament administration, rules or match disputes should be directed to:
Proving Grounds
Email: contact@pgrounds.sg
Official Tournament communications will also take place through the designated Proving Grounds Discord channel.
When contacting Tournament Administrators, Participants should provide their:
- team name;
- gamer tag;
- affected match, where applicable; and
- a clear description of the issue.