Steel Flower X Nicecactus Championship: Competition Handbook EN - English

Steel Flower x Nicecactus Championship
Competition Handbook
EN | English
Revision 43
SECTION 1. INTRODUCTION
1.1. Document introduction

The content of this document serves as an official document representing the Regulations
(”Ruleset”) for Steel Flower x Nicecactus Championship (abbreviated as “SFNC”) and
its related Events (referred as Event). The document is valid for all related phases of the
Event, including, “ Regional Qualifiers”, “Main Phase”, etc. All Participants
(“Players”, “Captains” and or “Teams) have to agree to abide by the Regulations and
any violation of the set Regulations will result in immediate action and possible issuing
of Penalties and/or forfeiture of any Prize Rewards (”Credits”, “Cases”, and Prize
Money) earned throughout the Event.
1.2. Privacy Policy

By participating in the Event you agree to share the following information to the Steel
Flower Tournaments (“Event Organizers”)
1.2.1. Personal Information
Full Name, Nickname, Country of Residence, Preferred Language of
Communication
1.2.2. Device Information
Device Make and Model, Serial Number, iOS Version or Android Version,
Linked Apple ID or Google Account
1.2.3. Critical Ops Account Information
In-Game Name, Account ID, Statistics
Steel Flower Tournament or Nicecactus will not share any confidential information to
any third party, including Critical Force.
1.3. Document notice

Steel Flower Tournament retains the rights to
(a) modify, amend or extend the contents of the document from time to time;
(b) immediately apply modifications to this document by releasing public announcements on
media that provides guidance to Participants;
(c) immediately apply amendments to this document with or without further notice to
Participants.
Tournament Officials also have the rights to make decisions which are not based on the
content of this Ruleset, and in special cases, decisions that are against this Ruleset, in
order to preserve fair play and sportsmanship.
SECTION 2. EVENT OVERVIEW

2.1. Terminology breakdown
Page 1
Revision 43
Produced by Steel Flower Tournament
2.1.1. Event. Refers to the Steel Flower x Nicecactus Championship, and its related
events (Q, MP, Community Events) as a whole.
2.1.2. Event Organizer. Refers to Steel Flower Tournament and Nicecactus, the hosts of
the Event.
2.1.3. Event Administrator (abbreviated Event Admin). Event Admins are employed
by Steel Flower Tournament and act as the primary point of communication between the
Event Organizer and the Participants.
2.1.4. Event Staff. Event Staff are employed by Event Admins. Serves as a secondary
point of communication between the Event Organizer and the Participants and handles
logistics during the Event.
2.1.5. Team. Refers to a group of five (5) to eight (8) Players who have grouped together
in order to participate on a single side of the Event.
2.1.6. Team Representative. A Team must have at least one (1) Team Representative
which acts as a primary point of contact for that Team for all concerns regarding that
Team, including but not limited to: map vetoes, protests, roster changes and match result
reports.
2.1.7. Phase Round. Refers to a group of Matches in the Tournament which determines
the eligibility of one Team in a single Match in order to advance to the next Phase Round
depending on the result of that Match.
2.1.8. Match. Refers to a single instance in the Event that is played until one Team meets
the victory condition of that Match. A Match can have a single Set (Best-of- One – Bo1)
or a series of Best-of-Three (Bo3) or Best-of-Five (Bo5) Sets.
2.1.9. Set. Refers to a single game in a Match.
2.1.10. Single Elimination. A tournament format in which a Team is eliminated from the
Event upon losing one (1) Match.
2.1.11. Double Elimination. A tournament format in which a Team is eliminated from

the Event upon losing two (2) Matches. A Team is moved to a Losers Bracket upon
losing their first Match, in which they are eliminated from the Event upon losing one (1)
Match in the Losers Bracket.
2.2. Event Admins List

Please contact the following Event Admins on Discord by Direct Messages for any queries
regarding the Event.
Page 2
Revision 43
Nickname Discord Position

