Skip to content
CTRLPOINT 2026 / Tournament

Official tournament rulebook.

CS2 + VALORANT

Ruleset version
1.0.3
Published
Status
Official / Published
General

General Event Rules

Document version 1.0.3

CTRLPOINT Pakistan 2026 — General Event Rulebook

Official event document — Version 1.0.3. Scheduled public release: 13 September 2026. Issued by Vidermedia.

This Rulebook applies to all participants in CTRLPOINT Pakistan 2026, including the Counter-Strike 2 and VALORANT competitions. It governs event-wide participation, conduct, media obligations, team support, prize administration and event operations.

Game-specific match procedures are governed by the relevant CS2 Official Rulebook or VALORANT Official Rulebook. Published event facts and disclosures are contained in the CS2 Additional Information and VALORANT Event Information documents.

1. Event Information

Tournament: CTRLPOINT Pakistan 2026

Tournament Operator: Vidermedia

Location: Karachi, Pakistan

Games: Counter-Strike 2 and VALORANT

Time Zone: Pakistan Standard Time (PKT, UTC+5)

Website: ctrlpoint.gg

Email: sm@vidermedia.live

Discord: discord.gg/vidergg

1.1 Event Calendar

MilestoneDate
Official information and rulebooks published13 September 2026
Registration opens for both qualifiers, both games21 September 2026, 6:00 PM PKT
Qualifier 1 registration closes29 September 2026, 11:00 PM PKT
Open Qualifier 11–4 October 2026
Qualifier 2 registration closes6 October 2026, 11:00 PM PKT
Open Qualifier 28–11 October 2026
Mandatory Media Day22 October 2026
LAN Finals24–25 October 2026

The detailed competitive schedule for each game is published separately. Tournament Administration may adjust individual match times where required, provided the published competition dates and applicable rules are respected.

2. Participation and Eligibility

2.1 Player Eligibility

The event is open only to Pakistani players. All starters and substitutes must hold Pakistani citizenship.

Players must be 16 years of age or older on 1 October 2026. Players under 18 must provide parent or legal guardian consent where requested by Tournament Administration.

Tournament Administration may privately verify age, citizenship, identity, account ownership and eligibility. Participants must not publish identity documents or other private verification material in public channels.

2.2 Team Composition

Each team may register:

  • Five starting players;
  • Up to two substitutes; and
  • One optional coach.

A coach may only play if they are also registered as one of the team’s substitutes and otherwise meet all player eligibility requirements.

A player may represent only one team per game during CTRLPOINT Pakistan 2026. Teams may not use unregistered players, ringers, impersonators or borrowed players from another participating roster.

Game-specific roster locks, substitution procedures and qualification-core rules are defined in the relevant game rulebook.

2.3 Registration

Entry is free. Each qualifier is capped at 128 teams per game.

Teams may register for Qualifier 1, Qualifier 2, or both. A team that qualifies through Qualifier 1 is removed from Qualifier 2.

Registration is only considered complete when all required information has been submitted correctly. Where a waiting list is required, priority is determined by the recorded completion time of eligible registrations.

3. Official Communication

The team captain is responsible for monitoring official tournament communications and ensuring that all team members receive relevant information.

Official communication may be issued through:

  • Email;
  • CTRLPOINT/ViderGG Discord;
  • ctrlpoint.gg;
  • The official tournament platform; or
  • Direct communication from authorised Tournament Administration.

Teams must maintain accurate contact information throughout the event.

Private tournament correspondence, eligibility documents, payment information and disciplinary evidence must not be published without permission, except where disclosure is legally required.

4. Match Scheduling and Attendance

4.1 Qualifier Hours

Qualifier matches are normally scheduled between 2:00 PM and 11:59 PM PKT. No new series normally starts after 10:00 PM PKT.

Tournament Administration may approve an exception where:

  • Both teams agree;
  • The requested time is operationally viable;
  • It does not unfairly affect another participant; and
  • It does not extend the published qualifier window.

Teams may not privately reschedule an official match without admin approval.

4.2 Match Readiness

Teams must follow the check-in and readiness requirements in the relevant game rulebook. Captains are responsible for ensuring that their team is available and prepared at the published match time.

Failure to appear or field the required number of eligible players may result in map or series forfeits.

4.3 LAN Attendance

All qualified teams must attend the LAN Finals in Karachi, Pakistan.

The five designated LAN players from every finalist team must attend mandatory Media Day on 22 October 2026 and the LAN Finals on 24–25 October 2026.

Substitutes, coaches and additional team staff may attend subject to event access rules, but their attendance is not funded unless separately confirmed in writing by Vidermedia.

5. Team Travel and Support

Vidermedia will book and cover the following for five designated players per qualified team:

  • Return travel within Pakistan;
  • Accommodation;
  • Meals; and
  • Local transfers connected to required event activities.

Coaches, substitutes outside the five supported players and additional team staff attend at their own expense.

Individual travel and accommodation arrangements will be communicated privately to each team. The Rulebook does not guarantee a specific airline, transport method, hotel, room type or travel schedule.

Teams must provide requested travel information by the applicable deadline. Failure to provide required information may affect Vidermedia’s ability to arrange support.

6. Code of Conduct

All participants must behave professionally and respectfully toward players, staff, spectators, broadcast personnel, sponsors and venue personnel.

The following are prohibited:

  • Harassment, discrimination, threats or intimidation;
  • Violence or attempted violence;
  • Abusive or deliberately disruptive behaviour;
  • Hate speech or targeted personal abuse;
  • Deliberately deceiving Tournament Administration;
  • Damage to venue, event or another participant’s property;
  • Participating while intoxicated or otherwise unable to compete safely; and
  • Conduct that materially threatens the safety or integrity of the event.

Good-faith criticism of the event, organisers or rules is not prohibited. Participants remain responsible for how they communicate and must not harass staff or other competitors.

7. Competitive Integrity

All participants must compete honestly and to the best of their ability.

The following are strictly prohibited:

  • Cheating or use of unauthorised software;
  • Account sharing or impersonation;
  • Smurfing or fielding an unregistered/ineligible player;
  • Match-fixing, intentional losing or collusion;
  • Stream-sniping or receiving hidden match information;
  • Betting on CTRLPOINT matches by players, coaches, team staff or event staff;
  • Sharing inside information for betting purposes;
  • Network attacks or deliberate technical interference; and
  • Any arrangement intended to manipulate qualification, placement or prize results.

Game-specific exploit, anti-cheat, pause and technical rules are contained in the relevant game rulebook.

8. Broadcast, Media and Content

8.1 Broadcast Rights

Official broadcast and event-content rights are controlled by Vidermedia subject to applicable publisher licences and agreements.

Teams may not refuse an authorised tournament broadcast or interfere with the approved production format.

Player POV streams, team co-streams or third-party rebroadcasts require prior written approval from Tournament Administration.

8.2 Media Day and Media Duties

Media Day on 22 October 2026 is mandatory for the five designated LAN players from every qualified team.

Media activities may include:

  • Official photography;
  • Player and team portraits;
  • Interviews;
  • Promotional video;
  • Social-media content;
  • Broadcast features; and
  • Sponsor-related event content.

Players must cooperate reasonably and wear appropriate team jerseys or matching attire where requested.

A genuine medical, welfare or other serious issue should be reported to Tournament Administration as early as possible.

8.3 Use of Event Content

By participating, players and teams allow Vidermedia to record and use their approved team names, player names/aliases, gameplay, interviews, photographs, event footage and team branding for the coverage, archive and promotion of CTRLPOINT Pakistan 2026 and related event recaps.

This permission does not create a right to falsely imply a personal endorsement unrelated to the event.

9. Prizes and Compensation

The total CTRLPOINT Pakistan 2026 prize pool is PKR 1,000,000:

  • Counter-Strike 2: PKR 500,000;
  • VALORANT: PKR 500,000.

Each game’s distribution is:

PlacementPrize
WinnerPKR 300,000
Runner-upPKR 150,000
Joint third–fourthPKR 25,000 per team

There are no qualifier cash prizes.

There is no additional compensation beyond the published prize pool and the five-player team support described in Section 5. No appearance fees, MVP bonuses, participation bonuses or revenue shares are provided.

Prize money will be paid within three calendar months of the conclusion of the LAN Finals, no later than 25 January 2027. Teams must provide accurate payee information and any required payment documents promptly.

The relevant game rulebook and event-information document govern disqualification, prize eligibility and payment administration for each competition.

10. Protests, Disputes and Administrative Decisions

Participants must report match-related issues through the procedures and deadlines in the relevant game rulebook.

For event-wide issues, captains should contact Tournament Administration as soon as reasonably possible through the official channels.

Tournament Administration may request evidence, statements or supporting material. Participants must cooperate honestly with investigations.

Decisions affecting match results, eligibility, disqualification or prize entitlement will be communicated to the affected teams with reasons. Where a formal appeal is available under the relevant game rulebook, the published appeal procedure must be followed.

Social-media posts do not replace an official protest or appeal.

11. Penalties and Sanctions

Penalties depend on the seriousness, impact, intent and repetition of the violation. Possible sanctions include:

  • Warning;
  • Required correction;
  • Loss of side/map-selection privilege;
  • Round, map or series penalty where applicable;
  • Forfeit;
  • Removal of a coach or team staff member;
  • Disqualification;
  • Prize review or forfeiture where directly connected to the violation; and
  • Suspension from future CTRLPOINT competitions for serious misconduct.

Serious cheating, match-fixing, identity fraud or deliberate use of an ineligible player may result in immediate disqualification.

