✅ The "Do's" (What we expect from you)

1. Do collaborate with your team: CTFs are a team effort! Share your findings, scripts, and thoughts with your registered teammates.

2. Do ask for help if something is broken: If a challenge instance seems down, unresponsive, or fundamentally broken, open a ticket or ping the admins in the official communication channels.

3. Do read the challenge descriptions carefully: Every word matters. Pay close attention to hints hidden in the text, formatting, or challenge titles.

4. Do write scripts and automate: Use Python, Bash, or whatever language you prefer to automate tedious tasks, but please be mindful of thread counts to avoid crashing the server.

5. Do take breaks and stay hydrated: Staring at a hex dump for 6 hours straight isn't healthy. Take breaks to keep your mind sharp!

❌ The "Don'ts" (What will get you disqualified)

1. Don't share your registration code: No player should share their One-Time registration code that is sent to their mail. Registration codes are strictly for individual/team use only.

2. Don't share flags or solutions: Collaboration between competing teams is strictly prohibited. Keep your flags and exploits to yourself until the event concludes.

3. Don't attack the infrastructure: Do not attempt to hack the scoreboard, the CTFd platform, or the underlying servers. You must only attack the specific challenge instances provided.

4. Don't perform DoS/DDoS attacks: Denial of Service attacks are strictly forbidden. If your automated exploit script is lagging the challenge server, lower your thread count.

5. Don't use commercial scanners: Tools like Nessus, Acunetix, or aggressive automated DirBuster scans with massive wordlists are prohibited. They create unnecessary traffic and disrupt the event for others.

6. Don't sabotage other teams: If you compromise a shared challenge instance, do not delete the flag, change the admin password, or lock other teams out. Leave the environment exactly as you found it.