Difference between revisions of "The 7DRL Contest (Initial Manifest)"
(Added sucess of Martin Read) |
|||
| Line 1: | Line 1: | ||
What is a Seven Day Roguelike? | == What is a Seven Day Roguelike? == | ||
A Seven Day Roguelike is a roguelike created in seven days. This means | A Seven Day Roguelike is a roguelike created in seven days. This means the author stopped writing code one hundred and sixty eight hours after they started writing code. | ||
the author stopped writing code one hundred and sixty eight hours after | |||
they started writing code. | |||
Seven Day Roguelikes are, for roguelike authors, what 24 hour comics would be to comic authors. (cf. http://www.24hourcomics.com/) | |||
They are also for roguelike authors what the National November Writers Month is for novel writers. (cf. http://www.nanowrimo.org/) | |||
== Is this really the best way to make a great roguelike? == | |||
After | Probably not. However, the short time frame forces the developer to actually plan on finishing. Normal roguelike design is open ended. One will still be working on the same roguelike years after starting. This can become dispiriting, as one may have new ideas that cannot fit inside one's current game. A Seven Day Roguelike is a way to experiment with the genre without fearing creating another life-work. After seven days, one can wash one's hands of the roguelike. | ||
== Why Seven Days? Why not 24 Hours? == | |||
Comic authors are clearly harder core than us wimpy roguelike developers :> | |||
Programming isn't an activity that I'd recommend be done in 24 hour | |||
marathons. Sure, it can be fun. But you don't learn much out of it, | |||
except maybe that programming with little sleep makes unreadable code. | |||
== Why Seven Days? Why not one month? == | |||
Novel writers clearly have longer attention spans than us easily distracted roguelike developers :> | |||
== How do I do a Seven Day Roguelike? == | |||
Choose a week to work on the roguelike. Post to rec.games.roguelike.development that you have started. After seven days passes, post to rec.games.roguelike.announce your successful creation. Or, you can beg for more time in rec.games.roguelike.development :> (You don't have to announce starting, of course.) | |||
rec.games.roguelike.development that you have started | |||
Note that while a 7DRL could be written at any time, the denziens of rec.games.roguelike.development may on occasion organize a specific week for people to accept the challenge in. 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. | |||
The first such Seven Day Roguelike Challenge will be held March 5th to March 13th 2005. | |||
== My roguelike took 10 days, but is really playable! Does it count? == | |||
It counts as a Ten Day Roguelike. :> | |||
< | == Can I use external libraries? Graphics files? Design Documents? | ||
"Done it. There's a load/save bug that's probably down to my imperfect | Code I wrote in the past? Existing roguelikes? == | ||
understanding of Berkeley random()'s operation, but I don't care; the | |||
game is playable | This is entirely up to the developer. | ||
It is recommended one has some design idea going into the project. | |||
You should say what pre-existing code you used. The goal isn't to see who can retype existing algorithms the fastest. The goal is for people to write playable and complete roguelikes. | |||
Remember: if you spend seven days patching Nethack, you likely will end up with something that looks a lot like Nethack, so thus not be considered very impressive. However, if you spend seven days patching Nethack and create an amazing new roguelike, you will be suitably honoured. | |||
== How do we judge the Winners? == | |||
The primary criterion is completeness. The resulting game should be complete and playable. The author is encouraged to not release another version. | |||
That being said, the only true judge of your "Winnerness" is yourself. | |||
== My friend and I want to work on a Seven Day Roguelike together... == | |||
Sure! This is definitely a Seven Day Roguelike. Keep in mind that your seven days occur in parallel. Also remmeber that adding more manpower to a late software project only makes it later... | |||
== What about licensing? == | |||
Clearly, the compiled roguelike itself must actually be released. No good claiming you have it, but won't release it :> | |||
Source code does not have to be released, but it is strongly encouraged that you release it. Heck, release it public domain! It was only seven days work, after all. (Of course, if you patched existing code, follow its licensing agreement...) | |||
== How many Seven Day Roguelikes have been done? == | |||
Two so far, but we are hoping the number will grow. The following is the list of certified Seven Day Roguelikes (7DRLs): | |||
<h1> [[Dungeon Monkey]] </h1> | |||
The first | |||
Link: http://www.geocities.com/pyrrho12/programming/monkey/index.html. | |||
Of course, it was done before anyone invented this categorization, so is retconned as a Seven Day Roguelike. | |||
<h1> [[MPR7DRL]] </h1> | |||
Martin Read, on January 30th, 2005: | |||
"Done it. There's a load/save bug that's probably down to my imperfect understanding of Berkeley random()'s operation, but I don't care; the game is playable | |||
http://www.chiark.greenend.org.uk/~mpread/mpr7drl.tar.gz | http://www.chiark.greenend.org.uk/~mpread/mpr7drl.tar.gz | ||
Revision as of 05:55, 2 February 2005
What is a Seven Day Roguelike?
A Seven Day Roguelike is a roguelike created in seven days. This means the author stopped writing code one hundred and sixty eight hours after they started writing code.
Seven Day Roguelikes are, for roguelike authors, what 24 hour comics would be to comic authors. (cf. http://www.24hourcomics.com/)
They are also for roguelike authors what the National November Writers Month is for novel writers. (cf. http://www.nanowrimo.org/)
Is this really the best way to make a great roguelike?
Probably not. However, the short time frame forces the developer to actually plan on finishing. Normal roguelike design is open ended. One will still be working on the same roguelike years after starting. This can become dispiriting, as one may have new ideas that cannot fit inside one's current game. A Seven Day Roguelike is a way to experiment with the genre without fearing creating another life-work. After seven days, one can wash one's hands of the roguelike.
Why Seven Days? Why not 24 Hours?
Comic authors are clearly harder core than us wimpy roguelike developers :>
Programming isn't an activity that I'd recommend be done in 24 hour marathons. Sure, it can be fun. But you don't learn much out of it, except maybe that programming with little sleep makes unreadable code.
Why Seven Days? Why not one month?
Novel writers clearly have longer attention spans than us easily distracted roguelike developers :>
How do I do a Seven Day Roguelike?
Choose a week to work on the roguelike. Post to rec.games.roguelike.development that you have started. After seven days passes, post to rec.games.roguelike.announce your successful creation. Or, you can beg for more time in rec.games.roguelike.development :> (You don't have to announce starting, of course.)
Note that while a 7DRL could be written at any time, the denziens of rec.games.roguelike.development may on occasion organize a specific week for people to accept the challenge in. 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.
The first such Seven Day Roguelike Challenge will be held March 5th to March 13th 2005.
My roguelike took 10 days, but is really playable! Does it count?
It counts as a Ten Day Roguelike. :>
== Can I use external libraries? Graphics files? Design Documents? Code I wrote in the past? Existing roguelikes? ==
This is entirely up to the developer.
It is recommended one has some design idea going into the project.
You should say what pre-existing code you used. The goal isn't to see who can retype existing algorithms the fastest. The goal is for people to write playable and complete roguelikes.
Remember: if you spend seven days patching Nethack, you likely will end up with something that looks a lot like Nethack, so thus not be considered very impressive. However, if you spend seven days patching Nethack and create an amazing new roguelike, you will be suitably honoured.
How do we judge the Winners?
The primary criterion is completeness. The resulting game should be complete and playable. The author is encouraged to not release another version.
That being said, the only true judge of your "Winnerness" is yourself.
My friend and I want to work on a Seven Day Roguelike together...
Sure! This is definitely a Seven Day Roguelike. Keep in mind that your seven days occur in parallel. Also remmeber that adding more manpower to a late software project only makes it later...
What about licensing?
Clearly, the compiled roguelike itself must actually be released. No good claiming you have it, but won't release it :>
Source code does not have to be released, but it is strongly encouraged that you release it. Heck, release it public domain! It was only seven days work, after all. (Of course, if you patched existing code, follow its licensing agreement...)
How many Seven Day Roguelikes have been done?
Two so far, but we are hoping the number will grow. The following is the list of certified Seven Day Roguelikes (7DRLs):
Dungeon Monkey
The first
Link: http://www.geocities.com/pyrrho12/programming/monkey/index.html.
Of course, it was done before anyone invented this categorization, so is retconned as a Seven Day Roguelike.
MPR7DRL
Martin Read, on January 30th, 2005:
"Done it. There's a load/save bug that's probably down to my imperfect understanding of Berkeley random()'s operation, but I don't care; the game is playable
http://www.chiark.greenend.org.uk/~mpread/mpr7drl.tar.gz
Disclaimer: Source code distro, not expected to work on things that aren't Linux. "