Seven Day Roguelike Challenge
History and Rationale
In 2005, the roguelike community established a yearly event, the 7DRL Challenge, in which all the world is challenged to create a roguelike in a one-week span. This allows one to have the shared misery of knowing you are not the only one tracking down a bad pointer at the 167th hour. As a suggested schema for proposing the challenge the 7DRL Voting Specification has been created.
The annual event occurs during a week in late February or early March. There is a chance that some other challenges may arise out of schedule, thus allowing more than one challenge per year.
7DRL Challenges are NOT about being a fast coder, but rather proving you can release a finished, playable roguelike to the world. There is no winner of the challenge, but rather all those who finish are honoured for their work, the criterion is completeness.
- You CAN use external libraries, game engines, pre-existing generic code/algorithms, pre-existing generic art, etc. You can even start your game from an existing game, if you are willing to turn it out into something unique, you must however say what resources were reused.
- It is allowed and recommended to have a rough design idea of your project before starting
How to participate
- After the initial date chosen for the challenge, post your starting development notice on rec.games.roguelike.development
- 168 or less hours after this initial post, post your results on rec.games.roguelike.development; if you were sucessful, post your announcement on rec.games.roguelike.announce
- The challenge is always Saturday to Sunday; if you start after Sunday you will have less than 168 hours as in-challenge 7DRLs must be completed by the closing time. You can still use 168 hours and have a normal, out of challenge, 7DRL, however
To the date, there have been five 7DRL challenges