Professional Documents
Culture Documents
Quark'23 Rulebook
Quark'23 Rulebook
Quark'23 Rulebook
EVENTS RULEBOOK
INDEX
CUBIX
ELECTRIFY
DIGILOGICA
μC MANIA
PROGRAMMERS INC
HACKATHON
CODEJAM
CODEWAR
BITS CTF
FOOLS CODING
SPECIALS
PAPER PRESENTATION
SCHOOL BAG
QUIZ
DEBATE
ENIGMATICA (Classes 8 to 12)
CORPORATE
REGALIA
CASE CRACKDOWN
BULLION BEATDOWN
POLICY MAVERICS
DESIGN & BUILD
BURNOUT
SEARCH AND RESCUE
TRAILBLAZERS
ELIXIR
QUARK NATIONAL QUIZ
GANIMATOONICS
ROBOFICIAL
ROBOWARS
ROBORACE
ROBO SOCCER
ROBO CLENCH
MAZE RUNNER
TIME CHALLENGE
MATKA
VALORANT
FIFA
BLOCKCHAINIFY
dApp-athon
CRYPTOMANIA
AnFTee
CUBIX
Events
2x2
3x3
4x4
3x3 one handed
3x3 blind folded
Pyraminx Rules:
The rules are as per the World Cubing Association (WCA)
regulations.
ELECTRIFY
μC MANIA
This event is very flexible with the microcontrollers the
participant wants to use.
Round 1
1. In this round the participants will be tested on how well
they apply their basic electronics knowledge and logical
reasoning in Arduino related problems.
2. There will be a time constraint for this round.
Round 2
1. Selected teams from the first round will be further tested
on their skills.
2. This round will contain complicated questions which
may need making small algorithms and complicated
connections.
3. Teams are to complete within the time limit.
Rules of participation:
DIGILOGICA
Do you think that Digital Design is just a boring course , just
about gates and logic? Well, you’re in for a huge surprise!
Welcome to the vast world of digital logic!
Get ready to go beyond with counters, multiplexers, flip-
flops, encoders, decoders and much more and be prepared
to be challenged at a whole new level!
General Rules
1. Each team shall consist of a maximum of 3 participants.
2. Any sort of malpractice or mishandling of equipment
will lead to immediate disqualification.
3. The decision of the jury is final and is to be abided by in
any case.
4. The above rules and judging criteria are subject to
change based on the jurisdiction of the Event Managers.
Round 1
A rapid series of mind puzzling MCQs with sand trickling
down the hourglass.
How many of these basic digital electronics questions
can you answer in the given time?
Teams would be short-listed for the next round based
on the quiz score.
In case of a tie, the completion time will be taken into
account.
This round is to be attempted online from any location
convenient for the team.
The questions are of variable weightage, and negative
marking would be there.
Round 2
Teams will have to design a combinational/sequential
circuit as the solution to the given problem.
A hardware implementation of the design has to be
done on the breadboard using the components
provided.
Datasheets and pin diagrams will be provided if
necessary.
Correctness and efficiency of the design will be
considered.
Final and intermediate outputs of the hardware
implementation will be observed and will be given high
weightage.
In case of a tie, the time taken for the design and the
implementation as well as the neatness of the circuit
would be taken into consideration.
This round will be carried out in the digital electronics
lab at BITS Pilani K. K. Birla Goa Campus.
All equipment-power supply, function generator, wire
stripper, breadboard, etc. will be provided.
Round 3
CODEJAM
Do you believe not just in writing code but making it
more efficient? If yes, this event is for you.
Quark presents to you a competitive programming
event. Rack your brains to solve puzzles and real world
problems. Compete with people all across the nation
and show off your programming skills.
CodeJam will have 2 rounds exclusive to each other,
and are individual events.
These rounds will be held on codechef.com
Round 1:
Anybody is allowed to sit for this, irrespective of their
participation in the first round (optional).
The contest will be hosted online on CodeChef for a
duration of 5 hours with 8 problems.
No team participation is allowed and plagiarism of any
sort will result in cancellation of participation.
For any wrong submission (none of the test cases
passed), a penalty of 15 mins will be imposed.
Judging Criteria
Participants will be judged based on the number of test
cases their program gives the correct answer for. Judging
will be done via the online judge.
Team size: 1
Rules
1. You are required to print the final output. Sample
output format will be provided in each problem
statement.
2. All the major programming languages are permitted.
3. The participants will be judged on both correctness and
time of submission of the solution.
4. Use of the internet, other than accessing Code chef, is
prohibited.
5. Any participants, if found using any unfair means, will
be disqualified from the event.
6. The decision of the organizers in declaring the results
will be final.
7. No queries in this regard will be entertained.
CODEWAR
Participants limit: 32
This is a 1v1 coding event with a special rule. Each problem
will have points associated with it according to its difficulty.
If a participant solves a problem, the other participant
cannot solve it and get points for that problem. So it’s all
about strategy and how one chooses the order to solve the
problems. The participants are responsible for bringing their
own laptops and chargers.
Judging Criteria
Participants will be judged on the cumulative points over
the entire set of problems.
In case of a tie, it will be sorted by adding the cumulative
time of al the solved questions Rules:
The competition is an online jeopardy style CTF with
multiple categories of challenges, accessible from the
Internet which has a duration of 48 hours.
The competition can be played by individuals or groups
(max team size of 5), only one account per team.
The participant must provide a real point of contact for
future notifications or claim the prize.
Participants that behave inappropriately will be
immediately disqualified, including:
i. Share solutions or hints.
ii. Attack computers or applications not designated
by the competition.
iii. Attack other participants.
iv. General brute force attacks over online
platforms unless specified.
v. Duplicated accounts.
vi. Other things we consider to be unfair.
vii. Attacking a contest server.
viii. Scoring system is dynamic.
FOOLS CODING
This event will push your logical, deductive and
mathematical skills to the limits.
Be the Bond of programming and figure out what is the
hidden source code by looking at its behavior on your
inputs.
The participants will be provided a portal with a black
box’ function and an input template.
The participant can generate as many outputs on any
desired input to guess what exactly the hidden
source code is doing (e.g. calculating the nth
Fibonacci number for every input n.) and code it.
The portal will test your function on several test cases,
and award a score accordingly. The score will vary
depending on the difficulty level of the problem.
The participants are responsible for bringing their own
laptops and ensuring that they are sufficiently
charged for a 3-hour event.
Judging Criteria
Rules
Competition Format
While the final event that takes place on campus is a
presentation by the group that worked on the project,
we will require you to submit the abstract of your paper
to us ahead of the competition, which would form the
preliminary round in the competition.
We will select the best papers based on the abstracts.
The decision of the judges and the organizers shall be
final and abiding vis-a-vis the selection of the papers
for the final presentation.
The last date for the submission of the abstract and the
paper is 23th February 2023.
The groups whose papers are selected will have to
come over to our campus to given a presentation.
•A presentation has to be created by the team based on
their paper which should be presented in the presence
of the judges.
Each group will be given 10 minutes to present on their
paper, owed by a questioning period by the judges of up
to 5 minutes.
Use of visual aids, like a PowerPoint presentation, are
encouraged. Each group can have a maximum of 4
participants.
We will be judging the participants not only based on
the presentation but also on the paper submitted, with
equal weightage for both components.
Round 1
1. The abstract should not be more than 500 words long
and should attempt to capture the essence of the
paper.
2. Abstracts should state clearly and concisely the
problem, the methodology used and central
conclusions, and may include figures and graphs.
3. Please ensure that your abstract matches the following:
a. The first sheet is blank, but for your project title,
names of the team members and their respective
institutes.
b. The last sheet, owing the abstract, may have a list of
references – websites, books, journals and so on,
which amply support the ideas or solutions
implemented or proposed.
The information in the abstract should not be very
descriptive or vague.
It is recommended that vital aspects of the project that
require special focus be mentioned as bold points.
Round 2
Teams selected from the first round will have to give
their presentation in Quark 2023. We will mail the groups
whose papers have been selected.
Those who are selected for the final round are required
to reply to the mail with follwing details:
Acknowledgement that you are aware of you
being selected.
Details of all the team members: Names,
Departments, Phone numbers and College.
For the final round, the participants will have to give
their presentation in Microsoft PowerPoint.
Only picture clippings and graphs may be used.
Recorded dialogues or movie clippings are not allowed.
We will provide a computer for presentation.
The teams will get 1 minute to set up their presentation
and 10 minutes to present their idea.
Exceeding the time limit carries penalties: 2 points or up
to 2 minutes extra, 15 points for between 2 and 5 minutes
extra, and 20 points for more than 5 minutes.
Please keep your presentation concise.
Judging criteria
The submitted papers will be marked on a scale of 1-10
on the basis of the following criteria:
A concise, informative abstract.
Adequacy of introduction and background to the
topic on which the paper is based on.
Logical development and analytical treatment in the
body.
Adequacy of conclusion to the paper.
Factual and technical accuracy in the paper.
Originality of ideas, experimental procedure, design, and
results or conclusion.
Summary Submission
A Quiz
A Debate
Category:
A: Classes 8-10
B: Classes 11-12
Rounds
• A written elimination round, from which select
teams from each of the categories will be
selected for the Quiz.
• The Final Quiz, consisting of several rounds.
Rules
There must be three members in each team.
A school may send a maximum of three teams per
category.
The decision of the quiz master in all regards will be
final.
The Debate
In the Schoolbag 2023 Debate, participants must lock
horns in verbal combat and stun their opponent in a
valley of cogent rebuttals.
Category
A: Classes 8-10
B: Classes 11-12
Rounds:
Rules
Rules
Round 1:
All participants will compete in an online quiz
Based on their performance, participants will move
on to the next round or be eliminated.
Round 2:
Shortlisted participants from round 1 will compete in
an online case solving competition
The problem statements will be provided by the
organizers.
Based on their performance, participants will move
on to the next round or be eliminated.
Round 3:
Shortlisted participants from round 2 will be able to
participate in an offline presentation of their case in
front of a panel of judges.
Judges will declare the top 3 teams
BULLION BEATDOWN
Group stage
In the first stage of the event, there will be a total of 10
rounds, 2 minutes each
5 teams(or 4, if there are 8 teams in all) will be given
+2000 units of a commodity, let’s say gold. The other
5(or 4)teams will be given -2000 units of gold. The base
price of each unit would be fixed at 200
The teams are free to trade amongst themselves. Each
trade should involve buying/ selling in multiples of 100
units. A team can buy or sell any number of units in each
round
The negotiators are expected to negotiate the
selling/buying price and bring it down to their
requirements in the 2-minute interval
The person at the table will officially “handle’’ the
transactions
After the end of all 10 rounds, every team has to bring
the number of units they have to zero and maximize
their profit
A limited number of teams with the maximum amount
of profit will proceed to the next stage of the event
Final round
A final round would be held in which all the teams finishing
first will be competing against each other. The organizing
committee will let the finalists know the rules for this round
on the spot.
POLICY MAVERICS
Stage 1 - Quiz
Each team after attempting a quiz are assigned to a
leaderboard and gets a certain number of points with
which they advance into the next round.
Stage 4 - Pitching
Teams that qualify will have to pitch the solution in front of
a panel of judges.
Rounds:
Round 1 :
Every team will be given 3 chances to pass
through the arena without any weight and their best
time will be recorded.
Round 2 :
There will be a standard weight (200-400
gms). Each team will be given 3 chances
to pass through the arena with the standard weight and
their best time will be recorded.
The timings of each time on day 1 and day 2 will be
added and on the basis of that, half of
the teams participating will advance to the finals.
Note: In case any team is not able to complete the tasks
on day 1 or day 2 they will be
eliminated straight away.
Round 3:
(Finals)There will be 5 weights (grams): 200, 400,
600, 800, 1000.
Each team will get 5 attempts to pass through the
arena with any of the weights above.
They must carry 200 and 400 gms at least once.
Considering the weight lifted and time taken for
passing through the arena, scoring will be done
(explained below).
Scoring (for finals) - for each of the five attempts,
(weight carried/time taken) will be added to each
team's score starting from 0. In case of a failure 0 will
be added to the score for that attempt.
The team having the most points in the end wins.
Note: Failure will be considered as not reaching the
destination with the weight.
If the weight falls down the team will not be allowed
to pick it up again.
It's okay if the drone hits obstacles as long as the
drone or the weight does not hit the ground.
The reason being that the whole point of this event is to
rescue people in case of a fire or emergency and if that
person falls down you have failed.
The details about the point system as well as the track
would be released on the Quark website.
TRAILBLAZERS
General Rules -
The competition consists of two rounds.
A maximum of 4 members in a team will be
allowed.
Multiple teams from the same college will be
allowed if their design has significant differences.
All teams are required to design, fabricate and fly
an RC aircraft.
No Readymade models, like RTF, ARF, BNF, etc., are
allowed.
No lighter-than-air systems and rotary systems are
allowed. Only fixed-wing aircraft are permitted.
The flying zone is a rectangle of dimensions 175
meters * 75 meters.
The location of the landing strip will be mentioned
during the competition.
Report Submission -
A report must be drafted and submitted detailing the
entire design process, technical details, weight
distribution, cost analysis, and a 2D aircraft drawing.
This report has to be submitted by March 12th, 2023.
Based on the viability of the design detailed in the report
submitted, the team will be invited for the fly-off.
No significant design changes will be allowed in the final
aircraft in the fly-off to the one detailed in the report.
For Round 1, all teams will have to estimate the time they
believe their aircraft can sustain in that round and
provide appropriate reasoning for the same.
Aircraft Specifications-
The propeller diameter should not be greater than 11
inches.
Wingspan should be a maximum of 1.5 meters.
Only electric motors (BLDC) would be allowed. No IC
engines or any other form of propulsion will be allowed.
Use of programming assistance in any way or form is
prohibited. (e.g., Gyroscopes, flight control boards)
There can be a maximum of one battery pack
connected to a propulsion system. A propulsion system
consists of one battery, one or more electronic speed
controllers (ESC), and one or more motors.
The maximum energy capacity of the battery must be
at most 30 Watt-hours.
Radiofrequency of 2.4GHz only should be used as a
control link.
Aircraft staging -
This is a technical inspection round, and all teams must
pass this round to qualify for further rounds.
A payload must fit within the dimensions of a 5cm * 5cm
* 5cm box and has to be fabricated. The weight for that
payload can be chosen (Based on round 1).
The payload must be carried internally to the aircraft. No
part of the payload can be part of or extruded outside of
the airplane's external surfaces or features.
The aircraft's empty weight(including battery and all
other non-payload subsystems.) must be less than 1000
grams.
All the battery packs, motors, ESCs, transmitters and
receivers, and other equipment to be used in
subsequent rounds must be shown to the organizers.
Only these pieces of equipment will be allowed to be
used. eg, If your team requires three batteries to
complete the competition, then all three batteries must
be shown to the organizers.
Battery packs, motors, ESCs, and propellers must be
commercially procured.
Round - 1
A suitable weight for the payload has to be chosen by
the teams. Let the weight (of only the payload) be W.
The aircraft must only be hand-launched and must land
within the flying zone.
If the aircraft strays away from the flying zone, the team
will be told to bring down the aircraft immediately, which
will be counted as a failed attempt.
The goal of the round is to fly the aircraft for as long as
possible. Your time will be calculated as the time
between takeoff and landing. Let the time be T.
The maximum allowed time Tmax will be ninety percent
of the theoretical time T estimated in the report. After
Tmax, you will be told to land the aircraft.
Only two attempts will be allowed.
The best one out of the two scores will be considered.
The flight score for each team will be calculated as
Score_1 = W * T
Round - 2
The objective of this round is to land at a specified
location and to achieve it with a minimum landing
distance.
The aircraft must only be hand-launched and must land
within the flying zone.
If the aircraft strays away from the flying zone, the team
will be told to bring down the aircraft immediately, which
will be counted as a failed attempt.
The landing zone will be 7.5 meters wide. The start of the
landing strip will be clearly mentioned.
If the aircraft undershoots the runway, i.e., lands before
the start of the landing strip, then it will be counted as a
failed attempt.
If the aircraft deviates from the runway, i.e., lands to the
right or left of the landing strip, it will be counted as a
failed attempt.
Let n represent the number of attempts the team made
to land the plane on the strip.
Let m (in meters) represent the distance between the
start of the landing strip and the point where your
aircraft comes to a complete stop.
Max time allotted to the team to complete this mission
will be 3 minutes.
Only the latest m value will be considered in the final
score calculation.
Final scoring -
GANIMATOONICS
Description
This quiz will be based on Ganimatoonics
i.e.
Games (not limited to just video games), Anime,
Cartoons and Comics over the years.
Anything related to these domains can be asked
in the quiz.
Team composition: 1-2 members; Cross college
teams are allowed.
Registration can be done on the spot.
TEAM SPECIFICATION:
Any team can participate in Robowars. A team may
consist of a maximum of 5 participants. The
participation is open to all.
Team Name:
Every team must have a name which must be unique.
Organizers must be notified during if a Team's name
has been changed.
Team Representative:
Each team must specify their Team Representative
(Leader) at the time of registration on the website. All
the important communications between organizers
and the registered teams will be done through their
Team Representative. The Team Representatives must
submit valid contact details (phone no., email ID etc.)
at the time of registration.
CERTIFICATION POLICY:
Certificate of Excellence will be given to all the winners.
Certificate of participation will be given to all the
participants. The teams which get disqualified due to
disobeying any of the competition rules will not be
considered for the certificate.
ROUNDS
4.1 TECHNICAL INSPECTION:
In this coordinator will check the robot for all technical
rules as stated above and will PASS the robot if all the
rules are abided, if robot fails to do so, necessary
changes have to be done in order to participate in the
robot else may lead to disqualification. (All rules under
section 2 should be abided).
Game Play
The robot will be placed at the start line.
The robot starts when the timer starts.
The robot should remain on track, otherwise it has
to start from last checkpoint crossed, though the
timer will not be stopped.
There are penalties for each obstacle skipped.
Penalties will be added to the total time.
Timer will stop as soon as the robot crosses the
finish line.
Scoring and penalties rules will be announced on
the day of the event.
Robot
The machine can be wired/wireless.
The machine must be controlled manually.
The dimension of the bot should be less than or
equal to 300mm X 250mm X 300mm (l x b x h),
failing which the team will be disqualified from the
competition.
An error of (± 5%) is permitted.
The machine must not be made from Lego parts,
or any ready-made assembly kits, and it must be
powered electrical by, use of IC engine is not
allowed.
The robot can be powered by a power source
such as a battery fixed on the robot or by a
stationary power source connected to the robot
by a cord.
Potential between any two points on the robot
should not exceed 12 V.
Participants should keep spare batteries,
otherwise it may lead to disqualification if bot is
not ready or stops in between the race.
The length of the wire (for wired bots) should be
long enough and the wire should remain slack
during the complete race.
Race Track
There will be only one Start and one Finish line.
The track surface and course line may have
unevenness.
There will be certain obstacles in the racetrack, which
will try to slow down the robot.
The design and size of the track may vary from that
shown in the pictures.
Track may consist of steep ramps, bridges, speed
breakers, marble pit, slippery path, rotating disc,
curve ramp down, seesaw etc.
Details about the dimensions of the obstacles in
the path and the 3D models of the race track will
be available on the website of Quark 2023.
Game Play
Gameplay
The event will be points based.
There will be a time limit to complete the course.
The bot has to begin from the START point.
The timer will be started.
The bot will have to pick up square blocks, climb up
the ramps and place the blocks at specified
locations to complete the course.
The team will be awarded points for each task of
an obstacle completed successfully.
The team can decide to skip a task of an obstacle
or the complete obstacle.
No points will be awarded for the skipped tasks.
If a bot performs a task incorrectly or topples over
during the competition, it will have to go back to
the previous checkpoint and start over from that
checkpoint.
The timer will not be stopped in any case.
Penalty
Arena
The arena will consist of ramps of different slopes,
vertical drops, and rumbles as obstacles.
Dimensions of square blocks are 100mm X 100mm.
The width of the track is 450mm.
Details about the dimensions of the obstacles in
the path and the 3D models of the race track will
be available on the website of Quark 2023.
Bot Specification
MAZE RUNNER
Problem Statement:
Teams have to build an autonomous robot which
can ow white lines and keep track of directions
while going through the maze.
The bot has to analyze the path in the dry run and
has to go through the maze from the starting
point to the ending point in the shortest path in
the actual run.
Arena
Bot Specifications
The autonomous bot must fit into the box of
dimension 21cm X 21cm X 22 cm ().
The Bot must be started individually by only one
switch. However, a team may have an onboard
switch for restart.
This switch has to be shown to the organizer before
the run.
The Bot must have a red LED which will glow once it
reaches the end zone of the arena.
During the run, the autonomous bot must not
damage the arena in any way.
It is not allowed to leave anything behind or make
any marks while traversing the arena.
Any bot found damaging the arena will be
immediately disqualified.
The final decision is at the discretion of the
organizers.
The Bot must have an ‘on board’ power supply.
When using the electric power supply, the potential
difference between any two points must not exceed
24 V at any point of time during the game.
The autonomous bot should not separate or split into
two or more units.
All bots/units which are touching each other or are in
the starting point will be considered as one bot.
Bot cannot be constructed using ready-made ‘Lego
kits’ or any ready-made mechanism.
But they can make use of readymade gear
assemblies.
Violating this clause will lead to disqualification of the
team.
Game Rules
Teams will be given 1 minute for calibration.
1. If any team is found to alter its code after
depositing its bots, then it will be immediately
disqualified from the competition. They are however
allowed to make any other hardware changes.
2. Only one autonomous bot per team is allowed.
3. When the autonomous bot starts, no team
member is allowed to touch the bot or enter the
arena.
4. At the start of the task, the bot will be placed at the
starting point.
Only 1 team members are allowed to be near the
game field while starting the bot.
5. Run will start only when organizers give the signal.
6. The starting procedure of the bot should be simple
and should not involve giving bot, any manual force
or impulse in any direction.
7. A total of 5 minutes and 30 seconds will be given.
The bot has to finish the dry run and main run in that
period only.
Restarts
1. The participants are allowed to take a maximum of 3
restarts in the entire match.
2. If the bot takes a restart in the first part (Dry Run) of
the competition, it has to start from the checkpoint.
3. Once Dry Run is completed by the bot, the team
won’t be given any other chance for Dry Run.
4. If the bot takes a restart in the second part (Actual
Run) of the competition, it has to start from the start
zone of the arena.
5. The timer will not be set back to zero and will not be
paused in any case.
6. During a restart, a contestant must not feed
information about the arena to the bot. However,
contestants are allowed to adjust sensors (gain,
position etc.) and make hardware changes.
7. The contestant must not alter the bot in any manner
that reduces its weight (e.g. removal of a bulky
sensor array or switching to lighter batteries to get
better speed). The organizers reserve the right to
arbitrate in such circumstances.
General Rules:
Only 1 member of the team is allowed to handle the bot.
Participants are not allowed to keep anything inside the
arena other than the bot.
Laptops/personal computers are not allowed near the
arena. Other Wi-Fi, Bluetooth, etc. devices must be
switched off. The organizers hold the right to check for
these devices and their usage and disqualify the team.
The time measured by the organizers will be final and
will be used for scoring of the teams.
Time measured by any contestant by any other means
is not acceptable for scoring.
In case of any disputes/discrepancies, the organizers’
decision will be final and binding.
The organizers reserve the rights to change any or all of
the above rules as they deem fit.
Change in rules, if any will be highlighted on the website
and notified to the registered teams.
30
• points will be awarded as it crosses any of the
Scoring:
•
A = 30 points * (Number of checkpoints covered
during the Dry Run)
B = 50 points if the bot successful y completes the
Dry Run
C = 240 - Total time taken in seconds in completing
the Dry Run
S = 50 Points if Bot successfully completes through
the Shortest Path
T = 180 - Total time taken to complete the Actual Run
(only if the bot completes in Shortest Path)
P = Penalties
Total = (A + B + C + S + L + T) – P
Game Play
Arena
Event Rules
Punctuality
All matches in Matka should start as stated on
the provided schedule, any changes in the time
must be accepted by the opposing party and
administrators (if rescheduling is generally
possible).
• All participants in a match should be on the server
and ready to go at the latest, 10 minutes before the
match is to start.
Removable Media
It is strictly forbidden to connect or use any removable
media on the tournament computers without prior
examination and approval from the tournament
administrators.
Warm-up Period
A warm-up period of 20 minutes is usually provided
before a match, although this period may not be
guaranteed.
This will include the time that might be required by a
player to set up his/her config and game settings.
In case a player arrives late, no extra time shall
be provided for configuration or setting
changes.
Cheating
The use of the owing programs will result in a cheat ban:
Multihacks, Wall hack, Aimbot, Colored Models, NoRecoil,
No-Flash, and Sound Changes.
These are only examples, other programs or methods
may be considered cheats as well .
The player who is found cheating shall be banned from
further participation in subsequent iterations of Matka
and his/her team shall be immediately disqualified from
the tournament.
VALORANT
1) Map Pool
The map pool for the event will be
Ascent
Breeze
Split
Haven
Fracture
Bind
Icebox
2) Veto Process
The veto process should be completed 10 mins before
the scheduled start time of the match. Only 1 player
from either team can participate in the process and
choices cannot be reverted after being made. The
captain who’ll take the first pick shall be decided with a
coin toss.
3) Map choice
For BO1-
For offline event: Ban A - Ban B - Ban A - Ban B - Pick A:
remaining map is being played.
For BO3
For offline event: BanA-BanB-PickA-PickB-BanA-BanB-
remaining map is being played as a decider map if
required.
4)Dropping of Players
If a player drops before the first kill in the first round
of a half, then the half will be restarted.
If a player drops after the first kill have been made
and has not returned when the round has been
decided, then the match will be paused at the start
of the next round.
If a player drops and the opponent has been
notified before any kills have occurred during that
round, then the round will be restarted.
If a player has not returned, or cannot be replaced
within 10 minutes after the pause has started, then
the team with the dropped player may forfeit the
match at admins discretion.
5)Draws
In case of a draw after all 24 rounds have been played,
normal overtime rules shall apply.
6)Pause Function
1 Technical Pause
If a player has a problem that prevents him from
playing on, he is allowed to use the pause function
(“!pause”). The pause function can be used at any
time but it will only come into effect during freeze
time (immediately, if used during freeze time, else at
the beginning of the next freeze time). The player has
to announce the reason before or immediately after
he paused the match. If no reason is given, the
opponent may unpause the game and continue
playing. Unpausing or pausing the game without any
reason will lead to penalty points.
• 2 Tactical Pause / Timeout
Each team is allowed to invoke a tactical pause of 30
seconds up to four times per map. If the Matka Game
Integration is being used, the special command
“!timeout” has to be used. Otherwise, the “!pause”
command has to be used and the team has to
announce the tactical pause via chat. The pause
function can be used at any time but it will only come
into effect during freeze time (immediately, if used
during freeze time, else at the beginning of the next
freeze time). If all tactical pauses had already been
used on the same map, the admin will unpause the
game and continue the game.
• 3 Admin Pause
The admin can also pause the game from his station
or from a player station when it seems required. also,
if for some reason the player pausing does not work,
they have to request the admin to do it.
FIFA
Tournament will be single elimination with a
maximum 256 participants.
All games will be played on FIFA 23.
Any regular season teams, as installed with the
original game, can be selected except for all-star
teams.
Games will be played for 6 minute halves.
The Game settings are as follows:
Difficulty Level: World Class
Injuries: On
Offside: On
Camera: Tele
Radar: 2D
Quick Subs: On
Allotted time for mid-game substitutions: 45 seconds
Overtime: If the game goes into extra time the winner
will be decided using penalty shots
Absence of the participant will result in forfeiture with
their opponent going through to the next round.
Controller settings will be set as:
Competitive Master Switch: Yes
Through Pass Assistance: Semi
Timed Finishing: Off
Next Player Switch Indicator
Pass Block Assistance: Off
Auto Switching: On Air balls and loose balls
Ground Pass Assistance: Semi
Cross Assistance: Semi
Analog Sprint: On
BLOCKCHAINIFY
dApp-athon
The quintessential BC / Web3 - based ‘hack’athon
Duration: 60 hours / 3 days
Teams of 1 - 4
NOTE:
A submission with a full - stack dApp would be given a
priority over one with just the smart contract, if the business
logic contained in the same is equally good and relevant to
the respective theme
CryptoMania
You get to buy, sell, and trade cryptocurrencies as a mock
crypto trader. Need I say more?
Duration: 3 days
A typical crypto - trading competition to be hosted on
Roostoo, unless otherwise Individual participation
AnFTee
Let the artist within you come to life to make something
truly ‘unique’ look like it.
Duration: 60 hours / 3 days
Individual participation