Hika Hika#0245 CEO 2.3.
Pearl Pearl#5133 CEO
Oliu Oliu#6132 CEO
sauce sauce#4239 Operations Head
TrapZ TrapZ#7621 Operations Head
Excited Excited#9999 AS Regional Director
EcoDynasty EcoDynasty#2331 NA Regional Director
JvnX JvnX#7777 SA Regional Director
Violence Violence#1234 EU Regional Director
Ezcrash Ezcrash#6636 EU Regional Director
1Time 1Time#2063 AS Regional Admin
Dominite Dominite#4307 AS Regional Admin
CnL CnL#5543 EU Regional Admin
Nataliax Nataliax#5081 EU Regional Admin
Media rights
All broadcasting rights of SFNC are owned by Steel Flower Tournament. This includes but is not
limited to, match live streams (shoutcast or not), interviews, articles, and video replays.
2.3.1. Rebroadcasting rights

A full livestream replay, shoutcast or not, may be reuploaded without monetization by the
Participants and Event Media Staff involved during the event of the livestream. This
includes but is not limited to, participating Teams and Participants, shoutcaster(s) and
Event Staff. A fraction of the replay in question, which duration is less than ten (10)
minutes, may be used in other materials by anyone.
2.4. Confidentiality
All communications with the Event Admin team, including but is not limited to, match protests,
recording assessment results and discussions are deemed strictly confidential and may not be
shared to any third party.
All audio recordings, anti-cheat video recordings and confidential identifying information is
deemed strictly confidential and will not be shared to any third-party, as stated in Sect. 1.2.
Privacy Policy.
2.5. External documents

All Participants are subject to Critical Ops Terms of Use and Code of Conduct, Nicecactus
Terms of Service, and Discord Terms of Service and Community Guidelines.
Page 3
Revision 43
SECTION 3. PARTICIPATION REQUIREMENTS, ELIGIBILITY AND

RESTRICTIONS
3.1. Age limitations
All Participants must be thirteen (13) years of age or older in order to participate in the Event.
3.2. Participation prerequisites

3.2.1. Required accounts
All Participants must own and possess the following accounts at the time of participation:
3.2.1.1. One (1) Critical Ops account linked to a social media
3.2.2.1. One (1) Nicecactus account
3.2.2.1. One (1) Discord account
3.2.2. Media Requirements

All participating Teams are required to post a pre-made tournament announcement on
their Discord server announcement channels (if applicable). Further details may be given
by the Event Admin team during registration.
3.3. Critical Ops account eligibility & requirements

3.3.1. Account eligibility
All Participants are required to own the Critical Ops account they are participating in the
Event with. Participants are required to claim ownership of the account by providing the
In-Game Name and Account ID of the account in question during registration.
3.3.1.1. Account trading and sharing are strictly prohibited throughout the
Event and will not be allowed under any circumstances, as stated in the Critical
Ops Code of Conduct. Violation of this rule will result in an immediate
disqualification from the tournament and forfeiture of any pending Prize Rewards
earned throughout the Event.
3.3.2. Account requirements

All Participants must have a Critical Ops account that meet the following requirements:
(a) must have at least 7500 Kills, Ranked Games and Custom Games combined, on
record
(b) must have at least 1 Ranked Game played on record
(c) must have a recognizable In-Game Name (In-Game Names like “dauygdsuyda”,
“273981729”, “OPS-123890729” (or “OPS-XXXX” or “OPERATIVE-XXXX” – replace
XXXX with a number string) are forbidden)
(d) must be linked to a social media account (Facebook, Game Center, Apple ID,
Google Play Games)
(e) must have an appropriate In-Game Name, the name cannot include any word or
phrase which others may find offensive, nor any blasphemous terms. If you would like to
Page 4
Revision 43
inquire about your In-Game Name and it's eligibility please contact a Steel Flower
Tournament Staff Member.
3.4. Regional restrictions

The Regional Qualifiers are split into 4 regions. Participants will compete exclusively within
their corresponding regions during this phase.
3.4.1. Region switching

A Team may only change their desired region before the Seeding Phase of an upcoming
Regional Qualifier.
3.5. Participation per Organization

