Godot Wild Jam 96 - 9-Day August Challenge Playbook 2026

If you searched godot wild jam in mid-August 2026, you are probably already inside Godot Wild Jam #96 - theme live, Discord loud, and the clock pointing at August 23, 2026. This is not a "should I join someday" essay. It is a finish playbook: cut scope, respect the no-AI rule, export something strangers can play, file a receipt, and survive voting week without rewriting your build after files lock.

Official jam page: Godot Wild Jam #96 on itch.io. Engine downloads: Godot Engine download. Export reference: Godot docs for exporting projects (link from the jam page / download hub).

Non-repetition: This is not the 5-night Godot juice challenge (PolishFX tool trial). It is not a Steam Next Fest dress rehearsal. It is GWJ #96 - monthly Godot community jam with explicit anti-AI rules and a 9-day window.

Why this matters now

As of the jam page: submissions open 2026-08-14 20:00 through 2026-08-23 20:00, with ~744 joined when this playbook was drafted. Mid-August means you are in Phase 4 (jam & play-test) - not Phase 1 theme brainstorming. The useful question is: can you ship a themed, Godot-made, human-authored playable before Aug 23 without breaking rules?

Why urgency is real:

Nine days is short once theme is known. Scope inflation kills more entries than missing a shader.
No generative AI - including the itch page. That rule is explicit and broad (code, art, music, dialogue, page copy).
Voting locks game files. After submit, you can polish the page; you cannot keep iterating the build unless a critical-bug ticket is approved.
Late tickets are narrow. Late submit (~2 hours) and critical bug fixes (~24 hours) exist via Discord #faq-and-support - they are not a plan A.

Who this is for

Reader	What you get
Beginners	Day-by-day cut list, first export path, common DQ risks
Developers	Export/playtest gates, team ≤5 honesty, template vs "new work" spirit
Creators	Discord paste + voting-week page tips
Search	Primary keyword godot wild jam + #96 / Aug 23 timing

Time left: depends on when you read this - treat remaining calendar days as sacred. Prerequisites: Godot installed (latest recommended by jam), itch account, Discord access for support tickets, and a project started during the jam window (no early start).

Official phase map (know where you are)

From the GWJ #96 page:

Phase	When	Your job mid-jam
1 Discord open	Week before kickoff	Already passed for #96
2 Channels close	Day before kickoff	Passed
3 Theme announced	2nd Friday 4pm NYC	Theme is live - stop debating
4 Jam & play-test	9 full days	You are here - build + export
5 Submission fixes	1 hour after end	Tickets only for breakers / missing submit
6 Voting	1 week	Rate others; game files locked

Wildcards are optional side challenges and should not affect ratings - do not burn your last day chasing every wildcard.

Hard rules that DQ entries (read twice)

Godot Engine - make the game in Godot (latest recommended).
Made in the jam window - do not start early.
Majority of code and assets by you - templates and licensed assets OK if disclosed/allowed; spirit is make something new.
No AI-generated content - vibe code, AI art, AI music, AI dialogue, AI assets of any kind - including the itch page.
No discrimination.
Solo or team ≤ 5.
Follow the theme and have fun (theme adherence is a judging category).

If you already used ChatGPT to write your design doc for the jam page or Midjourney for the capsule, stop and remake those assets human-side before submit - the rule is explicit.

Hour-by-hour final 24 hours (print this)

Hours to deadline	Focus	Explicit ban
T-24 to T-18	Freeze features; fix softlocks only	New mechanics
T-18 to T-12	Art/audio consistency pass (human-made)	New Asset Library packs
T-12 to T-8	Export + second-machine playtest	"Quick rewrite"
T-8 to T-4	itch draft upload; friends play exported build	Page pixel-peeping
T-4 to T-2	Submit for real; verify jam entry shows	Binary tweaks after submit
T-2 to T-0	Screenshots, short description, controls list	Starting a new scene
T+0 to T+1h	Phase 5 window - tickets only if missing/broken	Casual polish commits
Voting week	Rate others; update page media	Replacing the build

If you miss T-12 export, you are in emergency mode: strip content until the export is boring-but-bootable.

Theme without a cutscene

Voters judge theme adherence. You do not need a novella:

Verb matches theme - if theme is "echo," the player action should echo (clone, delay, reflect) not only the title.
First screen signal - title card or first prop telegraphs theme in under five seconds.
Fail forward - dying/restarting still teaches the theme (echo of last attempt, ghost trail, etc.).
Avoid bolted lore - a wall of text that explains theme while gameplay is generic will score poorly.

Write your theme proof on a sticky note next to the monitor. If a friend cannot guess the theme after 30 seconds of play, cut presentation noise and amplify the verb.

Accessibility minimums that fit a jam

You will not ship full remapping and narration in nine days. You can still:

Pause that actually pauses
Mute/volume or separate music/SFX sliders if cheap
Color-critical info also shown by shape/icon
Default controls listed on the itch page in plain language
Avoid seizure-risk flashing

The jam points jammers at community accessibility guideline lists - pick one or two items and check them off in your receipt. That alone differentiates unfinished prototypes that feel hostile.

Templates, packs, and the "spirit of the jam"