Tournament Administration should apply sanctions consistently and proportionately. A participant must not be penalised merely for raising a good-faith complaint or welfare concern.

12. Privacy and Participant Information

Vidermedia may collect information reasonably required to operate the tournament, including contact details, game-account identifiers, eligibility documents, travel details and payment information.

Private identity, payment and travel records will not be published as part of tournament results or public disciplinary notices.

Public competition records may include team names, player aliases, approved game identifiers, brackets, results, eligibility status and administrative decisions.

Participants should send sensitive information only through the official private channels provided by Tournament Administration.

13. Event Changes, Emergencies and Cancellation

Tournament Administration may make necessary operational decisions where unexpected technical, safety or scheduling issues arise.

Material changes to eligibility, dates, format, prizes or other published event terms must be communicated through official channels and recorded in the public rule/document history where applicable.

If an event stage is delayed, postponed or cancelled, Tournament Administration will communicate the effect on scheduling, qualification, prizes and team support as soon as reasonably possible.

No team may assume reimbursement for personal costs that were not expressly approved or booked by Vidermedia.

14. Rulebook Authority

This General Event Rulebook governs policies that apply across both games.

The following documents must be read together:

  1. CTRLPOINT Pakistan 2026 General Event Rulebook;
  2. Counter-Strike 2 Official Rulebook;
  3. CS2 Additional Information;
  4. VALORANT Official Rulebook; and
  5. VALORANT Event Information.

For game-specific matters such as maps, vetoes, server selection, pauses, disconnects, match recovery and gameplay settings, the relevant game rulebook applies.

For published event facts and required competition disclosures, the relevant Additional Information/Event Information document applies.

Applicable law and binding publisher/licensing requirements take precedence over CTRLPOINT rules where required.

Tournament Administration may interpret the rules where a situation is not expressly covered, but may not privately rewrite a published eligibility, prize, qualification or competition term after the fact.

15. Acceptance

By registering for or participating in CTRLPOINT Pakistan 2026, teams and players confirm that they have read, understood and agreed to the applicable event and game rules.

Captains are responsible for ensuring that all registered team members receive the current rules and official tournament notices.

CTRLPOINT Pakistan 2026 — General Event Rulebook Version 1.0.3 Issued by Vidermedia

CS2

Counter-Strike 2 Rules

Document version 1.0.3

CTRLPOINT Pakistan 2026 — Counter-Strike 2 Official Rulebook

Official competition document — Version 1.0.3. Scheduled public release: 13 September 2026. Issued by Vidermedia.

This rulebook applies to the Counter-Strike 2 competition at CTRLPOINT Pakistan 2026, organised by Vidermedia, Karachi, Pakistan. Players must read it before registering. Full event disclosures and official contacts are in CS2 Additional Information.

1. Tournament Information

Eligibility: Pakistani players only, including substitutes.

Format: Two open qualifiers; top two teams from each reach the four-team LAN.

Invitations: None.

LAN city: Karachi, Pakistan.

Time zone: Pakistan Standard Time (PKT, UTC+5).

Website: ctrlpoint.gg.

Contact: sm@vidermedia.live or discord.gg/vidergg.

StageDate / deadline
Complete information and rulebook publication13 September
Both qualifiers open for registration21 September, 6:00 PM
Qualifier 1 registration closes29 September, 11:00 PM
Qualifier 11–4 October
Qualifier 2 registration closes6 October, 11:00 PM PKT
Qualifier 28–11 October
Mandatory media day22 October
LAN finals24–25 October

All dates are in 2026. The detailed calendar is in SCHEDULE.md.

Entry: Free. Cap: 128 teams per qualifier, per game. Playing roster: Five starters and up to two substitutes.

2. Participation and Rosters

2.1 Player eligibility

All playing members must hold Pakistani citizenship. Pakistani citizens abroad and dual nationals remain eligible, provided they meet the server and attendance requirements. A team organisation’s nationality does not replace player eligibility.

Players must be 16 or older on 1 October 2026. Under-18s need guardian consent and an agreed responsible adult for LAN attendance. Admins may privately check citizenship, age and account ownership. Do not post identity documents in public channels.

Players must use their own registered accounts. Account sharing, impersonation and ban evasion are prohibited. An applicable active publisher, required-platform, ESIC or CTRLPOINT suspension prevents participation. Admins must check its scope; rumours or unrelated old bans are not automatic disqualifications.

2.2 Team size and roster lock

Register five starters, up to two substitutes and one optional coach. A coach may play only if also registered in one of the two substitute slots. Each player may represent only one team per game throughout this event. One organisation may enter one roster per game; competing teams cannot share a coach or controlling owner.

Q1 rosters lock when Q1 registration closes. Q2 rosters lock at 11:00 PM PKT on 6 October 2026. A returning Q1 team must keep at least three of its original five starters. Before Q2 locks, eligible additions are allowed within the roster limit, but players from another team in this event cannot be borrowed.

Each qualifier map must include at least three of that qualifier’s declared original five. Submit the starting lineup 30 minutes before a series. Registered substitutes may enter between maps only; notify admins within five minutes of the previous map ending. Players cannot share an account or swap during a live map.

2.3 LAN roster and emergencies

The five players who win the final qualification map form the team’s qualifying core. Each LAN map must include at least three of those five. The ordinary LAN roster is the registered roster that qualified, with a maximum of seven players. A slot cannot be sold or transferred to an unrelated lineup.

One emergency addition may be approved after a roster lock for a documented serious medical, family or comparable emergency. The replacement must meet every eligibility rule, belong to no other event roster, preserve the required core and fit the seven-player limit. The removed player cannot return during that stage. Performance changes, transfers and account bans are not emergency grounds. Known requests are due by 20 October, 6:00 PM; later unforeseen cases use the same test. Public roster notices must not expose private medical details.

3. Registration and Tournament Format

3.1 Registration

Captains may enter Q1, Q2 or both. Selecting only Q1 does not automatically enter Q2. Q1 qualifiers and their entire registered playing roster, including unused substitutes, are removed from Q2. Unsuccessful Q1 teams may try again.

The cap is 128 eligible teams per qualifier, accepted by the time their registration becomes complete. Later entries form a public, timestamp-ordered waiting list. An empty form does not reserve a place. Harmless corrections retain priority; missing required details or material roster changes use the new completion time. No late private entries are allowed.

Check-in opens 60 minutes and closes 30 minutes before the team’s first scheduled match; teams with byes follow the published qualifier check-in time. Before bracket lock, vacancies go to eligible, checked-in waiting-list teams. After play starts, missing teams receive forfeits; new teams are not inserted.

3.2 Match format

Round / stageFormat
Qualifiers: Round of 128, 64 and 32Single elimination, BO1
Qualifiers: Round of 16 and quarterfinalsBO3
Qualifier semifinalsBO3; both winners qualify
Losing semifinalistsOne BO3 to establish third/fourth reserve priority
Four-team LANSingle elimination; BO3 semifinals and BO3 final

There is no qualifier grand final and no LAN third-place match. LAN semifinal losers share third–fourth place. The reserve-order match is separate and does not itself award a LAN slot.

Each qualifier lasts at most four days: opening rounds on Days 1–2, quarterfinals on Day 3, and semifinals plus the reserve match on Day 4. Qualifier matches are scheduled between 2:00 PM and 11:59 PM PKT. No new series normally starts after 10:00 PM. Admins may approve an exception in advance where both teams agree and the change is operationally viable. Exceptions must not disrupt other matches or extend the published four-day qualifier window. Teams cannot reschedule matches without admin approval. Matches run concurrently where necessary. Fewer than four checked-in teams requires a published format/deadline review, not discretionary invitations.

3.3 Seeding

Both qualifiers and LAN use the 7 September 2026 Global VRS list, revised 9 September, pinned in Additional Information. Ranked rosters are seeded first, in VRS order; unranked rosters follow through a recorded random draw. There is no ranking requirement to enter.

A locked five must retain at least three players from the reference VRS roster to claim its seeding identity. If several references match, use the greatest overlap, then the better standing. Admins verify player identities and publish the mapping. Seeding identity does not guarantee later VRS credit.

Publish the draw, seed order and a one-hour correction window. Higher seeds receive available byes; LAN pairings are 1 vs 4 and 2 vs 3. Do not redraw for preferred opponents.

4. Qualification, Replacements and Match Times

4.1 LAN confirmation and reserve teams

Accept a LAN place through the official channel within 24 hours. Finalists submit attendance details by 14 October, 6:00 PM. Admins publish the finalist/reserve list by 12 October and the LAN bracket and appointments by 18 October, both at 6:00 PM.

Before 21 October, 6:00 PM, a vacant slot passes to: third in its qualifier, then fourth there, then third and fourth in the other qualifier. Skip already-qualified, ineligible, withdrawn or unavailable teams. Refusing the reserve match results in a forfeit and loss of reserve availability, unless a documented genuine emergency justifies an exception.

Process multiple vacancies in recorded order; simultaneous vacancies use Q1 before Q2, then original slot ID. A team may accept only one slot. Each reserve has 12 hours to reply, shortened only by the cutoff; do not issue an offer allowing fewer than two hours. Notify reserves of this process by 12 October and record offers and responses.

A replacement confirmed before bracket publication is seeded normally. Later accepted replacements take the vacant position without inheriting the departed team’s ranking. Recalculate veto priority between the actual teams; use a recorded toss where two unranked teams have no comparable draw position. No new team enters after the cutoff or after LAN play starts. Unfilled slots become byes/forfeits.

