Get Involved

Kerkerkruip is an open source game developed by a small and growing community. There are many ways for you to get involved and help Kerkerkruip become a better game.

Being involved as a player

The simplest way to contribute to Kerkerkruip is simply to play the game and tell other people about your experiences. The game will certainly benefit from a large and active group of users! We are very interested in your ideas, which you could discuss on this website, on the Interactive Fiction forum, on the Temple of the Roguelike forum, or really wherever you want. If you post in a different place, you might consider dropping me a line (see contact details below.) Another crucial contribution are bug reports. If you come across something that seems amiss, please tell us about it. You can either e-mail us, or file a bug report on our Github website. We would also love to see more actual play videos appear on Youtube; and the Kerkerkruip wiki needs contributors too.

Being involved as a developer

We very much appreciate code contributions to the game, whether they be bug fixes or new features. Kerkerkruip has been written in the Inform 7 programming language, and published under the GPL version 3+. The source code is available on Github. In general, it will be a good idea to discuss your design concepts before you actually start implementing them. For that, please create new issues on the Github site, or discuss your ideas on the Interactive Fiction forum. Because the Kerkerkruip team is quite small, active contributors will quickly become part of the (informal) design team.

Another area where you can contribute is graphics. We need more monster cards, and other graphical additions might also benefit the game. Don’t hesitate to contact us if you think your graphical skills might benefit Kerkerkruip.

Finally, an area where programming talent would be very welcome is in the improvement and porting of the Glulx interpreters used by Kerkerkruip. We’d love to be able to publish good-looking Android and iOS version of the game, for instance; and there are outstanding problems with some of the existing interpreters (e.g., Gargoyle) that a technically-minded programmer might want to tackle.


For most purposes, the web sites mentioned above should suffice. But you can also e-mail me (Victor Gijsbers) at (Put my actual first name instead of “myfirstname”.)