Allowed examples on the jam page include project templates and assets you have rights to. Spirit check:

OK	Risky / bad
Starter controller from a template, heavily modified loop	Uploading last month's Steam demo with a new title
CC0 Kenney pack credited	AI upscaled "original" art
Your own pre-made brush set used during jam	Porting a finished commercial prototype
Maack-style template for folders/autoload	Multi-jam spam of the same binary

When unsure, ask: "Did we make this game for GWJ #96 this window?" If the honest answer is no, do not submit.

Solo vs team - decision matrix

Situation	Solo	Team (≤5)
Decision speed	Fast	Needs standup
Art bandwidth	Low - use primitives	Split roles early
Merge pain	None	Freeze scenes; one exporter
DQ risk	Scope pride	>5 people / unclear credits
Best use	Micro puzzle / one-screen	Split art/audio/code

If your "team" is six Discord friends who each want a feature, cut to five or go solo. The rule is hard.

Playtest script (15 minutes with a stranger)

Do not speak for the first two minutes.
Note where they look / click / rage.
Ask: "What is the theme?" after three minutes.
Ask: "How do you restart?"
Fix only blockers (softlock, unclear goal). Ignore taste notes about "needs crafting."

Record findings in the receipt. One stranger playtest beats five developer opinions.

itch page checklist (voting week leverage)

Because files lock but the page does not:

Capsule/thumbnail readable at small size
3–6 screenshots of actual gameplay (not editor)
Controls section at top of description
Theme one-liner
Content warnings if needed
Credits + licenses
Link to jam Discord only if you want feedback - optional

Updating the page during voting is fair game and often raises play rate more than another unshipped particle system would have.

Receipt template

GWJ #96 FINISH RECEIPT - 2026-08-16
Hours to deadline at start: ___
Pitch (1 sentence): ___
Theme proof (1 sentence): ___
Scope cuts: ___
AI inventory: clean / replaced ___
Export target: ___
Exported playtest: PASS / FAIL
Stranger playtest: Y/N notes: ___
Submitted at: ___
Wildcards: none / list
Voting week page tasks: ___

More FAQ

What if I started the project before the jam?

Do not. The rules say make the game within the jam period and not start early. Begin a new project for #96.

Can I submit to other jams with the same game?

Allowed if clearly made for this jam, but the page warns multi-jam spam looks bad. Prefer one honest home.

What counts as a game-breaking bug for tickets?

Examples on the jam page: level does not load, enemies invulnerable, goal unreachable. Taste polish does not qualify.

Where do I open tickets?

GWJ Discord #faq-and-support (preferred). Community tab is secondary and not for critical fixes outside Discord per organizers.

Do wildcards change my score?

Organizers say wildcards are not intended to affect ratings. Treat them as optional fun.

Mid-jam finish plan (G1–G8)

G1 - Clock and team census

Write today's date, hours to Aug 23 20:00 (jam timezone on itch), team size (1–5), and roles.

G1: Deadline = 2026-08-23 20:00 (itch), hours left = <n>, team = <n>, roles = <...>.

G2 - One-sentence game + theme proof

One sentence: player verb + obstacle + win/lose. One sentence: how it shows the theme without a lore essay.

G2: Pitch = <...>. Theme proof = <...>.

If you cannot explain theme proof in one line, cut story systems first.

G3 - Scope cut table (do this today)

Keep	Cut	Park for post-jam
One verb loop	Second verb	Meta progression
One playable level	Three biomes	Mod tools
Keyboard or simple gamepad	Full remap UI	Steam Input
Placeholder SFX	Full OST	Voice acting
Readable UI	Fancy animated menus	Localization

G3: Keep loop = <verb>, cuts = <list>.

G4 - Anti-AI inventory

List every asset and who made it. Flag anything generated. Replace or remove before upload.

G4: AI inventory = clean / replaced <items> / BLOCKED.

Blocked means you do not submit until clean - better a smaller human game than a removed entry.

G5 - Playable vertical slice tonight

Definition of done for "playable":

Boot to a controllable character or cursor
One complete loop (start → challenge → fail/win feedback)
Quit/restart without editor
No softlock in the happy path

G5: Slice playable = Y/N, softlocks found = <...>.

G6 - Export smoke (non-negotiable)

Set export presets for your target (HTML5 is common for itch jams; desktop OK if you state it).
Export a build strangers can download/run.
Test the exported build - not only F5 in editor.
Upload to itch as draft; verify play/download works on a second machine or private window.

Official nudge: use Godot export docs via godotengine.org/download / project export documentation linked from the jam page.

G6: Export target = <HTML5/Win/…>, exported playtest = PASS/FAIL.

G7 - Submit before the cliff

Join the jam on itch if not already.
Submit with clear title, short description, theme note, controls, and credits.
Do not wait for "perfect." Submit when G5+G6 pass.
Note late-ticket rules only as emergency.

G7: Submitted = Y/N, time = <...>, late ticket needed = N/Y.

G8 - Voting-week posture

After deadline:

Game files locked during voting
Page (thumbnail, screenshots, description) can update
Vote on other entries (participants only)
Critical bug tickets within ~24h via Discord if truly game-breaking