4.2 Match readiness

Captains must monitor the official channel. Round appointments are published at least 24 hours before the qualifier starts, even where opponents are not yet known. Teams cannot privately reschedule. Allow at least 20 minutes between series and 10 minutes between maps. Starting early requires both captains’ agreement and admin approval.

Join the server/lobby 15 minutes before match time. Five eligible players are required to start. After 15 minutes of lateness, the team forfeits the first unplayed map. In a BO3, another 15 minutes of unavailability forfeits the series. Organiser-caused delays and common outages are handled separately. Two absent teams may both be eliminated.

Do not restart, surrender, change the server or alter a score without admin approval. Dual-game participation does not entitle a player to a schedule change.

5. Counter-Strike 2 Match Rules

5.1 Accounts, servers and maps

Online qualifiers use FACEIT, with the approved server pool of Dammam, Dubai and Riyadh. Register each player’s Steam and FACEIT IDs and use FACEIT Anti-Cheat throughout online matches. LAN matches use the organiser’s controlled local match server.

Map pool: Ancient, Anubis, Cache, Dust II, Inferno, Mirage and Nuke. Once published, it stays fixed unless a publisher restriction or serious technical issue requires an announced change.

Use the approved server pool. Under the server-selection procedure, test all ten players for five minutes and choose the stable server with the lowest worst-player median latency, then lowest average; break an exact tie in the order Dammam, Dubai, Riyadh. Record any unavailable or unstable option. Do not silently substitute a new location or change servers for tactical reasons.

5.2 Match settings

SettingValue
Players / regulation5v5; 12 rounds per half; first to 13
Round / bomb / freeze time1:55 / 40 seconds / 20 seconds
Starting money$800 in-game
Overtime at 12–12Three rounds per side; first to four; repeat if tied
Overtime money$12,500 at the start of each overtime half
Tactical pausesThree 30-second pauses in regulation; one per overtime block

Overtime starts on the side used at the end of regulation; switch after three rounds and continue alternating in later blocks. Unused regulation pauses do not carry over. Server demos and round backups must be enabled. These values must match the tested platform configuration.

5.3 Map veto

The higher seed chooses Team A or B. Each action has 60 seconds, followed by a final 30-second warning. If the clock expires, the admin records a random legal choice. Do not reverse a valid selection after the next action, except to fix an official’s recorded error.

BO1: A ban → B ban → A ban → B ban → A ban → B ban. Play the remaining map; knife-round winner chooses side.

BO3: A ban → B ban → A pick → B pick → A ban → B ban. Play the remaining map as Map 3. The opponent chooses the starting side on each picked map; knife-round winner chooses on Map 3. Stop the series when a team wins two maps.

Knife rounds are knife-only. If time expires, use surviving-player count, then remaining health; repeat an exact tie. The winner has 60 seconds to choose, otherwise it keeps its knife-round side.

6. Pauses, Disconnections and Recovery

Use tactical pauses during freeze time. The registered coach may speak during tactical pauses, approved halftime, pre-map and between-map breaks—not during live rounds, ordinary freeze time or technical pauses.

For a technical issue, type TECH and the reason, and contact the admin. Continue the live round unless told otherwise. Each team has up to 5 minutes per map for its own connection/equipment problems. Organiser equipment, network and server faults do not use this allowance. A documented short extension may be granted consistently; unresolved player unavailability can forfeit the map/series. Only technical discussion is allowed during a technical pause.

A disconnected player may reconnect on the same account. Substitutes enter between maps only. An individual round restart is considered only after an immediate report, before damage, decisive objective action or information that would make replay unfair. Misbuys and lost duels are not restart grounds.

For a common server crash, admins restore the interrupted round from a valid backup, preserving completed rounds and accurate game state. If reliable recovery is impossible, the head admin may suspend play and, as a last resort, order a full map replay with the original map and sides, giving written reasons. The leading team does not automatically win.

Admins retain demos, backups, vetoes, lineups and relevant logs for at least 90 days, longer for an open case. Captains must preserve requested evidence; passwords and server-admin credentials stay private.

7. Conduct and Fair Play

Treat players, officials, spectators and broadcast staff respectfully. Harassment, discrimination, threats, violence and abusive spam are prohibited. Players must compete honestly; match-fixing, betting on event matches and sharing inside information for betting are prohibited for participants and event staff.

Cheats, account sharing, unregistered players, stream-sniping, hidden-information tools, network attacks, recoil/movement automation and unapproved real-time assistance are prohibited. Legal native settings remain allowed. Do not exploit broken geometry, unintended invulnerability or game-breaking bugs. Ask an admin before using a doubtful interaction; unfamiliar legitimate play is not automatically an exploit.

Input-priority assistance, scripted jump/throw combinations and other multi-action automation prohibited by Valve are not allowed. Do not tamper with game assets, anti-cheat, demos or backups. Ordinary manual movement and legal boosts remain allowed.

Only active players, the permitted coach and authorised officials may join match communications. Managers, substitutes and spectators must not feed information. Players must not watch the live broadcast during a match.

Use registered nicknames and approved team/sponsor branding. Submit name/logo changes for approval. Sponsor content must meet the publisher and event restrictions in CS2 Additional Information. Do not claim publisher endorsement. Disclose relevant team/staff financial or ownership relationships; conflicted officials cannot decide the affected case. Valve-required relationship disclosures and approvals must also be satisfied; disclosure alone is not immediate approval.

8. Protests and Penalties

Report match issues immediately. The captain has 15 minutes after the series to submit a result/eligibility protest, preferably before dependent play begins. Include the rule, map/round, explanation, requested remedy and evidence. Newly discovered cheating or fraud may be reviewed later. A social-media accusation alone is not proof.

Admins give written reasons for decisions affecting results, prizes or eligibility. Disqualifications and amendments are published with private information removed. Live appeals are due within 15 minutes of the decision; other appeals within 24 hours. An unconflicted senior official reviews material errors, inconsistent enforcement, unfair sanctions or significant new evidence. The aim is a ruling before dependent play, normally within 48 hours otherwise. Play follows the existing ruling unless the appeal official pauses it.

BreachNormal response
First minor administrative errorWarning and correction deadline
LatenessMap/series forfeits in Section 4.2
Improper coaching or exploit abuseWarning, timeout loss, coach removal or round/map/series penalty, according to impact and repetition
Ineligible player, roster fraud, proven cheating or match-fixingMatch/stage disqualification and result/prize review; serious individual misconduct may bring a reasoned suspension up to 24 months
Serious harassment or threatsRemoval/disqualification; suspension up to 12 months, or 24 months for violence/repeated severe misconduct

Penalties must match the evidence and impact. Missing evidence alone does not prove cheating; deliberate obstruction may receive a stronger sanction. Use round penalties only where the game can apply and record them accurately. Record forfeits as administrative results, not invented played statistics. Good-faith criticism and valid welfare requests do not justify prize deductions. An accusation against one player does not automatically establish every teammate’s personal guilt.

9. LAN Attendance

All finalists must attend in person in Karachi, Pakistan. Media day is mandatory on 22 October for the five designated LAN players of each team. LAN matches take place on 24–25 October. Teams must arrive in time for their published media appointment. There is no compulsory media or match appointment on 23 October. Team support terms are in CS2 Additional Information.

Teams receive equal preparation time and published practice access. Players may use approved personal peripherals. USB drives, downloads and software/config changes need admin approval.

Follow venue safety rules and arrange ordinary breaks through officials. Urgent health needs take priority. Players must not compete while intoxicated, and necessary medical treatment must not be withheld. Staff will privately consider documented welfare or accessibility needs.

10. Broadcasts, Media and Privacy

Players must cooperate with official coverage and published interviews, photoshoots and ceremonies. Wear approved jerseys or matching attire. Report genuine attendance or welfare problems promptly; missing media does not automatically forfeit every prize.

Player POV streams and co-streams need written approval, requested 48 hours before the stage where practical. Approved online streams use at least 180 seconds’ delay. No clean live production feed or unapproved observer access is provided to teams.

Participants allow Vidermedia to record and use event gameplay, names/aliases, team branding, photos, interviews and approved match communications for this event’s coverage, archive and promotion, including event-related sponsor recaps. Archives may remain online. Unrelated advertising and false personal endorsements are not included. Guardian consent covers minors.

Comms and player-camera clips, including In The Comms, are published only after the series. Remove private, sensitive or security information. Public records may include approved game IDs, eligibility status, results and decisions—not identity scans, private contacts or bank details. Routine identity copies are deleted within 90 days after the event or verification dispute closes unless longer retention is legally required; relevant integrity/financial records follow their own retention duties. Raise privacy concerns through the published private contact.

11. Prizes and Team Support

The combined event prize pool is PKR 1,000,000. The prize pool for this game is PKR 500,000, distributed as follows:

PlacementPrize
WinnerPKR 300,000
Runner-upPKR 150,000
Joint third–fourthPKR 25,000 per team

Qualifier and reserve matches have no separate cash prizes. Vidermedia will book and cover return travel within Pakistan, accommodation, meals and local transfers for five designated players per qualified team. Coaches, substitutes outside those five and additional staff attend at their own expense. Teams name their five supported players when confirming LAN attendance; a lineup change does not add funded places. Individual arrangements are communicated directly to each team. The same five-player support entitlement applies to every finalist team.

There is no additional compensation beyond the published prize pool and five-player team support. No appearance fees, MVP bonuses, participation bonuses or revenue shares are provided.

