652 FREE TOOLS12 GAME KITS72 QUICK ANSWERS643 IN THE ORIGINAL SWEEP
What are you making it for?Flip it. Every badge in the issue follows.
Free hobby games for you and your friends. Almost every tool is fine here.Sold, ads, or on a store. Badges now show the selling license, and every catch gets a warning.
02LOADOUT · November 2026Contents
Twelve kinds of game, twelve short kits. Find the one closest to yours and set up only that. Every kit says what to use, what to try first and what to grab only if you need it.
Loading the kits...
04LOADOUT · November 2026Strategy Guide
Seventy-two quick answers from the study. Type what you're after, like music, dialogue or Game Boy, and the file narrows down.
File 18 / quick answers72 entriesChecked 2026-11-05
Showing all 72
18LOADOUT · November 2026Cheat Sheet
Two judges, one from each team, looked at the same evidence for 192 design-side tools: shipped games, showcase art, sample outputs and UI screenshots. Neither saw the other's calls. These are their real verdicts, word for word. No scores were made up for this page.
Matching calls show agreement on the same evidence, not how well a tool will work in your game. Only a real asset in a real game shows that. Where the judges split on tier, the kits use the more cautious call.
Loading the verdicts...
CROSSCHECK's original verdicts came from evidence reviews. These reports put tools into a real workflow and show what happened.
TESTED · NOV 14, 2026
A fact checklist for your AI's 3D scenes. We built three small games with it. Right chemistry and left-right bones, but not faster. Skill scores 2, 2.5 and 2 out of 5. Play all three.
Windows · headless Chrome. Needs python, not python3.
Read the 3D testTESTED · NOV 13, 2026
734 animated pieces drawn in letters. 733 passed the built-in check. Six ran at once on a self-hosted page with no outside requests. We built a small playable room on its kit.
Windows · headless Chrome. Godot and real phones untested.
Read the ASCII testTESTED WITH A FIX · NOV 11, 2026
A useful low-poly parts bin. Four imports matched their geometry metadata, but materials needed a color flag correction. Tested color-only GLB requests kept default paint.
Windows · Godot 4.7.2 · Compatibility/OpenGL · Quadro RTX 5000. Android and performance untested.
Read the Polyfork testTESTED COMPARISON · NOV 8, 2026
Pixel Art Lighter kept a painted letter flatter than Laigter's default normal map. One 48 × 48 sprite, the same moving light, thirteen rendered positions.
Windows · Godot 4.7.2 · Compatibility/OpenGL · Quadro RTX 5000. Other sprites, masks and Android untested.
Read the lighting testThe spine is Krita, Blender, Inkscape, Pixelorama and Godot. Both raised Effekseer for spell and hit effects. Hero work stays bespoke: the player, bosses, title screen and menus never come from a pack or a generator.
For 38 tools, Claude's judge said MEETS and Codex's judge said CONDITIONAL. Codex wants proof of repeatable production quality, not one good sample.
Claude's judge put 13 tools below the bar, including retro web UI kits like NES.css, the LPC character generator, raw SDXL output, RIFE and TripoSR. Codex held them at CONDITIONAL, because weak examples alone don't prove a low ceiling. Both moved them out of the kit.
Editors and engines meet the bar. Packs, presets, templates and AI generators are where the "safe" look comes from. That's what both judges found, working apart. Here is how a kit makes the safe look, and what to do about it.
The gray template menu, the stock dialogue box, the default Godot theme, stock particle presets, Inter everywhere. Each is competent and none has personality. Fix: a "no default survives" rule. Before any look review, ask which defaults are still visible.
Kenney, KayKit, Quaternius and the pixel packs are great and instantly recognizable. Mix three and the rooms look like they came from different games. Fix: one source family per game, repainted to the palette, relit under one light, and the hero set always made for the game.
Generators drift to the middle: stock props, sprites that are pixel-styled rather than pixel-made, faces that change between frames. A beautiful sample hides a broken back side or a drifting walk cycle. Fix: AI for concepts, paintovers, textures and distant props only. Require a character sheet, several views and an in-engine playback before an asset is accepted.
Bloom, vignette, scanlines and noise on everything make a dim, muddy, dated image, and loud effects can make a weak attack feel bigger without making it threatening. Fix: write one lighting idea per scene first, and build anticipation, contact and recovery before adding effects to explain those moments.
Preset shake on every hit reads generic. No hit-stop and tiny tweens read safe. Both miss weight and threat. Fix: a feel spec per action (anticipation frames, hit-stop in milliseconds, knockback, shake by attack weight), bespoke telegraphs for bosses, and review in captured video.
Automatic snapping keeps the shapes and crushes the ramps. Fix: assign shadow, mid and light per material by hand, then check labels, danger states and silhouettes at the smallest size they appear.
Materials that import and animation tracks that validate say nothing about character or feel. Fix: review one full encounter and one full menu against a written visual target, then polish the weakest visible thing.
22LOADOUT · November 2026CROSSCHECK
Every tool the two teams checked, all free to use, each with a license note. Pick a job from the key, narrow it by kind of game, and flip the cover sticker to see the selling license. Reference projects stay hidden until you tick them.
KEYColor means job. Tap one to filter, tap it again to clear.
28LOADOUT · November 2026Buyer's Guide
How people are making games with AI right now, what they make, and where the money really goes. The numbers come with their sources.
Most AI-made games right now are small. One person points a coding agent at real project files, plays every build and keeps the scope tight. Browser toys and jam entries make up the biggest crowd. A thinner stream of survivors-likes, tower defense and twin-stick shooters reaches Steam.
The builders are a mixed bunch. Vibe Jam drew over 1,000 entries in 2025 and 945 in 2026, when its rules required at least 90% AI-written code. The 2026 winner had about nine years of iOS work behind the game. Steam has a backend developer new to games, solo devs and small teams running Claude Code and Codex side by side. Parents build with their kids. Non-coders use hosted makers like Astrocade and Rosebud, whose big player counts are company claims.
Vibe Jam 2026 press page2025 jam results
None of the sources ranks these tools on a fair test, so read this as who shows up where. In one February 2026 snapshot of r/aigamedev, Claude came up in 15 of 87 readable posts, Codex in 9, Gemini in 8, ChatGPT in 3 and Cursor in 1. That is one day on one subreddit, counting mentions. Shipped games line up with it. Claude Code built the 2026 Vibe Jam winner and Codex Mortis on Steam. fly.pieter.com credits Cursor and Three.js. Codex often runs beside Claude.
People mix models freely. One writes code, an image model draws concepts, Suno makes music and ElevenLabs makes sound. In one forum thread, usage limits drove tool switching more than quality did. Codex's own research found no broad, current benchmark that crowns a winner. Running Claude Code and Codex on one project matches what the shipped examples use.
r/aigamedev snapshot (mirror)Codex Mortis on Steam
This is workflow fit, judged from file formats, headless runs and builder reports. None of the sources measures engines head to head. Agents do best when the whole game is text they can read and a build they can run and look at.
Scenes and scripts are plain text, and the engine runs headless. JAMER, SWE-Game and GameCraft-Bench all test on Godot, and JAMER says it chose Godot for those two traits. The common bug is Godot 3 code in a Godot 4 project. Choose GDScript whenever a web build might matter, because Godot 4.7 can't export C# projects to the web.
Code only, with no editor state to lose. Phaser 4 ships 28 skill folders for agents, including a v3-to-v4 migration skill. Three.js publishes an llms.txt that tells models which import pattern is current. Old-version code is the usual bug, so pin versions.
Agents reach these through bridges that drive a running editor, because scenes live in binary files or YAML full of cross-references. It can work. Infinite Night reached Steam with Claude Code and a Unity MCP bridge. This kit still skips Unity on cost and license grounds.
Godot 4.7 web export docsJAMER paperPhaser repo and skills
The AI label is common on Steam now, and the money mostly goes elsewhere. The games that work keep AI out of the first impression, stay small and have a person checking whether it's fun.
About half of new Steam games released in October 2026 disclosed AI content (50.9% by Sulka Haro's count, 49.9% by another), up from about one in three in Q2 2026 and 42% in the most recent full quarter, yet AI-disclosed games took only about 10 to 12% of estimated sales in those quarters (Haro, July and November 2026, review-based estimates).
October 2026 Steam releases that disclosed AI, 1,982 of 3,897.
Estimated share of Steam sales those games took, from review counts.
Share of AI-game revenue the top two AI titles take in each mature quarter.
Most of the money sits in big, ordinary games with light AI use. Ichiro Lambe roughly estimated $660M gross for 10,258 AI-disclosed games by November 2025. Twelve made eight figures, and 9,556 made under $10,000.
The label travels with fewer reviews. AI games reach 100 reviews at about 0.55 times the rate of other games. A vendor study of 9,879 paid games found 52.6% fewer first-month reviews after controls. Both are associations, and neither proves the label causes the drop.
Art is what players see first, and it shows up more in the flops. Among AI-disclosed games, 72% of flops mention AI art against 57% of successes. In October's Next Fest, 2 of the top 25 demos disclosed AI, against 35% of demos ranked 101 and below.
Haro, November 2026Haro, July 2026Zukowski on Next Fest
The few wins make a weird answer the fun. Infinite Craft caches every combination, so repeats cost nothing. Death by AI reports 20 million players in three months, a figure from the vendor that sells its AI. Story games built on open chat NPCs mostly land at Mixed, with Suck Up! at 62% and Vaudeville at 47%.
Hosted platforms can take your game with them. Gambo AI shut down in May 2026, and only exported games survived. Rec Room closed on June 1. Research firm Sacra says one Maker AI user cost more than a Plus subscriber's net revenue, while Rec Room blamed the VR market and wider gaming headwinds.
Every revenue number for a single AI-built game comes from its creator or a vendor, and none has been checked independently. Pieter Levels posted that fly.pieter.com hit "$1M ARR in 17 days," an annualized run rate from a strong launch month. His own projects page, updated November 3, 2026, files it under "Okay: Took off, Made money but not sustainable."
The typical result is far smaller. One builder ran a one-person Claude Code "studio" with 15 subagents, shipped 7 Android games in two months and earned 152 yen in ads over 30 days, about one US dollar. Infinite Night passed Steam review in April and shows no user reviews as of November 5.
Levels' projects pageThe seven-game write-upRec Room report (IBTimes)
Next Fest's top 25 demos had a median of 5,519 followers before the fest. Rank 101 and below had 15. The seven-game builder wrote that "the department setup did nothing for getting found."
The Vibe Jam winner playtested constantly. The seven-game studio checked nothing for fun until it added a critic agent.
Instant play, no login, low-poly looks. Flops chased ARPGs and MMOs or shipped raw AI art.
Winners brought years of app or engine work. Emilio Coppola of the Godot Foundation told Kotaku that "coding is rarely the roadblock in making a successful game."
A game for your family skips store politics and review penalties. Keep AI at build time and out of runtime chat. Wholesome and Cozy are Steam's least AI-heavy tags (6% and 10%), which hints that this audience prefers handmade work.
Local Co-Op is another low-AI tag at 11%. If an AI judges the game, cache its answers or run it locally so game night has no cloud bill. Ikemen GO is a free fighting game engine for a home arcade cabinet.
Pixel Graphics sits at 12% AI. Godot APKs sideload to Android handhelds, and GB Studio makes real Game Boy ROMs.
Ludum Dare and Global Game Jam allow AI tools, and Vibe Jam requires them. Most itch.io jam series now ban AI assets. In 11 recurring series, 94% of 2026 entries ran under a ban.
Lambe's $660M estimateHaro, Part 2Review penalty study (PC Gamer)
GDC's 2026 survey found 52% of industry respondents think gen AI harms the industry, up from 30% in 2025 and 18% in 2024. GameDiscoverCo asked about 3,800 players and found 43% fine with AI, 31% negative and 8% who would never buy, and 56% want coding tools disclosed too. Quantic Foundry found 85% of 1,799 gamers below neutral on gen AI in games. The surveys ask different questions. Sales data shows a real penalty and no boycott.
The r/aigamedev snapshot is one day of one subreddit, read through a mirror because Reddit blocks automated reads. It counts posts that mention a tool. Shipped games are a separate question. It also puts Codex second for 2026, ahead of Cursor.
Lovable, Replit, Windsurf, Copilot and Bolt each have a prototype or two on record, such as a father and son's Minecraft-themed learning game made with Copilot. No paid commercial release turned up for any of them.
In GDC's 2026 survey of 2,300+ industry people, 36% use gen AI at work and ChatGPT led the tool list at 74%. Code help was a use for 47% of those AI users, roughly 17% of everyone asked. Unity's 2026 report says 62% use AI for coding help, but it surveyed Unity users. Cursor was Vibe Jam 2026's title sponsor, so the jam's tool advice comes with a sponsor attached.
GDC 2026 surveyCapybara winner write-up (36Kr)fly.pieter.com
godot --doctool dumps the installed engine's API for the agent to read. Headless mode always uses a dummy renderer, so screenshots and movies need a separate run with rendering on, for example --write-movie in a normal run..gd.uid files. Put them in every agent's allowlist, or its changes can get stuck.40LOADOUT · November 2026Special Report
Two AI teams swept GitHub for free game tools on their own. Then each one reviewed the other's work. They agreed on the spine and split on emphasis. Codex built a smaller, tested release kit. Claude built a wider map with the agent layer, licenses and design rules. Put together, they cover each other's blind spots.
Use Claude's day-one kit to build, and Codex's release checks to ship. Then add one habit from Codex: before you trust any test, break the build on purpose and make sure the test fails.
Claude's sweep was thin on what breaks at launch. Codex filled it: glTF-Validator for every 3D build, Ajv with versioned example saves, scrcpy to record and drive an Android handheld from the PC, and an NVDA plus contrast pass on menus. Codex ran the save and glTF proofs.
Codex built a real 32 KB ROM and drove it with PyBoy, a Python-scriptable emulator, getting the same screens twice. That beats the GB Studio plus mGBA route for agent work. GB Studio stays as the visual route, mGBA for Game Boy Advance.
Its license file allows commercial use, so it's legally free. But since version 6.5 the authors ask commercial users to buy a license. Claude's team marked it plain free. Codex called the purchase terms binding, which goes too far the other way. Now: free with a catch.
In one of Codex's cases, a sound effect matched its spectral reference and still sounded wrong. So earshot becomes a helper, never the judge, and every audio file gets a human listen on the target speaker.
In another, Codex planted defects and a visual critic still missed one in the screenshot it cited. Add Claude's finding that Godot can exit "success" on a broken script, and the rule is: a test counts only after it has failed on a build you broke on purpose.
One Claude Code browser game in Codex's notes: 664 plays, 1.85% desktop and 1.23% mobile next-day return, a 14 MB first load and a portrait-mode blocker. Now every web build gets measured on first load, first action and first-minute drop-off.
Codex's loadout had no agent bridges, docs for agents or screenshot loop. The benchmarks say they matter: visual feedback took one model from 41% to 52% of game tasks solved. Codex is right that file edits and the command line do most of the work, so bridges stay helpers, not the foundation.
Codex picks GUT. Claude picks gdUnit4 for its scene runner, which fakes input and steps frames. Neither side has run either one. The honest next step is a one-hour bake-off on a real game, with Codex's game-level automation picks (Godot Stagehand, godot-e2e) in the same test.
Codex's loadout page listed Audacity as the only regular audio tool, though its own sweep had already named jsfxr, ZzFX, BeepBox and Furnace. Codex now brings the first three forward. For agent-made games the bigger win is sound and music as text: jsfxr and ZzFX arrays, BeepBox songs, MIDI. Correction after Codex's reply: the gap was in its shortlist, not its research.
Codex keeps AI generation outside the free baseline. Claude agrees it stays outside until tested, and disagrees that it should wait. Where they landed: one trial at a time, on a real asset task, compared with the current way.
Codex's design advice (keep the editable master, export one real asset) is right and not enough. The usual complaints about AI-made visuals are about defaults, packs and averaged output. The seven fixes on the CROSSCHECK pages go after exactly those.
Several of Codex's "try next" picks are days old or unused: Godot Stagehand has 9 stars, godot-e2e has 20, and saveweaver and Tickwise have none. The first two stay as trials. The 0-star ones wait until they have users.
"Code is no longer what stops people" went too far. Prototypes are faster; architecture, feel and platform work still stall games. "Every project" add-ons became "when it solves a named problem." Local AI gets adopted one job per game. The Godot screenshot wording was wrong: headless always uses a dummy renderer, whatever the GPU. All fixed.
Codex couldn't open the source for the 50.9% Steam figure. Claude re-checked it: Sulka Haro's post of November 4, 2026 counts 1,982 of 3,897 new games with the AI disclosure. The number stays.
Codex now backs testing Godot AI plus gdUnit4 on one real gameplay bug, keeps GUT for plain logic tests, moves Effekseer up first among the design tools, and wants its second sweep's release checks in the working kit. With that sweep added, 151 of its 315 repos are in the field guide.
Codex's reply closed the last gaps. Runtime feedback is now standard on every game, and the bridge stays a trial. The art direction sheet and feel spec join its export checks. Low-adoption repos stay out of defaults, though an isolated test is fine if a game needs one.
48LOADOUT · November 2026Head to Head
Previews from my own desk: three games I made with AI coding agents and free tools like the ones in this issue. Two of them you can play right now, free, in your browser.
"A birthday game became a living storybook."
How it grew: one offline browser file became a native Godot adventure
Read. Commit. Ruin.
A two-player mind-game fighter. Both players secretly pick one of six moves (strike, throw, guard, feint, charge, overdrive), then reveal.
Unofficial, non-commercial parody. Not affiliated with any game company.
Strike beats grab. Grab beats guard. Guard beats strike.
A rock-paper-scissors fighter in red on black. Strike beats grab, grab beats guard, guard beats strike, and both players lock in at the same moment.
Unofficial, non-commercial parody. Not affiliated with any game company.
54LOADOUT · November 2026Made With the Kit
Games drawn in letters.
Text art has been a game look since the first terminals. This department collects tools that make it move: animated pieces, drawing kits and engines that run on letters. Each entry is one we ran ourselves.
734 moving pictures made of letters. Free, and free to sell.
A campfire, a maze builder, a snake, a bat cave at dusk. Each piece is a small animation drawn with text characters, with color. Use one as a web component, or import it and draw it where you like. A small kit in the box (grid, shading, noise, palettes, 3D helpers) lets you draw your own.
runtime/, lib/ and only the pieces you use from your own site.
Hand it to your AI
Add ASCII Magic Art from https://github.com/kailashsr38/ascii-magic-art to my game. Install the package and pin the version. Serve runtime/, lib/ and only the pieces I use from my own site. Do not load anything from ascii-magic.com.
More entries coming as we test them.
56LOADOUT · November 2026ASCII
Every used game store has a back room. Ours is where the tools live.
We built eight small tools while making our games with AI. They fix boring problems: which test is out of date, who wins too often, which sound was the good one. They're free on GitHub under Apache 2.0, so use them in games you sell too.
Most run from the command line, and we tested them on Windows. Bring patience and your AI.
Does going first win too often? Find out before game night does.
Kids notice when a game is rigged. Usually after the fourth loss in a row.
Write your rules as a small JavaScript file. First Player Problem plays thousands of seeded bot games and gives each seat's win rate with an honest margin of error. Then turn a dial, like a head start for the second player, and see what changes.
First Player Problem Comet Race | seed 7 | Wilson 95%
custom | 1000 games | 3.8 min median / 5 p90 | cap hits 0
Seat 1 big 60.6% (57.5% to 63.6%) | Seat 2 big 39.4% (36.4% to 42.5%)
First Player Problem sweep Comet Race | 3 cases | cap hits 0 | Wilson 95%
Case 1 {"finish":12,"secondSeatBoost":0} | cap hits 0 | baseline
Case 2 {"finish":12,"secondSeatBoost":1} | cap hits 0
custom | Seat 1 big 60.6% to 51.8% (real change) | Seat 2 big 39.4% to 48.2% (real change)
Case 3 {"finish":12,"secondSeatBoost":2} | cap hits 0
custom | Seat 1 big 60.6% to 43.6% (real change) | Seat 2 big 39.4% to 56.4% (real change)Hand it to your AI
Set up First Player Problem from https://github.com/thebeefasaurusrex/first-player-problem for my game. Follow its README and run its tests first.
Make the same "boing" twice.
Generated sound effects are great until you can't get the good one back.
Write each sound as a recipe with a seed. Same recipe, same WAV, byte for byte. ChirpSmith checks for clipping, loudness and dead air.
The v0.4.0 workbench keeps the waveform and 3D frequency terrain in view as you scroll the take rack. Switch games in one tab, scrub the waveform or use Show on scope to inspect a take without playing it. Wider cards give your notes four full-width lines. Keep, Redo and notes save with each sound set.
Hand it to your AI
Set up ChirpSmith from https://github.com/thebeefasaurusrex/chirp-smith for my game. Follow its README and run its tests first.
A screenshot that says where the bug is.
"It broke" is not a bug report. "It broke here, on this build" is.
One button frames the game screen like a postcard: the build, where you are in the game, the date and a short report code. The player saves it and sends it if they want to. Nothing uploads on its own. Works in the browser and in Godot.
Hand it to your AI
Set up PausePostcard from https://github.com/thebeefasaurusrex/pause-postcard for my game. Follow its README and run its tests first.
Your tests passed. On which code?
An AI will happily tell you the tests passed. It won't always mention that was before it changed three files.
RunReceipt wraps the Godot checks you already have and saves a receipt tied to the exact source it tested. Change a file and the old receipt goes stale, loudly. You get a short summary instead of a wall of log.
PASS pass | 1/1 checks Stamp 5e9d2ee95d4f | Godot 4.7.2.stable.official.ed1daf0bf | headless/gl_compatibility STALE pass | evidence missing, changed or unavailable
Hand it to your AI
Set up RunReceipt from https://github.com/thebeefasaurusrex/run-receipt for my game. Follow its README and run its tests first.
Where is that function called from? Ask once.
Godot projects scatter logic across scenes and scripts. You, or your AI, end up searching the whole folder again and again.
SceneSift indexes your GDScript, scene files and JavaScript, then answers "where is this defined, and who calls it?" It keeps the index and only rereads files that changed.
Builder.make | 1 definitions | 1 call sites | 0 other references DEF complex.gd:18-27 | Builder.make | static func make( scene: PackedScene, label: String = "not: the end" ) -> Node: CALL complex.gd:30 | begin
Hand it to your AI
Set up SceneSift from https://github.com/thebeefasaurusrex/scene-sift for my game. Follow its README and run its tests first.
Where did all the tokens go?
AI coding sessions charge you to reread the same files over and over. You don't see it until the bill.
Point Token Taxman at Codex or Claude Code session logs on your own computer. It estimates the weighted token cost and counts repeated work, like reading a file again or running a command twice. No uploads, no network.
> token-taxman codex examples/codex.jsonl codex | 53 weighted tokens | 2 turns | 1 transcripts Input 50 | cached 30 | recorded output 6 Repeated file reads: 2 Repeated commands: none read/search | 100.0% estimated reread share | 2 calls
Hand it to your AI
Set up Token Taxman from https://github.com/thebeefasaurusrex/token-taxman for my game. Follow its README and run its tests first.
Test your Game Boy game on two emulators with one script.
A homebrew cart can behave on one emulator and act weird on another.
Write a tiny script: wait 60 frames, press A, expect this byte to be 1. PocketParity runs the same script on PyBoy and on Mesen, then saves the numbers, screenshots and a contact sheet.
PyBoy contact sheet: the example cart at start, after a move and at the phase flip. The same script runs on Mesen to compare.
Hand it to your AI
Set up PocketParity from https://github.com/thebeefasaurusrex/pocket-parity for my game. Follow its README and run its tests first.
Catch black screens, frozen frames and missing-texture pink before a player does.
Nobody watches every screenshot from an overnight test run.
A quick scanner flags frames that are almost flat, an exact repeat of the last one, or full of that bright missing-texture magenta. A scorer grades any detector you bring, AI or not, against frames you labeled yourself.
Four demo frames: one normal frame that passes, then the three bugs it catches. Frozen, flat black and missing-texture magenta.
Hand it to your AI
Set up Pixel Tripwire from https://github.com/thebeefasaurusrex/pixel-tripwire for my game. Follow its README and run its tests first.
58LOADOUT · November 2026The Back Room
Your AI can read this whole issue. Hand it the brief at the start of a project, or point it at the data files. No sign-up, no email, nothing to mail.
The brief. Every kit, the rules, the I-want-to list and the 351 tools worth knowing, in one Markdown file. Start here.
All 653 tools: job, role, kinds of game, license, fun and sell status with notes, and the design verdicts.
The 12 kits, the every-game kit and the 72 quick answers, with both license modes on every item.
All 653 tools as a spreadsheet.
A short index for AI agents that read the site on their own.
60LOADOUT · November 2026Take It To Your AI
Two AI teams did the digging. Claude and Codex each swept GitHub for free game-making tools, then reviewed each other's picks and argued it out. I went through it all and signed off on November 5, 2026.
Every tool here was free to use when we checked. Licenses change, so check the project's own page before you rely on one, especially if you might sell your game.
The design calls in CROSSCHECK come from two judges reading evidence boards, not from running every tool. Audio tools were judged without listening, so every audio verdict stays provisional until someone hears the output.