Process Shuck Month

A working concept for an annual public game jam organised by Shuck. The jam is Shuck Month. Shuck hosts it and participates in it. Pre-launch idea, not yet a commitment.

The shape of the idea

Once a year, Shuck runs a public month-long game jam open to anyone. The studio organises the jam (theme, rules, itch.io page, gallery, post-jam roundup), participates in it alongside everyone else, and pauses the main project for the duration. The jam is the event. Shuck is the host and an entrant.

This is the Amnesia Fortnight model widened: instead of a private studio event made public after the fact, an event that is public from day one and built so other developers can join in. Shuck gets the same structural value Double Fine got from Amnesia Fortnight (a regular event, parallel IP, public-by-default game-making at the seed), and the open-development community gets a piece of regular infrastructure they can rely on.

Why host the jam, not just enter one

Three reasons.

1. It walks the talk. An essay-arguing studio about open development that runs a public open jam is doing the practice at the level of the industry, not just at the level of one studio. The book's argument is that openness compounds; hosting the jam is one way to compound.
2. It builds shared culture. Other indies enter, mod, learn, ship, and the work becomes a cohort each year. Shuck Month becomes the moment a small piece of the open-development community gathers.
3. It is a marketing move that is not marketing. The jam is real value to other developers. Shuck's name attaches to that value. The studio is known for the work the jam produces, not for ads.

What changes for a solo studio (as the host)

Hosting a jam alone is real work. The format keeps it minimal:

• Itch.io jam page. The standard hosting venue. Includes rules, theme reveal, submission window, voting / rating round, gallery.
• Theme. Decided by Shuck, announced when the jam opens. One word or short phrase, broad enough to leave room.
• Rules. Short. Web-playable build, MIT or compatible licence preferred (not required), no AI generation in art assets (matches the essay's line, signals the studio's posture without mandating it). Teams allowed.
• Voting / rating. Itch.io's built-in entrant rating system. Shuck does not curate; the entrants rate each other.
• Post-jam roundup. A shuck.dev post highlighting standout entries, with permission. Not a winner; a roundup. The point is to surface work, not to crown it.
• Discord or forum. Optional in year one; necessary if the jam grows. Defer until needed.

What changes for a solo studio (as an entrant)

Even with a month-long jam, scope discipline matters. The instinct is to build one prototype across the whole month, but that loses the value of multiple swings. Better: keep the count up and crank scope down. Four or five small prototypes in twenty working days, each tightly bounded, beats one polished prototype every time. The constraint is the feature.

• Scale. Four to five prototypes across the month, three to four working days each, plus a few days of buffer for setup, integration and the post-jam wrap.
• Scope. Each prototype is a single mechanic on a single screen, with placeholder art and minimum viable input. No save system. No menus beyond a start button. No music (ambient sound at most). Web-playable. A target time-cap of around twenty-four working hours per prototype, including the build pipeline.
• Theme. Whatever Shuck announces for the year. Each prototype reads the theme differently and explores a different angle.
• Documentation. Devlog posts every two or three days (text + screenshot, sometimes a short clip) carry the record. Less intense than Double Fine's daily film schedule; still enough that the audience has something to follow.

A working format

Cadence. Once a year, in May: pre-summer, before vacation drift, no competing month-long jam already running. Deliberately not November (overlaps with GitHub Game Off and would split attention from a jam that already owns that window). Deliberately not the weekend-jam clusters around Ludum Dare or Global Game Jam.

Theme. Decided by Shuck six weeks out, announced on day one of the jam.

