frankenbit/game-jams
15
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Future jam: pick a real jam theme + use external constraint as the time-budget framing #1

New issue
Open
opened 2026-06-20 21:07:34 +02:00 by bosun · 0 comments
bosun commented 2026-06-20 21:07:34 +02:00
Owner
Copy link

Originally filed as cellblock#13 on 2026-06-20; moved here on 2026-06-20 evening per operator's organizational call — this is the natural home for cross-jam org work.

Idea

Operator-floated 2026-06-20: the 2026-06-19 CELLBLOCK jam used a Bosun-invented theme (multiplayer Tetris) and an operator-set time-box (15:00 deadline). Both worked, but both were internally-defined. A future jam could use a real game-jam theme — sourced from an actual ongoing or recently-closed external jam — which would give:

  1. External constraint → "use the time" framing comes for free. Jam-organizers set the duration; the crew accepts it from outside, not Bosun making up a time-box.
  2. Outside-imposed theme → design constraint isn't "what Bosun thought sounded fun" but a phrase that actively constrains decision-space. Better demonstration value.
  3. jam.frankenbit.de as a reference is more meaningful when entries share a common public vocabulary (theme + duration + format an outside reader can recognize from the jam scene).

Candidate jams

  • Ludum Dare — quarterly, themes on archive.ldjam.com after each event. Could pick a recently-closed theme retrospectively.
  • GMTK Game Jam (Game Maker's Toolkit) — annual, themes published at jam start.
  • Global Game Jam — annual, January-ish.
  • itch.io smaller themed jams — steady stream throughout the year.

Timing options

  • Sync with an active jam — run the crew's entry in parallel with the real submission window. Maximum demonstration authenticity.
  • Retrospective theme — pick a recently-closed theme, run it without formal submission. Sidesteps IP/competition complications, easier scheduling.

Substrate

Reusable from CELLBLOCK jam:

  • jam.frankenbit.de hosting
  • Retro template (BookStack book + per-jam chapter, see CELLBLOCK retro pattern)
  • Observability stack (Blackbox + journald → Loki + Grafana dashboard, see alcatraz-infra)
  • Crew-coordination via tmux-tell bus

New substrate per-jam:

  • Repo per jam entry
  • Possibly a new milestone shape on cellblock repo for the jam's scope

Operator decisions when picking up

  1. Which jam's theme (Ludum Dare / GMTK / Global Game Jam / itch.io specific)
  2. Sync vs retrospective
  3. Duration (jam's own time-box, or operator-shortened)
  4. Theme dispatch + start-time announcement to crew

Adjacent

  • Companion to cellblock polish sprint (separate tracker) — polish-arc is independent of repeat-jam, but learnings compose (the polish-sprint is the controlled experiment for the use-the-time-framing hypothesis that informs how the next jam dispatch is shaped).
*Originally filed as cellblock#13 on 2026-06-20; moved here on 2026-06-20 evening per operator's organizational call — this is the natural home for cross-jam org work.* --- ## Idea Operator-floated 2026-06-20: the 2026-06-19 CELLBLOCK jam used a Bosun-invented theme (multiplayer Tetris) and an operator-set time-box (15:00 deadline). Both worked, but both were internally-defined. A future jam could use a **real game-jam theme** — sourced from an actual ongoing or recently-closed external jam — which would give: 1. **External constraint** → "use the time" framing comes for free. Jam-organizers set the duration; the crew accepts it from outside, not Bosun making up a time-box. 2. **Outside-imposed theme** → design constraint isn't "what Bosun thought sounded fun" but a phrase that actively constrains decision-space. Better demonstration value. 3. **jam.frankenbit.de as a reference** is more meaningful when entries share a common public vocabulary (theme + duration + format an outside reader can recognize from the jam scene). ## Candidate jams - **Ludum Dare** — quarterly, themes on archive.ldjam.com after each event. Could pick a recently-closed theme retrospectively. - **GMTK Game Jam** (Game Maker's Toolkit) — annual, themes published at jam start. - **Global Game Jam** — annual, January-ish. - **itch.io smaller themed jams** — steady stream throughout the year. ## Timing options - **Sync with an active jam** — run the crew's entry in parallel with the real submission window. Maximum demonstration authenticity. - **Retrospective theme** — pick a recently-closed theme, run it without formal submission. Sidesteps IP/competition complications, easier scheduling. ## Substrate Reusable from CELLBLOCK jam: - jam.frankenbit.de hosting - Retro template (BookStack book + per-jam chapter, see CELLBLOCK retro pattern) - Observability stack (Blackbox + journald → Loki + Grafana dashboard, see alcatraz-infra) - Crew-coordination via tmux-tell bus New substrate per-jam: - Repo per jam entry - Possibly a new milestone shape on cellblock repo for the jam's scope ## Operator decisions when picking up 1. Which jam's theme (Ludum Dare / GMTK / Global Game Jam / itch.io specific) 2. Sync vs retrospective 3. Duration (jam's own time-box, or operator-shortened) 4. Theme dispatch + start-time announcement to crew ## Adjacent - Companion to cellblock polish sprint (separate tracker) — polish-arc is independent of repeat-jam, but learnings compose (the polish-sprint is the controlled experiment for the use-the-time-framing hypothesis that informs how the next jam dispatch is shaped).
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
frankenbit/game-jams#1
No description provided.