Game Jam Event

A weekend game jam: theme reveal, team finder, dev logs, submissions by platform, playtesting and a judges' table.

  • 7 categories
  • 37 channels
  • 12 roles
  • Medium
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

JAM HQ

  • jam-welcome

    Welcome to the jam. Read #jam-rules, pick a discipline, then find a team or go solo.

  • jam-rules

    Duration, what counts as pre-made assets, team size, engine rules, content rules and how results work.

  • jam-announcements

    Start, deadline changes, playtest voting and results. Organisers only.

  • theme-reveal

    The theme, posted by the organisers at the starting gun. Nothing else goes here.

  • deadlines

    Submission cut-off, playtest window and voting close, with time zones.

  • pick-your-discipline

    Pick Programmer, Artist, Composer or Designer so teams can find the skill they are missing.

TEAM FINDER

  • team-finder

    One thread per team or per person. Tag what you need; change it to Team full when you are set.

  • solo-jammers

    Going alone? Company, commiseration and scope advice from the other soloists.

  • engines-and-tools

    Which engine, which version, which asset pipeline. Setup help before the clock starts.

  • Meet Your Team

JAMMING

  • jam-chat

    The main room while the jam is on. Progress goes in #dev-logs; help requests in #ask-for-help.

  • dev-logs

    One thread per team. Post progress in it and tag the day; add Post-mortem after the jam.

  • wip-screenshots

    Screenshots and gifs of whatever is working, or not working, right now.

  • music-and-sfx-wip

    Loops, stingers and sound effects in progress. Composers share and swap feedback here.

  • art-wip

    Sprites, tiles, models and concept art in progress.

  • ask-for-help

    Stuck on a bug, a shader or an export? Ask here; someone from another team usually knows.

  • Crunch Room 1
  • Crunch Room 2
  • Crunch Room 3
  • Composer Corner
  • AFK

SUBMISSIONS

  • submission-checklist

    What a submission thread must include and how to name the build. Kept current by the organisers.

  • submitted-games

    One thread per game: title, download or play link, controls, team credits. Tag every platform it runs on.

  • submission-problems15s slowmode

    Upload failed, build broken, deadline questions. Organisers watch this channel in the last hour.

PLAYTESTING

  • playtest-requests

    Ask for players for your game: platform, length, what you want feedback on.

  • playtest-feedback

    Feedback on submitted games. Name the game, say what worked, say what did not, be specific.

  • jam-bug-reports

    Bugs found while playing entries, one message per bug with steps to reproduce.

  • Playtest Party 1
  • Playtest Party 2
  • Showcase Stage

JUDGES

  • judging-rubricHidden from @everyone

    Criteria and weighting, posted by the organisers before playtesting opens.

  • judge-notes

    Judges and organisers only. Notes per game as you play through them.

  • score-sheets

    One message per judge with scores for every entry against the rubric.

  • Judges Table

ORGANISERS

  • organiser-chat

    Organisers and moderators. Theme shortlist, timing, problems on the floor.

  • jam-logsHidden from @everyone

    Vetox posts join, role and moderation logs here.

  • Organiser Voice

Roles

  • Jam HostAdministrator
  • OrganiserModerator
  • ModeratorModerator
  • Judge
  • Team Lead
  • Jammer
  • Programmer
  • Artist
  • Composer
  • Designer
  • Muted

Overview

A server for a 48- or 72-hour game jam, whether it is your community's first or an annual fixture. Jam HQ is read-only: #theme-reveal is where the organisers drop the theme at the starting gun, #deadlines holds the submission and voting cut-offs, and #pick-your-discipline hands out the Programmer, Artist, Composer and Designer roles that make team finding work. Team Finder is a forum tagged by what a team still needs, with a #solo-jammers channel for people going alone and a Meet Your Team voice room. Jamming is the busiest category: #jam-chat, a #dev-logs forum with one thread per team tagged by day, separate channels for work-in-progress screenshots, music and art, an #ask-for-help channel, three five-seat Crunch Rooms and a Composer Corner. Submissions has a checklist the organisers keep current, a #submitted-games forum tagged by platform and a #submission-problems channel for the last hour. Playtesting pairs #playtest-requests and #playtest-feedback with two Playtest Party voice rooms and a Showcase Stage for streaming the entries. Judges and Organisers are hidden categories: the rubric, judge notes, score sheets and a Judges Table for one; chat, Vetox logs and a voice room for the other.

When to use it

The theme drops on Friday evening and fifty people need to find teams by midnight. Over the weekend, teams want to post progress without spamming chat, composers want a room of their own, and on Sunday night everyone is uploading at once and something breaks. After the deadline, the games need players and the judges need a quiet table. This layout gives each of those phases its own space so the organisers can stop answering the same question in chat.

What makes it different

  • #team-finder is a forum tagged Need programmer, Need artist, Need audio and Need designer, so teams form fast.
  • #dev-logs gives every team one thread tagged by day, so progress is visible without flooding #jam-chat.
  • #submitted-games is tagged by platform, which makes playtesting on the right machine a filter, not a hunt.
  • Two Playtest Party rooms and a Showcase Stage turn the post-deadline hours into an event.
  • The judging rubric, notes and score sheets are hidden from jammers until results are announced.

Recommended Vetox setup

  • Self-Roles

    Post a Self-Roles panel in #pick-your-discipline for Programmer, Artist, Composer and Designer so a team can ping the discipline it is missing.

  • Reminders

    Set Reminders in #deadlines at 24, 6 and 1 hours before submissions close and again before playtest voting ends.

  • Temp Voice

    Point Temp Voice at Meet Your Team so a fourth or fifth team gets a Crunch Room without permanent channels piling up.

  • Starboard

    Turn on Starboard from #wip-screenshots so the best progress shots of the weekend collect in one place for the recap.

Questions

How is the winner decided?

Either way works. For a judged jam, the Judges category holds the rubric and score sheets. For a community vote, post polls in #jam-announcements and use #playtest-feedback as the discussion channel. Many jams do both: a judges' pick and a community favourite.

Do jammers need to be on a team?

No. #solo-jammers is for people going alone, and the Solo tag in #team-finder marks a post that is looking for feedback rather than members.

What is the Showcase Stage for?

After submissions close, an organiser streams the entries one by one on the stage while the makers answer questions in #playtest-feedback. It is the closest thing an online jam has to a demo night.

Common mistakes

  • Announcing the theme in chat, where it scrolls away; #theme-reveal is read-only so the theme is the only thing in it.
  • Skipping a submission-problems channel, which means the last hour of the jam is a support queue inside #jam-chat.

Consider instead

  • Hackathon Event The projects are apps or hardware with sponsor challenges and a formal judging panel.

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages