Create a traditional roguelike in two weeks!

A traditional roguelike?

For this jam it is specifically desired to create games that retain some attributes from the first generation of roguelikes, working within their boundaries to experiment with new gameplay mechanics or thematic adaptations.

You are challenged to create a game that features gameplay that is:

Turn-based, focusing on strategic thinking over quick reflexes.

Run-based, with no meta-progression (the player loses all tangible progress after each run).

Subject to  permanent consequences (the player cannot freely roll back mistakes).

Impacted by Procedural Content Generation in a meaningful way.

Focused on the development of A character, or a party of characters (no abstract puzzle or "god" games).

This is a list of arbitrary design choices that were picked for this jam, and by no means an effort to define what a roguelike is.  The values described above are not black or white; innovative gameplay ideas may lie in a grey areas and they are welcome as they can be useful to create fun games, which is the ultimate goal. If in doubt about your ideas, feel free to discuss in the community.

Why "traditional" roguelikes?

The last fifteen years have seen the roguelike word evolve to encompass a wide variety of games; while it is impossible to stop its adoption to describe games that took some elements from the original roguelikes, (or even from a second, or third generation of roguelike-inspired games), there is value on preserving the knowledge of the original roguelike gameplay and keep it alive in the minds of players and designers, and there is no better way to do this than toying around with new game ideas. 

There is still a lot of uncovered potential on this formula that is worth exploring.

The Rules

1. Your entry should be a traditional roguelike, as described in the section above
2. You can work in teams.
3. You can work in the design for your project before the jam starts, provided you don't extend your work to create actual content that will be added to the game (i.e detailed list of enemies, spells, items, etc).
   
4. You can use pre-existing code and assets for the game, provided they could be used for other projects.
5. Content that is specific to your game, including assets, code, and data, should be developed within the time frame of the jam.
6. You can develop post-jam versions of the game, provided you keep a link to the original version
7. You must add screenshots to your entry page.

FAQ

• Why two weeks? Seven days should be enough

Completing a game in 7 days is a great exercise on product management, however it may not be enough time to fully develop and polish an interesting gameplay idea at a healthy pace of work.