A roster nominates an authorised payee. Prize money will be paid within three calendar months of the conclusion of the LAN finals, no later than 25 January 2027. Teams must promptly provide accurate payee information and any required payment documents through the official private contact. A genuine payee or integrity dispute may hold only the affected award, with written reasons and updates; other awards remain payable on time.

Awards are gross PKR; any legally required withholding must be evidenced. Vidermedia covers sender-side fees. Sponsor delays do not excuse non-payment. No hidden fines or deductions are permitted.

A team that never competes at LAN does not earn a placement prize. Disqualification or cancellation consequences require a published decision; the normal pool is not silently reduced or redistributed. Record actual paid awards accurately and preserve unaffected teams’ entitlements.

12. Administration and Rule Changes

The approved rulebook and CS2 Additional Information apply together, subject to binding publisher rules and law. Event facts, full support terms and source records remain in the event-information documents. Unpublished staff notes are not binding on players.

Changes must be dated, recorded on GitHub and announced through official channels. Do not change eligibility, format, dates, prizes or seeding privately or retrospectively. Material amendments require the relevant notice/licensing review. See AMENDMENT-POLICY.md.

For outages, safety emergencies or serious bugs, admins may stop play, preserve evidence and issue a fair documented ruling. Cancellation/postponement notices must explain schedule, prize and support consequences. A fifth qualifier day or extra mandatory attendance day is not automatically authorised. Non-refundable personal costs are not automatically reimbursed; rights that cannot legally be excluded remain protected.

Captains share the current rules with all members. Adults accept personally; minors require guardian consent. There are no automatic 2027 league rights or guaranteed ranking points from entering this event.

CS2 Additional Information

CS2 Additional Information

Document version 1.0.3

CTRLPOINT Pakistan 2026 — CS2 Additional Information

Official competition document — Version 1.0.3. Scheduled public release: 13 September 2026. Issued by Vidermedia.

1. Event identity and regulatory status

Required itemDisclosure
Tournament nameCTRLPOINT Pakistan 2026 — Counter-Strike 2
Tournament operator / brandVidermedia; legal entity and contacts in Section 2
GameCounter-Strike 2, PC, five-versus-five
Declared operating formatTier 2; all places earned through open qualification
Ranking intentionOperated to meet Valve’s Ranked Tournament requirements. HLTV coverage, covered stages and actual VRS inclusion remain unconfirmed until separately established.
Direct VRS invitations0
Wildcard invitations0
Other discretionary LAN invitations0
Eligible player populationPakistani citizens, including every substitute who plays
Qualifying structureTwo online open qualifiers, top two from each; four-team LAN
Tournament playing dates1–4 October; 8–11 October; 24–25 October 2026
Entire tournament period1–25 October 2026, including mandatory media day on 22 October. Main-event attendance window: 22–25 October; required appointments are those published for each team.
Host / visa regionPakistan
Main-event attendance window22–25 October 2026, including media day on 22 October and LAN matches on 24–25 October; Karachi, Pakistan
Time zonePKT / Asia/Karachi / UTC+5
Planned complete-information publication13 September 2026; actual time to be recorded
Actual publication evidenceThe initial public GitHub release, its history and the website record establish the actual publication time; see Publication Record.
Applicable Valve requirementsVersion current at the Additional Information deadline, 17 September 2026 for the 1 October qualifier; record the exact then-applicable commit in the publication record
Required itemDisclosure
Licence requirementThe operator must hold the applicable Valve tournament licence. This document does not imply Valve endorsement or a special exception.
Official rulebookCS2 Competition Rulebook

This event is independent of Valve. It is not a Valve Major, a Valve-operated event, or a guarantee of ranking points. Results are not to be advertised as definitely VRS-counting before that status and scope are established.

2. Operator and official channels

ItemOfficial information
Event owner / operating brandVidermedia / CTRLPOINT
Tournament operator / locationVidermedia, Karachi, Pakistan
Tournament administrationVidermedia competition administration, reachable through the contacts below
Tournament support emailsm@vidermedia.live
Official participant support / Discorddiscord.gg/vidergg
Registration and official websitectrlpoint.gg; qualifier registration links are published there
Public version historyGitHub copy linked through ctrlpoint.gg; this release and subsequent amendments are retained
LAN cityKarachi, Pakistan
Private eligibility, privacy and safeguarding enquiriessm@vidermedia.live

Only the published support channel may issue administrative instructions. Messages from an organiser’s personal account do not grant an unrecorded exemption or amend the rules.

3. Complete dates and registration

Date / time (PKT, UTC+5)Milestone
13 September 2026 — scheduled public releasePublish the complete CS2 Additional Information, CS2 Rulebook, registration conditions and both CS2 qualifier schedules. Record the actual publication timestamp.
17 September 2026Valve Additional Information deadline for the 1 October first qualifier. Recheck the applicable Valve requirements version.
21 September 2026, 18:00Registration opens for CS2 Qualifier 1 and CS2 Qualifier 2.
29 September 2026, 23:00CS2 Qualifier 1 registration and submitted-roster editing close.
Date / time (PKT, UTC+5)Milestone
30 September 2026Qualifier 1 verification, check-in instructions, seeding and bracket publication.
1–4 October 2026Qualifier 1, maximum four competition days.
6 October 2026, 23:00 PKTCS2 Qualifier 2 registration and submitted-roster editing close. The published CS2 reserve-order match is included in Qualifier 1 activity. Publish the exact closure timestamp and event log.
7 October 2026Qualifier 2 verification, check-in instructions, seeding and bracket publication.
8–11 October 2026Qualifier 2, maximum four competition days.
Within 24 hours of earning a LAN placeCaptain confirms acceptance and ability to attend; failure triggers the published replacement process.
12 October 2026, 18:00Publish the initial finalist and reserve register, subject only to identified pending decisions.
14 October 2026, 18:00Finalists submit LAN attendance, accreditation and payment-contact details privately. This does not reopen playing-roster additions.
18 October 2026, 18:00Publish LAN seeding, bracket, detailed match times, practice allocation and media appointments.
20 October 2026, 18:00Final roster administration check and deadline for known, documented emergency-addition applications. Later unforeseen emergencies use the same narrow eligibility test.
21 October 2026, 18:00Ordinary reserve-replacement cutoff. Thereafter, no new team enters; unresolved vacancies become published byes / forfeits.
22 October 2026Mandatory media day for all five designated LAN players of every CS2 finalist team. Exact appointments are published by 18 October.
23 October 2026No scheduled competition or compulsory media activity; preparation / rest day.
24–25 October 2026Four-team CS2 LAN finals.
25 January 2027Prize-payment deadline: three calendar months after the LAN finals conclude. Teams must supply complete payee documents promptly.

Both qualifiers open together. A captain selects Q1, Q2 or both. Selecting Q1 alone does not register the team for Q2. Q1 qualifiers and their registered playing roster are removed from Q2. Q1 non-qualifiers may compete in Q2 subject to the same roster and entry rules. CS2 Qualifier 2 registration and submitted-roster editing close on 6 October 2026 at 23:00 PKT.

Qualifier matches are scheduled between 2:00 PM and 11:59 PM PKT. No new series normally starts after 10:00 PM. Admins may approve an exception in advance where both teams agree and the change is operationally viable. Exceptions must not disrupt other matches or extend the published four-day qualifier window. Teams cannot reschedule matches without admin approval.

4. Open qualifier conditions

Confirmed CS2 event settings: Free entry; 128 accepted teams per qualifier; five starters and up to two substitutes; two single-elimination qualifiers, BO1 through the Round of 32 and BO3 from the Round of 16; both semifinal winners qualify; the losing semifinalists play a BO3 reserve-order match. The four-team LAN uses BO3 semifinals and a BO3 final, with no third-place match. The CS2 prize pool is PKR 500,000, distributed 60% / 30% / 5% / 5%.

Every playing participant must hold Pakistani citizenship; dual citizenship does not remove eligibility where Pakistani citizenship remains valid. A foreign-owned organisation may register an otherwise eligible Pakistani roster, but a Pakistani organisation may not field an ineligible foreign player. Citizenship is not residence: this event does not add a Pakistan-residency requirement. Players must be able to use the published server region and attend the LAN. No player receives a special server or schedule concession based on their location.

Entries are accepted in the order of complete, eligible registration up to 128 per qualifier. Verification may finish after the cutoff but must apply objective published tests. Remaining eligible entries form a timestamp-ordered waiting list. No purchase, invitation or sponsor relationship grants entry priority.

The public registration ledger contains an entry ID, team name, player aliases / approved game identifiers, qualifier selection, original submission timestamp, material amendment timestamp, completeness timestamp, order and acceptance status. Private identity evidence, birth dates, phone numbers and bank information are never included. First-come-first-served order must be publicly inspectable before registration opens and thereafter retained with history.

A single-elimination qualifier uses BO1 through the Round of 32 and BO3 from the Round of 16. The two semifinal winners qualify. The semifinal losers play one BO3 reserve-order match within the four-day window. Fewer than four eligible checked-in rosters in a qualifier requires an announced corrective decision; it does not authorise private invitations or fabricated qualifying matches.