One (1) Team is considered to belong to one (1) Organization the Team is representing.
3.5.1. An Organization is allowed to own and operate up to three (3) Teams, either
(a) across up to three (3) regions, with one (1) Team per region OR
(b) within one (1) single region, with up to three (3) Teams in the same
region.
3.5.2. All Teams within an organization must be separately distinguished from each
other.
e. g. Steel Flower Asia / Steel Flower Europe
Steel Flower Competitive / Steel Flower Casual
Steel Flower Red / Blue
3.5.3. An Organization must be represented by a centralized Organization

Representative. This may be a Team Representative of a currently existing Team
within the Organization in question, or a separate individual. The Organization
Representative may be able to act as a Team Representative of all teams within
the Organization.
3.5.3.1. A Team Representative may not be the Team Representative of a

different Team that does not belong to the Organization that owns
the original Team.
3.5.4. During registration, the Organization or Team Representative must notify the
Event Admin team of any Team(s) within their Organization that participate in the Event.
3.5.5. The Organization Representative must notify the Event Admin team of any active
team acquisition, separation or disbandment of any team within their Organization during
the Event.
Page 5
Revision 43
3.6. Software version

3.6.1. Operating system/Firmware Version
Players must use the latest stock OS for their devices. The following is the list of latest
OS versions for certain devices:
Page 6
Revision 43
iPhone 6s (Plus), iPhone 7 (Plus), iPhone 8 iOS 14.6

(Plus), iPhone X, iPhone Xs (Max), iPhone
XR, iPhone 11 (Pro, Pro Max), iPhone 12 3.6.2.
(Pro, Pro Max), iPhone SE (1st generation and
2nd generation)
iOS 14.6 Game
iPad Pro (1st generation (2016) – 5th
generation (2021, M1)), iPad (5th generation –
7th generation), iPad mini (4th generation and
5th generation), iPad Air (2nd generation – 4th
generation)
iOS 12.5.4
iPhone 6 (Plus), iPhone 5s
Android 11
Google Pixel 2 / 2 XL / 3 / 3 XL / 3a / 3a XL /
4 / 4 XL / 4a / 4a 5G / 5
Samsung Galaxy S10 / S10 Plus / S10e / S10

Lite / S20 / S20 Plus / S20 Ultra / S20 FE /
S21 / S21 Plus / S21 Ultra
Samsung Galaxy A32 / A51 / A52 / A72
Samsung Galaxy Note 10 / Note 10 Plus /

Note 10 Lite / Note 20 / Note 20 Ultra
OnePlus 8 / 8 Pro / 8T / 9 / 9 Pro
Sony Xperia 1 II / 5 II / 10 II
Xiaomi Mi 10 / Mi 10 Pro / Mi 10T / Mi 10T

Pro / Mi Note 10 / Mi 11 / Mi 11 Ultra / Mi
11 Lite 5G
Xiaomi Pocophone F1 / F2 Pro / X3 Pro
Xiaomi Redmi Note 10 / Note 10 Pro
Nokia 1.4 / 3.4 / 8.3 5G / X20
LG Velvet
Lenovo Legion Phone Duel 2
Nubia Red Magic 6
Asus
Page 7ROG Phone 5
Revision 43
Version
3.6.2.1. Must use the latest live version of the game available
3.6.2.2. Participants are prompted to update their version of the
game as soon as it becomes available.
3.7. Devices & equipment
3.7.1. Allowed devices
(a) Smartphones
(b) Tablets
3.7.2. Prohibited devices
(a) PC
(b) Emulation
3.7.3. Allowed equipment
(a) Headphones and earphones, wired or wireless
(b) Gloves
(c) Capture Cards (for screen recording)
(d) Stands
3.7.4. Illegal equipment
(a) Keyboard and/or Mouse
(b) Controllers, wired or wireless
(c) Third party apps or equipment which gives the participant an unfair
advantage
SECTION 4. EVENT DETAILS

