Spellmerge

Merge spells. Cause chaos. Together. · Every spell is a merge request.

A 2D top-down roguelite about building deep, combinable spells, for 1–4 local co-op players. Build spells on your staffs from cards read left to right: infusions (what a spell is made of: fire, frost, void...), modifiers (how it behaves) and triggers (what happens next, holding another spell) change the carrier after them (what leaves the staff: a bolt, a beam, a dash, a pulse), and multicasts cast more at once; find relics that bend the rules, and fight through rooms with up to three friends on one screen, with nobody ever waiting for anybody.

Play: in the browser · today's nightly · latest preview (rebuilt after each merge) · Windows and Linux downloads

Status: milestone M2, the spell system. The infrastructure (M0) and the core loop prototype (M1) are in place; spell cards, the spell builder and the spell limits are being built. See the roadmap.

Built by an AI, in the open

Claude, an AI by Anthropic, writes the code and the assets and ships a new build every day, all on GitHub's servers. The owner (@peterdk31) sets the vision in docs/DESIGN.md and controls the protected infrastructure. Every AI change is made by the spellmerge-bot account, so it's always visible as such, and every bot action is listed in that day's Daily log issue (label daily-log).

Players shape the game: report a bug, share an idea, art or sound in Discussions, or send a pull request. Claude reads and answers every post within a day, schedules bugs, good ideas and good work, and finishes contributors' pull requests on top of their commits. See CONTRIBUTING.md.

Free on the web forever

The web version and the daily desktop builds stay free; the Steam version (later) funds development. No ads, no microtransactions.

License

Code: GPL-3.0-or-later. Assets: CC-BY-SA-4.0, unless a file says otherwise (see REUSE.toml). A copyright concern? Use the Report a copyright concern issue form; taking the asset out is scheduled first while it's checked. GitHub's DMCA process also applies.

For maintainers

• docs/PLAN.md: the full plan
• docs/NEXT.md: what Claude works on next
• docs/DECISIONS.md: why things are the way they are
• tools/check.sh: the hard rules on your local changes; ci/build/build.sh: a full local build