Valve disclosure fieldValue
VRS list used for Direct VRS InvitesNot applicable — no Direct VRS Invites
Filters applied to Direct VRS InvitesNot applicable; Pakistani citizenship is an OPEN-QUALIFIER condition, not a VRS invitation filter
Starting VRS rank for invitationsNot applicable
Number of Direct VRS Invites0
Number of Wildcard Invites0
Invitation dateNot applicable
VRS publication for Direct VRS InvitesNot applicable
VRS publication used for seedingGlobal invitation VRS dated 7 September 2026, fixed snapshot for both qualifiers and LAN
Official seeding sourceValve Global standings, 7 September 2026
Source identity checked during draftingSource blob SHA: 90b04a816d58fd6415b128817b3f2 b5dfbb8ac1e; verified against commit 84ccfa4d751fa38 01ae6430097a9a66f104ee131 (revision published 9 September 2026 at 18:45:20 UTC)
Valve disclosure fieldValue
Immutable seeding source permalinkImmutable seeding source

For initial seeding, rosters identifiable in that Global VRS snapshot are placed ahead of all unranked rosters, ordered by rank. Among unranked rosters, a recorded random draw determines order. Individual FACEIT Elo, reputation, sponsorship and a captain’s preferred placement do not supersede this rule. The same fixed snapshot is deliberately used for Q2 and LAN; there is no silent switch to October rankings. Details of roster-to-VRS matching and public seed records are in the CS2 rulebook.

6. Stages, LAN progression and replacements

Both qualifiers are online. The four-team main stage is played in person on an organiser-controlled LAN server. The approved LAN seeding gives semifinal pairings 1 versus 4 and 2 versus 3. Both semifinals and the final are BO3. There is no LAN third-place match; both semifinal losers share third–fourth place and equal prizes.

A withdrawal before the reserve cutoff is filled through the vacated qualifier’s third-place roster, then fourth-place roster, then the other qualifier’s third and fourth, excluding already-qualified or ineligible rosters. A reserve receives no preferential treatment because it is personally known to the operator. The complete sequence, acceptance clocks, multiple vacancies and late-withdrawal rules are binding in the rulebook. No replacement enters after the main stage starts.

7. Prize pool, distribution and payment

Final placementShareAmount (PKR 500,000 CS2 pool)
1st60%PKR 300,000
2nd30%PKR 150,000
Joint 3rd–4th: each semifinal loser5% eachPKR 25,000 each
Total100%PKR 500,000

The CS2 prize pool is PKR 500,000 and the placement distribution above is confirmed by the organiser. Qualifier and reserve-order matches have no separate cash prizes. No additional compensation is provided beyond the published prize pool and five-player team support: no appearance fees, MVP or participation bonuses, or revenue shares. Joint placements receive identical prize amounts.

Prizes are stated in PKR and are not contingent on a sponsor paying the operator. Prize money will be paid within three calendar months of the conclusion of the LAN finals, no later than 25 January 2027. Teams must promptly provide accurate payee information and any required payment documents through the official private contact. Any legally required withholding must be identified and evidenced. No unexplained processing charge or discretionary fine is deducted. Actual paid prizes and forfeited awards must be recorded accurately.

The nominated payee must be authorised by the playing roster or by an evidenced team agreement. The operator will not decide undisclosed private splits. A genuine payee dispute affects only the disputed award and does not justify delaying everyone else’s prizes. The full cancellation, disqualification and payment provisions appear in the CS2 rulebook.

8. All compensation and team provisions

ProvisionPublished entitlement / policy
Qualifier and LAN entry feesPKR 0
Supported delegationFive designated registered players per qualified team, with the same entitlement for every finalist team.
Return travel within PakistanBooked and paid for directly by Vidermedia for the five supported players. Individual arrangements are communicated directly to each team.
AccommodationCovered for the five supported players for the official stay needed to attend media day and the LAN finals. Individual arrangements are communicated directly to each team.
Meals and local transfersCovered for the five supported players during the official stay, including required media-day and competition activities. Arrangements are communicated directly to each team.
Coaches, additional substitutes and staffAttend at their own expense outside the five-player support allocation. Accreditation remains subject to the published role and roster rules.
Nomination and substitutionsCaptains nominate the supported five with LAN attendance details by 14 October. Lineup changes do not create additional funded places. Changes to the supported five require advance coordination and do not waive eligibility rules.
Preparation and practiceEquivalent preparation time and available practice access for teams at the same stage. Appointments are communicated with the team schedule.
Appearance payments, bonuses, revenue shares and other compensationNone beyond the published prize pool and five-player team support.

Vidermedia’s arrangements must allow supported players to attend media day on 22 October and LAN matches on 24–25 October in Karachi. Detailed bookings and accommodation arrangements are communicated privately; the published support entitlement applies equally to all finalists. Self-arranged expenditure is not an additional reimbursement entitlement.

Apply the support allocation and same-stage facilities consistently to all finalist teams. No private side letter may add selective benefits. Coaches and extra players being self-funded does not change their permitted competitive role or justify unequal treatment between teams. The final implementation must meet the applicable publisher requirements.

9. Technical arrangements

ItemDisclosure
Online competition / server platformFACEIT; qualifier registration links are published through ctrlpoint.gg, with matchrooms supplied through the official channels
ItemDisclosure
Approved online server poolDammam, Dubai and Riyadh. The rulebook’s objective latency test selects between available locations; the listed order breaks exact ties.
Mandatory client-side anti-cheatFACEIT Anti-Cheat required and enforced for online matches
Server securityVAC-secured environment or a verified publisher-compliant alternative, plus the published anti-cheat controls
LAN serverLocal organiser-controlled server; live client compatibility and recovery tested before play
Adopted map poolAncient, Anubis, Cache, Dust II, Inferno, Mirage, Nuke
Map-pool policyFixed named pool for this event, subject only to documented publisher / technical necessities; no discretionary map swap after teams are known
BroadcastOfficial online-stream links are published through ctrlpoint.gg. Any distribution must remain within the applicable licence; no linear TV or paywall under Valve’s limited licence
RecordingServer demos, match logs, veto records, lineups and results retained; access details shared securely with approved coverage staff

The current supported Valve client is used. Admins test the published server pool, Anti-Cheat enforcement, map pool, pause configuration and recovery before play. An unavailable location is excluded under the published selection procedure; adding a new location requires a recorded amendment. No unsupported or modified game build is authorised.

10. Objective integrity and exclusion rules

Eligibility exclusions are limited to the published citizenship / age / account / roster conditions; active game- or tournament-applicable Valve, chosen-platform or ESIC suspensions; a binding CTRLPOINT suspension issued through the published disciplinary procedure; documented cheating, account sharing, match manipulation or material falsification; and unresolved prohibited conflicts of interest. An old unrelated-game ban or a vague rumour is not automatically treated as a current Counter-Strike competition ban.

Every exclusion identifies its rule and evidence basis, offers the stated appeal route and is recorded publicly with proportionate redaction. A protective suspension pending investigation must be identified as provisional, not as a finding of cheating. Rules apply equally regardless of the affected roster. Financial interests or operator / staff relationships with participants are disclosed and handled under Valve Section 5.3; this rulebook does not substitute for the required relationship disclosures and approvals.

Any relevant operator or staff relationship with a participant must be publicly disclosed and approved as required by Valve Section 5.3 before that participation is allowed. Public disclosures and decisions are recorded in records/DECISIONS.md.

11. Publication and amendments

The public GitHub repository is the version-history record; the website must mirror the same release. PUBLICATION-RECORD.md records the real initial publication evidence. CHANGELOG.md records what changed, why, effective time and the relevant commit. Prior public versions are retained. No rebasing, force-pushing, deleting and re-uploading to conceal changes, or backdating announcements is permitted.

A material amendment is not made compliant merely by recording it. Dates, eligibility, qualification slots, prize/support terms, seeding and format changes require a fresh deadline review and, when necessary, a Valve exception or rescheduling. The publication process is defined in AMENDMENT-POLICY.md.

12. Source and coverage status

Primary authority: Valve Tournament Operating Requirements and Limited Game Tournament License. Coverage submission follows the current HLTV event-organiser instructions. GitHub publication proves the document history; it does not guarantee HLTV coverage or VRS inclusion.

VALORANT

VALORANT Rules

Document version 1.0.3

CTRLPOINT Pakistan 2026 — VALORANT Official Rulebook

Official competition document — Version 1.0.3. Scheduled public release: 13 September 2026. Issued by Vidermedia.

This rulebook applies to the VALORANT competition at CTRLPOINT Pakistan 2026, organised by Vidermedia, Karachi, Pakistan. Players must read it before registering. Full event disclosures and official contacts are in VALORANT Event Information.

1. Tournament Information

Eligibility: Pakistani players only, including substitutes.

Format: Two open qualifiers; top two teams from each reach the four-team LAN.

Invitations: None.

LAN city: Karachi, Pakistan.

Time zone: Pakistan Standard Time (PKT, UTC+5).

Website: ctrlpoint.gg.

Contact: sm@vidermedia.live or discord.gg/vidergg.

StageDate / deadline
Complete information and rulebook publication13 September
Both qualifiers open for registration21 September, 6:00 PM
Qualifier 1 registration closes29 September, 11:00 PM
Qualifier 11–4 October
Qualifier 2 registration closes6 October, 11:00 PM PKT
Qualifier 28–11 October
Mandatory media day22 October
LAN finals24–25 October

All dates are in 2026. The detailed calendar is in SCHEDULE.md.

Entry: Free. Cap: 128 teams per qualifier, per game. Playing roster: Five starters and up to two substitutes.

2. Participation and Rosters

2.1 Player eligibility

All playing members must hold Pakistani citizenship. Pakistani citizens abroad and dual nationals remain eligible, provided they meet the server and attendance requirements. A team organisation’s nationality does not replace player eligibility.

