“Everyone has great ideas. What makes great games is the people willing to bring their great ideas to life through hard work and dedication. Learn to code, learn to draw, learn to write compelling stories. Learn all of it. Do it. Don't tell yourself "Oh I'm not good at that". Nobody's born an artist, a coder, or a writer. You become one. Get on it.”

Theme

Rules

Allowed :

• Participate solo or with a team
• The reuse of code, previously made assets
• Use of any Game Engine ( Godot, Unity,Unreal, GameMaker, Pygame, etc..)

Useful (optional):

• Make sure you have a web version or at least a windows version of the game (keep in mind that by not providing a web build not all the participants will be able to play and rate your game)
• Follow the theme of the jam
• Make sure your game works when submitted

Important (mandatory)

• Only submissions for this jam are allowed
• Don’t submit already created games! Instead, create the game during the specified Jam period
• No late submissions are allowed. Be sure to check the itch.io's counter as this is the most accurate one
• Not allowed: discriminatory, offensive, or NSFW content or behaviors.

Voting

1. Technical - Does the game work? Does the game show off the engine? Does it do anything particularly impressive? Is it feature rich?
2. Artistic - Is it pretty? Are the sound and visuals effective and fitting? Is the style coherent to the gameplay? Are the text boxes legible?
3. Design - Does the game teach you how to play it? Do the mechanics make sense?
4. Gameplay - Is it fun? Does the difficulty scale? Are there accessibility options? Have I played the same game before or is it innovative?
5. Theme - Does the game fit the theme? Is it surface level or is the theme at the core of the game?

All participants and jam organizers can vote. 

Golden Rules of Rapid Game Development

1. Keep. It. Stupid. Simple.

Less is more. Reduce to your core concept. The simpler the game concept:

• The clearer the game rules
• The lesser effort towards implementation
• The earlier a prototype exists
• The quicker play testing can start
• The faster flaws are recognized and dealt with

2. Play to your strengths. 

Get to know your teammates intimately. What are their expertise, their specialties, their professional and gaming preferences? Which tools and development environments are people familiar with?

3. Paper Prototyping 

If at all possible for your concept: Do paper prototyping. It takes very little time and effort, and quickly shows issues in rules design and general Fun-ness of the game.

4. Align Vision 

Make sure that everyone is absolutely, unequivocally, completely aligned on ideas how the game will be in rules, art and mood and technical design. Reach consensus, document and review, before writing a single line of code! But again, keep it simple!

5. Choose your foundations wisely

Choose the best tools, libraries or development environment for the situation. Consider both familiarity in the team members and the type of game desired.

6. Task Distribution 

Define tasks clear and concise. Avoid any ambiguity whatsoever. Distribute these tasks wisely. Every team member needs to have a clear role in general and an impressive to-do list at any time. Organize this: Class diagrams, Art asset lists, Scrum, etc.

7. Early Play Testing

 Do your play testing as early as possible. Together with paper prototyping, this is extremely valuable in recognizing game flaws. Bonus points for involving an audience outside the team.

8. Version Control Use it. 

You'll thank me after that game breaking bug 10 minutes before the deadline. (Make sure everyone understands whatever version control system is used!)

9. Eat and Sleep 

Nobody likes a sleep/food deprived (or even sick!) zombie introducing more bugs than features. A shower might also help but is optional depending on circumstances.

10. Keep. It. Stupid. Simple.

 Repeated because it is That Important!