G8: Page polish plan = <screenshots/thumb>, bug ticket = none/open.

Day-remaining playbooks

If you have 5+ days left

Day N: lock pitch + cut list (G2–G3)
Day N+1: greybox loop (G5)
Day N+2: art/audio pass that stays human-made
Day N+3: juice lightly - do not restart genre
Day N+4: export + friend playtest (G6)
Final day: submit morning; afternoon buffer for itch page only

If you have 48 hours left

Cut to one screen / one enemy type / one win condition.
Ban new systems.
Export tonight even if ugly.
Sleep; morning submit; afternoon page polish.

If you have 12 hours left

Strip to prototype that shows theme in 30 seconds.
Export HTML5 or simplest desktop.
Submit with honest "prototype" framing.
Skip wildcards entirely.

Judging categories - design for voters

Voters score Theme, Fun, Controls, Graphics, Audio, Accessibility, Originality (jam page). Practical tips:

Theme: Show it in the first 20 seconds of play.
Fun: One clear verb beats five half systems.
Controls: Document keys on the itch page; avoid hidden combos.
Graphics/Audio: Coherent > detailed. Consistency reads as quality.
Accessibility: Even one item from community accessibility lists (remappable or color-safe critical info, pause, volume) helps - jam encourages basic accessibility guidelines.
Originality: One surprising twist on a small idea beats a genre museum.

Team of 2–5 - communication rules

One "build owner" who exports and uploads.
Art/audio freeze 12 hours before deadline.
No parallel main scenes without merge plan.
Discord standup: what ships today / what is cut.
Credits file with real names - no AI tools listed as authors.

Beginner path - first Godot jam

Download Godot from godotengine.org/download.
Join GWJ #96 and the Discord.
Make a new project now (if you have not started, you are late but still may finish a micro-game).
Build a single scene loop.
Export and upload.
Do not open the Asset Library rabbit hole for "ultimate controller."

Common beginner DQ risks: starting from a pre-jam vertical slice you already shipped; AI capsule art; forgetting export; team of 6.

Developer depth - export and playtest checklist

Check	Pass criteria
Export preset exists	Named preset committed or screenshot in receipt
Headless/second PC test	Build runs outside your machine
Input	Default keys work without remap required
Resolution	Readable at 1280-wide itch embed if HTML5
Audio	Not ear-destroying default volumes
Credits	Templates/asset packs licensed and named
Theme	Mentioned in description + shown in play

HTML5 tips: test in Chrome and Firefox; watch for autoplay audio blocks; keep first load small.

Desktop tips: zip structure clear; README with controls; mark OS.

Creator Monday / Discord paste

GWJ #96 status: hours left <n>. Pitch locked. Scope cuts <list>. AI inventory clean. Export <target> playtest PASS/FAIL. Submit plan <time>. Wildcards skipped/kept: <...>.

Keep finish / hold expand / rewrite genre

Decision	When	Action
KEEP finish	Slice playable; theme clear	Export + submit
HOLD expand	Tempted to add RPG inventory day 8	Freeze features
REWRITE genre	Only if current loop is unplayable and ≥3 days remain	Rare - usually wrong

Failure modes

Failure	Fix
Feature creep day 7	G3 cut table again
AI page blurb	Rewrite yourself
Editor-only "done"	G6 export smoke
Submit at T-2 minutes	Aim for T-12 hours
Post-vote binary upload	Not allowed - page only
Wildcard tunnel vision	Optional - ignore

CapEx / studio note (why leads care)

A Wild Jam finish builds:

Proof a teammate can ship under constraint
A public itch URL for hiring/portfolio
Habit of export discipline before Steam demos

It does not replace a Steam Next Fest plan. Different format ladder.

Format ladder

URL	Job
This GWJ #96 playbook	August Wild Jam finish
5-night Godot juice challenge	Tool polish challenge
Godot 4.6 Jolt switch	Physics migration keep/hold
Next Fest upload challenges (catalog)	Steam demo pipelines

Key takeaways

GWJ #96 runs through Aug 23, 2026 - mid-jam means finish mode (itch jam).
No AI content including the itch page - inventory before upload.
Export the build strangers play; editor F5 is not submit-ready.
Voting locks files - polish the page, not the binary.
Cut scope harder than you want; theme clarity beats content volume.
Team ≤ 5, Godot-only, made in-window.

FAQ

When does Godot Wild Jam 96 end?

Submissions are due 2026-08-23 20:00 per the itch jam page (confirm the live countdown).

Can I use generative AI if I disclose it?

No. The jam forbids AI-generated content of any kind for the game and the itch page.

Can I update my game after submitting?

During voting, game files are locked. You may update page media/text. Critical bugs may get a Discord ticket window (~24h) - case by case.

Can I use a template?

Yes (example: Maack's Template is cited on the jam page) - still make a new jam game; do not reskin an old release.

HTML5 or desktop?

Either can work. Pick one early and export-smoke it. HTML5 is convenient for voters; desktop is fine if clearly labeled.

Are wildcards required?

No. Optional and not meant to affect ratings.

Where do I get Godot?

godotengine.org/download.