Catholic Game Jam
7 days. Infinite grace. One epic quest to make games for the glory of God.
The Quest
Insert coin. Press start. Make something holy.
Level Up Together
Pro tip: you don't have to start from zero. Templates, asset packs, open-source engines—use whatever helps you ship. Or go full hardcore mode and build from scratch. Your call, your quest.
Either way, your creation joins the commons. The next jammer can build on your work. Together, we're growing the body of Catholic games—one jam at a time.
Game Stats
When
February 7, 2026
6:00 PM CST
↓
February 14, 2026
6:00 PM CST
One week quest!
Theme
Make it unmistakably Catholic.
Saints, sacraments, scripture, miracles—2,000 years of epic material awaits.
Party Size
Go solo or assemble your guild.
Lone wolves and raid parties both welcome.
Loadout
Bring whatever weapons you've got.
Any engine, any language. Just respect the licenses.
The New Evangelization
"Do not be afraid to go out on the streets and into public places like the first apostles who preached Christ and the Good News of salvation in the squares of cities, towns, and villages." — St. John Paul II
This jam is part of the New Evangelization—the Church's call to proclaim the Gospel through modern means. Games are one of the most engaging media of our time. By creating games rooted in Catholic faith, we meet people where they are and plant seeds that can grow into something eternal.
Every game you build becomes a tool for evangelization. Every asset you share helps the next creator. Together, we're building a commons of Catholic games that will outlast any of us.
St. John Paul II (1920–2005) The Commandments
- 1 Thou shalt use only free/open-source assets
All assets (art, music, code, fonts) must be free and MIT-compatible so others can fork your game and build sequels. Sources like OpenGameArt, CC0/CC-BY content, and itch.io freebies are great. Paid asset packs are not allowed.
Prior work: You can use your own pre-existing code/assets, as long as they're MIT-licensed.
AI tools: Allowed if the generator grants you full rights to release output under MIT license.
OK: OpenGameArt sprites, Kenney assets, Google Fonts, your own pixel art, Suno AI music (check terms).
Not OK: Unity Asset Store purchases, stock photo subscriptions, ripped game sprites, fonts that say "personal use only." - 2 Thou shalt release under MIT license
Your entire project—code and assets—must be MIT-licensed so future jammers can build on your work freely. No GPL, no "non-commercial only," no restrictive licenses. Include a LICENSE file in your repo.
Why MIT? It's simple, permissive, and lets anyone use your work for anything—including commercial projects. The goal is growing a commons of Catholic games that anyone can build on.
OK: MIT, CC0, Unlicense, public domain.
Not OK: GPL (viral, forces same license), CC-BY-NC (no commercial), CC-BY-SA (share-alike), "All rights reserved," no license at all. - 3 Thou shalt keep it holy (T for Teen)
Content rating: T for Teen / PG-13. Fantasy violence, mild peril, and intensity are fine (think Zelda or strategy games). No gore, no sexual content, no profanity. Treat the faith with respect—humor and creative takes welcome, mockery of sacraments or Church teaching is not. AMDG.
OK: Defeating demons with a holy sword, a tense exorcism scene, martyrdom depicted respectfully, funny saints doing funny things.
Not OK: Graphic torture, crude jokes about the Eucharist, portraying priests as villains because they're priests, excessive blood/dismemberment. - 4 Thou shalt make it playable
Your game must be accessible without dev tools. Provide a web build, downloadable executable, or dead-simple install instructions. "Clone repo and run npm install" is fine; requiring Unity Editor is not.
Game definition: Anything interactive counts—traditional games, visual novels, interactive fiction, toys, sandboxes. If a player can engage with it, it qualifies.
OK: Web game on GitHub Pages, .exe/.app download, "run `npm start` and open localhost:3000", HTML file you double-click.
Not OK: "Open in Unity and press Play," raw Python script with 10 dependencies, "compile from source with special flags." - 5 Thou shalt host on GitHub with a README
Upload your project to GitHub with documentation: what the game is, how to play, how to run it, and credits for any assets used. This is how your work joins the commons.
README must include: Game title and description, how to play/controls, how to run it (link to play or install steps), credits listing all third-party assets with sources, and screenshots or a gameplay GIF.
Good README: "St. Michael's Quest - A roguelike where you battle demons. WASD to move, Space to attack. Play at [link] or run `npm start`. Music: 'Epic Battle' by ComposerName (OpenGameArt, CC0)."
Bad README: "my game" with no instructions, missing credits, or no way to actually play it. - 6 Thou shalt submit by the deadline
Judging is based on your repo state at jam end (Feb 14, 6PM CST). You can keep working after—the repo lives on—but judges score the deadline snapshot. Submit as many games as you want. No team size limits.
Late submissions: Accepted but scored with a penalty.
Rule violations: Disqualified from judging entirely.
How We Judge
Every game gets scored on four criteria. Top scores win glory.
Judges may submit games but recuse themselves from scoring their own entries. Results announced within one week of jam end.
Catholic Integration
Is the faith woven into gameplay, or just decoration? We're looking for games where Catholicism shapes the experience.
5: Mechanics based on sacraments, prayer as game system, theological choices matter.
3: Saints as characters, rosary as inventory, church setting.
1: Cross on the title screen, generic game with "Catholic" in the name.
Gameplay/Fun
Is it enjoyable to play? Clear goals, satisfying loop, makes you want to keep going.
5: "One more run" feeling, clear objectives, rewarding progression, tight controls.
3: Functional gameplay, some fun moments, a few rough edges.
1: Confusing goals, frustrating controls, nothing to do, or softlocked.
Polish/Completeness
Does it feel finished? No major bugs, clear instructions, playable from start to end.
5: Title screen, clear UI, sound effects, win/lose states, no bugs, feels complete.
3: Playable start to finish, some placeholder art or missing sounds, minor bugs.
1: Crashes, no end state, placeholder everything, clearly unfinished.
Documentation
Can the next jammer build on your work? Clear README, commented code, easy to understand and extend.
5: Great README with screenshots/GIF, code comments, clear file structure, easy to extend.
3: Basic README with instructions, code is readable but sparse comments, no visuals.
1: No README, cryptic variable names, impossible to understand or extend.
Awards
Join the Party
Ready, player? Lock in your spot and prepare for a week of caffeinated creativity.
Help Menu
Do I need to be Catholic to play?
Nope! All skill levels and faith backgrounds welcome. Just bring respect for the theme and a willingness to make something awesome.
Can I bring my own party?
Absolutely. Roll in with a full raid group or brave it solo. Both paths lead to glory.
Do I HAVE to use existing code?
Nope! Use a template if it helps you ship, or start from scratch if that's your style. Just remember: all assets must be free/open-source and MIT-compatible. No paid asset packs.
Can I use AI tools?
Yes—for code, art, music, whatever—as long as the AI generator grants you full rights to release the output under MIT license. Check your tool's terms of service.
How do I submit my game?
Host your project on GitHub with a README, then submit the link through our submission portal (opens when the jam starts). Include a playable build or dead-simple install instructions.
What's the prize?
Eternal glory. And the joy of contributing to the Catholic game commons. No cash prizes—just the satisfaction of a quest completed.
Can I use Unity/Godot/Unreal?
Yes. Engine licenses are separate from your game's license. Your code and assets must be MIT, but the engine itself can have its own terms.
Can I fork someone else's jam submission?
Absolutely—that's the whole point of MIT licensing. Build on others' work, give credit, and keep the chain going.
Can I submit the same game to other jams?
Yes. MIT means your game is free to use anywhere. Enter as many jams as you like.
How specific do credits need to be?
List what you used and where it came from. "Music: 'Epic Battle' by ComposerName from OpenGameArt (CC0)" is perfect. A simple credits section in your README works great.
Can I sell my game after the jam?
Yes! MIT license means you (and anyone else) can use the code commercially. Build a business, release on Steam, go wild. The commons grows either way.
Is there an age requirement?
You must be 13 or older to participate (COPPA compliance). Minors should have parental permission.
Can I stream my development?
Yes, and we encourage it! Stream on Twitch, post devlogs, share progress on social media. Tag us and use #CatholicGameJam. Building in public builds community.