Players must be 16 or older on 1 October 2026. Under-18s need guardian consent and an agreed responsible adult for LAN attendance. Admins may privately check citizenship, age and account ownership. Do not post identity documents in public channels.

Players must use their own registered accounts. Account sharing, impersonation and ban evasion are prohibited. An applicable active publisher, required-platform, ESIC or CTRLPOINT suspension prevents participation. Admins must check its scope; rumours or unrelated old bans are not automatic disqualifications.

2.2 Team size and roster lock

Register five starters, up to two substitutes and one optional coach. A coach may play only if also registered in one of the two substitute slots. Each player may represent only one team per game throughout this event. One organisation may enter one roster per game; competing teams cannot share a coach or controlling owner.

Q1 rosters lock when Q1 registration closes. Q2 rosters lock at 11:00 PM PKT on 6 October 2026. A returning Q1 team must keep at least three of its original five starters. Before Q2 locks, eligible additions are allowed within the roster limit, but players from another team in this event cannot be borrowed.

Each qualifier map must include at least three of that qualifier’s declared original five. Submit the starting lineup 30 minutes before a series. Registered substitutes may enter between maps only; notify admins within five minutes of the previous map ending. Players cannot share an account or swap during a live map.

2.3 LAN roster and emergencies

The five players who win the final qualification map form the team’s qualifying core. Each LAN map must include at least three of those five. The ordinary LAN roster is the registered roster that qualified, with a maximum of seven players. A slot cannot be sold or transferred to an unrelated lineup.

One emergency addition may be approved after a roster lock for a documented serious medical, family or comparable emergency. The replacement must meet every eligibility rule, belong to no other event roster, preserve the required core and fit the seven-player limit. The removed player cannot return during that stage. Performance changes, transfers and account bans are not emergency grounds. Known requests are due by 20 October, 6:00 PM; later unforeseen cases use the same test. Public roster notices must not expose private medical details.

3. Registration and Tournament Format

3.1 Registration

Captains may enter Q1, Q2 or both. Selecting only Q1 does not automatically enter Q2. Q1 qualifiers and their entire registered playing roster, including unused substitutes, are removed from Q2. Unsuccessful Q1 teams may try again.

The cap is 128 eligible teams per qualifier, accepted by the time their registration becomes complete. Later entries form a public, timestamp-ordered waiting list. An empty form does not reserve a place. Harmless corrections retain priority; missing required details or material roster changes use the new completion time. No late private entries are allowed.

Check-in opens 60 minutes and closes 30 minutes before the team’s first scheduled match; teams with byes follow the published qualifier check-in time. Before bracket lock, vacancies go to eligible, checked-in waiting-list teams. After play starts, missing teams receive forfeits; new teams are not inserted.

3.2 Match format

Round / stageFormat
Qualifiers: Round of 128, 64 and 32Single elimination, BO1
Qualifiers: Round of 16 and quarterfinalsBO3
Qualifier semifinalsBO3; both winners qualify
Losing semifinalistsOne BO3 to establish third/fourth reserve priority
Four-team LANSingle elimination; BO3 semifinals and BO3 final

There is no qualifier grand final and no LAN third-place match. LAN semifinal losers share third–fourth place. The reserve-order match is separate and does not itself award a LAN slot.

Each qualifier lasts at most four days: opening rounds on Days 1–2, quarterfinals on Day 3, and semifinals plus the reserve match on Day 4. Qualifier matches are scheduled between 2:00 PM and 11:59 PM PKT. No new series normally starts after 10:00 PM. Admins may approve an exception in advance where both teams agree and the change is operationally viable. Exceptions must not disrupt other matches or extend the published four-day qualifier window. Teams cannot reschedule matches without admin approval. Matches run concurrently where necessary. Fewer than four checked-in teams requires a published format/deadline review, not discretionary invitations.

3.3 Seeding

Both qualifiers and LAN use a recorded random draw, with the entrant list and resulting seed order published. Teams have a one-hour correction window before bracket lock. Higher seeds receive available byes; LAN pairings are 1 vs 4 and 2 vs 3. Do not redraw for preferred opponents. CS2’s VRS rules do not apply to VALORANT.

4. Qualification, Replacements and Match Times

4.1 LAN confirmation and reserve teams

Accept a LAN place through the official channel within 24 hours. Finalists submit attendance details by 14 October, 6:00 PM. Admins publish the finalist/reserve list by 12 October and the LAN bracket and appointments by 18 October, both at 6:00 PM.

Before 21 October, 6:00 PM, a vacant slot passes to: third in its qualifier, then fourth there, then third and fourth in the other qualifier. Skip already-qualified, ineligible, withdrawn or unavailable teams. Refusing the reserve match results in a forfeit and loss of reserve availability, unless a documented genuine emergency justifies an exception.

Process multiple vacancies in recorded order; simultaneous vacancies use Q1 before Q2, then original slot ID. A team may accept only one slot. Each reserve has 12 hours to reply, shortened only by the cutoff; do not issue an offer allowing fewer than two hours. Notify reserves of this process by 12 October and record offers and responses.

A replacement confirmed before bracket publication is seeded normally. Later accepted replacements take the vacant position without inheriting the departed team’s ranking. Recalculate veto priority between the actual teams; use a recorded toss where two unranked teams have no comparable draw position. No new team enters after the cutoff or after LAN play starts. Unfilled slots become byes/forfeits.

4.2 Match readiness

Captains must monitor the official channel. Round appointments are published at least 24 hours before the qualifier starts, even where opponents are not yet known. Teams cannot privately reschedule. Allow at least 20 minutes between series and 10 minutes between maps. Starting early requires both captains’ agreement and admin approval.

Join the server/lobby 15 minutes before match time. Five eligible players are required to start. After 15 minutes of lateness, the team forfeits the first unplayed map. In a BO3, another 15 minutes of unavailability forfeits the series. Organiser-caused delays and common outages are handled separately. Two absent teams may both be eliminated.

Do not restart, surrender, change the server or alter a score without admin approval. Dual-game participation does not entitle a player to a schedule change.

5. VALORANT Match Rules

5.1 Accounts, servers and maps

Register each player’s Riot ID and tag. Matches use the Middle East server pool: Bahrain and Dubai. Every account must legitimately access those servers in the same custom-game lobby; account sharing or region-restriction bypasses are not allowed.

Use the supported PC client with Vanguard enabled. On-site finals do not themselves provide an offline Riot server. No borrowed accounts or assumed tournament-client access are allowed.

Use the approved server pool. Under the server-selection procedure, test all ten players for five minutes and choose the stable server with the lowest worst-player median latency, then lowest average; break an exact tie in the order Bahrain, Dubai. Record any unavailable or unstable option. Do not silently substitute a new location or change servers for tactical reasons.

Map pool: Abyss, Ascent, Haven, Lotus, Split, Summit and Sunset. Once published, it stays fixed unless a publisher restriction or serious technical issue requires an announced change.

An agent must have been available in the live competitive queue for 14 full days before the stage begins. Eligibility does not change halfway through a qualifier or LAN. Disabled agents and specific bugged content cannot be used; admins publish any additional restrictions equally.

5.2 Lobby and match settings

SettingValue
Platform / modePC; closed Standard custom game
PlayersFive eligible players per team
Tournament ModeOn
Allow CheatsOff
Overtime: Win By TwoOn
Play Out All Rounds / Hide Match HistoryOff / Off
Observer accessApproved officials/broadcast only; registered coach in supported coach slot

Broadcast observers use Show Blood off. Admins verify the settings and pause controls on the match client before play. Admins approve the host and verify both teams before starting.

Regulation uses 12-round halves. First to 13 wins unless tied 12–12; then use repeated win-by-two overtime with native overtime economy and side changes. No draws or private changes to overtime are allowed.

5.3 Map veto and agent selection

The higher seed chooses Team A or B. Each action has 60 seconds and a final 30-second warning. If time expires, the admin records a random legal choice. A valid selection is final after the next action, except to correct an official’s recorded error.

BO1: A ban → B ban → A ban → B ban → A ban → B ban. Play the remaining map; A chooses attack or defence.

BO3: A ban → B ban → A pick → B pick → A ban → B ban. The opponent chooses the starting side on each picked map. The remaining map is Map 3; A chooses its starting side. Stop after two map wins.

Report an accidental agent selection before the selection timer ends and state the intended agent immediately. An admin may permit one correction without changing other revealed selections or allowing counter-picking. Technical lobby remakes keep the map, sides and revealed selections. Deliberate dodging is prohibited.

6. Pauses, Disconnections and Recovery

Each team has two 60-second tactical timeouts in regulation and one 60-second timeout for the overtime portion. Unused regulation timeouts do not carry over. Request within the first 20 seconds of the buy phase; later requests wait for the next legal phase. No tactical timeout interrupts live action.

Coaches may speak during tactical timeouts, approved halftime, pre-map and between-map breaks—not during live rounds, normal buy phases or technical pauses.

For a technical issue, report TECH and the reason immediately. Pause only through the approved controls at a legal phase. Each team has up to 5 minutes per map for its own connection/equipment problems. Organiser equipment, network and common Riot outages do not use this allowance. A documented short extension may be granted consistently. Only technical discussion is allowed during the pause.

A disconnected player may reconnect on their own account. No account handover or different player joining mid-map is allowed. If the player cannot return in the allowed time, an admin may declare a map/series forfeit. Registered substitutes may enter between maps within the usual break.