4.1. Phases
4.1.1. Regional Qualifiers
The Regional Qualifiers are held for four (4) days and are hosted using Nicecactus.gg,
with two (2) extra “turnaround” days to complete any overdue matches at the discretion
of the Event Admin team. Before each Phase Round all Participants are notified through
the exclusive captain Discord channel and through Nicecactus.
4.1.1.1. This phase uses the Single Elimination format. (See Sect. 4.1.1.2.
The last standing four (4) teams from each Regional Qualifier will advance to the
Main Stage.
4.1.2.1. There will be no Event Staff present in Qualifier Matches from the
start of the phase until Phase Round of 16. From Phase Round of 8 Event Staff
will always be present in Matches.
Page 8
Revision 43
4.1.2.1.1. In this case, Team Representatives are required to host the

Match Room for their Matches.
4.1.1.3. All matches until the Qualifier Finals will be Bo1 Matches. The
finals will be a Bo3 Match.
4.1.1.4. Each Round of the phase must be completed within twelve-hours

(12) hours, from 10:00 (10:00 AM) to 22:00 (10:00 PM) during the day.
4.1.1.4.1. All Matches must be scheduled within the day. In the case a
team refuses to play or to schedule the match, the team in question will be
disqualified from the Event.
4.1.1.4.2. Any self-hosted rooms must be hosted ten (10) minutes
before the agreed scheduled time.
4.1.1.5. Players must join the room as soon as the match information is
given out to the Team Representatives. Players have a maximum of fifteen (15)
minutes to join the room after the match information has been sent.
4.1.1.5.1. Any Player that joined after the maximum allowed time
must provide a reason for late arrival to an Event Admin. The allowed
overtime before the Player in question violates this rule is five (5) minutes.
If a player fails to show completely the team in question will be subject to
penalties.
4.1.1.6. After each match, each Team Representative must submit and
verify the match results, including the scoreboard screenshot. This is not required
if the losing Team Representative performs the submission.
4.1.1.7. The Match may only be marked as FINISHED if the Event Admin
team has verified and finalized the results.
4.1.1.7.1. If the Match requires a Rematch (“RM”), the Match will
be rescheduled on a “turnaround” day. The time may be fixed by an Event
Admin if necessary.
4.1.1.8. No players should leave the Match before the final match
scoreboard. Doing so will result in penalties to the player and or team.
4.1.1.9. Using the ALL CHAT feature for any reason other than
administrative communications is prohibited. Teams are given one (1) strike for
each offense, for a maximum of three (3) strikes before the Team in question is
issued a forced match forfeiture.
4.1.1.10. For any substitutions during a Match, the Team Representative(s)
must notify the Event Admin team in advance. This can be done during the match
within the In-Game Chat, on discord, or before the match begins.
Page 9
Revision 43
4.1.1.11. If any substitute player joins the player in question is required to, be
on the teams roster, and perform the applicable anti-cheat measures.
4.1.1.12. The Match may begin if the number of Players per team is or
higher than four (4) players.
4.2.1. Main Stage
The Main Stage is hosted as a global event. Duration and exact schedule is to be
determined.
4.2.1.1. This phase uses the Double Elimination format. (See Sect. 2.1.11.)
4.2.1.2. All teams are required to join a voice channel in the captain
Discord server. All team voice communications are audio recorded. All
recordings will be kept confidential, as stated in Sect. 1.2. Privacy Policy.
4.2.1.3. All Matches will be Bo3 Matches. The Grand Final Match will be
a Bo5 Match.
4.2.1.4. The schedule of the Matches will be fixed by the Event Admin
team. There will always be Event Staff (and Event Admin, if necessary) present in
all Matches.
4.2.1.4.1. Map vetos must be finished sixty (60) minutes before the
Match.
4.2.1.5. Players must join the room as soon as the match information is
given out to the Team Representatives (maximum of twenty (20) minutes after the
agreed schedule).
4.2.1.5.1. There will be no overtime applied in case of a late arrival,
however late arrival overtimes can be explicitly applied for up to ten (10)
minutes in case of an emergency.
4.2.1.6. The match may begin after the second restart (also known as Live
on 2 Restarts – Lo2) and the LIVE announcement given by an Event Admin
thereafter.
4.2.1.7. All Participants must not use ALL CHAT in Matches this phase, as
stated in sect. 4.1.1.9.
4.2.1.8. The Match result for a match is confirmed as soon as the Match
ends.
4.2.1.8.1. Team Representatives present in the Match are still
required to take a screenshot of the final scoreboard for reference (if
necessary).
Page 10
Revision 43
4.2.1.8.2. Players must not leave the room prematurely before the end
of the match, as stated in rule 4.1.1.8.
4.2.1.9. Substitutions are allowed during the match. Although, no more
then 1 player can be substituted in during a match, per team. The same
substitution rules apply as seen in Sect. 4.1.1.10. And Sect. 4.1.1.11.
4.2.1.10. The Match may only start if there are five (5) players per Team in
the Match.
4.2. Map veto
All matches require a map veto. The map veto procedure is done as follows.
All map vetoes require a random method of determining the map veto order. For all of the
following map veto procedures, Captain A goes first.
4.2.1. For Bo1 Matches
(1) Captain A removes(bans) one (1) map
(2) Captain B removes(bans) one (1) map
(7) Both captains can mutually decide on the last map. Or they can coin-flip
for the map, with Captain A deciding which side of the coin he wants (heads or
tails).
(3) Captain A picks one (1) map
(4) Captain B chooses own starting faction for MP1
(5) Captain B picks one (1) map
(6) Captain A chooses own starting faction for MP2
(7) Captain A removes one (1) map
(8) Captain B removes one (1) map
(9) Decider: Mutually agree or a coin-flip, same rules as BO1 Matches.
4.2.2.1. Play order: MP1, MP2, Decider
Page 11
Revision 43

(7) Decider: Blind veto
4.2.3.1. Play order: MP1, MP2, MP3, MP4, MP5, MP6, Decider
4.2.4. Blind veto

Blind veto is used to determine the decider map for a Bo5 match.
4.2.4.1. Both captains privately send their bans to an Event Admin present
in the Match.
4.2.4.2. After all bans have been sent, the Event Admin will publicly
announce the decider map based on the sent bans.
4.2.4.3. It is possible for both captains to either
(1) ban both of the remaining two (2) maps
(2) ban each of the remaining two (2) maps, one (1) map each
If the veto meets case (1), the remaining map will be played.
Otherwise, a random map out of two (2) remaining maps will be selected.
4.3. Room settings
All Matches will use the following configurations for the match room.
Room Name SFNC TEAM vs TEAM DD/MM 1
Password SFNCXXXXX 2 1
Mode DEFUSE Replace
TEAM with Team
Tags e.g. E8, nM
2
Replace DD/MM with Date e.g. 2/9, 11/11
COALITION MAX PLAYERS 8
THE BREACH MAX PLAYERS 8
PHASE ROUND TIME 1m50s
FREEZE TIME YES
PHASE ROUNDS TO WIN 13
START MONEY 800
INFINITE BUY TIME NO
AUTO BALANCE NO
START WITH ARMOR NO
COALITION MAX HEALTH 100
THE BREACH MAX HEALTH 100
WEAPONS
Page 12
Revision 43
4.4. Game Server

The game server for a Match is selected upon mutual agreement between participating
Teams. If a server is not agreed upon, a “server banning,” process will happen.
For cross-regional Matches, the server for each map is selected based on the region of the
Team that conducted the map pick in question. After Captain A picks their map they will
also be able to pick their server, then Captain B will do the same.
The decider’s map server will be decided using ‘Round Balance’. Whoever gets more
rounds in the Match will be able to choose the server they wish to play on (within their
respective region).
4.4.1. Server Banning:
BO1 Matches:
(1) Captain A bans a server
(2) Captain B bans a server
(7) The last server left will be played.
Bo3 Matches:
(1) After Captain A bans their map, they choose their server.
(2) After Captain B picks their map, they choose their server.
(3) The last map (decider map) server will be chosen by whichever team wins “Round
Balance”, as noted in Sect. 4.4.
Bo5 Matches:
(1) After Captain A picks their map, they will choose their server.
(2) After Captain B picks their map, they will choose their server.
(3) After Captain A picks their map, they will choose their server.
(4) After Captain B picks their map, they will choose their server.
(5) The last map will be chosen by whichever team wins “Round Balance,” as noted in
Sect. 4.4.
4.5. Timeouts and pauses

4.5.1. Tactical timeouts
Page 13
Revision 43
4.5.1.1. The number of tactical timeouts given to each Team during a

Match or Set depends on the current Phase or Phase Round the Match or Set in
question belongs to. Timeouts are prohibited in the Qualifiers Phase.
4.5.1.2. Teams may request a tactical timeout by using the ALL CHAT
function to request a timeout invocation.
4.5.1.3. Tactical timeouts are only available in matches with a present
Event Staff.
4.5.1.4. Teams are not allowed to substitute players during tactical
timeouts.
4.5.1.5. Tactical timeouts are initiated at the start of the following Round
when requested and lasts for sixty (60) seconds.
4.5.1.6. Tactical timeouts may not be requested to halt prematurely.
4.5.1.7. Number of tactical timeout requests allowed per Set per Team by
Phase Round:
Regional Qualifiers Ro64 – Ro16 0 (zero)
Regional Qualifiers Finals 2 (two)
Main Event (excluding Grand Final) 3 (three)
Grand Final 4 (four)
4.5.2. Technical timeouts

4.5.2.1. Teams may request a technical timeout invocation by using the
ALL CHAT function to request a timeout a revocation.
4.5.2.2. The Team invoking the timeout must provide the reason for the
timeout before or immediately after the timeout is initiated.
4.5.2.3. A technical timeout may be automatically invoked if a Player is
disconnected during the game.
4.5.2.3.1. Automatic technical timeouts may be invoked up to two (2)
times during one Set.
4.6. Disconnections
4.6.1. The Event Admin team have the rights to enforce additional anti-cheat measures
on disconnected players, if necessary.
4.6.2 If a player cannot return after a disconnection, due to technical problems or an
emergency a In-Game Staff Member must be notified. A substitute would then be
allowed to replace the disconnected player.
Page 14
Revision 43
4.7. Anti-cheat measures

4.7.1. In the qualifiers teams are not required to submit any Anti-cheat recordings after
the match, unless the opposing team protests them to do so. If this happens the protester
can only request one (1) recording. Although, teams are asked to keep their Anti-cheat
recordings until a Steel Flower Staff Member allows them to be deleted.
4.7.2 Teams within the Main Event are required to submit mandatory anti-cheat
recordings after every Match. This includes anti-cheat recordings for every Set within a
single Match. Game recordings may also be requested if necessary.
4.7.2. The Event Admin team have the rights to enforce additional anti-cheat measures
on one or multiple Players, if necessary.
4.7.3. Device Recordings must be submitted within thirty (30) minutes after a Match,
with additional fifteen (15) minutes for every Set. During the additional time
players/teams are requested to provide proof of the recording uploading, preferably with
a screenshot.
4.7.4 If necessary teams/players may be required to submit their In-Game Set
recording. If so they will have one (1) hour and thirty (30) minutes to do so. Although,
this time may differ depending on the number of In-Game rounds that were recorded. If
the recording is not submitted within that timeframe the same additional time and ‘proof’
as Sect. 4.7.3 is required.
4.8. Protests and disputes
4.8.1. Protest requests
Protest request tickets must be filed fifteen (15) minutes after a Qualifier or Main
Event Match.
4.8.2. Accusation of cheating
For any cheating accusations the protestor(s) must provide a timetable based on
the Match progress, live stream replay or anti-cheat recording replay. It is
recommended for the protestor(s) to hand the timetable along with the start of the
protest ticket. Nevertheless the protestor(s) must provide the timetable within 24
hours from the end of the Match.
4.8.2.1. The accused party must then provide counter-evidence after the
ticket is opened. Failure to provide counter-evidence will result in an immediate
disqualification.
4.9. Schedule
Page 15
Revision 43
SA Regional Qualifiers July 21st – July 24th, 10:00 to 22:00 BRT

NA Regional Qualifiers July 25th – July 28th, 10:00 to 22:00 EST
Asia Regional Qualifiers July 29th – August 1st, 10:00 to 22:00 SGT
EU Regional Qualifiers August 2nd – August 5th, 10:00 to 22:00 CET
Roster Change To Be Determined
Main Event To Be Determined
Grand Final To Be Determined
SECTION 5. ROSTER RESTRICTIONS

5.1. Roster changes
Roster changes are only allowed between Regional Qualifiers and the Main Event. The
Event Admin team will notify Participants about the allowed time that Teams may adjust
their lineups.
5.1.1. A Team may only issue up to two (2) roster changes during the Event.
5.2. Blacklisted players
Blacklisted players may not be in a Team roster, nor can play the event at all. If any
blacklisted player is found to be playing the event (on another account or through another
way) the team will be automatically disqualified and blacklisted from future Steel Flower
Events.
5.3. Team disbandment

A Team Representative may disband a Team if they are the only Player remaining in the
roster or if the team can no longer play. A Team disbandment forfeits all Prize Rewards
and qualification status (if applicable) of that Team.
5.4. Emergency substitutions
In case of an emergency, a Team Representative may request an emergency roster change
at any point during the Event.
5.4.1. The substituted player may join an active Match after the first half. They will be
required to follow the same Anti-cheat measures as all other players within the match.
5.4.2. The substitute will play for the remainder of the Match and cannot be substituted
out.
Page 16
Revision 43
5.5. Separation from an Organization

A Team may be separated from an Organization. The Team in question simply changes
to an independent state and may continue participating in the Event as normal.
5.6. Branding change
A Team may only change their branding (logo and Team name) during the roster change
phase.
If a Team is acquired by an Organization, they must change their branding to suit their
acquisition in the roster change phase, if necessary.
SECTION 6. INCENTIVES AND PRIZE REWARDS DISTRIBUTION

6.1. Regional Qualifiers
Participants who reached the Semi-Finals Round of any Regional Qualifier will be
qualified for the Main Event.
6.2. Main Event
Each Team is awarded prize money as a whole based on their final standings at the end of
the Event.
1st Place $400
2nd Place $250
3rd Place $100
4th Place $50
Total $800
Prizes
are distributed through and by Nicecactus.
SECTION 7. CODE OF CONDUCT

7.1. Cheating
Cheating in general is not tolerated. This includes but not limited to:
(a) usage of third party software that interferes with the game process;
(b) abuse of bugs and exploits to own’s advantage;
(c) modifying one’s hardware to own’s advantage;
(d) illegally restricting one’s connection to the game;
(e) modifying the Critical Ops game client in any way.
7.2. Account sharing
Page 17
Revision 43
Players must solely possess their own game account and may not share or distribute their
game accounts to anyone in anyway. Doing so will result in an immediate
disqualification from the event.
7.3. Competitive integrity
Players are expected to play at their best at all times. Any behavior that jeopardizes the
competitive integrity of a Match in anyway is not tolerated.
7.4. Bribery
It is forbidden to reward or pay an Event Staff to alter one’s decision in Matches.
7.5. Collusion
Collusion is defined as an agreement between participating Teams in order to
purposefully alter the results of a Match. Any Teams found doing so will receive an
immediate disqualification from the Event, as well as additional bans taken on the Team
from future events.
7.6. Player behavior
7.6.1. Harassment
Any type of harassment is strictly forbidden and will result in an immediate ban from
future events. This includes but not limited to, extended hostility towards other
Participants and Event Staff, discrimination, racism and sexism.
7.6.2. Compliance
Participants must comply by the instructions and decisions of the Event Admins. To
protest a decision, please open a support ticket.
7.6.3. Criminal activity
No Participants may engage in activities that are deemed illegal by common law, local
law, statute, etc.
SECTION 8. PENALTIES
Any Participant that is found to be engaged in any activity that violates the content of this Ruleset will
be subject to one or more penalties. Participants, including their entire Team may also be subject to
multiple of these penalties, if necessary. If the violation is beyond the reasonable doubt, the Event
Admin team may issue one or more of the following penalties:
8.1. Verbal warning
8.2. Minor Strike
Each Minor Strike will result in a 1% Prize Reward reduction.
8.3. Major Strike
Page 18
Revision 43
Each Major Strike is given when two (2) Minor Strikes are issued. Each Major Strike will
result in a 10% Prize Reward reduction.
8.4. Forfeiture of Match
8.5. Disqualification (“DQ”)
A DQ may be issued when two (2) Major Strikes are issued. A DQ will lead to a full
forfeiture of all Prize Rewards earned.
8.6. Tournament Blacklist
Repeated offenses may lead to escalating penalties, up to penalty 8.6. It should be noted that penalties
may not be imposed in a successive manner. In some cases, the Event Admin team may issue an
immediate disqualification on the first offense if the severity of the offense is major enough to issue a
disqualification.
8.7 Reporting to local or general law enforcement.
Depending on the severity of the violation, law enforcement may need to be involved. If so the player
and team in question will automatically be Disqualified and their punishment will be left up to local
authorities.
Page 19
Revision 43
Steel Flower Tournament (SFLT). All rights reserved 2021.
Page 20
Revision 43

Steel Flower X Nicecactus Championship: Competition Handbook EN - English

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Steel Flower X Nicecactus Championship: Competition Handbook EN - English

Uploaded by

Copyright:

Available Formats

Steel Flower x Nicecactus Championship

1.1. Document introduction

1.2. Privacy Policy

1.3. Document notice

SECTION 2. EVENT OVERVIEW

2.1.9. Set. Refers to a single game in a Match.

2.1.11. Double Elimination. A tournament format in which a Team is eliminated from

2.2. Event Admins List

Nickname Discord Position

2.3.1. Rebroadcasting rights

2.5. External documents

SECTION 3. PARTICIPATION REQUIREMENTS, ELIGIBILITY AND

3.2. Participation prerequisites

3.2.2. Media Requirements

3.3. Critical Ops account eligibility & requirements

3.3.2. Account requirements

3.4. Regional restrictions

3.4.1. Region switching

3.5. Participation per Organization

3.5.3. An Organization must be represented by a centralized Organization

3.5.3.1. A Team Representative may not be the Team Representative of a

3.6. Software version

iPhone 6s (Plus), iPhone 7 (Plus), iPhone 8 iOS 14.6

Samsung Galaxy S10 / S10 Plus / S10e / S10

Samsung Galaxy A32 / A51 / A52 / A72

Samsung Galaxy Note 10 / Note 10 Plus /

OnePlus 8 / 8 Pro / 8T / 9 / 9 Pro

Xiaomi Mi 10 / Mi 10 Pro / Mi 10T / Mi 10T

Xiaomi Pocophone F1 / F2 Pro / X3 Pro

Xiaomi Redmi Note 10 / Note 10 Pro

Nokia 1.4 / 3.4 / 8.3 5G / X20

Lenovo Legion Phone Duel 2

Nubia Red Magic 6

SECTION 4. EVENT DETAILS

4.1.2.1.1. In this case, Team Representatives are required to host the

4.1.1.4. Each Round of the phase must be completed within twelve-hours

(3) Captain A picks one (1) map

4.2.4. Blind veto

4.4. Game Server

4.5. Timeouts and pauses

4.5.1.1. The number of tactical timeouts given to each Team during a

4.5.2. Technical timeouts

4.7. Anti-cheat measures

SA Regional Qualifiers July 21st – July 24th, 10:00 to 22:00 BRT

SECTION 5. ROSTER RESTRICTIONS

5.3. Team disbandment

5.5. Separation from an Organization

SECTION 6. INCENTIVES AND PRIZE REWARDS DISTRIBUTION

1st Place $400

2nd Place $250

3rd Place $100

4th Place $50

SECTION 7. CODE OF CONDUCT

Steel Flower Tournament (SFLT). All rights reserved 2021.

You might also like