Quick answer: Jam hours are precious enough that tooling is strategy: an engine you already know configured before the theme drops, instant audio (jsfxr for effects, free music libraries), proven asset shortcuts (Kenney packs, Lospec palettes, Google Fonts), and a tested one-command web export. The meta-tool is the prep checklist — everything installable, downloadable, and testable belongs to the night before.
Jam hours are precious enough that tooling is strategy: an engine you already know configured before the theme drops, instant audio (jsfxr for effects, free music libraries), proven asset shortcuts (Kenney packs, Lospec palettes, Google Fonts), and a tested one-command web export. The meta-tool is the prep checklist — everything installable, downloadable, and testable belongs to the night before. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.
The pre-jam checklist is worth half a day
Before the theme drops: engine installed and updated, a blank project template with your usual folder structure and input handling, version control initialized, asset packs and font/palette bookmarks downloaded locally (jam-weekend wifi and crashing asset sites are traditions), and — critically — a full build-and-upload dry run to itch, because discovering your web export is broken at hour 46 is the classic jam tragedy.
Template projects deserve real investment between jams: a personal starter with menus, scene transitions, screen shake, audio manager, and pause already wired saves the same three hours every single jam.
Audio and art in minutes, not hours
Sound effects: the sfxr family (jsfxr in-browser) generates jumps, hits, pickups, and explosions in seconds — every jam game's audio can be functional within ten minutes, and audio-early transforms feel ratings. Music: free libraries and loop packs (license-checked) or a generative tool; one looping track suffices. Art: Kenney's CC0 packs cover whole genres, Lospec palettes make your own art coherent, and Google Fonts beats default-font shame.
The principle underneath: jam ratings reward feel and completeness, not asset originality (Compo rules aside). Hours saved on commodity assets are hours spent on the one thing that must be original — the mechanic.
Ship-fast infrastructure
The shipping stack: web export as default target (browser builds get several times the plays and ratings), butler or drag-and-drop itch upload tested in advance, a screenshot/GIF tool ready (the page needs them and you'll be tired), and version control with remote — the jam-crash-at-hour-30 horror story is always missing-backups underneath.
Add the humble timer: alarms at your scope checkpoints (one-third: loop playable; two-thirds: feature freeze) because flow state is wonderful and has no clock. Tools can't make the game good, but they reliably refund the hours that make good possible.
Finished and small beats ambitious and broken
Jam ratings and jam memories both go to entries people could actually play. A tiny, complete loop with one good idea outperforms an ambitious wreck every time. The brutal math of a weekend: every system you add halves the polish every other system gets.
Decide your core loop in the first hour, build it ugly by the halfway mark, and spend the entire back half making it feel good. That schedule wins jams.
The jam ends; the feedback doesn't have to
The flood of comments after a jam is the most honest, fastest feedback your work will ever get — strangers with no stake telling you exactly where they got confused or quit. Most devs read it once and move on. The better move is mining it.
Sort comments into 'confused', 'bored', and 'delighted'. The confusions are UX bugs, the boredom marks pacing problems, and the delights tell you what the full game should be about.
The quiet work that protects all of this
Everything in this post gets undone by an unstable build. A great store page, a clever marketing beat, a perfect jam entry — none of it survives 'crashed twice, refunded'. Stability isn't a feature players praise, but it's the floor everything else stands on.
Give yourself visibility before you need it: crash reports with stack traces, a simple way for players to flag issues from inside the game, and a habit of fixing the top recurring error before adding anything new.
Putting it to work
Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.
Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.
Lock the loop early, cut without mercy, and spend the last hours on feel.