Live Event Monitoring

HackArenaHackArena2K26

Code. Compete. Conquer.

Enforcing discipline, tracking real-time activity, and managing submissions for an elevated, professional hackathon experience.

Event Rules & Regulations

Failure to comply with the HackArena tracking algorithms will result in automated strikes or immediate disqualification.

1. Continuous Commits

All development must be tracked incrementally. Dumping code in a single massive commit at the end is strictly prohibited and leads to immediate manual disqualification.

2. The Strike System

The master system assigns 1 inactivity strike for every 60 full minutes without a GitHub push. See the detailed breakdown below.

3. Three Strikes = Out

Accumulating 3 inactive strikes flags your team for disqualification review. Push code to erase strikes and restore your stability score.

4. Final Deployment Submission

You must deploy your project to a live URL (Vercel, Render, Firebase, etc.) and submit the link via the Final Submission portal before the countdown ends. Localhost links are not accepted and will not be judged.

Core Mechanic: The Strike System

0-59 Minutes (0 Strikes)

Status is ACTIVE. Your team is coding consistently and retains a 100% Stability Score.

60-179 Minutes (1-2 Strikes)

Status drops to WARNING. 1 strike is assigned at 60 mins, and a 2nd at 120 mins. Your Stability Score drops significantly (down to 20%).

180+ Minutes (3+ Strikes)

Status falls to INACTIVE. The system sends an automated alert to the judges flagging your team for disqualification review.

The Forgiveness Reset

The strike system is perfectly automated and entirely forgiving. It purely calculates the time since your latest valid positive GitHub push.

Pushing genuine code instantly resets your inactivity timer to 0 minutes, clearing all strikes immediately.

Engine Evaluation Score

The HackArena master server constantly calculates a precise 0.0 to 10.0 technical health score for your team. This score is updated in real-time on your dashboard and provides judges with objective technical data.

Activity (40%)

Scores how recently you have pushed code. It degrades linearly over 24 hours.

Push code to lock at 100%

Deployment (40%)

Scores your live link presence. 100% if the site resolves rapidly, 50% if slow, 0% if down or missing.

Submit a working live link

Stability (20%)

Tied directly to your Strike Count. 0 strikes = 100%, 1 strike = 50%, 2 strikes = 20%, 3+ strikes = 0%.

Keep strikes at 0

How it works

The technical details of the HackArena architecture.

Repository Tracking

We strictly monitor your linked public GitHub repository for commits.

Hourly Activity Checks

Push code within 60 minutes to stay active. Over 120 minutes leads to strikes.

Anti-Cheat & Strikes

Accumulate 3 strikes and your team is automatically disqualified.

Final Submission

Deploy your app and submit the link before time runs out.