THE EXPEDITION HANDBOOK

A few rules.
Endless possibilities.

MAYASABHA is a team-based cybersecurity journey through historic Indian monuments. Follow clues, submit flags, and reach the final assembly in Delhi.

01

One team. One expedition.

Use your assigned team account on one laptop. A new browser login replaces the previous session. Other tabs in the same browser share your session.

02

Choose your passage.

Inspect the starting checkpoints freely. Your first answer submission—even an incorrect one—commits your route. Complete each checkpoint in sequence. Skips are not allowed.

03

Make every point count.

Points are both your balance and your competitive score. Hints, extra attempts, and point-based route changes deduct from that balance. Purchased hints remain available. Negative balances are not permitted. Current prices are displayed in the game.

04

Keep moving.

A challenge begins losing value when an expedition first commits to or reaches it. That unlock and current value are shared across teams. Starting-challenge previews do not trigger decay. The exact scoring formula is held by the organizers.

05

Change course, thoughtfully.

Travel to another route by paying the displayed cost or waiting through a flight. During the timed flight, gameplay is frozen. Cancel before arrival to stay on your original route; the time already spent waiting is lost. Your discoveries are preserved, and you may return via another switch.

06

The first seal brings a choice.

If enabled for a checkpoint, the first correct solver may forfeit its reward to temporarily block other teams’ submissions. Choose this preference before submitting. A checkpoint can be blocked once; its point value continues to decay during the block.

07

There is a way forward.

If you run out of attempts and cannot afford another, visit the recovery desk. Submit answers from the organizers’ tasks to earn limited points. Cooldowns and caps apply. A timed recovery attempt remains available without adding score.

08

Reach the final assembly.

Clear a complete route and solve the Delhi final challenge to become eligible for victory. That solve ends your gameplay and seals your score. Finishers rank by remaining points, fewer consumed assistance units, then earlier completion. Unfinished teams appear separately.

09

Stay within the challenge.

Use only the supplied files and explicitly designated challenge sites. The contest platform, login system, organizers’ infrastructure, and other teams are outside the challenge scope. Downloads already received may remain on your laptop.

10

The shared clock is authoritative.

Refreshes and disconnections do not reset attempts, penalties, or time. Wait for server confirmation before treating an action as accepted. Retry an unconfirmed action using the safe retry control. Organizers can pause all gameplay timers if an event-wide problem occurs.

Displayed prices and event configuration take precedence over illustrative default values. Organizers announce adjustments through the game interface.

Return to the expedition