Welcome to the Core Mechanics Challenge!

Can you replicate well known games or game mechanics? How well?

This game jam is perfect for everyone—whether you’re a beginner learning to code and make games, or an experienced developer seeking a fun challenge!

It’s a great opportunity to learn programming, explore a new engine, build your portfolio, and finish with a complete, playable game.

For seasoned developers, it’s a chance to showcase your expertise or refresh skills that may need a little polishing!

Previous jam: https://itch.io/jam/core-mechanics-challenge-2025-summer

TASK (Theme): BOMBERMAN

Difficulty: Medium

Old school game where the player controls the character that can place bombs, and they explode after a set amount of time. Goal is to escape while destroying obstacles and enemies.

https://en.wikipedia.org/wiki/Bomberman

Core mechanic:

• Player controls character movements
• Character can place bombs
• Bombs explode, effecting surrounding environment

Optional features:

• Bomb modifiers (x1): There should be acquirable bomb modifier. For example, higher explosion radius, bomb can be pickable, explosion can be triggered by player etc.
• Player modifiers (x1): There should be acquirable player modifiers. For example, player speed increased, double jump, could place more bombs etc.
• Smart opponent (x5): Add an opponent to your game. Best option is to have a player controlled opponent (second player using other inputs), or good enough AI.
• More levels (x3): Game must have more than one playable level. When a player finishes one, he gets to play another one, or it can be picked beforehand (it must be unlocked first).

About This Jam

The time needed to complete the jam depends on your skill level: 1–2 days for a pro and 8–12 hours for a beginner (joking .. kinda ^_^ ). If you finish early, use the extra time to refine your code, enhance visuals, add features like controller support or multiplayer, and make your game unique to stand out.

This jam is designed to mimic a real development cycle, complete with evolving requirements and code reviews, giving you the experience of delivering a "polished", finished game.

Best game and code may get prizes! (will be announced if any sponsors)

Previous jam: 
https://itch.io/jam/core-mechanics-challenge-2025-summer (Task: IDLE)
https://itch.io/jam/core-mechanics-challenge (Task: RUNNER)

Discord: https://discord.gg/6uxk2A3KD3 (Still figuring it out). Can join and ask any questions about Jam, Rules, ask for advice, share your progress etc.

How It Works

At the start of the jam, you’ll be provided with a well-known game and a detailed description of its core mechanic. Your task is to implement it in a way that is flexible, reusable, and extendable, while documenting your progress using a version control system like Git.

Midway through the jam, new requirements may be introduced, challenging you to adapt and refine your solution (code) to meet the updated criteria.

After submissions close, you’ll evaluate other participants’ entries. Judging will focus on code quality, playability, and any unique twists they’ve added to the base mechanics (more details below).

What you will need

To participate, you will need:

• git: public git hosting service, especially https://github.com/ is highly recommended!
• Godot engine: latest godot engine. You can get it from https://godotengine.org/ (You can use Unity or other engines that allow code git history, but note, that not all participants may check and rate your submission)
• Assets pack: you can create your own or use any you have rights to. I recommend Kenney's https://kenney.nl/assets/minimap-pack or https://kenney.nl/assets/pico-8-platformer or any other that fits your idea.

Rules

MUST

• All code must be developed during the jam! (try not to use code assets that can be core mechanic related, assets for UI or networking can be fine)
• Project source must be publicly accessible and represent submitted game state!
• Reused assets must be credited and comply with licensing.

SHOULD

Source code should be publicly hosted on GitHub. While GitHub is preferred for its popularity and ease of access for judges, repositories hosted on other public Git platforms (e.g., GitLab, Bitbucket) are also allowed. Alternatively, participants can upload their source code along with the full `.git` folder to preserve version history. Please note that GitHub is recommended for smoother judging and community interaction.

AI tools and tutorials are allowed, but you must understand and adapt the solutions you use.

Judging Criteria

(subject to change depending on community likes, theme etc.)

• Code style (3x): How "pretty" the code is for you? Is it the same across whole code project (same code style)? How readable and understandable it is to you?
• Solution and game architecture (3x). Is the solution "clean", fast, modular, reusable can be built upon? How easy it would be for you to change/work with this code or use it somewhere else?
• Git and development history (1x). How good and understandable commit messages are? Can you see the "flow" of a project?
• The GAME (1x). How good it is in general? Art, sound, game play, uniqueness etc. Has something extra: a nice twist, extended mechanics, levels, extra art and graphics, controller support, multiplayer etc. Anything that expands on initial game jam requirements.
• consistent art (1x): art is same style across whole game and "fits" (no mixing of photo realistic assets with pixel art and ASCII). For example, if the game is done as ASCII then it uses it across the whole game. (this is to prevent people from dropping random assets just for a checkbox)
• consistent sound (1x): same as with art, (should not mix good quality professional sounds with random bad mic ones for example)
• has UI/UX (1x): menus, start/end screens, score etc.