Early restarts require an immediate report before damage, a planted spike or decisive revealed information. Completed valid rounds stand wherever technically recoverable. CTRLPOINT does not assume access to VCT rollback tools or enable arbitrary cheats to recreate a score.

For a common fault that cannot be faithfully restored, the head admin may suspend play and, as a last resort, order a full map replay with the original map, sides and agents. Record the reason; an individual disconnect or being ahead does not automatically award a replay or win.

Captains submit the final score screenshot and lineup within 10 minutes. Admins retain available replays, screenshots, vetoes and relevant recordings/logs for at least 90 days, longer for an open case.

7. Conduct and Fair Play

Treat players, officials, spectators and broadcast staff respectfully. Harassment, discrimination, threats, violence and abusive spam are prohibited. Players must compete honestly; match-fixing, betting on event matches and sharing inside information for betting are prohibited for participants and event staff.

Cheats, account sharing, unregistered players, stream-sniping, hidden-information tools, network attacks, recoil/movement automation and unapproved real-time assistance are prohibited. Legal native settings remain allowed. Do not exploit broken geometry, unintended invulnerability or game-breaking bugs. Ask an admin before using a doubtful interaction; unfamiliar legitimate play is not automatically an exploit.

Do not tamper with Vanguard or use automated agent-selection tools. Report suspected bugs with evidence. No professional challenge token is required; admins publish specific restrictions rather than banning every unfamiliar ability lineup.

Only active players, the permitted coach and authorised officials may join match communications. Managers, substitutes and spectators must not feed information. Players must not watch the live broadcast during a match.

Use registered nicknames and approved team/sponsor branding. Submit name/logo changes for approval. Sponsor content must meet the publisher and event restrictions in VALORANT Event Information. Do not claim publisher endorsement. Disclose relevant team/staff financial or ownership relationships; conflicted officials cannot decide the affected case.

8. Protests and Penalties

Report match issues immediately. The captain has 15 minutes after the series to submit a result/eligibility protest, preferably before dependent play begins. Include the rule, map/round, explanation, requested remedy and evidence. Newly discovered cheating or fraud may be reviewed later. A social-media accusation alone is not proof.

Admins give written reasons for decisions affecting results, prizes or eligibility. Disqualifications and amendments are published with private information removed. Live appeals are due within 15 minutes of the decision; other appeals within 24 hours. An unconflicted senior official reviews material errors, inconsistent enforcement, unfair sanctions or significant new evidence. The aim is a ruling before dependent play, normally within 48 hours otherwise. Play follows the existing ruling unless the appeal official pauses it.

BreachNormal response
First minor administrative errorWarning and correction deadline
LatenessMap/series forfeits in Section 4.2
Improper coaching or exploit abuseWarning, timeout loss, coach removal or round/map/series penalty, according to impact and repetition
Ineligible player, roster fraud, proven cheating or match-fixingMatch/stage disqualification and result/prize review; serious individual misconduct may bring a reasoned suspension up to 24 months
Serious harassment or threatsRemoval/disqualification; suspension up to 12 months, or 24 months for violence/repeated severe misconduct

Penalties must match the evidence and impact. Missing evidence alone does not prove cheating; deliberate obstruction may receive a stronger sanction. Use round penalties only where the game can apply and record them accurately. Record forfeits as administrative results, not invented played statistics. Good-faith criticism and valid welfare requests do not justify prize deductions. An accusation against one player does not automatically establish every teammate’s personal guilt.

9. LAN Attendance

All finalists must attend in person in Karachi, Pakistan. Media day is mandatory on 22 October for the five designated LAN players of each team. LAN matches take place on 24–25 October. Teams must arrive in time for their published media appointment. There is no compulsory media or match appointment on 23 October. Team support terms are in VALORANT Event Information.

Teams receive equal preparation time and published practice access. Players may use approved personal peripherals. USB drives, downloads and software/config changes need admin approval.

Follow venue safety rules and arrange ordinary breaks through officials. Urgent health needs take priority. Players must not compete while intoxicated, and necessary medical treatment must not be withheld. Staff will privately consider documented welfare or accessibility needs.

10. Broadcasts, Media and Privacy

Players must cooperate with official coverage and published interviews, photoshoots and ceremonies. Wear approved jerseys or matching attire. Report genuine attendance or welfare problems promptly; missing media does not automatically forfeit every prize.

Player POV streams and co-streams need written approval, requested 48 hours before the stage where practical. Approved online streams use at least 180 seconds’ delay. No clean live production feed or unapproved observer access is provided to teams.

Participants allow Vidermedia to record and use event gameplay, names/aliases, team branding, photos, interviews and approved match communications for this event’s coverage, archive and promotion, including event-related sponsor recaps. Archives may remain online. Unrelated advertising and false personal endorsements are not included. Guardian consent covers minors. Riot may also use event content under its applicable competition licence; the participant notice must explain those rights separately.

Comms and player-camera clips, including In The Comms, are published only after the series. Remove private, sensitive or security information. Public records may include approved game IDs, eligibility status, results and decisions—not identity scans, private contacts or bank details. Routine identity copies are deleted within 90 days after the event or verification dispute closes unless longer retention is legally required; relevant integrity/financial records follow their own retention duties. Raise privacy concerns through the published private contact.

11. Prizes and Team Support

The combined event prize pool is PKR 1,000,000. The prize pool for this game is PKR 500,000, distributed as follows:

PlacementPrize
WinnerPKR 300,000
Runner-upPKR 150,000
Joint third–fourthPKR 25,000 per team

Qualifier and reserve matches have no separate cash prizes. Vidermedia will book and cover return travel within Pakistan, accommodation, meals and local transfers for five designated players per qualified team. Coaches, substitutes outside those five and additional staff attend at their own expense. Teams name their five supported players when confirming LAN attendance; a lineup change does not add funded places.

Individual arrangements are communicated directly to each team. The same five-player support entitlement applies to every finalist team.

There is no additional compensation beyond the published prize pool and five-player team support. No appearance fees, MVP bonuses, participation bonuses or revenue shares are provided.

A roster nominates an authorised payee. Prize money will be paid within three calendar months of the conclusion of the LAN finals, no later than 25 January 2027. Teams must promptly provide accurate payee information and any required payment documents through the official private contact. A genuine payee or integrity dispute may hold only the affected award, with written reasons and updates; other awards remain payable on time.

Awards are gross PKR; any legally required withholding must be evidenced. Vidermedia covers sender-side fees. Sponsor delays do not excuse non-payment. No hidden fines or deductions are permitted.

A team that never competes at LAN does not earn a placement prize. Disqualification or cancellation consequences require a published decision; the normal pool is not silently reduced or redistributed. Record actual paid awards accurately and preserve unaffected teams’ entitlements.

12. Administration and Rule Changes

The approved rulebook and VALORANT Event Information apply together, subject to binding publisher rules and law. Event facts, full support terms and source records remain in the event-information documents. Unpublished staff notes are not binding on players.

Changes must be dated, recorded on GitHub and announced through official channels. Do not change eligibility, format, dates, prizes or seeding privately or retrospectively. Material amendments require the relevant notice/licensing review. See AMENDMENT-POLICY.md.

For outages, safety emergencies or serious bugs, admins may stop play, preserve evidence and issue a fair documented ruling. Cancellation/postponement notices must explain schedule, prize and support consequences. A fifth qualifier day or extra mandatory attendance day is not automatically authorised. Non-refundable personal costs are not automatically reimbursed; rights that cannot legally be excluded remain protected.

Captains share the current rules with all members. Adults accept personally; minors require guardian consent. There are no automatic 2027 league rights or guaranteed ranking points from entering this event.

VALORANT Event Information

VALORANT Event Information

Document version 1.0.3

CTRLPOINT Pakistan 2026 — VALORANT Event Information

Official competition document — Version 1.0.3. Scheduled public release: 13 September 2026. Issued by Vidermedia.

1. Identity and licensing

CTRLPOINT Pakistan 2026 — VALORANT is an independent PC community competition operated by Vidermedia, with two online qualifiers, mandatory media day on 22 October, and four on-site finalists competing in Karachi, Pakistan, on 24–25 October 2026. The main-event attendance window is 22–25 October, with appointments as published. It is not a VCT, Challengers, Premier promotion event or a Riot-operated competition. No Riot circuit qualification, points or endorsement is promised.

This competition is not affiliated with or sponsored by Riot Games, Inc. or VALORANT Esports. This independence statement is not a substitute for the actual applicable licence.

The event is subject to the applicable Riot Community Competition Guidelines or a separate written licence where required. The operator is responsible for the required event notification and permissions. No Riot approval, tournament-realm access or linear-TV right is implied by publication of these rules.

ItemOfficial information
Event owner / operating brandVidermedia / CTRLPOINT
Tournament operator / locationVidermedia, Karachi, Pakistan
Tournament administrationVidermedia competition administration, reachable through the contacts below
Tournament support emailsm@vidermedia.live
Official participant support / Discorddiscord.gg/vidergg
Registration and official websitectrlpoint.gg; qualifier registration links are published there
Public version historyGitHub copy linked through ctrlpoint.gg; this release and subsequent amendments are retained
LAN cityKarachi, Pakistan
Private eligibility, privacy and safeguarding enquiriessm@vidermedia.live

2. Eligibility and entry

Pakistani citizens only, including substitutes. Citizenship is assessed at player level, not by team flag or organisation headquarters. Dual citizenship is permitted where Pakistani citizenship is valid. This event does not add a Pakistan-residency condition. Players must have legitimate Riot accounts in the published shard, meet the common minimum age of 16 on 1 October 2026 and be able to attend in person if qualified.

