Theme: Runner
Rules and mechanic description below.
Welcome to the Core Mechanics Challenge!
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!
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!
Previous jam: https://itch.io/jam/classics (link like this for legacy purposes)
Recently created discord room: https://discord.gg/F25RK4jG 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).
Theme RUNNER
Main Mechanic Description:
Player controls "forever" running game character and tries to avoid upcoming obstacles to get to the objective or as far as possible!
Examples of a runner games could be Subway Surfers or Google T-Rex (the one that you play on Chrome browser when no internet :) )
Note that game can be 2D, 3D, side-scroller, top-down view etc. There is no limitation.
Core Mechanics:
- Player character automatically moves forward.
- Player must take action to avoid an upcoming obstacles
Optional Features:
- (Easy) Game speed must dynamically change depending on environment. Like level progression, terrain, power-ups etc.
- (Easy) Game must have different environments with different obstacles. It can be levels, terrains, day-night cycle.
- (Medium) Implement scoring/goal system. It may be time alive or steps count or distance traveled, obstacles avoided etc.. It may be boring just to run forever!
- (Medium) Game must have collectables. It can be simple items increasing your score, buffs, speed modifiers etc. "Obstacle" that player should try to grab and not avoid.
- (Advanced) Scoring system must be meaningful, completing the "game loop".
For example:- There can be a score board and player might replay to have higher score.
- Or player could collect points to upgrade himself and make further game-play easier. (rogue-like)
- Or player can be rated on his score that would unlock extra levels, abilities, features, mods etc.
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 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
- Code style: 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. Is solution "clean", fast, modular, reusable can be build upon? How easy it would be for you to change/work with this code or use it somewhere else?
- Git and development history. How good and understandable commit messages are? Can you see the "flow" of a project?
- The GAME. How good it is in general? Art, sound, game play, uniqueness etc.
Manually ranked by judges:
- Is it a game? One star for each point:
- consistent art: 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 whole game. (this is to prevent people from dropping random assets just for a checkbox)
- consistent sound: same as with art, (should not mix good quality professional sounds with random bad mic ones for example)
- can be played, has win and/or loose conditions: as it makes sense for a current theme. You should be able to start the game, play it and finish it (by winning or loosing).
- has UI/UX: menus, start/end screens, score 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.
- Optional features (as described in mechanics section)
Submissions(5)
No submissions match your filter
