Difference between revisions of "The Annual Roguelike Release Party"
m (Make FAQs subheadings and remove top heading.) |
m (→Event list) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 23: | Line 23: | ||
== Event list == | == Event list == | ||
* [[2017 ARRP]] | |||
* [[2016 ARRP]] | * [[2016 ARRP]] | ||
* [[2015 ARRP]] | * [[2015 ARRP]] | ||
Latest revision as of 20:30, 13 September 2017
Too many roguelikes can languish with half-fixed features. If we can, once a year, ensure our roguelikes are polished and updated, we can avoid this trap.
All active roguelike developers are encouraged to release an update to their roguelikes on the appropriate date in September.
A simultaneous release will:
- provide moral support as we struggle with resurrecting code we left in an untenable state three months earlier
- encourage developers to release at least yearly through the wonders of deadlines
- celebrate the size and vibrancy of our community
FAQ
Why September?
The ARRP date is set for the first Sunday that is over 6 months after the 7DRL Challenge deadline.
Do I need to register/announce before the event?
Nope. While announcing your game before the date might put the pressure you need to get motivation, nothing keeps you from releasing out of the dark without any preliminary announce.
Can I release a game that has already been released?
Of course. The annual roguelike release party is about increasing the amount of roguelikes and improving the overall quality. You're strongly encouraged to upgrade your existing roguelikes at this occasion.
Are there any requirements to participate?
Nope. Any release is worth on ARRP day. An early walking @ prototype (if you follow release early and often philosophy), a small patch to your already released game, a new major version or your 10 years old genroguelike. The point is to give you a motivation boost with a hard deadline and more exposition by joining a big, annual event.