Development

OpenClonk is an open project. That means it depends on people coming in and helping out. People just like you! This page should give you an idea what you could do in order to get involved.

Use Development Snapshots

OpenClonk is continously in development. The "current" version can change daily! If you want to follow the development, it is a good idea to make sure you are able to run development versions. You will not need to build them yourself - just use the development snapshots linked below and you should be ready to go.

• Development Snapshots - www.openclonk.org/snapshots/
• Blog - blog.openclonk.org
• Changelog - github.com/openclonk/openclonk/commits/master
• Browse source - github.com/openclonk/openclonk

Report Bugs

We cannot possibly account for every possible configuration out there. If you see something that's wrong, we would really like to know about it. Especially if you are willing to actively work with us in finding a solution for the problem.

Here's how you can reach us:

• IRC - #openclonk-dev on irc.euirc.net (Problems connecting? Use irc.ham.de.euirc.net)
• Bugtracker - bugs.openclonk.org
• Forum - forum.openclonk.org

Contribute Scripts or Game Content

Just like Clonk Rage before, most things in OpenClonk can be changed without touching the engine. Instead, we rely on a script language and a flexible game content system to make up our game content. This means that you can get involved easily - without having to learn C++ first! Traditionally, developing own objects and scenarios and sharing them with others has been how pretty much all of today's developers started out.

• Developer Documentation docs.openclonk.org/en/sdk/
• Forum - forum.openclonk.org
• Style Guide - wiki.openclonk.org/w/C4Script_Style_Guidelines
• Contribute changes - Git Workflow
• Are you a sound artist? Here is a list of missing sounds you can contribute.
• Game content external to the main game: List Of Community Creations

Build OpenClonk Yourself

When delving deeper into OpenClonk, you will often find yourself in the situation that you need a closer look at what makes OpenClonk tick internally. At that point, it is a good idea to assume the perspective of developers - get the source code and build it in your own development environment.

• Tutorial for Windows - wiki.openclonk.org/w/Building_with_Windows
• Tutorial for Linux - wiki.openclonk.org/w/Building_with_Linux
• General instructions - wiki.openclonk.org/w/Build_OpenClonk
• Git Workflow Guide - wiki.openclonk.org/w/Git_Workflow
• Git Repository - github.com/openclonk/openclonk
• Source Code Structure - wiki.openclonk.org/w/Source_code_structure

Hack the OpenClonk Engine

Maybe you already are well-versed in C++ and want to help out actually diagnosing problems? Or - even better - have your own ideas on engine improvements? We are always glad to look at patches.

• Wondering where to start? - Ideas page
• Debugging synchronization losses - wiki.openclonk.org/w/Sync_Losses
• Style Guide - wiki.openclonk.org/w/Style_Guidelines
• Forum, developers' corner - forum.openclonk.org
• Contribute changes - Git Workflow

Internal Links

• Release Steps
• The release button

Legal Stuff

OpenClonk uses the ISC license for code (engine and script) and CC-by for most other media. Read more about the license stuff here.