Scope discipline (the rules for Shuck's own entries).

• One mechanic per prototype.
• Single screen.
• Placeholder art only (free packs, programmer art, traced shapes).
• No save, no menus beyond a start button.
• No music; ambient sound at most.
• Web-playable build.
• Target around twenty-four working hours per prototype, including export and upload.
• The submission deadline is the deadline. No "polish week" added afterwards.

Deliverables (per Month, for Shuck).

• 8-12 devlog posts on shuck.dev across the month
• 4-5 playable web builds at the end (Itch-hosted as Shuck's jam entries)
• A short post-mortem after the jam closes, naming what each prototype taught
• The source for each on the Shuck Games GitHub org under MIT (matching Volley!'s licence)
• A community roundup post highlighting other entrants' work

Funding. Self-funded as Shuck R&D in early years. The jam itself is free to enter and free to host (itch.io covers the venue at no cost). If the audience grows, optional supporters (Patreon-style) can pledge per Month. Never a paywall on the prototypes.

What happens after. Most prototypes get shelved. The strongest one might earn a future development pass, running alongside the next thing the studio is shipping. The shelved prototypes stay public; the source stays MIT; contributors can fork them if they want.

What the main project does during a Month

Nothing. Volley! (or whatever Shuck is shipping at the time) pauses for the four weeks. This is the point of the Amnesia framing: stepping fully away. If the main project is in a tight delivery window, the Month is postponed; if it is in normal development, the pause is restorative and helps the work when it resumes.

Risks and mitigations

• Solo host fatigue. Hosting a jam AND entering it AND keeping the studio's main posture is a lot. Mitigation: keep year-one infrastructure minimal. No Discord. No bespoke theme reveal video. Plain itch.io page, a short rules doc, a roundup post. Add infrastructure only as the jam grows enough to need it.
• No one enters. Real risk in year one. Mitigation: enter alongside the call; even a jam with five entrants is a jam. Do not measure year one by entrant count; measure it by whether it ran cleanly and Shuck shipped its prototypes.
• Solo developer prototype fatigue. A month of prototyping, even at jam pace, is a lot of context-switching. Mitigation: build slack into the schedule. Some days are explicitly for thinking, not building. The 24-hour cap per prototype is a target, not a minimum.
• Audience fatigue with main-project pauses. Shuck Month has to feel like a different kind of treat, not a delay. Naming it as the studio's annual event matters more than describing it as "the main project is paused".
• Prototype creep. The temptation to keep working on a prototype past its slot is real. Mitigation: the slot is the slot. Anything beyond is a separate decision after the jam closes.
• Contributors. Resolved by the jam framing. Standard jam team-formation rules apply. Anyone who wants to join Shuck's team for the month can; team membership ends when the jam does. Paid commission only if a prototype calls for art/music beyond what placeholder packs supply.
• Conflict-of-interest concerns. Shuck both hosts and enters. Mitigation: no winners, no prizes, no curated standout. The roundup post highlights work Shuck enjoyed, with permission, and Shuck's own entries are flagged honestly.

What this gives Shuck

• A regular event the audience anticipates
• A pipeline for new IP without disrupting the main project
• A documented practice of public game-making at the seed
• A piece of community infrastructure that does not exist before Shuck builds it
• A natural channel for contributors via standard jam team formation
• A counterweight to the multi-year arc of building a single game in public
• Material for the next essay (or chapter of the book)

When the first Month runs

Not until Volley! ships v1.0. The Amnesia framing requires fully stepping away from the main project; that is unsustainable while Volley! is still on its way to release. Until then, every working day belongs to the game in flight.

Once Volley! v1.0 is out, the studio is in a different posture: maintenance, post-launch content, the start of whatever comes next. Shuck Month fits naturally into that cadence as the structural event that marks "Shuck is more than one game" and as the studio's first contribution to community infrastructure beyond its own work.

The first Month should be small, possibly under-attended, and almost certainly produce prototypes that do not become anything. That is fine. The point is to start the cadence at a moment when the studio can afford to.

Pre-Month checklist (deferred until Volley! v1.0 has shipped):

• shuck.dev infrastructure for devlog posts and the jam roundup
• An itch.io jam page with a clear rules document
• A repository naming convention (e.g. shuck-games/month-YYYY-prototype-name)
• A theme decided six weeks before the jam opens
• A short Shuck Month rules document, separate from this concept doc