OpenClonk Wiki - User contributions [en]

Release Steps

2016-01-24T13:37:46Z

Newton:

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* '''Update the Version.txt''' to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
* Then go to the '''[http://londeroth.org/~ck/oc-release/oc-release.cgi release button]''' and release from the correct branch.

=== After Release ===

* '''Create a stable branch''' named stable-X for bugfix releases.
* '''Make announcements''' in our blog and in our forum.
* Notify an openclonk.org admin to '''transfer the [https://git.openclonk.org/openclonk.git/archive/ source package]''' to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
* Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.
* '''Notify our Linux package maintainers''' for [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ others] that a new version has been released.

=== Optional ===

* '''Update external websites''': [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt], [http://en.wikipedia.org/wiki/OpenClonk wikipedia article],[https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:37:43Z

Newton: /* Release */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* '''Update the Version.txt''' to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* Then go to the '''[http://londeroth.org/~ck/oc-release/oc-release.cgi release button]''' and release from the correct branch.

=== After Release ===

* '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
* '''Create a stable branch''' named stable-X for bugfix releases.
* '''Make announcements''' in our blog and in our forum.
* Notify an openclonk.org admin to '''transfer the [https://git.openclonk.org/openclonk.git/archive/ source package]''' to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
* Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.
* '''Notify our Linux package maintainers''' for [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ others] that a new version has been released.

=== Optional ===

* '''Update external websites''': [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt], [http://en.wikipedia.org/wiki/OpenClonk wikipedia article],[https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:37:16Z

Newton: /* Optional */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* Update the Version.txt to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== After Release ===

* '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
* '''Create a stable branch''' named stable-X for bugfix releases.
* '''Make announcements''' in our blog and in our forum.
* Notify an openclonk.org admin to '''transfer the [https://git.openclonk.org/openclonk.git/archive/ source package]''' to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
* Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.
* '''Notify our Linux package maintainers''' for [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ others] that a new version has been released.

=== Optional ===

* '''Update external websites''': [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt], [http://en.wikipedia.org/wiki/OpenClonk wikipedia article],[https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:37:03Z

Newton: /* Optional */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* Update the Version.txt to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== After Release ===

* '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
* '''Create a stable branch''' named stable-X for bugfix releases.
* '''Make announcements''' in our blog and in our forum.
* Notify an openclonk.org admin to '''transfer the [https://git.openclonk.org/openclonk.git/archive/ source package]''' to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
* Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.
* '''Notify our Linux package maintainers''' for [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ others] that a new version has been released.

=== Optional ===

* Update external websites: [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt], [http://en.wikipedia.org/wiki/OpenClonk wikipedia article],[https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:36:46Z

Newton: /* After Release */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* Update the Version.txt to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== After Release ===

* '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
* '''Create a stable branch''' named stable-X for bugfix releases.
* '''Make announcements''' in our blog and in our forum.
* Notify an openclonk.org admin to '''transfer the [https://git.openclonk.org/openclonk.git/archive/ source package]''' to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
* Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.
* '''Notify our Linux package maintainers''' for [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ others] that a new version has been released.

=== Optional ===

* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:36:36Z

Newton: /* Optional */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* Update the Version.txt to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== After Release ===

* '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
* '''Create a stable branch''' named stable-X for bugfix releases.
* '''Make announcements''' in our blog and in our forum.
* Notify an openclonk.org admin to '''transfer the [https://git.openclonk.org/openclonk.git/archive/ source package]''' to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
* Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.
* '''Notify our Linux package maintainers''' for [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ others] that a new version has been released.
* Make it known that OpenClonk has been released on other websites. I.e. [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt], [http://en.wikipedia.org/wiki/OpenClonk wikipedia article].

=== Optional ===

* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:36:20Z

Newton: /* Post Release */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* Update the Version.txt to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== After Release ===

* '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
* '''Create a stable branch''' named stable-X for bugfix releases.
* '''Make announcements''' in our blog and in our forum.
* Notify an openclonk.org admin to '''transfer the [https://git.openclonk.org/openclonk.git/archive/ source package]''' to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
* Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.
* '''Notify our Linux package maintainers''' for [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ others] that a new version has been released.
* Make it known that OpenClonk has been released on other websites. I.e. [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt], [http://en.wikipedia.org/wiki/OpenClonk wikipedia article].

=== Optional ===

Optional steps:
* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:15:02Z

Newton: /* Release */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Optional: Update all Version.txt files in planet/ to the new version number.
* Update the Version.txt to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== Post Release ===

After the release has been uploaded do the following:
* Tag the released changeset with the vX.Y tag (leightweight: git tag vX.Y).
* Create a stable branch named stable-X for bugfix releases.
* Check if installers for all operating systems are existing (contact Mortimer for Mac).
* Basic tests: download, check installer content, run game, play game, play network game.
* Make announcements in our blog and in our forum.
* Update external game portals: [[http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt].
* Notify our [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ other] package maintainers that a new version has been released.
* Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.
* Update [http://en.wikipedia.org/wiki/OpenClonk wikipedia article].

=== Optional ===

Optional steps:
* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:14:05Z

Newton: /* Release */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* (Update all Version.txt files in planet/ to the new version number and commit/push.)
* Update the Version.txt to the new version number and put the extra version in Version.txt to nothing [SET(C4VERSIONEXTRA FALSE)]. Commit/push.
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== Post Release ===

After the release has been uploaded do the following:
* Tag the released changeset with the vX.Y tag (leightweight: git tag vX.Y).
* Create a stable branch named stable-X for bugfix releases.
* Check if installers for all operating systems are existing (contact Mortimer for Mac).
* Basic tests: download, check installer content, run game, play game, play network game.
* Make announcements in our blog and in our forum.
* Update external game portals: [[http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt].
* Notify our [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ other] package maintainers that a new version has been released.
* Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.
* Update [http://en.wikipedia.org/wiki/OpenClonk wikipedia article].

=== Optional ===

Optional steps:
* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:12:44Z

Newton: /* Pre Release */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Before Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Update all Version.txt files in planet/ to the new version number and commit/push.
* Update the Version.txt to the new version number and commit/push.
* Set the extra version in Version.txt to nothing [SET(C4VERSIONEXTRA FALSE)]
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== Post Release ===

After the release has been uploaded do the following:
* Tag the released changeset with the vX.Y tag (leightweight: git tag vX.Y).
* Create a stable branch named stable-X for bugfix releases.
* Check if installers for all operating systems are existing (contact Mortimer for Mac).
* Basic tests: download, check installer content, run game, play game, play network game.
* Make announcements in our blog and in our forum.
* Update external game portals: [[http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt].
* Notify our [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ other] package maintainers that a new version has been released.
* Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.
* Update [http://en.wikipedia.org/wiki/OpenClonk wikipedia article].

=== Optional ===

Optional steps:
* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Release Steps

2016-01-16T11:12:05Z

Newton: /* Post Release */

__NOTOC__
This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all steps have been considered.

=== Pre Release ===

Steps to do before the release, and after the feature freeze.

* If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
* Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].
* Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.
* Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

=== Release ===

If it is made sure that the current [https://git.openclonk.org/openclonk.git master branch] or the current stable branch does not contain any bugs one can initiate the release procedure.

* Update all Version.txt files in planet/ to the new version number and commit/push.
* Update the Version.txt to the new version number and commit/push.
* Set the extra version in Version.txt to nothing [SET(C4VERSIONEXTRA FALSE)]
* Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.

=== Post Release ===

After the release has been uploaded do the following:
* Tag the released changeset with the vX.Y tag (leightweight: git tag vX.Y).
* Create a stable branch named stable-X for bugfix releases.
* Check if installers for all operating systems are existing (contact Mortimer for Mac).
* Basic tests: download, check installer content, run game, play game, play network game.
* Make announcements in our blog and in our forum.
* Update external game portals: [[http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt].
* Notify our [https://packages.debian.org/de/sid/openclonk Debian], [https://aur.archlinux.org/packages/openclonk/ Arch], [http://www.freshports.org/games/openclonk/ FreeBSD] and [http://www.openclonk.org/download/ other] package maintainers that a new version has been released.
* Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.
* Update [http://en.wikipedia.org/wiki/OpenClonk wikipedia article].

=== Optional ===

Optional steps:
* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Spread the word! More advertisement!

Old Screenshots

2015-11-27T21:18:01Z

Newton:

__NOTOC__

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T21:17:55Z

Newton:

__NOTOC__

== 2015 ==
{|
| [[File:Boompack.png|280xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|280xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|280xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|280xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|280xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|280xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|280xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|280xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|280xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|280xpx|thumb|Mission selection]]
| [[File:ItemOverview.png|280xpx|thumb|Item overview]]
| [[File:BoompackMayhem.png|280xpx|thumb|Massive explosion]]
|-
| [[File:GrottoSettlement.png|280xpx|thumb|Cave settlement]]
| [[File:PowerSettlement.png|280xpx|thumb|Settlement powering]]
| [[File:GemMining.png|280xpx|thumb|Gem mining]]
|-
| [[File:RaidAttack.png|280xpx|thumb|Raid attack]]
| [[File:DeepSeaMining.png|280xpx|thumb|Deep sea mining]]
| [[File:ChineCannon.png|280xpx|thumb|Cannon transport]]
|-
| [[File:IronPeak.png|280xpx|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|280xpx|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|280xpx|thumb|Mushrooms]]
| [[File:GemGrabbers.png|280xpx|thumb|Grab some gems]]
|-
| [[File:AcidGoldMine.png|280xpx|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|280xpx|thumb|First OC Settlement]]
| [[File:Krakatoa.png|280xpx|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|280xpx|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|280xpx|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|280xpx|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|280xpx|thumb|Introducing a new power system]]
|}

[[Old Screenshots]] from in development

Old Screenshots

2015-11-27T21:15:18Z

Newton: Created page with "== September 2011 == {| | Editor on Linux |} == September 2010 == {| | Tutorial 3: Ranged Weapons..."

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T21:15:06Z

Newton:

Screenshots

2015-11-27T21:08:50Z

Newton: /* 2012 */

== 2015 ==
{|
| [[File:Boompack.png|280xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|280xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|280xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|280xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|280xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|280xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|280xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|280xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|280xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|280xpx|thumb|Mission selection]]
| [[File:ItemOverview.png|280xpx|thumb|Item overview]]
| [[File:BoompackMayhem.png|280xpx|thumb|Massive explosion]]
|-
| [[File:GrottoSettlement.png|280xpx|thumb|Cave settlement]]
| [[File:PowerSettlement.png|280xpx|thumb|Settlement powering]]
| [[File:GemMining.png|280xpx|thumb|Gem mining]]
|-
| [[File:RaidAttack.png|280xpx|thumb|Raid attack]]
| [[File:DeepSeaMining.png|280xpx|thumb|Deep sea mining]]
| [[File:ChineCannon.png|280xpx|thumb|Cannon transport]]
|-
| [[File:IronPeak.png|280xpx|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|280xpx|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|280xpx|thumb|Mushrooms]]
| [[File:GemGrabbers.png|280xpx|thumb|Grab some gems]]
|-
| [[File:AcidGoldMine.png|280xpx|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|280xpx|thumb|First OC Settlement]]
| [[File:Krakatoa.png|280xpx|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|280xpx|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|280xpx|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|280xpx|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|280xpx|thumb|Introducing a new power system]]
|}

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T21:08:23Z

Newton: /* 2013 */

== 2015 ==
{|
| [[File:Boompack.png|280xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|280xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|280xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|280xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|280xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|280xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|280xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|280xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|280xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|280xpx|thumb|Mission selection]]
| [[File:ItemOverview.png|280xpx|thumb|Item overview]]
| [[File:BoompackMayhem.png|280xpx|thumb|Massive explosion]]
|-
| [[File:GrottoSettlement.png|280xpx|thumb|Cave settlement]]
| [[File:PowerSettlement.png|280xpx|thumb|Settlement powering]]
| [[File:GemMining.png|280xpx|thumb|Gem mining]]
|-
| [[File:RaidAttack.png|280xpx|thumb|Raid attack]]
| [[File:DeepSeaMining.png|280xpx|thumb|Deep sea mining]]
| [[File:ChineCannon.png|280xpx|thumb|Cannon transport]]
|-
| [[File:IronPeak.png|280xpx|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|280xpx|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|280xpx|thumb|Mushrooms]]
| [[File:GemGrabbers.png|280xpx|thumb|Grab some gems]]
|-
| [[File:AcidGoldMine.png|280xpx|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|270xpx|thumb|First OC Settlement]]
| [[File:Krakatoa.png|270xpx|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|270xpx|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|270xpx|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|270xpx|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|270xpx|thumb|Introducing a new power system]]
|}

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T21:08:00Z

Newton: /* 2015 */

== 2015 ==
{|
| [[File:Boompack.png|280xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|280xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|280xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|280xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|280xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|280xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|280xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|280xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|280xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|280xpx|thumb|Mission selection]]
| [[File:ItemOverview.png|280xpx|thumb|Item overview]]
| [[File:BoompackMayhem.png|280xpx|thumb|Massive explosion]]
|-
| [[File:GrottoSettlement.png|280xpx|thumb|Cave settlement]]
| [[File:PowerSettlement.png|280xpx|thumb|Settlement powering]]
| [[File:GemMining.png|280xpx|thumb|Gem mining]]
|-
| [[File:RaidAttack.png|280xpx|thumb|Raid attack]]
| [[File:DeepSeaMining.png|280xpx|thumb|Deep sea mining]]
| [[File:ChineCannon.png|280xpx|thumb|Cannon transport]]
|-
| [[File:IronPeak.png|280xpx|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|270xpx|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|270xpx|thumb|Mushrooms]]
| [[File:GemGrabbers.png|270xpx|thumb|Grab some gems]]
|-
| [[File:AcidGoldMine.png|270xpx|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|270xpx|thumb|First OC Settlement]]
| [[File:Krakatoa.png|270xpx|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|270xpx|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|270xpx|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|270xpx|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|270xpx|thumb|Introducing a new power system]]
|}

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T21:05:43Z

Newton: /* 2012 */

== 2015 ==
{|
| [[File:Boompack.png|260xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|260xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|260xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|260xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|260xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|260xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|260xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|260xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|260xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|280xpx|thumb|Mission selection]]
| [[File:ItemOverview.png|280xpx|thumb|Item overview]]
| [[File:BoompackMayhem.png|280xpx|thumb|Massive explosion]]
|-
| [[File:GrottoSettlement.png|280xpx|thumb|Cave settlement]]
| [[File:PowerSettlement.png|280xpx|thumb|Settlement powering]]
| [[File:GemMining.png|280xpx|thumb|Gem mining]]
|-
| [[File:RaidAttack.png|280xpx|thumb|Raid attack]]
| [[File:DeepSeaMining.png|280xpx|thumb|Deep sea mining]]
| [[File:ChineCannon.png|280xpx|thumb|Cannon transport]]
|-
| [[File:IronPeak.png|280xpx|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|270xpx|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|270xpx|thumb|Mushrooms]]
| [[File:GemGrabbers.png|270xpx|thumb|Grab some gems]]
|-
| [[File:AcidGoldMine.png|270xpx|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|270xpx|thumb|First OC Settlement]]
| [[File:Krakatoa.png|270xpx|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|270xpx|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|270xpx|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|270xpx|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|270xpx|thumb|Introducing a new power system]]
|}

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T21:04:39Z

Newton: /* 2013 */

== 2015 ==
{|
| [[File:Boompack.png|260xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|260xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|260xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|260xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|260xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|260xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|260xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|260xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|260xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|280xpx|thumb|Mission selection]]
| [[File:ItemOverview.png|280xpx|thumb|Item overview]]
| [[File:BoompackMayhem.png|280xpx|thumb|Massive explosion]]
|-
| [[File:GrottoSettlement.png|280xpx|thumb|Cave settlement]]
| [[File:PowerSettlement.png|280xpx|thumb|Settlement powering]]
| [[File:GemMining.png|280xpx|thumb|Gem mining]]
|-
| [[File:RaidAttack.png|280xpx|thumb|Raid attack]]
| [[File:DeepSeaMining.png|280xpx|thumb|Deep sea mining]]
| [[File:ChineCannon.png|280xpx|thumb|Cannon transport]]
|-
| [[File:IronPeak.png|280xpx|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|270xpx|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|270xpx|thumb|Mushrooms]]
| [[File:GemGrabbers.png|270xpx|thumb|Grab some gems]]
|-
| [[File:AcidGoldMine.png|270xpx|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|300px|thumb|First OC Settlement]]
| [[File:Krakatoa.png|300px|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|275px|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|300px|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|300px|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|275px|thumb|Introducing a new power system]]
|}

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T21:01:52Z

Newton: /* 2014 */

== 2015 ==
{|
| [[File:Boompack.png|260xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|260xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|260xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|260xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|260xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|260xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|260xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|260xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|260xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|280xpx|thumb|Mission selection]]
| [[File:ItemOverview.png|280xpx|thumb|Item overview]]
| [[File:BoompackMayhem.png|280xpx|thumb|Massive explosion]]
|-
| [[File:GrottoSettlement.png|280xpx|thumb|Cave settlement]]
| [[File:PowerSettlement.png|280xpx|thumb|Settlement powering]]
| [[File:GemMining.png|280xpx|thumb|Gem mining]]
|-
| [[File:RaidAttack.png|280xpx|thumb|Raid attack]]
| [[File:DeepSeaMining.png|280xpx|thumb|Deep sea mining]]
| [[File:ChineCannon.png|280xpx|thumb|Cannon transport]]
|-
| [[File:IronPeak.png|280xpx|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|400px|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|355px|thumb|Mushrooms]]
|-
| [[File:GemGrabbers.png|400px|thumb|Grab some gems]]
| [[File:AcidGoldMine.png|355px|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|300px|thumb|First OC Settlement]]
| [[File:Krakatoa.png|300px|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|275px|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|300px|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|300px|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|275px|thumb|Introducing a new power system]]
|}

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Screenshots

2015-11-27T20:59:32Z

Newton: /* 2015 */

== 2015 ==
{|
| [[File:Boompack.png|260xpx|thumb|Combat in Thunderous Skies]]
| [[File:Building.png|260xpx|thumb|Building an elevator]]
| [[File:DarkMine.png|260xpx|thumb|Standoff in Dark Mine]]
|-
| [[File:Overcast2.png|260xpx|thumb|Battle in Overcast]]
| [[File:Gemgrabber.png|260xpx|thumb|A base in Gemgrabbers]]
| [[File:Dynamite.jpg|260xpx|thumb|Blasting some gems]]
|}
{|
| [[File:Climbing.png|260xpx|thumb|A race scenario]]
| [[File:Underground_Base.png|260xpx|thumb|An underground base from Krakatoa's Krach]]
| [[File:OC-Spiral.png|260xpx|thumb|more underground settling]]
|}

== 2014 ==
{|
| [[File:MissionSelection.png|200px|thumb|Mission selection]]
| [[File:ItemOverview.png|200px|thumb|Item overview]]
| [[File:BoompackMayhem.png|200px|thumb|Massive explosion]]
| [[File:DeepSeaMining.png|200px|thumb|Deep sea mining]]
|-
| [[File:GrottoSettlement.png|200px|thumb|Cave settlement]]
| [[File:PowerSettlement.png|200px|thumb|Settlement powering]]
| [[File:GemMining.png|200px|thumb|Gem mining]]
| [[File:RaidAttack.png|200px|thumb|Raid attack]]
|-
| [[File:ChineCannon.png|200px|thumb|Cannon transport]]
| [[File:IronPeak.png|200px|thumb|Iron peak]]
|
|
|}

== 2013 ==
{|
| [[File:Kill_The_King.jpg|400px|thumb|Kill the king - a new mission]]
| [[File:MushroomCave.jpg|355px|thumb|Mushrooms]]
|-
| [[File:GemGrabbers.png|400px|thumb|Grab some gems]]
| [[File:AcidGoldMine.png|355px|thumb|Acid Gold Mine - a especially hard settling scenario]]
|}

== 2012 ==
{|
| [[File:FirstOCSettlement.png|300px|thumb|First OC Settlement]]
| [[File:Krakatoa.png|300px|thumb|New scenario: Krakatoa]]
| [[File:Controls2012.png|275px|thumb|Control System 2012]]
|-
| [[File:SkylandsPromo.jpg|300px|thumb|Early sky island scenario]]
| [[File:IntroducingMissions.png|300px|thumb|Introducing Missions]]
| [[File:PowerSystem.jpg|275px|thumb|Introducing a new power system]]
|}

== September 2011 ==
{|
| [[File:Editor_linux.png|x300px|thumb|Editor on Linux]]
|}

== September 2010 ==
{|
| [[File:Sept10Tut3.png|x300px|thumb|Tutorial 3: Ranged Weapons]]
|}

== March 2010 ==
{|
| [[File:ringmenu.png|x300px|thumb|The ringmenu prototype shows the contents of the clonk's backpack]]
| [[File:cursor.jpg|x300px|thumb|Aiming the bow with the gamepad]]
| [[File:ladderclimb.png|x300px|thumb|The clonk learned to climb ladders]]
|}

== February 2010 ==
{|
| [[File:bow.png|x300px|thumb|Using the bow and the javelin]]
| [[File:boompack1.png|x300px|thumb|The boompack, a makeshift "jetpack"]]
| [[File:boompack2.png|x300px|thumb|...or perhaps just firework]]
| [[File:musket.png|x300px|thumb|Shooting and aiming with the musket]]
|}
== January 2010 ==
{|
| [[File:newhud.png|x300px|thumb|Half-done new interface and free digging controls]]
| [[File:Realtimerender.png|x300px|thumb|Real time rendering of the clonk]]
| [[File:Networkgame.png|x300px|thumb|First OC network game]]
|}

Texture Archives

2015-07-05T10:49:34Z

Newton: /* Mostly free with own license */

== Free / no Copyright / CC-BY ==
Here are some links to archives which offer textures "without any copyright", compatible CC licenses or public domain. Attention: If you want to extend this list, note that "free" or the lack of any copyright message doesn't mean anything. To be public domain or "without any copyright", it must be explicitly noted.

* [http://www.flickr.com Flickr] - mixed CC licenses
* [http://www.opengameart.org/textures/ OpenGameArt (3400+)] - various open source licenses
* [http://www.lughertexture.com/ LuGher Texture (3400+)] - free to use in personal and commercial projects
* [http://www.accustudio.com/index.php?option=com_phocagallery&view=category&id=1&Itemid=77 Accustudio (~1000)] - free of any copyrights
* [http://texturebarn.headfirstdm.com/ The Texture Barn (~500)] - "Royalty-free textures for computer graphics, illustration, game design and everything else"
* [http://www.bencloward.com/resources_textures.shtml Ben Cloward (~300)] - free but author would like to be notified where it is used
* [https://community.renderman.pixar.com/article/114/library-pixar-one-twenty-eight.html Pixar] - CC-BY 4.0

== Mostly free with own license ==
The most and the biggest free texture archives offer the textures free for any purpose, but it is not allowed to redistribute them as a texture pack. The issue with these terms of use is that they limit how these textures may be redistributed which in turn would limit how OpenClonk may be redistributed. But OpenClonk content is released under the CC Attribution license which doesn't impose this kind of restriction. So the textures from these archives are not open source, we can't include any textures from these sources.

However, if you find really good textures there, it doesn't hurt to ask the original authors whether it is possible to grant permission to use a certain texture under a CC license that is compatible with open source.
Same holds for images collected for example from flickr that are not licensed under a CC license.

* [http://www.cgtextures.com/ CG Textures (30000+)]
* [http://www.imageafter.com/textures.php Image After (~10000)]
* [http://mayang.com/textures/ Mayang's Free Texture Library (3800+)] - max. 30 textures may be used
* [http://texturemate.com/ texturemate (4400+)]
* [http://www.2textured.com/main.php 2Textured (2700+)] - "The textures may be used freely in commercial or personal works but reselling or redistributing of the textures on other texture sites is forbidden"
* [http://www.freetextures.org/pgs/graphic/graphic_1.html Freetextures.org (~1000)]
* [http://texturez.com/ Texturez (800+)]
* [http://freestocktextures.com/ Free Stock Textures (800+)]
* [http://www.dougturner.net/blendersite/index.html Free Texture Site (600+)]
* [http://zentextures.com/ Zen Textures (450+)]
* [http://noctua-graphics.de/english/freetex_e.htm Noctua Graphics (400+)]
* [http://www.textureking.com/ Texture King (300+)]

Texture Archives

2015-07-05T10:46:12Z

Newton: /* Free / no Copyright / CC-BY */

== Free / no Copyright / CC-BY ==
Here are some links to archives which offer textures "without any copyright", compatible CC licenses or public domain. Attention: If you want to extend this list, note that "free" or the lack of any copyright message doesn't mean anything. To be public domain or "without any copyright", it must be explicitly noted.

* [http://www.flickr.com Flickr] - mixed CC licenses
* [http://www.opengameart.org/textures/ OpenGameArt (3400+)] - various open source licenses
* [http://www.lughertexture.com/ LuGher Texture (3400+)] - free to use in personal and commercial projects
* [http://www.accustudio.com/index.php?option=com_phocagallery&view=category&id=1&Itemid=77 Accustudio (~1000)] - free of any copyrights
* [http://texturebarn.headfirstdm.com/ The Texture Barn (~500)] - "Royalty-free textures for computer graphics, illustration, game design and everything else"
* [http://www.bencloward.com/resources_textures.shtml Ben Cloward (~300)] - free but author would like to be notified where it is used
* [https://community.renderman.pixar.com/article/114/library-pixar-one-twenty-eight.html Pixar] - CC-BY 4.0

== Mostly free with own license ==
The most and the biggest free texture archives offer the textures free for any purpose, but it is not allowed to redistribute them as a texture pack. The issue with these terms of use is that they limit how these textures may be redistributed which in turn would limit how OpenClonk may be redistributed. But OpenClonk content is released under the CC Attribution license which doesn't impose this kind of restriction. So the textures from these archives are not open source, we can't include any textures from these sources.

However, if you find really good textures there, it doesn't hurt to ask the original authors whether it is possible to grant permission to use a certain texture under a CC license that is compatible with open source.
Same holds for images collected for example from flickr that are not licensed under a CC license.

* [http://www.cgtextures.com/ CG Textures (30000+)]
* [http://www.imageafter.com/textures.php Image After (~10000)]
* [http://mayang.com/textures/ Mayang's Free Texture Library (3800+)] - max. 30 textures may be used
* [http://www.2textured.com/main.php 2Textured (2700+)] - "The textures may be used freely in commercial or personal works but reselling or redistributing of the textures on other texture sites is forbidden"
* [http://www.freetextures.org/pgs/graphic/graphic_1.html Freetextures.org (~1000)]
* [http://texturez.com/ Texturez (800+)]
* [http://www.dougturner.net/blendersite/index.html Free Texture Site (600+)]
* [http://zentextures.com/ Zen Textures (450+)]
* [http://noctua-graphics.de/english/freetex_e.htm Noctua Graphics (400+)]
* [http://www.textureking.com/ Texture King (300+)]

FAQ

2015-03-15T20:18:59Z

Newton: /* What is license for OpenClonk? */

If you don't find your particular question answered here, post in the [http://forum.openclonk.org/ forum]! You don't need to register but can ask as Anonymous there.

__TOC__

=== I cannot start the game! What do I do? ===
For some people, the game crashes if they enable Triple Buffering for OpenGL in their graphics driver. Try disabling it:
If you have an AMD graphics card go into the Catalyst Control Center. (You will find it by typing ccc into the start menu on Windows). Go to Games and then 3D Application Settings. Scroll all the way down and at the very bottom un-select Triple Buffering.

If this doesn't help, describe your problem in the bugtracker and post any relevant information:
* There is a Clonk.log in your OpenClonk directory. On Windows, it's in C:\Users\[Username]\AppData\Roaming\OpenClonk\
* What's your video card? Are your drivers up-to-date? Intel Express Chipsets reportedly have problems with OpenGL
* Which version of this game are you using? Did you try out the latest development snapshot? Does the problem persist then?

=== I can not host a round on the internet! What can I do? ===

If you want to host a game on the internet and are behind a router, you need to forward the ports 11111-11113 (TCP & UDP) in your home router configuration.
How to forward the ports completely depends on your router software, so you have to refer to your router's manual there.

For more information on ports, see [[#Which ports does OpenClonk use?|Which ports does OpenClonk use?]]

=== Which ports does OpenClonk use? ===

OpenClonk uses the same ports as Clonk Rage. From the FAQ on clonk.de:

By default, Clonk uses port 11112 TCP and port 11113 UDP for game connections. For best speed it is recommended to forward both of these ports through your router or firewall.

For directly joining an IP address (without internet server) port 11111 TCP is required incoming on the host.

Automatic game discovery in LAN works through port 11114 UDP. If necessary, these ports can be adjusted in the options dialog. For other functions the game will connect to the internet and league server clonk.de on port 84 and port 11115 for additional hole punching.

=== How do I submit a patch? ===
This answer assumes that you are using TortoiseGit. After you [[Git Workflow|checked out the source code]] and made your changes, you need to ''commit'' these changes. Afterwards, you can use the context menu to create a patch. This will create a new file which you can paste into a forum post. If you made or changed a binary file, please also attach it to your post.

If you use GitHub, you can also create a pull request for [https://github.com/openclonk/openclonk our project on GitHub]. Be advised however that the repository on GitHub is just a mirror of our repository.

=== Why is this page in English? Isn't Clonk a German game? ===
Clonk has been a German shareware game and thus its community has been mainly German. With the switch to the English language for the OpenClonk community, we intended to widen the community to an international level and make it possible for non-Germans to contribute to and participate in OpenClonk.
However, there is a German subforum now.

And of course, German, as well as other languages will continue to be supported in the game. Just the ''development'' and the community of OpenClonk will be in English.

=== Why did you start from scratch regarding the game content? ===
During shareware Clonk development, the game content stayed mainly about the same and was just extended by add-ons. This and the decision to keep the game as backward compatible as possible blocked lots of good changes and new concepts that could have been introduced in the game.

OpenClonk is a different game than the old Clonk series, it is not be just a sequel in the fashion of previous Clonk development. The aim of OpenClonk is not to replace Clonk Rage by "making it better" while keeping everything as it was before.
Clonk is about mining, about production lines and economy, fast and fiddly melees, known for flexibility in scenario design and whatnot. In this project, we aim to improve these strengths, which means that during OpenClonk development more fundamental changes must be (and are) possible.

Clonk Rage on the other hand will continue to exist alongside OpenClonk as the last title of the shareware series and will continue to include all that classical and that the community has come to love. Also read
[http://forum.openclonk.org/topic_show.pl?pid=1677#pid1677 this old forum discussion] on this topic.

=== Will you convert all those great Clonk Rage expansions for OpenClonk? ===
No, and we never will. OpenClonk is not backwards compatible with Clonk Rage, and never will be. We have broken ties with the old game content which all these expansions rely on. Hence the name, they are expansions for Clonk Rage. Specifically, Clonk Rage. OpenClonk is a different game with different game content, graphics, and script language, and therefore cannot have it's game content expanded with expansions designed for a completely different game.

=== What is the license for OpenClonk? ===
The code is licensed under the ISC license.

The game content is licensed under mixed CC 3.0 licenses of which none is more restrictive than CC-BY-SA (CC-BY, CC 0 and CC-BY-SA). Actually, the vast majority are CC-BY, there are only one or two files that are CC-BY-SA. Nevertheless, as a whole, it can thus only be distributed under the CC-BY-SA.

See [[License]] for more information.

=== Am I able to play with several players on one PC? ===
Generally yes. However, currently this is not possible yet.

=== Where can I upload / download mods for OpenClonk? Are there any? ===
Have a look in the [http://forum.openclonk.org/board_show.pl?bid=18 Player Creations board] in the forum. You might also want to check the [http://www.ccan.de CCAN]

=== Will there be keyboard-only controls? ===
No. OpenClonk is played with keyboard and mouse as the whole game is designed to utilize the advantages of mouse control. This adds a completely new set of gameplay possibilities to the game that would never have been possible in the shareware Clonk titles. <s>However, gamepad controls are supported in the game and they work quite well considering that a gamepad doesn't have a pointing device.</s>
However you can create your own keyboard-only control scheme based on the gamepad control scheme.

Currently, gamepad controls undergo an overhaul and are not functioning properly.

=== Are other Clonk games available as source code? ===
The source code for most older Clonk versions [http://www.clonk.de/source.php is available from Redwolf Design]. Here is a list of modified versions:
* [http://wiki.gp2x.org/articles/c/l/o/Clonk2X.html Clonk Planet for GP2x]
* [http://www.goldwipf.de/ The GWE] ([http://www.ccan.de/cgi-bin/ccan/ccan-view.pl?a=view&i=5757 download from CCAN])

=== Is there an editor for OpenClonk? ===
Yes, the [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4DT], the Clonk Development Tools for Eclipse, maintained by Mortimer. Eclipse is a powerful open source IDE that you will have heard of if you ever developed in Java. C4DT is a plugin for Eclipse that makes it possible to develop for Clonk in C4Script and even debug your code one-instruction-at-a-time using this powerful IDE.

The old explorer-like Editor.exe that you might know from Clonk Rage doesn't exist anymore in OpenClonk. However, the editor mode still exists for drawing and designing scenarios. Just start clonk with the commandline parameter ''--editor''.

For more information on how to develop content for the game, see the [[C4Script Documentation]].

=== How can I create my own game content? ===
If you are looking to develop your own game content for or based on OpenClonk, have a look at the [[C4Script Documentation]], you should find everything there. See also a related FAQ answer: [[#Is there an editor for OpenClonk?|Is there an editor for OpenClonk?]]

If you are interested in getting involved and contributing to OpenClonk, this introduction on [[Development|development]] should make you happy :-).
For any other open questions regarding this, consider dropping by in our [http://forum.openclonk.org/ forum] or in our [irc://irc.euirc.net/openclonk IRC channel]!

=== Where can I report bugs? ===
In the [http://bugs.openclonk.org bugtracker].

=== How can I build OpenClonk myself? ===
Check out [[Build_OpenClonk|this tutorial]].

FAQ

2015-03-15T20:18:44Z

Newton: add License question to FAQ

If you don't find your particular question answered here, post in the [http://forum.openclonk.org/ forum]! You don't need to register but can ask as Anonymous there.

__TOC__

=== I cannot start the game! What do I do? ===
For some people, the game crashes if they enable Triple Buffering for OpenGL in their graphics driver. Try disabling it:
If you have an AMD graphics card go into the Catalyst Control Center. (You will find it by typing ccc into the start menu on Windows). Go to Games and then 3D Application Settings. Scroll all the way down and at the very bottom un-select Triple Buffering.

If this doesn't help, describe your problem in the bugtracker and post any relevant information:
* There is a Clonk.log in your OpenClonk directory. On Windows, it's in C:\Users\[Username]\AppData\Roaming\OpenClonk\
* What's your video card? Are your drivers up-to-date? Intel Express Chipsets reportedly have problems with OpenGL
* Which version of this game are you using? Did you try out the latest development snapshot? Does the problem persist then?

=== I can not host a round on the internet! What can I do? ===

If you want to host a game on the internet and are behind a router, you need to forward the ports 11111-11113 (TCP & UDP) in your home router configuration.
How to forward the ports completely depends on your router software, so you have to refer to your router's manual there.

For more information on ports, see [[#Which ports does OpenClonk use?|Which ports does OpenClonk use?]]

=== Which ports does OpenClonk use? ===

OpenClonk uses the same ports as Clonk Rage. From the FAQ on clonk.de:

By default, Clonk uses port 11112 TCP and port 11113 UDP for game connections. For best speed it is recommended to forward both of these ports through your router or firewall.

For directly joining an IP address (without internet server) port 11111 TCP is required incoming on the host.

Automatic game discovery in LAN works through port 11114 UDP. If necessary, these ports can be adjusted in the options dialog. For other functions the game will connect to the internet and league server clonk.de on port 84 and port 11115 for additional hole punching.

=== How do I submit a patch? ===
This answer assumes that you are using TortoiseGit. After you [[Git Workflow|checked out the source code]] and made your changes, you need to ''commit'' these changes. Afterwards, you can use the context menu to create a patch. This will create a new file which you can paste into a forum post. If you made or changed a binary file, please also attach it to your post.

If you use GitHub, you can also create a pull request for [https://github.com/openclonk/openclonk our project on GitHub]. Be advised however that the repository on GitHub is just a mirror of our repository.

=== Why is this page in English? Isn't Clonk a German game? ===
Clonk has been a German shareware game and thus its community has been mainly German. With the switch to the English language for the OpenClonk community, we intended to widen the community to an international level and make it possible for non-Germans to contribute to and participate in OpenClonk.
However, there is a German subforum now.

And of course, German, as well as other languages will continue to be supported in the game. Just the ''development'' and the community of OpenClonk will be in English.

=== Why did you start from scratch regarding the game content? ===
During shareware Clonk development, the game content stayed mainly about the same and was just extended by add-ons. This and the decision to keep the game as backward compatible as possible blocked lots of good changes and new concepts that could have been introduced in the game.

OpenClonk is a different game than the old Clonk series, it is not be just a sequel in the fashion of previous Clonk development. The aim of OpenClonk is not to replace Clonk Rage by "making it better" while keeping everything as it was before.
Clonk is about mining, about production lines and economy, fast and fiddly melees, known for flexibility in scenario design and whatnot. In this project, we aim to improve these strengths, which means that during OpenClonk development more fundamental changes must be (and are) possible.

Clonk Rage on the other hand will continue to exist alongside OpenClonk as the last title of the shareware series and will continue to include all that classical and that the community has come to love. Also read
[http://forum.openclonk.org/topic_show.pl?pid=1677#pid1677 this old forum discussion] on this topic.

=== Will you convert all those great Clonk Rage expansions for OpenClonk? ===
No, and we never will. OpenClonk is not backwards compatible with Clonk Rage, and never will be. We have broken ties with the old game content which all these expansions rely on. Hence the name, they are expansions for Clonk Rage. Specifically, Clonk Rage. OpenClonk is a different game with different game content, graphics, and script language, and therefore cannot have it's game content expanded with expansions designed for a completely different game.

=== What is license for OpenClonk? ===
The code is licensed under the ISC license.

The game content is licensed under mixed CC 3.0 licenses of which none is more restrictive than CC-BY-SA (CC-BY, CC 0 and CC-BY-SA). Actually, the vast majority are CC-BY, there are only one or two files that are CC-BY-SA. Nevertheless, as a whole, it can thus only be distributed under the CC-BY-SA.

See [[License]] for more information.

=== Am I able to play with several players on one PC? ===
Generally yes. However, currently this is not possible yet.

=== Where can I upload / download mods for OpenClonk? Are there any? ===
Have a look in the [http://forum.openclonk.org/board_show.pl?bid=18 Player Creations board] in the forum. You might also want to check the [http://www.ccan.de CCAN]

=== Will there be keyboard-only controls? ===
No. OpenClonk is played with keyboard and mouse as the whole game is designed to utilize the advantages of mouse control. This adds a completely new set of gameplay possibilities to the game that would never have been possible in the shareware Clonk titles. <s>However, gamepad controls are supported in the game and they work quite well considering that a gamepad doesn't have a pointing device.</s>
However you can create your own keyboard-only control scheme based on the gamepad control scheme.

Currently, gamepad controls undergo an overhaul and are not functioning properly.

=== Are other Clonk games available as source code? ===
The source code for most older Clonk versions [http://www.clonk.de/source.php is available from Redwolf Design]. Here is a list of modified versions:
* [http://wiki.gp2x.org/articles/c/l/o/Clonk2X.html Clonk Planet for GP2x]
* [http://www.goldwipf.de/ The GWE] ([http://www.ccan.de/cgi-bin/ccan/ccan-view.pl?a=view&i=5757 download from CCAN])

=== Is there an editor for OpenClonk? ===
Yes, the [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4DT], the Clonk Development Tools for Eclipse, maintained by Mortimer. Eclipse is a powerful open source IDE that you will have heard of if you ever developed in Java. C4DT is a plugin for Eclipse that makes it possible to develop for Clonk in C4Script and even debug your code one-instruction-at-a-time using this powerful IDE.

The old explorer-like Editor.exe that you might know from Clonk Rage doesn't exist anymore in OpenClonk. However, the editor mode still exists for drawing and designing scenarios. Just start clonk with the commandline parameter ''--editor''.

For more information on how to develop content for the game, see the [[C4Script Documentation]].

=== How can I create my own game content? ===
If you are looking to develop your own game content for or based on OpenClonk, have a look at the [[C4Script Documentation]], you should find everything there. See also a related FAQ answer: [[#Is there an editor for OpenClonk?|Is there an editor for OpenClonk?]]

If you are interested in getting involved and contributing to OpenClonk, this introduction on [[Development|development]] should make you happy :-).
For any other open questions regarding this, consider dropping by in our [http://forum.openclonk.org/ forum] or in our [irc://irc.euirc.net/openclonk IRC channel]!

=== Where can I report bugs? ===
In the [http://bugs.openclonk.org bugtracker].

=== How can I build OpenClonk myself? ===
Check out [[Build_OpenClonk|this tutorial]].

FAQ

2015-03-15T13:21:34Z

Newton:

If you don't find your particular question answered here, post in the [http://forum.openclonk.org/ forum]! You don't need to register but can ask as Anonymous there.

__TOC__

=== I cannot start the game! What do I do? ===
For some people, the game crashes if they enable Triple Buffering for OpenGL in their graphics driver. Try disabling it:
If you have an AMD graphics card go into the Catalyst Control Center. (You will find it by typing ccc into the start menu on Windows). Go to Games and then 3D Application Settings. Scroll all the way down and at the very bottom un-select Triple Buffering.

If this doesn't help, describe your problem in the bugtracker and post any relevant information:
* There is a Clonk.log in your OpenClonk directory. On Windows, it's in C:\Users\[Username]\AppData\Roaming\OpenClonk\
* What's your video card? Are your drivers up-to-date? Intel Express Chipsets reportedly have problems with OpenGL
* Which version of this game are you using? Did you try out the latest development snapshot? Does the problem persist then?

=== I can not host a round on the internet! What can I do? ===

If you want to host a game on the internet and are behind a router, you need to forward the ports 11111-11113 (TCP & UDP) in your home router configuration.
How to forward the ports completely depends on your router software, so you have to refer to your router's manual there.

For more information on ports, see [[#Which ports does OpenClonk use?|Which ports does OpenClonk use?]]

=== Which ports does OpenClonk use? ===

OpenClonk uses the same ports as Clonk Rage. From the FAQ on clonk.de:

By default, Clonk uses port 11112 TCP and port 11113 UDP for game connections. For best speed it is recommended to forward both of these ports through your router or firewall.

For directly joining an IP address (without internet server) port 11111 TCP is required incoming on the host.

Automatic game discovery in LAN works through port 11114 UDP. If necessary, these ports can be adjusted in the options dialog. For other functions the game will connect to the internet and league server clonk.de on port 84 and port 11115 for additional hole punching.

=== How do I submit a patch? ===
This answer assumes that you are using TortoiseGit. After you [[Git Workflow|checked out the source code]] and made your changes, you need to ''commit'' these changes. Afterwards, you can use the context menu to create a patch. This will create a new file which you can paste into a forum post. If you made or changed a binary file, please also attach it to your post.

If you use GitHub, you can also create a pull request for [https://github.com/openclonk/openclonk our project on GitHub]. Be advised however that the repository on GitHub is just a mirror of our repository.

=== Why is this page in English? Isn't Clonk a German game? ===
Clonk has been a German shareware game and thus its community has been mainly German. With the switch to the English language for the OpenClonk community, we intended to widen the community to an international level and make it possible for non-Germans to contribute to and participate in OpenClonk.
However, there is a German subforum now.

And of course, German, as well as other languages will continue to be supported in the game. Just the ''development'' and the community of OpenClonk will be in English.

=== Why did you start from scratch regarding the game content? ===
During shareware Clonk development, the game content stayed mainly about the same and was just extended by add-ons. This and the decision to keep the game as backward compatible as possible blocked lots of good changes and new concepts that could have been introduced in the game.

OpenClonk is a different game than the old Clonk series, it is not be just a sequel in the fashion of previous Clonk development. The aim of OpenClonk is not to replace Clonk Rage by "making it better" while keeping everything as it was before.
Clonk is about mining, about production lines and economy, fast and fiddly melees, known for flexibility in scenario design and whatnot. In this project, we aim to improve these strengths, which means that during OpenClonk development more fundamental changes must be (and are) possible.

Clonk Rage on the other hand will continue to exist alongside OpenClonk as the last title of the shareware series and will continue to include all that classical and that the community has come to love. Also read
[http://forum.openclonk.org/topic_show.pl?pid=1677#pid1677 this old forum discussion] on this topic.

=== Will you convert all those great Clonk Rage expansions for OpenClonk? ===
No, and we never will. OpenClonk is not backwards compatible with Clonk Rage, and never will be. We have broken ties with the old game content which all these expansions rely on. Hence the name, they are expansions for Clonk Rage. Specifically, Clonk Rage. OpenClonk is a different game with different game content, graphics, and script language, and therefore cannot have it's game content expanded with expansions designed for a completely different game.

=== Am I able to play with several players on one PC? ===
Generally yes. However, currently this is not possible yet.

=== Where can I upload / download mods for OpenClonk? Are there any? ===
Have a look in the [http://forum.openclonk.org/board_show.pl?bid=18 Player Creations board] in the forum. You might also want to check the [http://www.ccan.de CCAN]

=== Will there be keyboard-only controls? ===
No. OpenClonk is played with keyboard and mouse as the whole game is designed to utilize the advantages of mouse control. This adds a completely new set of gameplay possibilities to the game that would never have been possible in the shareware Clonk titles. <s>However, gamepad controls are supported in the game and they work quite well considering that a gamepad doesn't have a pointing device.</s>
However you can create your own keyboard-only control scheme based on the gamepad control scheme.

Currently, gamepad controls undergo an overhaul and are not functioning properly.

=== Are other Clonk games available as source code? ===
The source code for most older Clonk versions [http://www.clonk.de/source.php is available from Redwolf Design]. Here is a list of modified versions:
* [http://wiki.gp2x.org/articles/c/l/o/Clonk2X.html Clonk Planet for GP2x]
* [http://www.goldwipf.de/ The GWE] ([http://www.ccan.de/cgi-bin/ccan/ccan-view.pl?a=view&i=5757 download from CCAN])

=== Is there an editor for OpenClonk? ===
Yes, the [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4DT], the Clonk Development Tools for Eclipse, maintained by Mortimer. Eclipse is a powerful open source IDE that you will have heard of if you ever developed in Java. C4DT is a plugin for Eclipse that makes it possible to develop for Clonk in C4Script and even debug your code one-instruction-at-a-time using this powerful IDE.

The old explorer-like Editor.exe that you might know from Clonk Rage doesn't exist anymore in OpenClonk. However, the editor mode still exists for drawing and designing scenarios. Just start clonk with the commandline parameter ''--editor''.

For more information on how to develop content for the game, see the [[C4Script Documentation]].

=== How can I create my own game content? ===
If you are looking to develop your own game content for or based on OpenClonk, have a look at the [[C4Script Documentation]], you should find everything there. See also a related FAQ answer: [[#Is there an editor for OpenClonk?|Is there an editor for OpenClonk?]]

If you are interested in getting involved and contributing to OpenClonk, this introduction on [[Development|development]] should make you happy :-).
For any other open questions regarding this, consider dropping by in our [http://forum.openclonk.org/ forum] or in our [irc://irc.euirc.net/openclonk IRC channel]!

=== Where can I report bugs? ===
In the [http://bugs.openclonk.org bugtracker].

=== How can I build OpenClonk myself? ===
Check out [[Build_OpenClonk|this tutorial]].

Dynamic Map Generator

2014-08-09T16:41:41Z

Newton: /* Dynamic Map Generator */

== Dynamic Map Generator ==

OpenClonk has a dynamic map generator that can be used to generate maps that look different everytime but still have specified recurring patterns, like lava lakes, mountains, or sky islands. The documentation is available in the [http://docs.openclonk.org/en/sdk/scenario/MapCreatorS2.html C4Script reference here].
Mape is used to edit and display both Landscape.txts and Map.c.

=== Mape ===

[[File:Mape.png|450px|border|right|Screenshot of Mape]]

Mape is a tool that shows a live preview of the generated mape as the Landscape.txt code is being typed. The tool is available from the [http://www.openclonk.org/nightly-builds/ Development Snapshots] page for all major platforms. Its source code lives in the OpenClonk git repository.

The tool is meant both for beginners and experts alike. Beginners can easily play around with all the possibilities and immediately see their effect on the generated map. Experts can easily tweak the map to their liking without having to restart the engine for every change they make.

The mape window has four panels. The upper right part is the largest one which is where the Landscape.txt code can be edited. The panel to the left of it shows the file system tree. This is where one can select the Material.ocg file to be loaded. This specifies the materials and textures available to the map generator. The loaded materials and textures can be seen at the bottom panel once loaded which provides an easy view to what materials and textures are available. Finally in the lower right corner there is a preview of the generated map which updates as one types. The status bar contains error messages from the Landscape generator in case the Landscape.txt code is not correct.

=== Tips and Tricks ===

* The options allow to specify the width and height of the generated mape. To avoid any surprises, especially when specifying parameters with pixels instead of percentages, this should always be set to the same size as the OpenClonk map that one plans to create.

* In the options there is also the possibility to use a fixed seed for the random number generator. This allows to always create the same map when using the same Landscape.txt code, even if it contains randomness. This can come handy when trying to get a part of the map right and one does not want the rest of the map to change with every keystroke.

* If the random seed is not fixed, the map preview can be clicked on to generate another version of the map using the same Landscape.txt code but the randomness is re-evaluated.

* For big maps, rendering the map can take a while, up to a few seconds. This considerably slows down the feedback one gets for changing little things here and there. In this case, one can comment out the parts of the map that one does not work on right now and concentrate only on one specific feature or aspect of it, and then put it all together in the end.

* For overlays that use algo=script, the Script.c file that contains the script function that is being evaluated by the algorithm needs to be in the same directory as the Landscape.txt file. Therefore the Landscape.txt file must be saved at least once before algo=script can be used, so that mape knows where to look for the Script.c file. The landscape preview does not update automatically when the Script.c file is changed, but a simple click on it re-generates it.

=== Bug Reports and Feature Requests ===

Bug Reports and Feature Requests can be reported in the [http://bugs.openclonk.org bug tracker]. There is a category for mape.

Development

2014-06-10T16:42:37Z

Newton:

__NOTOC__
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 - [http://www.openclonk.org/nightly-builds/ www.openclonk.org/nightly-builds/]
* Blog - [http://blog.openclonk.org blog.openclonk.org]
* Changelog - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]
* Browse source - [http://git.openclonk.org/openclonk.git/tree/refs/heads/master git.openclonk.org/openclonk.git/tree/refs/heads/master]

=== 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 - [irc://irc.euirc.net/openclonk-dev/ #openclonk-dev] on irc.euirc.net (Problems connecting? Use irc.ham.de.euirc.net)
* Bugtracker - [http://bugs.openclonk.org bugs.openclonk.org]
* Forum - [http://forum.openclonk.org 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 [http://docs.openclonk.org/en/sdk/ docs.openclonk.org/en/sdk/]
* Forum - [http://forum.openclonk.org forum.openclonk.org]
* Style Guide - [http://wiki.openclonk.org/w/C4Script_Style_Guidelines wiki.openclonk.org/w/C4Script_Style_Guidelines]
* Contribute changes - [[Git Workflow]]
* [http://crucible.openclonk.org Crucible] for code review

=== 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 - [http://wiki.openclonk.org/w/Building_with_Windows wiki.openclonk.org/w/Building_with_Windows]
* General instructions - [http://wiki.openclonk.org/w/Build_OpenClonk wiki.openclonk.org/w/Build_OpenClonk]
* Git Workflow Guide - [http://wiki.openclonk.org/w/Git_Workflow wiki.openclonk.org/w/Git_Workflow]
* Git Repository - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]
* Source Code Structure - [http://wiki.openclonk.org/w/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? - [[GSoC2011Ideas|Ideas page]]
* Debugging synchronization losses - [http://wiki.openclonk.org/w/Sync_losses wiki.openclonk.org/w/Sync_Losses]
* Style Guide - [http://wiki.openclonk.org/w/Style_Guidelines wiki.openclonk.org/w/Style_Guidelines]
* Forum, developers' corner - [http://forum.openclonk.org/board_show.pl?bid=5 forum.openclonk.org]
* Contribute changes - [[Git Workflow]]

=== Internal Links ===

[http://londeroth.org/~ck/oc-release/oc-release.cgi 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 | license stuff]] here.

Script: CR to OC

2014-04-29T05:40:11Z

Newton: /* Obsolete stuff */

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage.

A good example:
<code type="c4script">
// create rock, the owner of the rock is the controller of the calling object
CreateObject(Rock, 0, 10);
// same as above
CreateObject(Rock, 0, 10, nil);
// create rock, the owner is player 0!
CreateObject(Rock, 0, 10, 0);
</code>
So, nil is not 0. It is normally used to deliberately not specify optional parameters.

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= Obsolete stuff =
The backward compatibility was dropped, so certain deprecated/obsolete stuff was finally dropped. Most of this will not apply to someone wanting to convert something from Clonk Rage. A non exhaustive list:

* <tt>#strict</tt> is gone. All scripts are "strict".
* constants like <tt>C4D_*</tt>, <tt>COMD_*</tt>, <tt>VIS_*</tt> or <tt>OCF_*</tt> are now only defined as constants and not also as functions: e.g. <tt>C4D_Living<s>()</s></tt>
* Arithmetic functions like <tt>Sum()</tt>, <tt>Div()</tt>, <tt>Mul()</tt>, ... and logic functions like <tt>GreaterThan()</tt>, <tt>And()</tt>, <tt>Not</tt>, ... are gone. Use operators.
* Numbered variables like <tt>Global()</tt>, <tt>Local()</tt>, <tt>EffectVar()</tt> are gone.

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>
Graphics like these will be shown at 1:1 if zoomed in x4.

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

= Map Scripts =
Additionally to static bitmap landscapes and dynamic Landscape.txt landscapes, one can define dynamic maps in script, also at runtime. The old Landscape.txt landscape generation is not obsolete but can still be used. [http://docs.openclonk.org/en/sdk/script/MapScript.html See reference].

= Controls =
The player controls are defined completely in script now, using PlayerControls.txt. So, to create controls similar as they were in Clonk Rage should be possible. Even on a per-scenario basis. [http://docs.openclonk.org/en/sdk/playercontrols.html See reference].

Script: CR to OC

2014-04-29T05:39:40Z

Newton: /* Obsolete stuff */

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage.

A good example:
<code type="c4script">
// create rock, the owner of the rock is the controller of the calling object
CreateObject(Rock, 0, 10);
// same as above
CreateObject(Rock, 0, 10, nil);
// create rock, the owner is player 0!
CreateObject(Rock, 0, 10, 0);
</code>
So, nil is not 0. It is normally used to deliberately not specify optional parameters.

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= Obsolete stuff =
The backward compatibility was dropped, so certain deprecated/obsolete stuff was finally dropped. Most of this will not apply to someone wanting to convert something from Clonk Rage. A non exhaustive list:

* <tt>#strict</tt> is gone. All scripts are "strict".
* constants like <tt>C4D_*</tt>, <tt>COMD_*</tt>, <tt>VIS_*</tt> or <tt>OCF_*</tt> are now only defined as constants and not also as functions: e.g. <tt>C4D_Living<s>()</s></tt>
* Arithmetic functions like <tt>Sum()</tt>, <tt>Div()</tt>, <tt>Mul()</tt>, ... and logic functions like <tt>GreaterThan()</tt>, <tt>And()</tt>, <tt>Not</tt>, ... are gone. Use operators.
* Numbered variables like <tt>Global</tt>(), <tt>Local</tt>, <tt>EffectVar</tt> are gone.

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>
Graphics like these will be shown at 1:1 if zoomed in x4.

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

= Map Scripts =
Additionally to static bitmap landscapes and dynamic Landscape.txt landscapes, one can define dynamic maps in script, also at runtime. The old Landscape.txt landscape generation is not obsolete but can still be used. [http://docs.openclonk.org/en/sdk/script/MapScript.html See reference].

= Controls =
The player controls are defined completely in script now, using PlayerControls.txt. So, to create controls similar as they were in Clonk Rage should be possible. Even on a per-scenario basis. [http://docs.openclonk.org/en/sdk/playercontrols.html See reference].

Script: CR to OC

2014-04-29T05:39:01Z

Newton: add section obsolete stuff

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage.

A good example:
<code type="c4script">
// create rock, the owner of the rock is the controller of the calling object
CreateObject(Rock, 0, 10);
// same as above
CreateObject(Rock, 0, 10, nil);
// create rock, the owner is player 0!
CreateObject(Rock, 0, 10, 0);
</code>
So, nil is not 0. It is normally used to deliberately not specify optional parameters.

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= Obsolete stuff =
The backward compatibility was dropped, so certain deprecated/obsolete stuff was finally dropped. So most of this will not apply to someone wanting to convert something from Clonk Rage. A non exhaustive list:

* <tt>#strict</tt> is gone. All scripts are "strict".
* constants like <tt>C4D_*</tt>, <tt>COMD_*</tt>, <tt>VIS_</tt> or <tt>OCF_*</tt> are now only defined as constants and not also as functions: e.g. <tt>C4D_Living<s>()</s></tt>
* Arithmetic functions like <tt>Sum()</tt>, <tt>Div()</tt>, <tt>Mul()</tt>, ... and logic functions like <tt>GreaterThan()</tt>, <tt>And()</tt>, <tt>Not</tt>, ... are gone. Use operators.
* Numbered variables like <tt>Global</tt>(), <tt>Local</tt>, <tt>EffectVar</tt> are gone.

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>
Graphics like these will be shown at 1:1 if zoomed in x4.

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

= Map Scripts =
Additionally to static bitmap landscapes and dynamic Landscape.txt landscapes, one can define dynamic maps in script, also at runtime. The old Landscape.txt landscape generation is not obsolete but can still be used. [http://docs.openclonk.org/en/sdk/script/MapScript.html See reference].

= Controls =
The player controls are defined completely in script now, using PlayerControls.txt. So, to create controls similar as they were in Clonk Rage should be possible. Even on a per-scenario basis. [http://docs.openclonk.org/en/sdk/playercontrols.html See reference].

Script: CR to OC

2014-04-29T05:12:00Z

Newton: /* zoomed Graphics.png */

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage.

A good example:
<code type="c4script">
// create rock, the owner of the rock is the controller of the calling object
CreateObject(Rock, 0, 10);
// same as above
CreateObject(Rock, 0, 10, nil);
// create rock, the owner is player 0!
CreateObject(Rock, 0, 10, 0);
</code>
So, nil is not 0. It is normally used to deliberately not specify optional parameters.

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>
Graphics like these will be shown at 1:1 if zoomed in x4.

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

= Map Scripts =
Additionally to static bitmap landscapes and dynamic Landscape.txt landscapes, one can define dynamic maps in script, also at runtime. The old Landscape.txt landscape generation is not obsolete but can still be used. [http://docs.openclonk.org/en/sdk/script/MapScript.html See reference].

= Controls =
The player controls are defined completely in script now, using PlayerControls.txt. So, to create controls similar as they were in Clonk Rage should be possible. Even on a per-scenario basis. [http://docs.openclonk.org/en/sdk/playercontrols.html See reference].

Script: CR to OC

2014-04-29T05:10:59Z

Newton: add example to nil value

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage.

A good example:
<code type="c4script">
// create rock, the owner of the rock is the controller of the calling object
CreateObject(Rock, 0, 10);
// same as above
CreateObject(Rock, 0, 10, nil);
// create rock, the owner is player 0!
CreateObject(Rock, 0, 10, 0);
</code>
So, nil is not 0. It is normally used to deliberately not specify optional parameters.

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

= Map Scripts =
Additionally to static bitmap landscapes and dynamic Landscape.txt landscapes, one can define dynamic maps in script, also at runtime. The old Landscape.txt landscape generation is not obsolete but can still be used. [http://docs.openclonk.org/en/sdk/script/MapScript.html See reference].

= Controls =
The player controls are defined completely in script now, using PlayerControls.txt. So, to create controls similar as they were in Clonk Rage should be possible. Even on a per-scenario basis. [http://docs.openclonk.org/en/sdk/playercontrols.html See reference].

Script: CR to OC

2014-03-22T06:11:52Z

Newton: controls

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

= Map Scripts =
Additionally to static bitmap landscapes and dynamic Landscape.txt landscapes, one can define dynamic maps in script, also at runtime. The old Landscape.txt landscape generation is not obsolete but can still be used. [http://docs.openclonk.org/en/sdk/script/MapScript.html See reference].

= Controls =
The player controls are defined completely in script now, using PlayerControls.txt. So, to create controls similar as they were in Clonk Rage should be possible. Even on a per-scenario basis. [http://docs.openclonk.org/en/sdk/playercontrols.html See reference].

Script: CR to OC

2014-03-22T06:02:13Z

Newton: add map scripts

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

= Map Scripts =
Additionally to static bitmap landscapes and dynamic Landscape.txt landscapes, one can define dynamic maps in script, also at runtime. The old Landscape.txt landscape generation is not obsolete but can still be used. [http://docs.openclonk.org/en/sdk/script/MapScript.html See reference].

Script: CR to OC

2014-03-22T05:58:48Z

Newton: add docs links

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

The reference has an overview over the [http://docs.openclonk.org/en/sdk/definition/properties.html object properties] and (remaining) [http://docs.openclonk.org/en/sdk/definition/defcore.html DefCore values].

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

Script: CR to OC

2014-03-22T05:56:55Z

Newton: add saving as scenario

If you are coming from ClonkRage scripting, you will find some new things in OpenClonk. Not much and not very difficult, but you will have to know them. 
This page does not explain every thing in detail, but should give you an overview.

= IDs =
Every object has an ID. In ClonkRage that were 4-character-strings like "CLNK" or "ROCK". In OpenClonk they can have any length and consist of the typical characters, for example "Clonk", "Rock", "Rule_NoPowerNeed". 
That makes code so much more readable!

= Proplists =
Proplists are what you might know from other languages as a "map". You can assign values to keys.
<code type="c4script">
var my_proplist = { foo = 3, bar = "Hello!" };
Log("%s %d", my_proplist.bar, my_proplist.foo);
// the following line does the same
Log("%s %d", my_proplist["bar"], my_proplist["foo"]);
// create new property!
my_proplist.test = 123;
</code>
A lot of things are now proplists, for example the objects:
<code type="c4script">
var clonk = FindObject(Find_ID(Clonk));
// print Name property of the clonk
Log("Hello, I am %s!", clonk.Name);
</code>
or effects and the ActMap (see below).

= ActMap =
The ActMap.txt is completely gone, you can declare actions directly in the script of an object now, like this: 
<code type="c4script">
local ActMap=
{
Attach =
{
Prototype = Action,
Name="Attach",
Procedure=DFA_ATTACH,
NextAction="Be",
Length=1,
FacetBase=1,
}
};
</code>
 
This has the positive effect that you can modify actions when the game is running!

= DefCore =
A lot of entries from the DefCore.txt went into script, too. Here an example from the axe script: 
<code type="c4script">
local Collectible = 1;
local Name = "$Name$";
local Description = "$Description$";
local UsageHelp = "$UsageHelp$";
local Rebuy = true;
local ChopStrength = 10;
</code>
This helps if you need your own entries. Sadly there is no system which DefCore entries have moved to script and which haven't. 
You can access those entries like properties in a proplist
<code type="c4script">
var axe = FindObject(Find_ID(Axe));
// can collect the axe?
if (axe.Collectible)
Collect(axe);
</code>

= nil value =
Variables can now have the value "nil" which simply stands for "nothing". An unassigned variable will now have the value "nil" instead of "0" in ClonkRage

= -> for function calls =
In ClonkRage you could had "object" parameters for most of the functions. You could for example both write: 
<pre>
Collect(my_item, clonk); // or
clonk->Collect(my_item, 0);
</pre>
in OpenClonk a lot of the "object" parameters are gone and you should always use the direct call with the "->" 
<code type="c4script">
clonk->Collect(my_item);
// wrong: Collect(my_item, clonk);
</code>

= zoomed Graphics.png =
You can use 2D graphics just like in CR. But you can also defined versions for zoom levels so that the graphics do not look too pixelized at high zoom. You do that by simply putting a dot and the zoom level into the graphics name: 
<pre>
Graphics.4.png
Overlay.4.png
</pre>

= 3D Models =
As you know, OpenClonk now supports 3D models. I won't go over how to create a model here, that would be overkill. I'd much rather just give a short overview: 
Model files have to be named "Graphics.mesh", similarly to "Graphics.png". The skeleton-file name for the animation and the material-file name for the texture do not follow such a restriction. 
Note that materials have a global namespace, so two different objects with the material "Gold" would not work (Nugget & Idol, for example) - prefix your material names with the object ID (Nugget_Gold and Idol_Gold)! 
OpenClonk provides several functions to work with models or "meshes". Good entry points are: 
<code type="c4script">
int PlayAnimation(string animation, int slot, array position, array weight, int sibling);
</code>
and the properties "MeshTransformation" and "PictureTransformation" that you can use to f.e. rotate models.

= Effect variables =
Remember "EffectVar" from ClonkRage that you could use to store variables in effects? The effect is now a proplist and that means that you can simply assign properties to it if you need variables:
<code>
func FxMyEffectStart(object target, effect fx, bool temp)
{
// invent new property!
fx.max_time = 100;
}

func FxMyEffectTimer(object target, effect fx, int time)
{
if (time > fx.max_time) return -1;
Message("Not over yet!");
}
</code>
There are also some standard properties like "Interval" that you can use to change the interval at which Fx*Timer is called (see the [http://docs.openclonk.org/en/sdk/script/Effects.html#Properties reference])

= Scenario saving =
Remember the hassle with the "saving as scenario" in editor mode? There is no huge Objects.txt anymore, instead, all the objects placed in the editor mode are serialized into a script, Objects.c. Only standard properties are saved and only if they are different from the default. This makes scenarios created in the editor much more maintainable.

Each object can define certain properties which shall be saved on a scenario save, for example some switch will save its target object:

<code type="c4script">local target;

func SetTarget(object new_target) { target = new_target; return true; }

func SaveScenarioObject(props)
{
if (!inherited(props, ...)) return false;
if (target) props->AddCall("Target", this, "SetTarget", target);
return true;
}</code>

This results in the generation of this script on scenario save in Objects.c:

<code type="c4script">var door235 = CreateObject(Door,2354,124);
...
var switch001 = CreateObject(Switch,124,354);
switch001->SetTarget(door235);</code>

So, to make a complex object properly savable into a scenario, it needs to define which properties should be saved. See the [http://docs.openclonk.org/en/sdk/definition/script.html#ScenSave reference] for more information.

Development

2014-02-23T08:44:02Z

Newton: add link to crucible

__NOTOC__

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 - [http://www.openclonk.org/nightly-builds/ www.openclonk.org/nightly-builds/]
* Blog - [http://blog.openclonk.org blog.openclonk.org]
* Changelog - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]
* Browse source - [http://git.openclonk.org/openclonk.git/tree/refs/heads/master git.openclonk.org/openclonk.git/tree/refs/heads/master]

=== 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 - [irc://irc.euirc.net/openclonk-dev/ #openclonk-dev] on irc.euirc.net (Problems connecting? Use irc.ham.de.euirc.net)
* Bugtracker - [http://bugs.openclonk.org bugs.openclonk.org]
* Forum - [http://forum.openclonk.org 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 [http://docs.openclonk.org/en/sdk/ docs.openclonk.org/en/sdk/]
* Forum - [http://forum.openclonk.org forum.openclonk.org]
* Style Guide - [http://wiki.openclonk.org/w/C4Script_Style_Guidelines wiki.openclonk.org/w/C4Script_Style_Guidelines]
* Contribute changes - [[Git Workflow]]
* [http://crucible.openclonk.org Crucible] for code review

=== 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 - [http://wiki.openclonk.org/w/Building_with_Windows wiki.openclonk.org/w/Building_with_Windows]
* General instructions - [http://wiki.openclonk.org/w/Build_OpenClonk wiki.openclonk.org/w/Build_OpenClonk]
* Git Workflow Guide - [http://wiki.openclonk.org/w/Git_Workflow wiki.openclonk.org/w/Git_Workflow]
* Git Repository - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]
* Source Code Structure - [http://wiki.openclonk.org/w/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? - [[GSoC2011Ideas|Ideas page]]
* Debugging synchronization losses - [http://wiki.openclonk.org/w/Sync_losses wiki.openclonk.org/w/Sync_Losses]
* Style Guide - [http://wiki.openclonk.org/w/Style_Guidelines wiki.openclonk.org/w/Style_Guidelines]
* Forum, developers' corner - [http://forum.openclonk.org/board_show.pl?bid=5 forum.openclonk.org]
* Contribute changes - [[Git Workflow]]

=== Internal Links ===

[http://londeroth.org/~ck/oc-release/oc-release.cgi 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 | license stuff]] here.

C4Script Documentation

2014-02-16T09:31:17Z

Newton: /* Tutorials */

__NOTOC__
[[File:C4Script.png|right|frame]]
Like the previous Clonk titles, OpenClonk offers countless possibilites to create your own scenarios, objects and campaigns. Since [http://www.clonk.de/classics.php?lng=en Clonk 4], one of Clonk's most remarkable features has been it's extensibility. The complete content is scripted in C4Script, Clonk's own powerful scripting language, has been developed further since 1998. Now, it feels pretty much like a typical C-style scripting language. If you know other programming languages, you will have no problem to familarize yourself with C4Script and if you never programmed before, it can be a good introduction and practice to programming.

You may want to develop based on the latest game data there is. See the [http://www.openclonk.org/nightly-builds/ nightly builds] page for the most current builds.

== [http://docs.openclonk.org/en/sdk/ OpenClonk Documentation] ==

[[File:Cpem.gif|left|link=http://docs.openclonk.org/en/sdk/]] The [http://docs.openclonk.org/en/sdk/ documentation] is a complete reference for everything you need to know about the script language C4Script and its data structures, how the the game data is organized and about the APIs for e.g. dynamic landscape generation, using the particle or the effect system.
Note that the documentation is also still [http://docs.openclonk.org/de/sdk/ available in German], however it lacks maintenance, so always refer to the English version for recent stuff.

== [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit] ==

[[File:C4dt.png|left|52px|link=http://wiki.openclonk.org/w/Developing_Content_with_Eclipse]] The [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit], or short C4DT, is a plugin for Eclipse. Using Eclipse with C4DT for Clonk development makes it very comfortable as the editor offers many useful features for editing and debugging scripts you might know from other IDEs.

== Tutorials series ==
* [[Tutorial: Scenario Creation]]
* [[Tutorial: Map Generator - The Basics]]

== Further links ==
* [[Artists Guide|Graphics]] - Render and texture 3D-models
* [[Artists_Guide#Sounds_.26_Music|Sounds and music]] - Include sound effects and music into the game
* [[C4Script Style Guidelines]]
* [http://forum.openclonk.org/board_show.pl?bid=7 Scenario & Object Development forum]
* [[Git Workflow]] - How to use our repository
* [[Developers Guide]] - For engine developers

C4Script Documentation

2014-02-16T09:26:14Z

Newton: /* C4 Development Toolkit */

__NOTOC__
[[File:C4Script.png|right|frame]]
Like the previous Clonk titles, OpenClonk offers countless possibilites to create your own scenarios, objects and campaigns. Since [http://www.clonk.de/classics.php?lng=en Clonk 4], one of Clonk's most remarkable features has been it's extensibility. The complete content is scripted in C4Script, Clonk's own powerful scripting language, has been developed further since 1998. Now, it feels pretty much like a typical C-style scripting language. If you know other programming languages, you will have no problem to familarize yourself with C4Script and if you never programmed before, it can be a good introduction and practice to programming.

You may want to develop based on the latest game data there is. See the [http://www.openclonk.org/nightly-builds/ nightly builds] page for the most current builds.

== [http://docs.openclonk.org/en/sdk/ OpenClonk Documentation] ==

[[File:Cpem.gif|left|link=http://docs.openclonk.org/en/sdk/]] The [http://docs.openclonk.org/en/sdk/ documentation] is a complete reference for everything you need to know about the script language C4Script and its data structures, how the the game data is organized and about the APIs for e.g. dynamic landscape generation, using the particle or the effect system.
Note that the documentation is also still [http://docs.openclonk.org/de/sdk/ available in German], however it lacks maintenance, so always refer to the English version for recent stuff.

== [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit] ==

[[File:C4dt.png|left|52px|link=http://wiki.openclonk.org/w/Developing_Content_with_Eclipse]] The [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit], or short C4DT, is a plugin for Eclipse. Using Eclipse with C4DT for Clonk development makes it very comfortable as the editor offers many useful features for editing and debugging scripts you might know from other IDEs.

== Tutorials ==
* [[Tutorial: Scenario Creation]]
* [[Tutorial: Map Generator - The Basics]]

== Further links ==
* [[Artists Guide|Graphics]] - Render and texture 3D-models
* [[Artists_Guide#Sounds_.26_Music|Sounds and music]] - Include sound effects and music into the game
* [[C4Script Style Guidelines]]
* [http://forum.openclonk.org/board_show.pl?bid=7 Scenario & Object Development forum]
* [[Git Workflow]] - How to use our repository
* [[Developers Guide]] - For engine developers

C4Script Documentation

2014-02-16T09:25:32Z

Newton: /* Tutorials */

__NOTOC__
[[File:C4Script.png|right|frame]]
Like the previous Clonk titles, OpenClonk offers countless possibilites to create your own scenarios, objects and campaigns. Since [http://www.clonk.de/classics.php?lng=en Clonk 4], one of Clonk's most remarkable features has been it's extensibility. The complete content is scripted in C4Script, Clonk's own powerful scripting language, has been developed further since 1998. Now, it feels pretty much like a typical C-style scripting language. If you know other programming languages, you will have no problem to familarize yourself with C4Script and if you never programmed before, it can be a good introduction and practice to programming.

You may want to develop based on the latest game data there is. See the [http://www.openclonk.org/nightly-builds/ nightly builds] page for the most current builds.

== [http://docs.openclonk.org/en/sdk/ OpenClonk Documentation] ==

[[File:Cpem.gif|left|link=http://docs.openclonk.org/en/sdk/]] The [http://docs.openclonk.org/en/sdk/ documentation] is a complete reference for everything you need to know about the script language C4Script and its data structures, how the the game data is organized and about the APIs for e.g. dynamic landscape generation, using the particle or the effect system.
Note that the documentation is also still [http://docs.openclonk.org/de/sdk/ available in German], however it lacks maintenance, so always refer to the English version for recent stuff.

== [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit] ==

[[File:C4dt.png|left|64px|link=http://wiki.openclonk.org/w/Developing_Content_with_Eclipse]] The [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit], or short C4DT, is a plugin for Eclipse. Using Eclipse with C4DT for Clonk development makes it very comfortable as the editor offers many useful features for editing and debugging scripts you might know from other IDEs.

== Tutorials ==
* [[Tutorial: Scenario Creation]]
* [[Tutorial: Map Generator - The Basics]]

== Further links ==
* [[Artists Guide|Graphics]] - Render and texture 3D-models
* [[Artists_Guide#Sounds_.26_Music|Sounds and music]] - Include sound effects and music into the game
* [[C4Script Style Guidelines]]
* [http://forum.openclonk.org/board_show.pl?bid=7 Scenario & Object Development forum]
* [[Git Workflow]] - How to use our repository
* [[Developers Guide]] - For engine developers

C4Script Documentation

2014-02-16T09:23:09Z

Newton: add info from Content Developers Guide

__NOTOC__
[[File:C4Script.png|right|frame]]
Like the previous Clonk titles, OpenClonk offers countless possibilites to create your own scenarios, objects and campaigns. Since [http://www.clonk.de/classics.php?lng=en Clonk 4], one of Clonk's most remarkable features has been it's extensibility. The complete content is scripted in C4Script, Clonk's own powerful scripting language, has been developed further since 1998. Now, it feels pretty much like a typical C-style scripting language. If you know other programming languages, you will have no problem to familarize yourself with C4Script and if you never programmed before, it can be a good introduction and practice to programming.

You may want to develop based on the latest game data there is. See the [http://www.openclonk.org/nightly-builds/ nightly builds] page for the most current builds.

== [http://docs.openclonk.org/en/sdk/ OpenClonk Documentation] ==

[[File:Cpem.gif|left|link=http://docs.openclonk.org/en/sdk/]] The [http://docs.openclonk.org/en/sdk/ documentation] is a complete reference for everything you need to know about the script language C4Script and its data structures, how the the game data is organized and about the APIs for e.g. dynamic landscape generation, using the particle or the effect system.
Note that the documentation is also still [http://docs.openclonk.org/de/sdk/ available in German], however it lacks maintenance, so always refer to the English version for recent stuff.

== [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit] ==

[[File:C4dt.png|left|64px|link=http://wiki.openclonk.org/w/Developing_Content_with_Eclipse]] The [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4 Development Toolkit], or short C4DT, is a plugin for Eclipse. Using Eclipse with C4DT for Clonk development makes it very comfortable as the editor offers many useful features for editing and debugging scripts you might know from other IDEs.

== Tutorials ==
* [http://wiki.openclonk.org/w/Tutorial:_Scenario_Creation Tutorial: Scenario Creation]
* [http://wiki.openclonk.org/w/Tutorial:_Map_Generator_-_The_Basics Dynamic Map Generator]

== Further links ==
* [[Artists Guide|Graphics]] - Render and texture 3D-models
* [[Artists_Guide#Sounds_.26_Music|Sounds and music]] - Include sound effects and music into the game
* [[C4Script Style Guidelines]]
* [http://forum.openclonk.org/board_show.pl?bid=7 Scenario & Object Development forum]
* [[Git Workflow]] - How to use our repository
* [[Developers Guide]] - For engine developers

File:C4dt.png

2014-02-16T08:55:02Z

Newton: C4DT Icon

C4DT Icon

C4Script Documentation

2014-02-16T08:53:28Z

Newton: add icon for openclonk documentation

[[File:C4Script.png|right]]
Like the previous Clonk titles, OpenClonk offers countless possibilites to create your own scenarios, objects and campaigns. Since [http://www.clonk.de/classics.php?lng=en Clonk 4], one of Clonk's most remarkable features has been it's extensibility. The complete content is scripted in C4Script, Clonk's own powerful scripting language, has been developed further since 1998. Now, it feels pretty much like a typical C-style scripting language. If you know other programming languages, you will have no problem to familarize yourself with C4Script and if you never programmed before, it can be a good introduction and practice to programming.

[[File:Cpem.gif|left]] The function list and everything about the script language, the game data and the APIs is documented in our
'''[http://docs.openclonk.org/en/sdk/ OpenClonk Documentation]'''

You may want to [http://www.openclonk.org/download/ download] the latest game data first before you add or edit any game content. See the [http://www.openclonk.org/nightly-builds/ nightly builds] page for the most current builds.

== Further links ==
* [[Artists Guide|Graphics]] - Render and texture 3D-models
* [[Artists_Guide#Sounds_.26_Music|Sounds and music]] - Include sound effects and music into the game
* [[Content Developers Guide|Game content]] - including creating objects, scenarios and campaigns with C4Script
* [[Git Workflow]] - How to use our repository
* [[Developers Guide]] - For engine developers

File:Cpem.gif

2014-02-16T08:44:52Z

Newton: C4Script Documentation Icon

C4Script Documentation Icon

Dynamic Map Generator

2014-01-26T07:11:50Z

Newton: add note about Map.c

== Dynamic Map Generator ==

OpenClonk has a dynamic map generator that can be used to generate maps that look different everytime but still have specified recurring patterns, like lava likes, mountains, or sky islands. The documentation is available in the [http://docs.openclonk.org/en/sdk/scenario/MapCreatorS2.html C4Script reference here].
Mape is used to edit and display Landscape.txts, it doesn't support Map.c.

=== Mape ===

[[File:Mape.png|450px|border|right|Screenshot of Mape]]

Mape is a tool that shows a live preview of the generated mape as the Landscape.txt code is being typed. The tool is available from the [http://www.openclonk.org/nightly-builds/ Development Snapshots] page for all major platforms. Its source code lives in the OpenClonk git repository.

The tool is meant both for beginners and experts alike. Beginners can easily play around with all the possibilities and immediately see their effect on the generated map. Experts can easily tweak the map to their liking without having to restart the engine for every change they make.

The mape window has four panels. The upper right part is the largest one which is where the Landscape.txt code can be edited. The panel to the left of it shows the file system tree. This is where one can select the Material.ocg file to be loaded. This specifies the materials and textures available to the map generator. The loaded materials and textures can be seen at the bottom panel once loaded which provides an easy view to what materials and textures are available. Finally in the lower right corner there is a preview of the generated map which updates as one types. The status bar contains error messages from the Landscape generator in case the Landscape.txt code is not correct.

=== Tips and Tricks ===

* The options allow to specify the width and height of the generated mape. To avoid any surprises, especially when specifying parameters with pixels instead of percentages, this should always be set to the same size as the OpenClonk map that one plans to create.

* In the options there is also the possibility to use a fixed seed for the random number generator. This allows to always create the same map when using the same Landscape.txt code, even if it contains randomness. This can come handy when trying to get a part of the map right and one does not want the rest of the map to change with every keystroke.

* If the random seed is not fixed, the map preview can be clicked on to generate another version of the map using the same Landscape.txt code but the randomness is re-evaluated.

* For big maps, rendering the map can take a while, up to a few seconds. This considerably slows down the feedback one gets for changing little things here and there. In this case, one can comment out the parts of the map that one does not work on right now and concentrate only on one specific feature or aspect of it, and then put it all together in the end.

* For overlays that use algo=script, the Script.c file that contains the script function that is being evaluated by the algorithm needs to be in the same directory as the Landscape.txt file. Therefore the Landscape.txt file must be saved at least once before algo=script can be used, so that mape knows where to look for the Script.c file. The landscape preview does not update automatically when the Script.c file is changed, but a simple click on it re-generates it.

=== Bug Reports and Feature Requests ===

Bug Reports and Feature Requests can be reported in the [http://bugs.openclonk.org bug tracker]. There is a category for mape.

FAQ

2013-11-23T03:37:59Z

Newton: add faq

If you don't find your particular question answered here, post in the [http://forum.openclonk.org/ forum]! You don't need to register but can ask as Anonymous there.

__TOC__

=== I cannot start the game! What do I do? ===
For some people, the game crashes if they enable Triple Buffering for OpenGL in their graphics driver. Try disabling it:
If you have an AMD graphics card go into the Catalyst Control Center. (You will find it by typing ccc into the start menu on Windows). Go to Games and then 3D Application Settings. Scroll all the way down and at the very bottom un-select Triple Buffering.

If this doesn't help, describe your problem in the bugtracker and post any relevant information:
* There is a Clonk.log in your OpenClonk directory. On Windows, it's in C:\Users\[Username]\AppData\Roaming\OpenClonk\
* What's your video card? Are your drivers up-to-date? Intel Express Chipsets reportedly have problems with OpenGL
* Which version of this game are you using? Did you try out the latest development snapshot? Does the problem persist then?

=== I can not host a round on the internet! What can I do? ===

If you want to host a game on the internet and are behind a router, you need to forward the ports 11111-11113 (TCP & UDP) in your home router configuration.
How to forward the ports completely depends on your router software, so you have to refer to your router's manual there.

For more information on ports, see [[#Which ports does OpenClonk use?|Which ports does OpenClonk use?]]

=== Which ports does OpenClonk use? ===

OpenClonk uses the same ports as Clonk Rage. From the FAQ on clonk.de:

By default, Clonk uses port 11112 TCP and port 11113 UDP for game connections. For best speed it is recommended to forward both of these ports through your router or firewall.

For directly joining an IP address (without internet server) port 11111 TCP is required incoming on the host.

Automatic game discovery in LAN works through port 11114 UDP. If necessary, these ports can be adjusted in the options dialog. For other functions the game will connect to the internet and league server clonk.de on port 84 and port 11115 for additional hole punching.

=== How do I submit a patch? ===
This answer assumes that you are using TortoiseGit. After you [[Git Workflow|checked out the source code]] and made your changes, you need to ''commit'' these changes. Afterwards, you can use the context menu to create a patch. This will create a new file which you can paste into a forum post. If you made or changed a binary file, please also attach it to your post.

If you use GitHub, you can also create a pull request for [https://github.com/openclonk/openclonk our project on GitHub]. Be advised however that the repository on GitHub is just a mirror of our repository.

=== Why is this page in English? Isn't Clonk a German game? ===
Clonk has been a German shareware game and thus its community has been mainly German. With the switch to the English language for the OpenClonk community, we intended to widen the community to an international level and make it possible for non-Germans to contribute to and participate in OpenClonk.
However, there is a German subforum now.

And of course, German, as well as other languages will continue to be supported in the game. Just the ''development'' and the community of OpenClonk will be in English.

=== Why did you start from scratch regarding the game content? ===
During shareware Clonk development, the game content stayed mainly about the same and was just extended by add-ons. This and the decision to keep the game as backward compatible as possible blocked lots of good changes and new concepts that could have been introduced in the game.

OpenClonk is a different game than the old Clonk series, it is not be just a sequel in the fashion of previous Clonk development. The aim of OpenClonk is not to replace Clonk Rage by "making it better" while keeping everything as it was before.
Clonk is about mining, about production lines and economy, fast and fiddly melees, known for flexibility in scenario design and whatnot. In this project, we aim to improve these strengths, which means that during OpenClonk development more fundamental changes must be (and are) possible.

Clonk Rage on the other hand will continue to exist alongside OpenClonk as the last title of the shareware series and will continue to include all that classical and that the community has come to love. Also read
[http://forum.openclonk.org/topic_show.pl?pid=1677#pid1677 this old forum discussion] on this topic.

=== Will you convert all those great Clonk Rage expansions for OpenClonk? ===
No, and we never will. OpenClonk is not backwards compatible with Clonk Rage, and never will be. We have broken ties with the old game content which all these expansions rely on. Hence the name, they are expansions for Clonk Rage. Specifically, Clonk Rage. OpenClonk is a different game with different game content, graphics, and script language, and therefore cannot have it's game content expanded with expansions designed for a completely different game.

=== Am I able to play with several players on one PC? ===
Generally yes. However, currently this is not possible yet.

=== Where can I upload / download mods for OpenClonk? Are there any? ===
Have a look in the [http://forum.openclonk.org/board_show.pl?bid=18 Player Creations board] in the forum. You might also want to check the [http://www.ccan.de CCAN]

=== Will there be keyboard-only controls? ===
No. OpenClonk is played with keyboard and mouse as the whole game is designed to utilize the advantages of mouse control. This adds a completely new set of gameplay possibilities to the game that would never have been possible in the shareware Clonk titles. However, gamepad controls are supported in the game and they work quite well considering that a gamepad doesn't have a pointing device.
However you can create your own keyboard-only control scheme based on the gamepad control scheme.

=== Are other Clonk games available as source code? ===
The source code for most older Clonk versions [http://www.clonk.de/source.php is available from Redwolf Design]. Here is a list of modified versions:
* [http://wiki.gp2x.org/articles/c/l/o/Clonk2X.html Clonk Planet for GP2x]
* [http://www.goldwipf.de/ The GWE] ([http://www.ccan.de/cgi-bin/ccan/ccan-view.pl?a=view&i=5757 download from CCAN])

=== Is there an editor for OpenClonk? ===
Yes, the [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4DT], the Clonk Development Tools for Eclipse, maintained by Mortimer. Eclipse is a powerful open source IDE that you will have heard of if you ever developed in Java. C4DT is a plugin for Eclipse that makes it possible to develop for Clonk in C4Script and even debug your code one-instruction-at-a-time using this powerful IDE.

The old explorer-like Editor.exe that you might know from Clonk Rage doesn't exist anymore in OpenClonk. However, the editor mode still exists for drawing and designing scenarios. Just start clonk with the commandline parameter ''--editor''.

For more information on how to develop content for the game, see the [[C4Script Documentation]].

=== How can I create my own game content? ===
If you are looking to develop your own game content for or based on OpenClonk, have a look at the [[C4Script Documentation]], you should find everything there. See also a related FAQ answer: [[#Is there an editor for OpenClonk?|Is there an editor for OpenClonk?]]

If you are interested in getting involved and contributing to OpenClonk, this introduction on [[Development|development]] should make you happy :-).
For any other open questions regarding this, consider dropping by in our [http://forum.openclonk.org/ forum] or in our [irc://irc.euirc.net/openclonk IRC channel]!

=== What is the newest version? 5 or 3? ===
There has been some confusion regarding the version numbers of OpenClonk, so here is a little explanation: The full (''engine'') version number of for example OpenClonk 3.2 is 5.3.2 -
;5 = OpenClonk (the OC engine is a further development of [http://www.clonk.de/ Clonk Rage] which had 4 as it's first version number)
;3 = 3rd major release
;2 = 2nd update of the major release

=== Where can I report bugs? ===
In the [http://bugs.openclonk.org bugtracker].

=== How can I build OpenClonk myself? ===
Check out [[Build_OpenClonk|this tutorial]].

FAQ

2013-11-06T04:38:31Z

Newton: add info on port forwarding

If you don't find your particular question answered here, post in the [http://forum.openclonk.org/ forum]! You don't need to register but can ask as Anonymous there.

__TOC__

=== I cannot start the game! What do I do? ===
For some people, the game crashes if they enable Triple Buffering for OpenGL in their graphics driver. Try disabling it:
If you have an AMD graphics card go into the Catalyst Control Center. (You will find it by typing ccc into the start menu on Windows). Go to Games and then 3D Application Settings. Scroll all the way down and at the very bottom un-select Triple Buffering.

If this doesn't help, describe your problem in the bugtracker and post any relevant information:
* There is a Clonk.log in your OpenClonk directory. On Windows, it's in C:\Users\[Username]\AppData\Roaming\OpenClonk\
* What's your video card? Are your drivers up-to-date? Intel Express Chipsets reportedly have problems with OpenGL
* Which version of this game are you using? Did you try out the latest development snapshot? Does the problem persist then?

=== I can not host a round on the internet! What can I do? ===

If you want to host a game on the internet and are behind a router, you need to forward the ports 11111-11113 (TCP & UDP) in your home router configuration.
How to forward the ports completely depends on your router software, so you have to refer to your router's manual there.

For more information on ports, see [[#Which ports does OpenClonk use?|Which ports does OpenClonk use?]]

=== Which ports does OpenClonk use? ===

OpenClonk uses the same ports as Clonk Rage. From the FAQ on clonk.de:

By default, Clonk uses port 11112 TCP and port 11113 UDP for game connections. For best speed it is recommended to forward both of these ports through your router or firewall.

For directly joining an IP address (without internet server) port 11111 TCP is required incoming on the host.

Automatic game discovery in LAN works through port 11114 UDP. If necessary, these ports can be adjusted in the options dialog. For other functions the game will connect to the internet and league server clonk.de on port 84 and port 11115 for additional hole punching.

=== How do I submit a patch? ===
This answer assumes that you are using TortoiseGit. After you [[Git Workflow|checked out the source code]] and made your changes, you need to ''commit'' these changes. Afterwards, you can use the context menu to create a patch. This will create a new file which you can paste into a forum post. If you made or changed a binary file, please also attach it to your post.

If you use GitHub, you can also create a pull request for [https://github.com/openclonk/openclonk our project on GitHub]. Be advised however that the repository on GitHub is just a mirror of our repository.

=== Why is this page in English? Isn't Clonk a German game? ===
Clonk has been a German shareware game and thus its community has been mainly German. With the switch to the English language for the OpenClonk community, we intended to widen the community to an international level and make it possible for non-Germans to contribute to and participate in OpenClonk.
However, there is a German subforum now.

And of course, German, as well as other languages will continue to be supported in the game. Just the ''development'' and the community of OpenClonk will be in English.

=== Why did you start from scratch regarding the game content? ===
During shareware Clonk development, the game content stayed mainly about the same and was just extended by add-ons. This and the decision to keep the game as backward compatible as possible blocked lots of good changes and new concepts that could have been introduced in the game.

OpenClonk is a different game than the old Clonk series, it is not be just a sequel in the fashion of previous Clonk development. The aim of OpenClonk is not to replace Clonk Rage by "making it better" while keeping everything as it was before.
Clonk is about mining, about production lines and economy, fast and fiddly melees, known for flexibility in scenario design and whatnot. In this project, we aim to improve these strengths, which means that during OpenClonk development more fundamental changes must be (and are) possible.

Clonk Rage on the other hand will continue to exist alongside OpenClonk as the last title of the shareware series and will continue to include all that classical and that the community has come to love. Also read
[http://forum.openclonk.org/topic_show.pl?pid=1677#pid1677 this old forum discussion] on this topic.

=== Will you convert all those great Clonk Rage expansions for OpenClonk? ===
No, and we never will. OpenClonk is not backwards compatible with Clonk Rage, and never will be. We have broken ties with the old game content which all these expansions rely on. Hence the name, they are expansions for Clonk Rage. Specifically, Clonk Rage. OpenClonk is a different game with different game content, graphics, and script language, and therefore cannot have it's game content expanded with expansions designed for a completely different game.

=== Am I able to play with several players on one PC? ===
Generally yes. However, currently this is not possible yet.

=== Will there be keyboard-only controls? ===
No. OpenClonk is played with keyboard and mouse as the whole game is designed to utilize the advantages of mouse control. This adds a completely new set of gameplay possibilities to the game that would never have been possible in the shareware Clonk titles. However, gamepad controls are supported in the game and they work quite well considering that a gamepad doesn't have a pointing device.
However you can create your own keyboard-only control scheme based on the gamepad control scheme.

=== Are other Clonk games available as source code? ===
The source code for most older Clonk versions [http://www.clonk.de/source.php is available from Redwolf Design]. Here is a list of modified versions:
* [http://wiki.gp2x.org/articles/c/l/o/Clonk2X.html Clonk Planet for GP2x]
* [http://www.goldwipf.de/ The GWE] ([http://www.ccan.de/cgi-bin/ccan/ccan-view.pl?a=view&i=5757 download from CCAN])

=== Is there an editor for OpenClonk? ===
Yes, the [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4DT], the Clonk Development Tools for Eclipse, maintained by Mortimer. Eclipse is a powerful open source IDE that you will have heard of if you ever developed in Java. C4DT is a plugin for Eclipse that makes it possible to develop for Clonk in C4Script and even debug your code one-instruction-at-a-time using this powerful IDE.

The old explorer-like Editor.exe that you might know from Clonk Rage doesn't exist anymore in OpenClonk. However, the editor mode still exists for drawing and designing scenarios. Just start clonk with the commandline parameter ''--editor''.

For more information on how to develop content for the game, see the [[C4Script Documentation]].

=== How can I create my own game content? ===
If you are looking to develop your own game content for or based on OpenClonk, have a look at the [[C4Script Documentation]], you should find everything there. See also a related FAQ answer: [[#Is there an editor for OpenClonk?|Is there an editor for OpenClonk?]]

If you are interested in getting involved and contributing to OpenClonk, this introduction on [[Development|development]] should make you happy :-).
For any other open questions regarding this, consider dropping by in our [http://forum.openclonk.org/ forum] or in our [irc://irc.euirc.net/openclonk IRC channel]!

=== What is the newest version? 5 or 3? ===
There has been some confusion regarding the version numbers of OpenClonk, so here is a little explanation: The full (''engine'') version number of for example OpenClonk 3.2 is 5.3.2 -
;5 = OpenClonk (the OC engine is a further development of [http://www.clonk.de/ Clonk Rage] which had 4 as it's first version number)
;3 = 3rd major release
;2 = 2nd update of the major release

=== Where can I report bugs? ===
In the [http://bugs.openclonk.org bugtracker].

=== How can I build OpenClonk myself? ===
Check out [[Build_OpenClonk|this tutorial]].

FAQ

2013-11-05T17:45:56Z

Newton: -> bugtracker

If you don't find your particular question answered here, post in the [http://forum.openclonk.org/ forum]! You don't need to register but can ask as Anonymous there.

__TOC__

=== I cannot start the game! What do I do? ===
For some people, the game crashes if they enable Triple Buffering for OpenGL in their graphics driver. Try disabling it:
If you have an AMD graphics card go into the Catalyst Control Center. (You will find it by typing ccc into the start menu on Windows). Go to Games and then 3D Application Settings. Scroll all the way down and at the very bottom un-select Triple Buffering.

If this doesn't help, describe your problem in the bugtracker and post any relevant information:
* There is a Clonk.log in your OpenClonk directory. On Windows, it's in C:\Users\[Username]\AppData\Roaming\OpenClonk\
* What's your video card? Are your drivers up-to-date? Intel Express Chipsets reportedly have problems with OpenGL
* Which version of this game are you using? Did you try out the latest development snapshot? Does the problem persist then?

=== How do I submit a patch? ===
This answer assumes that you are using TortoiseGit. After you [[Git Workflow|checked out the source code]] and made your changes, you need to ''commit'' these changes. Afterwards, you can use the context menu to create a patch. This will create a new file which you can paste into a forum post. If you made or changed a binary file, please also attach it to your post.

If you use GitHub, you can also create a pull request for [https://github.com/openclonk/openclonk our project on GitHub]. Be advised however that the repository on GitHub is just a mirror of our repository.

=== Why is this page in English? Isn't Clonk a German game? ===
Clonk has been a German shareware game and thus its community has been mainly German. With the switch to the English language for the OpenClonk community, we intended to widen the community to an international level and make it possible for non-Germans to contribute to and participate in OpenClonk.
However, there is a German subforum now.

And of course, German, as well as other languages will continue to be supported in the game. Just the ''development'' and the community of OpenClonk will be in English.

=== Why did you start from scratch regarding the game content? ===
During shareware Clonk development, the game content stayed mainly about the same and was just extended by add-ons. This and the decision to keep the game as backward compatible as possible blocked lots of good changes and new concepts that could have been introduced in the game.

OpenClonk is a different game than the old Clonk series, it is not be just a sequel in the fashion of previous Clonk development. The aim of OpenClonk is not to replace Clonk Rage by "making it better" while keeping everything as it was before.
Clonk is about mining, about production lines and economy, fast and fiddly melees, known for flexibility in scenario design and whatnot. In this project, we aim to improve these strengths, which means that during OpenClonk development more fundamental changes must be (and are) possible.

Clonk Rage on the other hand will continue to exist alongside OpenClonk as the last title of the shareware series and will continue to include all that classical and that the community has come to love. Also read
[http://forum.openclonk.org/topic_show.pl?pid=1677#pid1677 this old forum discussion] on this topic.

=== Will you convert all those great Clonk Rage expansions for OpenClonk? ===
No, and we never will. OpenClonk is not backwards compatible with Clonk Rage, and never will be. We have broken ties with the old game content which all these expansions rely on. Hence the name, they are expansions for Clonk Rage. Specifically, Clonk Rage. OpenClonk is a different game with different game content, graphics, and script language, and therefore cannot have it's game content expanded with expansions designed for a completely different game.

=== Am I able to play with several players on one PC? ===
Generally yes. However, currently this is not possible yet.

=== Will there be keyboard-only controls? ===
No. OpenClonk is played with keyboard and mouse as the whole game is designed to utilize the advantages of mouse control. This adds a completely new set of gameplay possibilities to the game that would never have been possible in the shareware Clonk titles. However, gamepad controls are supported in the game and they work quite well considering that a gamepad doesn't have a pointing device.
However you can create your own keyboard-only control scheme based on the gamepad control scheme.

=== Are other Clonk games available as source code? ===
The source code for most older Clonk versions [http://www.clonk.de/source.php is available from Redwolf Design]. Here is a list of modified versions:
* [http://wiki.gp2x.org/articles/c/l/o/Clonk2X.html Clonk Planet for GP2x]
* [http://www.goldwipf.de/ The GWE] ([http://www.ccan.de/cgi-bin/ccan/ccan-view.pl?a=view&i=5757 download from CCAN])

=== Is there an editor for OpenClonk? ===
Yes, the [http://wiki.openclonk.org/w/Developing_Content_with_Eclipse C4DT], the Clonk Development Tools for Eclipse, maintained by Mortimer. Eclipse is a powerful open source IDE that you will have heard of if you ever developed in Java. C4DT is a plugin for Eclipse that makes it possible to develop for Clonk in C4Script and even debug your code one-instruction-at-a-time using this powerful IDE.

The old explorer-like Editor.exe that you might know from Clonk Rage doesn't exist anymore in OpenClonk. However, the editor mode still exists for drawing and designing scenarios. Just start clonk with the commandline parameter ''--editor''.

For more information on how to develop content for the game, see the [[C4Script Documentation]].

=== How can I create my own game content? ===
If you are looking to develop your own game content for or based on OpenClonk, have a look at the [[C4Script Documentation]], you should find everything there. See also a related FAQ answer: [[#Is there an editor for OpenClonk?|Is there an editor for OpenClonk?]]

If you are interested in getting involved and contributing to OpenClonk, this introduction on [[Development|development]] should make you happy :-).
For any other open questions regarding this, consider dropping by in our [http://forum.openclonk.org/ forum] or in our [irc://irc.euirc.net/openclonk IRC channel]!

=== What is the newest version? 5 or 3? ===
There has been some confusion regarding the version numbers of OpenClonk, so here is a little explanation: The full (''engine'') version number of for example OpenClonk 3.2 is 5.3.2 -
;5 = OpenClonk (the OC engine is a further development of [http://www.clonk.de/ Clonk Rage] which had 4 as it's first version number)
;3 = 3rd major release
;2 = 2nd update of the major release

=== Where can I report bugs? ===
In the [http://bugs.openclonk.org bugtracker].

=== How can I build OpenClonk myself? ===
Check out [[Build_OpenClonk|this tutorial]].