Confirmed event settings: Free entry; 128 accepted teams per qualifier per game; five starters and up to two substitutes; two single-elimination qualifiers, BO1 through the Round of 32 and BO3 from the Round of 16; both semifinal winners qualify; the losing semifinalists play a BO3 reserve-order match. The four-team LAN uses BO3 semifinals and a BO3 final, with no third-place match. Each game has a confirmed PKR 500,000 prize pool, distributed 60% / 30% / 5% / 5%.

Every participant must be eligible under their Riot account’s binding restrictions. The rules do not authorise account sharing, borrowed tournament accounts or bypassing a regional account restriction.

3. Shared timetable

Date / time (PKT, UTC+5)Milestone
13 September 2026 — scheduled public releasePublish complete event information, both rulebooks, all registration conditions and the two qualifier schedules. Record actual publication timestamp.
17 September 2026Valve Additional Information deadline for the 1 October first qualifier. Recheck the applicable Valve requirements version.
21 September 2026, 18:00Registration opens for Qualifier 1 and Qualifier 2, for CS2 and VALORANT simultaneously.
29 September 2026, 23:00 PKTQualifier 1 registration and submitted-roster editing close for both games.
30 September 2026Qualifier 1 verification, check-in instructions, seeding and bracket publication.
1–4 October 2026Qualifier 1, maximum four competition days.
6 October 2026, 11:00 PM PKTQualifier 2 registration and submitted-roster editing close simultaneously for both games. Includes the published reserve-order matches. Publish the exact closure timestamp and event log.
7 October 2026Qualifier 2 verification, check-in instructions, seeding and bracket publication.
8–11 October 2026Qualifier 2, maximum four competition days.
Within 24 hours of earning a LAN placeCaptain confirms acceptance and ability to attend; failure triggers the published replacement process.
12 October 2026, 18:00Publish the initial finalist and reserve register, subject only to identified pending decisions.
14 October 2026, 18:00Finalists submit LAN attendance, accreditation and payment-contact details privately. This does not reopen playing-roster additions.
18 October 2026, 18:00Publish LAN seeding, bracket, detailed match times, practice allocation and media appointments.
20 October 2026, 18:00Final roster administration check and deadline for known, documented emergency-addition applications. Later unforeseen emergencies use the same narrow eligibility test.
21 October 2026, 18:00Ordinary reserve-replacement cutoff. Thereafter, no new team enters; unresolved vacancies become published byes / forfeits.
Date / time (PKT, UTC+5)Milestone
22 October 2026Mandatory media day for all five designated LAN players of every finalist team, in both games. Exact appointments are published by 18 October.
23 October 2026No scheduled competition or compulsory media activity; preparation / rest day.
24–25 October 2026Four-team CS2 LAN finals and four-team VALORANT on-site finals.
25 January 2027Prize-payment deadline: three calendar months after the LAN finals conclude. Teams must supply complete payee documents promptly.

Both qualifier registration forms open together. Teams may select either qualifier or both. Q1 qualifiers cannot enter Q2. Q2 registration closes at 11:00 PM PKT on 6 October 2026 for both games. Teams that qualified through Q1 are removed from Q2 before the Q2 bracket is finalised.

Qualifier matches are scheduled between 2:00 PM and 11:59 PM PKT. No new series normally starts after 10:00 PM. Admins may approve an exception in advance where both teams agree and the change is operationally viable. Exceptions must not disrupt other matches or extend the published four-day qualifier window. Teams cannot reschedule matches without admin approval.

4. Format and seeding

Two independent single-elimination qualifiers: BO1 through Round of 32; BO3 from Round of 16. Each qualifier sends its two semifinal winners to the main event. The losing semifinalists play a BO3 reserve-order match within the four-day window. There is no qualifier final and no extra LAN slot from the reserve-order match.

Initial VALORANT seeding is a recorded random draw. CS2 VRS, FACEIT Elo, Riot ranked tiers and organiser reputation assessments are not VALORANT seeding rules. LAN seeding is a fresh recorded random draw of the four qualified rosters, with semifinals 1 versus 4 and 2 versus 3. The LAN uses BO3 semifinals and a BO3 final. The two semifinal losers share third–fourth place; no third-place LAN match is held.

Replacements follow the same published qualifier-based reserve sequence as the rulebook; they are not discretionary invitations. Ordinary replacements end at 18:00 PKT on 21 October and no replacement enters after the main stage begins.

5. Prize and support

Final placementShareAmount per game (PKR 500,000 pool)
1st60%PKR 300,000
2nd30%PKR 150,000
Joint 3rd–4th: each semifinal loser5% eachPKR 25,000 each
Total100%PKR 500,000

The combined CS2 and VALORANT event prize pool is PKR 1,000,000. The equal split and placement distribution above are confirmed by the organiser. Qualifier and reserve-order matches have no separate cash prizes. No additional compensation is provided beyond the published prize pool and five-player team support: no appearance fees, MVP or participation bonuses, or revenue shares. Joint placements receive identical prize amounts.

Prize money will be paid within three calendar months of the conclusion of the LAN finals, no later than 25 January 2027. Teams must promptly provide accurate payee information and any required payment documents through the official private contact. Any legally required withholding must be evidenced. Payment is not contingent on sponsor payment. Detailed rules are in VALORANT-RULEBOOK.md.

ProvisionPublished entitlement / policy
Qualifier and LAN entry feesPKR 0
Supported delegationFive designated registered players per qualified team, with the same entitlement for every finalist team.
Return travel within PakistanBooked and paid for directly by Vidermedia for the five supported players. Individual arrangements are communicated directly to each team.
AccommodationCovered for the five supported players for the official stay needed to attend media day and the LAN finals. Individual arrangements are communicated directly to each team.
Meals and local transfersCovered for the five supported players during the official stay, including required media-day and competition activities. Arrangements are communicated directly to each team.
Coaches, additional substitutes and staffAttend at their own expense outside the five-player support allocation. Accreditation remains subject to the published role and roster rules.
Nomination and substitutionsCaptains nominate the supported five with LAN attendance details by 14 October. Lineup changes do not create additional funded places. Changes to the supported five require advance coordination and do not waive eligibility rules.
Preparation and practiceEquivalent preparation time and available practice access for teams at the same stage. Appointments are communicated with the team schedule.
Appearance payments, bonuses, revenue shares and other compensationNone beyond the published prize pool and five-player team support.

Vidermedia’s arrangements must allow supported players to attend media day on 22 October and LAN matches on 24–25 October in Karachi. Detailed bookings and accommodation arrangements are communicated privately; the published support entitlement applies equally to all finalists. Self-arranged expenditure is not an additional reimbursement entitlement.

Apply the support allocation and same-stage facilities consistently to all finalist teams. No private side letter may add selective benefits. Coaches and extra players being self-funded does not change their permitted competitive role or justify unequal treatment between teams. The final implementation must meet the applicable publisher requirements.

6. Technical environment

ItemDisclosure
PlatformPC VALORANT; current supported live client unless Riot expressly provides a different authorised environment
Match account shardAccounts must legitimately access the Middle East Bahrain/Dubai custom-game server pool together. Admins verify server access before matches.
Approved server poolMiddle East: Bahrain and Dubai. The rulebook’s objective latency test selects between available locations; Bahrain then Dubai breaks exact ties.
Online lobby processOrganiser-controlled private custom matches; higher seed may create an unbroadcast lobby only under the published admin procedure
Anti-cheatRiot Vanguard must operate normally on each playing machine
On-site finalsPlayers attend the same physical venue; live-client matches still use the published Riot-hosted server unless an authorised tournament environment is explicitly secured
Fixed map poolAbyss, Ascent, Haven, Lotus, Split, Summit, Sunset
New agentsEligible only after 14 complete days from live competitive release before the start of the relevant qualifier / LAN stage, subject to published disables
Custom-game baselineStandard mode; Tournament Mode on; cheats off; win-by-two overtime on; play out all rounds off; match history visible
Official streamsOfficial stream links are published through ctrlpoint.gg
Player / coach / observer accessOnly registered players, the authorised non-playing coach slot where supported, and approved officials / observers

The fixed map pool is an event choice, not a claim that VCT mandates it for CTRLPOINT. Admins test the supported client and published custom-lobby settings before play. Any necessary server or map change follows the recorded amendment process. No private Riot LAN server, tournament realm, round rollback or live scoreboard API is promised.

Review every sponsor, participant jersey, overlay and activation against the current Riot community licence. Sponsors may be described in the permitted supporting / presenting form, not by misrepresenting Riot endorsement. VALORANT assets may promote the competition but must not be used as a product endorsement. The community licence does not permit linear-TV distribution. Official online-stream links are announced through the event website and Discord.

This event adopts an additional family-appropriate production policy: Show Blood off on observer and broadcast clients, moderated public chat, and no prohibited sponsor content. These production choices do not import superseded licence thresholds.

8. Public records and amendments

The website mirrors the same release as GitHub. Actual publication evidence, changelog, registration records, Q2 closure, seeding, results and reasoned disciplinary outcomes are retained through the public record structure. Private identity, welfare and payment data are excluded.

The VALORANT rulebook and any mandatory Riot terms govern VALORANT, not Valve’s CS2 operating requirements. The shared registration schedule is an operational choice. Follow AMENDMENT-POLICY.md; no silent changes or retrospective eligibility exceptions.

Full rules: VALORANT-RULEBOOK.md. Research and source distinctions: SOURCES.md.