Skip to content

Rules

Seven rules. Read them once and you'll be fine.

# Rule Short version
1 Be kind and respectful Treat others how you'd like to be treated
2 Stay on topic Post in the channel that fits
3 Share responsibly Source code, never an .exe
4 Ethical coding only White hat, and say what you're doing
5 Moderators have final say Their call ends the dispute
6 No jobs or employment advertising Use a real job board
7 Ask effective questions Code, error, and what you tried

1. Be kind and respectful

Treat others the way you'd like to be treated. No mean-spirited comments or behaviour — keep conversations positive and constructive.

Disagree as much as you like, but direct it at the code, the approach or the claim, never at the person holding it. Condescension counts, and "just being blunt" isn't a defence.

Harassment, slurs and bigotry get you removed without a warning ladder. See Code of conduct for what that covers.

2. Stay on topic

Stick to the subject of the channel you're posting in. If your question doesn't fit anywhere obvious, ask anyway — we'd rather help you find your way then you not ask because you didn't know where to ask.

Channels says what goes where.

3. Share responsibly

No self-promotion or unsolicited ads. Sharing a personal project is welcome and encouraged, as long as you aren't looking to sign people up for something.

When you share something you built:

  • Always include the source code. A repository, a gist, or a fenced block.
  • Never post an .exe, or any other compiled binary. Nobody can read it, and nobody should run it. Ever.

Got something you genuinely need to advertise? Ask a moderator first through the /ticket system. If your heart is pure, and your intentions are good, we will probably let you do it!

Nobody from staff will DM you first

Staff open a thread or use the ticket system. A DM claiming to be staff and asking you for anything is a scam. Report it.

4. Ethical coding only

Learning and exploring are the point of this server. Hacking and other unethical practices are not.

White hat work is welcome as long as you're transparent about what you're doing and why. If you can't say who authorised it, don't ask about it here.

5. Moderators have final say

If you have a concern or a dispute, the moderators have the final word. They work hard to keep this place safe and enjoyable, so trust their judgement — they're here to help.

Arguing a decision in public channels after it's been made is itself a problem. Moderation explains how to appeal properly.

6. No jobs or employment advertising

Discord isn't where you'll find work — use a real job board. Job posts and recruitment pitches get deleted, and you'll be warned or banned depending on how we feel about it. See rule 5.

7. Ask effective questions

When you want help, give people something to work with:

  • Describe the problem clearly and concisely.
  • Include the relevant code, the full error message, and screenshots where they actually add something.
  • Say what you've already tried and what you're trying to achieve.
  • Be patient and open to guidance. We're here to help you grow.

Paste code as text in a fenced block — not a screenshot of it, not a photo of your monitor. Helpers need to copy and run your code, and they can't copy a JPEG.

Asking good questions covers this in detail, with examples.

Reporting something

Use the /ticket system. It reaches the moderators without putting the incident in a public channel.

Ping staff directly when something needs a moderator now — a raid, a scam, or someone in crisis.

What happens if you break a rule

Moderation sets out the enforcement ladder, what the bot does automatically, and how to appeal.