https://wiki.openclonk.org/api.php?action=feedcontributions&feedformat=atom&user=Maikel 2026-04-06T09:14:30Z User contributions MediaWiki 1.44.3 https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1875 2018-05-14T19:12:33Z

<p>Maikel: /* Room Icon */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing<br /> create_tower.py --pack<br /> will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository somewhere in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. When you save the room, it will warn about any possible problems, for example a missing entrance. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> Alternatively you can use the editor scenario template which already has the room entrance and exit objects.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Room Icon ====<br /> Each room needs a unique icon so that the player can easily identify the respective rooms. The icon is taken from the graphics of Room&lt;InsertName&gt;.ocd, where the default graphic is a brick frame of 128x128 pixels. You can overlay your icon on the existing graphic ([https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Graphics.png Graphics.png]) using an editor like GIMP and save the file. Also you can change the default background color by modifying and combining the files [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/GraphicsBackground.png GraphicsBackground.png] and [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/GraphicsFrame.png GraphicsFrame.png]. These come at a resolution of 256x256 pixels, but you can take any between 128 and 256 pixels. Be sure to modify the Picture entry in the DefCore. Alternatively, you can also make a highly zoomed in screenshot of your room and overlay the GraphicsFrame.png on top.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1863 2018-04-28T20:52:43Z

<p>Maikel: /* Room Icon */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing<br /> create_tower.py --pack<br /> will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository somewhere in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. When you save the room, it will warn about any possible problems, for example a missing entrance. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> Alternatively you can use the editor scenario template which already has the room entrance and exit objects.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Room Icon ====<br /> Each room needs a unique icon so that the player can easily identify the respective rooms. The icon is taken from the graphics of Room&lt;InsertName&gt;.ocd, where the default graphic is a brick frame of 128x128 pixels. You can overlay your icon on the existing graphic using an editor like GIMP and save the file. Also you can change the default background color by modifying and combining the files GraphicsBackground.png and GraphicsFrame.png. These come at a resolution of 256x256 pixels, but you can take any between 128 and 256 pixels. Be sure to modify the Picture entry in the DefCore. Alternatively, you can also make a highly zoomed in screenshot of your room and overlay the GraphicsFrame.png on top.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1862 2018-04-28T20:34:28Z

<p>Maikel: /* Creating a Room */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing<br /> create_tower.py --pack<br /> will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository somewhere in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. When you save the room, it will warn about any possible problems, for example a missing entrance. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> Alternatively you can use the editor scenario template which already has the room entrance and exit objects.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Room Icon ====<br /> Each room needs a unique icon so that the player can easily identify the respective rooms. The icon is taken from the graphics of Room&lt;InsertName&gt;.ocd, where the default graphic is a brick frame of 128x128 pixels. You can overlay your icon on the existing graphic using an editor like GIMP and save the file. Also you can change the default background color by modifying and combining the files GraphicsBackground.png and GraphicsFrame.png. These come at a resolution of 256x256 pixels, but you can take any between 128 and 256 pixels. Be sure to modify the Picture entry in the DefCore.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1857 2018-02-05T20:33:54Z

<p>Maikel: /* Editing &amp; Saving */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing<br /> create_tower.py --pack<br /> will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository somewhere in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. When you save the room, it will warn about any possible problems, for example a missing entrance. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> Alternatively you can use the editor scenario template which already has the room entrance and exit objects.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1856 2018-02-05T20:30:16Z

<p>Maikel: /* Cloning the Tower Repository */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing<br /> create_tower.py --pack<br /> will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository somewhere in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> Alternatively you can use the editor scenario template which already has the room entrance and exit objects.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Release_Steps&diff=1855 2018-02-04T20:28:54Z

<p>Maikel: </p> <hr /> <div>__NOTOC__<br /> 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.<br /> <br /> === Before Release ===<br /> <br /> Steps to do before the release, and after the feature freeze.<br /> <br /> * If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.<br /> * Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].<br /> * Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.<br /> * Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.<br /> <br /> === Release ===<br /> <br /> 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.<br /> <br /> * Optional: Update all Version.txt files and Version= entries in planet/ to the new version number.<br /> * '''Update the Version.txt''' to the new version number and put the extra version in Version.txt to FALSE. Commit and push.<br /> * Then go to the '''[http://londeroth.org/~ck/oc-release/oc-release.cgi release button]''' and release from the correct branch.<br /> <br /> === After Release ===<br /> <br /> * '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y). '''Only push''' the tag if sure the release has worked.<br /> * '''Create a stable branch''' named stable-X for bugfix releases (if not already created).<br /> * '''Make announcements''' in our blog and in our forum.<br /> * 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.<br /> * Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.<br /> * '''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.<br /> <br /> === Optional ===<br /> <br /> * '''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].<br /> * Spread the word! More advertisement!</div>

Maikel https://wiki.openclonk.org/index.php?title=Release_Steps&diff=1854 2018-01-27T17:58:40Z

<p>Maikel: /* Release */</p> <hr /> <div>__NOTOC__<br /> 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.<br /> <br /> === Before Release ===<br /> <br /> Steps to do before the release, and after the feature freeze.<br /> <br /> * If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.<br /> * Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].<br /> * Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.<br /> * Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.<br /> <br /> === Release ===<br /> <br /> 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.<br /> <br /> * Optional: Update all Version.txt files in planet/ to the new version number.<br /> * '''Update the Version.txt''' to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.<br /> * '''Create a tag''' for the released changeset with the vX.Y tag (lightweight: git tag vX.Y). '''Only push''' the tag if sure the release has worked.<br /> * Then go to the '''[http://londeroth.org/~ck/oc-release/oc-release.cgi release button]''' and release from the correct branch.<br /> <br /> === After Release ===<br /> <br /> * '''Create a stable branch''' named stable-X for bugfix releases.<br /> * '''Make announcements''' in our blog and in our forum.<br /> * 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.<br /> * Notify an openclonk.org admin to '''mark this version as released in the bugtracker''' and add the next version to the roadmap.<br /> * '''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.<br /> <br /> === Optional ===<br /> <br /> * '''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].<br /> * Spread the word! More advertisement!</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1853 2018-01-21T14:04:50Z

<p>Maikel: /* Editing &amp; Saving */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing<br /> create_tower.py --pack<br /> will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> Alternatively you can use the editor scenario template which already has the room entrance and exit objects.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1852 2018-01-21T14:03:17Z

<p>Maikel: /* Download &amp; Play */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing<br /> create_tower.py --pack<br /> will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1851 2018-01-21T14:02:52Z

<p>Maikel: /* Download &amp; Play */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower. Executing create_tower.py --pack will create the OCTowerVX.Y.ocs packed scenario which can be played using the latest OpenClonk snapshot.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1823 2017-06-22T07:52:24Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed by the OpenClonk community and which do not appear in the main game. Download links to the latest version are provided if available as well as links to a repository. The OC Version indicates what version of OC is needed to play this creation.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> ! Main author(s)<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Sven2<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://forum.openclonk.org/topic_show.pl?tid=3268 Knüppeln]<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! KKenny<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://forum.openclonk.org/topic_show.pl?tid=2817 Lands of Mystery]<br /> ! <br /> !<br /> !<br /> ! Sayned<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Tower_of_Despair Tower of Despair]<br /> ! [[File:Download.png|text-bottom|x18px|link=https://mwf-data.clonkspot.org/60/14860/OCTowerV0.5.ocs]]<br /> ! [https://github.com/MDT-Maikel/OCTower GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel, Sven2<br /> |-<br /> ! [[File:Ocd.png|text-bottom|x18px|link=]]<br /> ! Some object<br /> !<br /> !<br /> !<br /> !<br /> |-<br /> |}<br /> <br /> Please complete this list by adding your own creations. The list is sorted alphabetically according to the name of the creation.</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1822 2017-06-22T07:51:02Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed by the OpenClonk community and which do not appear in the main game. Download links to the latest version are provided if available as well as links to a repository. The OC Version indicates what version of OC is needed to play this creation.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> ! Main author(s)<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Sven2<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! KKenny<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://forum.openclonk.org/topic_show.pl?tid=2817 Lands of Mystery]<br /> ! <br /> !<br /> !<br /> ! Sayned<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Tower_of_Despair Tower of Despair]<br /> ! [[File:Download.png|text-bottom|x18px|link=https://mwf-data.clonkspot.org/60/14860/OCTowerV0.5.ocs]]<br /> ! [https://github.com/MDT-Maikel/OCTower GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel, Sven2<br /> |-<br /> ! [[File:Ocd.png|text-bottom|x18px|link=]]<br /> ! Some object<br /> !<br /> !<br /> !<br /> !<br /> |-<br /> |}<br /> <br /> Please complete this list by adding your own creations. The list is sorted alphabetically according to the name of the creation.</div>

Maikel https://wiki.openclonk.org/index.php?title=Development&diff=1821 2017-06-22T07:42:09Z

<p>Maikel: /* Contribute Scripts or Game Content */</p> <hr /> <div>__NOTOC__<br /> 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.<br /> <br /> === Use Development Snapshots ===<br /> <br /> OpenClonk is continously in development. The &quot;current&quot; 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.<br /> <br /> * Development Snapshots - [http://www.openclonk.org/nightly-builds/ www.openclonk.org/nightly-builds/]<br /> * Blog - [http://blog.openclonk.org blog.openclonk.org]<br /> * Changelog - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]<br /> * Browse source - [http://git.openclonk.org/openclonk.git/tree/refs/heads/master git.openclonk.org/openclonk.git/tree/refs/heads/master]<br /> <br /> === Report Bugs ===<br /> <br /> 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.<br /> <br /> Here's how you can reach us:<br /> <br /> * IRC - [irc://irc.euirc.net/openclonk-dev #openclonk-dev] on irc.euirc.net (Problems connecting? Use irc.ham.de.euirc.net)<br /> * Bugtracker - [http://bugs.openclonk.org bugs.openclonk.org]<br /> * Forum - [http://forum.openclonk.org forum.openclonk.org]<br /> <br /> === Contribute Scripts or Game Content ===<br /> <br /> 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.<br /> <br /> * Developer Documentation [http://docs.openclonk.org/en/sdk/ docs.openclonk.org/en/sdk/]<br /> * Forum - [http://forum.openclonk.org forum.openclonk.org]<br /> * Style Guide - [http://wiki.openclonk.org/w/C4Script_Style_Guidelines wiki.openclonk.org/w/C4Script_Style_Guidelines]<br /> * Contribute changes - [[Git Workflow]]<br /> * [http://crucible.openclonk.org Crucible] for code review<br /> * Are you a sound artist? Here is a list of [[missing sounds]] you can contribute.<br /> * Game content external to the main game: [[List Of Community Creations]]<br /> <br /> === Build OpenClonk Yourself ===<br /> <br /> 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.<br /> <br /> * Tutorial for Windows - [http://wiki.openclonk.org/w/Building_with_Windows wiki.openclonk.org/w/Building_with_Windows]<br /> * General instructions - [http://wiki.openclonk.org/w/Build_OpenClonk wiki.openclonk.org/w/Build_OpenClonk]<br /> * Git Workflow Guide - [http://wiki.openclonk.org/w/Git_Workflow wiki.openclonk.org/w/Git_Workflow]<br /> * Git Repository - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]<br /> * Source Code Structure - [http://wiki.openclonk.org/w/Source_code_structure wiki.openclonk.org/w/Source_code_structure]<br /> <br /> === Hack the OpenClonk Engine ===<br /> <br /> 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.<br /> <br /> * Wondering where to start? - [[GSoC2011Ideas|Ideas page]]<br /> * Debugging synchronization losses - [http://wiki.openclonk.org/w/Sync_losses wiki.openclonk.org/w/Sync_Losses]<br /> * Style Guide - [http://wiki.openclonk.org/w/Style_Guidelines wiki.openclonk.org/w/Style_Guidelines]<br /> * Forum, developers' corner - [http://forum.openclonk.org/board_show.pl?bid=5 forum.openclonk.org]<br /> * Contribute changes - [[Git Workflow]]<br /> <br /> === Internal Links ===<br /> <br /> * [[Release Steps]]<br /> * [http://londeroth.org/~ck/oc-release/oc-release.cgi The release button]<br /> <br /> === Legal Stuff ===<br /> <br /> 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.</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1820 2017-06-22T07:41:49Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed by the OpenClonk community and which do not appear in the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> ! Main author(s)<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! KKenny<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Sven2<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Tower_of_Despair Tower of Despair]<br /> ! [[File:Download.png|text-bottom|x18px|link=https://mwf-data.clonkspot.org/60/14860/OCTowerV0.5.ocs]]<br /> ! [https://github.com/MDT-Maikel/OCTower GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel, Sven2<br /> |-<br /> ! [[File:Ocd.png|text-bottom|x18px|link=]]<br /> ! Some object<br /> !<br /> !<br /> !<br /> !<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1819 2017-06-22T07:41:29Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed by the OpenClonk community and which do not appear in the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> ! Main author(s)<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! KKenny<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Sven2<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Tower_of_Despair Tower of Despair]<br /> ! [[File:Download.png|text-bottom|x18px|link=https://mwf-data.clonkspot.org/60/14860/OCTowerV0.5.ocs]]<br /> ! [https://github.com/MDT-Maikel/OCTower GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> ! Maikel, Sven2<br /> |-<br /> ! [[File:Ocd.png|text-bottom|x18px|link=]]<br /> ! Some object<br /> !<br /> !<br /> !<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1818 2017-06-22T07:40:26Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed by the OpenClonk community and which do not appear in the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Tower_of_Despair Tower of Despair]<br /> ! [[File:Download.png|text-bottom|x18px|link=https://mwf-data.clonkspot.org/60/14860/OCTowerV0.5.ocs]]<br /> ! [https://github.com/MDT-Maikel/OCTower GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocd.png|text-bottom|x18px|link=]]<br /> ! Some object<br /> !<br /> !<br /> !<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_External_Creations&diff=1817 2017-06-22T07:39:45Z

<p>Maikel: Maikel moved page List Of External Creations to List Of Community Creations</p> <hr /> <div>#REDIRECT [[List Of Community Creations]]</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1816 2017-06-22T07:39:45Z

<p>Maikel: Maikel moved page List Of External Creations to List Of Community Creations</p> <hr /> <div>Below a list of all scenarios and objects developed outside of the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Tower_of_Despair Tower of Despair]<br /> ! [[File:Download.png|text-bottom|x18px|link=https://mwf-data.clonkspot.org/60/14860/OCTowerV0.5.ocs]]<br /> ! [https://github.com/MDT-Maikel/OCTower GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocd.png|text-bottom|x18px|link=]]<br /> ! Some object<br /> !<br /> !<br /> !<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1815 2017-06-21T18:37:51Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed outside of the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocf.png|text-bottom|x18px|link=]]<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocs.png|text-bottom|x18px|link=]]<br /> ! [http://wiki.openclonk.org/w/Tower_of_Despair Tower of Despair]<br /> ! [[File:Download.png|text-bottom|x18px|link=https://mwf-data.clonkspot.org/60/14860/OCTowerV0.5.ocs]]<br /> ! [https://github.com/MDT-Maikel/OCTower GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! [[File:Ocd.png|text-bottom|x18px|link=]]<br /> ! Some object<br /> !<br /> !<br /> !<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=File:Download.png&diff=1814 2017-06-21T18:32:17Z

<p>Maikel: </p> <hr /> <div></div>

Maikel https://wiki.openclonk.org/index.php?title=File:Ocs.png&diff=1813 2017-06-21T18:32:07Z

<p>Maikel: </p> <hr /> <div></div>

Maikel https://wiki.openclonk.org/index.php?title=File:Ocf.png&diff=1812 2017-06-21T18:31:58Z

<p>Maikel: </p> <hr /> <div></div>

Maikel https://wiki.openclonk.org/index.php?title=File:Ocd.png&diff=1811 2017-06-21T18:29:55Z

<p>Maikel: </p> <hr /> <div></div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1810 2017-06-21T18:21:52Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed outside of the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> |-<br /> ! <br /> ! [http://wiki.openclonk.org/w/Base_Melees Base Melees]<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> !<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> !<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Development&diff=1809 2017-06-21T18:18:59Z

<p>Maikel: /* Contribute Scripts or Game Content */</p> <hr /> <div>__NOTOC__<br /> 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.<br /> <br /> === Use Development Snapshots ===<br /> <br /> OpenClonk is continously in development. The &quot;current&quot; 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.<br /> <br /> * Development Snapshots - [http://www.openclonk.org/nightly-builds/ www.openclonk.org/nightly-builds/]<br /> * Blog - [http://blog.openclonk.org blog.openclonk.org]<br /> * Changelog - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]<br /> * Browse source - [http://git.openclonk.org/openclonk.git/tree/refs/heads/master git.openclonk.org/openclonk.git/tree/refs/heads/master]<br /> <br /> === Report Bugs ===<br /> <br /> 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.<br /> <br /> Here's how you can reach us:<br /> <br /> * IRC - [irc://irc.euirc.net/openclonk-dev #openclonk-dev] on irc.euirc.net (Problems connecting? Use irc.ham.de.euirc.net)<br /> * Bugtracker - [http://bugs.openclonk.org bugs.openclonk.org]<br /> * Forum - [http://forum.openclonk.org forum.openclonk.org]<br /> <br /> === Contribute Scripts or Game Content ===<br /> <br /> 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.<br /> <br /> * Developer Documentation [http://docs.openclonk.org/en/sdk/ docs.openclonk.org/en/sdk/]<br /> * Forum - [http://forum.openclonk.org forum.openclonk.org]<br /> * Style Guide - [http://wiki.openclonk.org/w/C4Script_Style_Guidelines wiki.openclonk.org/w/C4Script_Style_Guidelines]<br /> * Contribute changes - [[Git Workflow]]<br /> * [http://crucible.openclonk.org Crucible] for code review<br /> * Are you a sound artist? Here is a list of [[missing sounds]] you can contribute.<br /> * Game content external to the main game: [[List Of External Creations]]<br /> <br /> === Build OpenClonk Yourself ===<br /> <br /> 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.<br /> <br /> * Tutorial for Windows - [http://wiki.openclonk.org/w/Building_with_Windows wiki.openclonk.org/w/Building_with_Windows]<br /> * General instructions - [http://wiki.openclonk.org/w/Build_OpenClonk wiki.openclonk.org/w/Build_OpenClonk]<br /> * Git Workflow Guide - [http://wiki.openclonk.org/w/Git_Workflow wiki.openclonk.org/w/Git_Workflow]<br /> * Git Repository - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]<br /> * Source Code Structure - [http://wiki.openclonk.org/w/Source_code_structure wiki.openclonk.org/w/Source_code_structure]<br /> <br /> === Hack the OpenClonk Engine ===<br /> <br /> 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.<br /> <br /> * Wondering where to start? - [[GSoC2011Ideas|Ideas page]]<br /> * Debugging synchronization losses - [http://wiki.openclonk.org/w/Sync_losses wiki.openclonk.org/w/Sync_Losses]<br /> * Style Guide - [http://wiki.openclonk.org/w/Style_Guidelines wiki.openclonk.org/w/Style_Guidelines]<br /> * Forum, developers' corner - [http://forum.openclonk.org/board_show.pl?bid=5 forum.openclonk.org]<br /> * Contribute changes - [[Git Workflow]]<br /> <br /> === Internal Links ===<br /> <br /> * [[Release Steps]]<br /> * [http://londeroth.org/~ck/oc-release/oc-release.cgi The release button]<br /> <br /> === Legal Stuff ===<br /> <br /> 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.</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1808 2017-06-21T14:28:48Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed outside of the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Type<br /> ! Name<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> |-<br /> ! <br /> ! Base Melees<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> !<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> !<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1807 2017-06-21T14:28:15Z

<p>Maikel: </p> <hr /> <div>Below a list of all scenarios and objects developed outside of the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Scenario Pack<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> |-<br /> ! Base Melees<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! Knueppeln<br /> ! <br /> ! [https://github.com/TheThow/OpenClonk-Stuff GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> ! ClonkFest<br /> ! <br /> ! [https://github.com/clonkspot/ClonkFest.ocs GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=List_Of_Community_Creations&diff=1806 2017-06-21T14:25:06Z

<p>Maikel: Created page with &quot;Below a list of all scenarios and objects developed outside of the main game. {| border=&quot;1&quot; class=&quot;wikitable&quot; |- ! Scenario Pack ! DL ! Repository ! OC Version |- ! Base Mele...&quot;</p> <hr /> <div>Below a list of all scenarios and objects developed outside of the main game.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Scenario Pack<br /> ! DL<br /> ! Repository<br /> ! OC Version<br /> |-<br /> ! Base Melees<br /> ! <br /> ! [https://github.com/MDT-Maikel/basemelees GitHub]<br /> ! [http://www.openclonk.org/nightly-builds/ snapshot]<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=C4Script_Style_Guidelines&diff=1805 2017-02-04T18:25:53Z

<p>Maikel: </p> <hr /> <div>Since many people are involved in the project, it is necessary to define some styling guidelines so that other developers can read your code more easily. Objects that have a public interface should be documented in a Javadoc-like syntax. Please adhere to this example if you edit or add new scripts. <br /> <br /> === Example ===<br /> <br /> /**<br /> ''Object title''<br /> ''Description, including implementation details that might be interesting for other scripters''<br /> <br /> @author ''Author(s)''<br /> */<br /> <br /> local some_variable;<br /> <br /> /** ''Explanation of what the function does''<br /> @param foo ''What the parameter foo is''<br /> @return ''What comes out of this function''<br /> */<br /> public func DoSomething(int foo)<br /> {<br /> // ''implementation commentars''<br /> if (foo == DIR_Left)<br /> {<br /> some_variable++;<br /> CreateObject(Goal_Melee);<br /> }<br /> <br /> if (foo &amp;&amp; some_variable)<br /> foo = foo + 1;<br /> <br /> return foo;<br /> }<br /> <br /> === In words ===<br /> <br /> ====Naming conventions====<br /> * generally, use meaningful identifiers which are self explanatory: e.g. &lt;tt&gt;weapon_strength&lt;/tt&gt; rather than &lt;tt&gt;iStr&lt;/tt&gt;<br /> * for variables don't use hungarian notation, preferably use &lt;tt&gt;lowercase_separated_by_underscores&lt;/tt&gt;<br /> * for functions use &lt;tt&gt;CamelCase()&lt;/tt&gt;<br /> * for static constants use &lt;tt&gt;PREFIX_Identifier&lt;/tt&gt;<br /> * Prepend new style effects with &lt;tt&gt;Fx&lt;/tt&gt; like &lt;tt&gt;FxNewStyleEffect&lt;/tt&gt;<br /> <br /> ====Indents, braces and spaces====<br /> * indent code with one tab<br /> * use the braces on own lines on the same indent level as the control structure / function declaration<br /> * &lt;code&gt;{...}&lt;/code&gt; braces are not required for single line statements but can be added if it improves readability<br /> * use spaces between operators like +, -, *, /, &amp;&amp;, || etc.<br /> * keywords (&lt;tt&gt;if&lt;/tt&gt;, &lt;tt&gt;while&lt;/tt&gt;, &lt;tt&gt;for&lt;/tt&gt;, etc.) are followed by a space.<br /> * function names are not followed by space, commas are<br /> <br /> ====Access specifiers for object methods====<br /> Non-global methods that are part of a public interface and intended to be called from other objects or scripts, should be prefixed with the &lt;tt&gt;public&lt;/tt&gt; keyword. As a part of the public interface of an object &lt;tt&gt;public&lt;/tt&gt; methods should be documented with comments accordingly.<br /> Non-interface methods should be prefixed with the &lt;tt&gt;private&lt;/tt&gt; keyword. Do not leave out the access specifier. The keyword &lt;tt&gt;protected&lt;/tt&gt; is deprecated.<br /> <br /> ====Comments and Documentation====<br /> * especially for library objects or objects with an interface used by other objects, write an introductory comment including title, author(s) and a description<br /> * please comment your script where it is necessary for other scripters to understand what you've done<br /> * please use Javadoc-like syntax when documenting your code so that a reference can be automatically created from it later<br /> <br /> ====Naming prefixes for IDs====<br /> * for libraries, icons and GUI elements: &lt;tt&gt;Library_*&lt;/tt&gt;, &lt;tt&gt;Icon_*&lt;/tt&gt;, &lt;tt&gt;GUI_*&lt;/tt&gt;<br /> * for goals, rules and environment objects: &lt;tt&gt;Goal_*&lt;/tt&gt;, &lt;tt&gt;Rule_*&lt;/tt&gt;, &lt;tt&gt;Environment_*&lt;/tt&gt;<br /> * for spells: &lt;tt&gt;Magic_*&lt;/tt&gt;<br /> * objects which are exclusively used by their parent objects should prefix their parent object name. e.g. &lt;tt&gt;ParkourCheckpoint&lt;/tt&gt; for a checkpoint of the parkour goal<br /> <br /> ====Misc====<br /> * For C4Script veterans: You don't need to write &lt;code&gt;#strict 2&lt;/code&gt; at the start of each script. All scripts are considered to be in ''strict 2'' style<br /> * If you need multiple statements in a block, use one (&lt;tt&gt;if (...) { foo(); bar(); }&lt;/tt&gt;)! Avoid constructs like &lt;tt&gt;if (...) foo() &amp;&amp; bar();&lt;/tt&gt; or &lt;tt&gt;if (...) Or(foo(), bar());&lt;/tt&gt;</div>

Maikel https://wiki.openclonk.org/index.php?title=C4Script_Style_Guidelines&diff=1804 2017-02-04T18:25:13Z

<p>Maikel: /* Naming conventions */</p> <hr /> <div>Since many people are involved in the project, it is necessary to define some styling guidelines so that other developers can read your code more easily. Objects that have a public interface should be documented in a Javadoc-like syntax. Please adhere to this example if you edit or add new scripts. <br /> <br /> === Example ===<br /> <br /> /**<br /> ''Object title''<br /> ''Description, including implementation details that might be interesting for other scripters''<br /> <br /> @author ''Author(s)''<br /> */<br /> <br /> local some_variable;<br /> <br /> /** ''Explanation of what the function does''<br /> @param foo ''What the parameter foo is''<br /> @return ''What comes out of this function''<br /> */<br /> public func DoSomething(int foo)<br /> {<br /> // ''implementation commentars''<br /> if (foo == DIR_Left)<br /> {<br /> some_variable++;<br /> CreateObject(Goal_Melee);<br /> }<br /> <br /> if (foo &amp;&amp; some_variable)<br /> foo = foo + 1;<br /> <br /> return foo;<br /> }<br /> <br /> === In words ===<br /> <br /> ====Naming conventions====<br /> * generally, use meaningful identifiers which are self explanatory: e.g. &lt;tt&gt;weapon_strength&lt;/tt&gt; rather than &lt;tt&gt;iStr&lt;/tt&gt;<br /> * for variables don't use hungarian notation, preferably use &lt;tt&gt;lowercase_separated_by_underscores&lt;/tt&gt;<br /> * for functions use &lt;tt&gt;CamelCase()&lt;/tt&gt;<br /> * for static constants use &lt;tt&gt;PREFIX_Identifier&lt;/tt&gt;<br /> * Prepend new style effects with &lt;tt&gt;Fx&lt;/tt&gt; like &lt;tt&gt;FxNewStyleEffect&lt;/tt&gt;<br /> <br /> ====Indents, braces and spaces====<br /> * indent code with one tab<br /> * use the braces on own lines on the same indent level as the control structure / function declaration<br /> * &lt;code&gt;{...}&lt;/code&gt; braces are not required for single line statements but can be added if it improves readability<br /> * use spaces between operators like +, -, *, /, &amp;&amp;, || etc.<br /> * keywords (&lt;tt&gt;if&lt;/tt&gt;, &lt;tt&gt;while&lt;/tt&gt;, &lt;tt&gt;for&lt;/tt&gt;, etc.) are followed by a space.<br /> * function names are not followed by space, commas are<br /> <br /> ====Access specifiers for object methods====<br /> Non-global methods that are part of a public interface and intended to be called from other objects or scripts, should be prefixed with the &lt;tt&gt;public&lt;/tt&gt; keyword. As a part of the public interface of an object &lt;tt&gt;public&lt;/tt&gt; methods should be documented with comments accordingly.<br /> Non-interface methods should be prefixed with the &lt;tt&gt;private&lt;/tt&gt; keyword. Do not leave out the access specifier. The keyword &lt;tt&gt;protected&lt;/tt&gt; is deprecated.<br /> <br /> ====Comments and Documentation====<br /> * especially for library objects or objects with an interface used by other objects, write an introductory comment including title, author(s) and a description<br /> * please comment your script where it is necessary for other scripters to understand what you've done<br /> * please use Javadoc-like syntax when documenting your code so that a reference can be automatically created from it later<br /> <br /> ====Naming prefixes for IDs====<br /> * for libraries, icons and GUI elements: &lt;tt&gt;Library_*&lt;/tt&gt;, &lt;tt&gt;Icon_*&lt;/tt&gt;, &lt;tt&gt;GUI_*&lt;/tt&gt;<br /> * for goals, rules and environment objects: &lt;tt&gt;Goal_*&lt;/tt&gt;, &lt;tt&gt;Rule_*&lt;/code&gt;, &lt;tt&gt;Environment_*&lt;/tt&gt;<br /> * for spells: &lt;tt&gt;Magic_*&lt;/tt&gt;<br /> * objects which are exclusively used by their parent objects should prefix their parent object name. e.g. &lt;tt&gt;ParkourCheckpoint&lt;/tt&gt; for a checkpoint of the parkour goal<br /> <br /> ====Misc====<br /> * For C4Script veterans: You don't need to write &lt;code&gt;#strict 2&lt;/code&gt; at the start of each script. All scripts are considered to be in ''strict 2'' style<br /> * If you need multiple statements in a block, use one (&lt;tt&gt;if (...) { foo(); bar(); }&lt;/tt&gt;)! Avoid constructs like &lt;tt&gt;if (...) foo() &amp;&amp; bar();&lt;/tt&gt; or &lt;tt&gt;if (...) Or(foo(), bar());&lt;/tt&gt;</div>

Maikel https://wiki.openclonk.org/index.php?title=C4Script_Style_Guidelines&diff=1803 2017-02-04T18:24:40Z

<p>Maikel: </p> <hr /> <div>Since many people are involved in the project, it is necessary to define some styling guidelines so that other developers can read your code more easily. Objects that have a public interface should be documented in a Javadoc-like syntax. Please adhere to this example if you edit or add new scripts. <br /> <br /> === Example ===<br /> <br /> /**<br /> ''Object title''<br /> ''Description, including implementation details that might be interesting for other scripters''<br /> <br /> @author ''Author(s)''<br /> */<br /> <br /> local some_variable;<br /> <br /> /** ''Explanation of what the function does''<br /> @param foo ''What the parameter foo is''<br /> @return ''What comes out of this function''<br /> */<br /> public func DoSomething(int foo)<br /> {<br /> // ''implementation commentars''<br /> if (foo == DIR_Left)<br /> {<br /> some_variable++;<br /> CreateObject(Goal_Melee);<br /> }<br /> <br /> if (foo &amp;&amp; some_variable)<br /> foo = foo + 1;<br /> <br /> return foo;<br /> }<br /> <br /> === In words ===<br /> <br /> ====Naming conventions====<br /> * generally, use meaningful identifiers which are self explanatory: e.g. &lt;tt&gt;weapon_strength&lt;/tt&gt; rather than &lt;tt&gt;iStr&lt;/tt&gt;<br /> * for variables don't use hungarian notation, preferably use &lt;tt&gt;lowercase_separated_by_underscores&lt;/tt&gt;<br /> * for functions use &lt;tt&gt;CamelCase()&lt;/tt&gt;<br /> * for static constants use &lt;tt&gt;PREFIX_Identifier&lt;/tt&gt;<br /> * for new style effects use &lt;tt&gt;FxNewStyleEffect&lt;/tt&gt;<br /> <br /> ====Indents, braces and spaces====<br /> * indent code with one tab<br /> * use the braces on own lines on the same indent level as the control structure / function declaration<br /> * &lt;code&gt;{...}&lt;/code&gt; braces are not required for single line statements but can be added if it improves readability<br /> * use spaces between operators like +, -, *, /, &amp;&amp;, || etc.<br /> * keywords (&lt;tt&gt;if&lt;/tt&gt;, &lt;tt&gt;while&lt;/tt&gt;, &lt;tt&gt;for&lt;/tt&gt;, etc.) are followed by a space.<br /> * function names are not followed by space, commas are<br /> <br /> ====Access specifiers for object methods====<br /> Non-global methods that are part of a public interface and intended to be called from other objects or scripts, should be prefixed with the &lt;tt&gt;public&lt;/tt&gt; keyword. As a part of the public interface of an object &lt;tt&gt;public&lt;/tt&gt; methods should be documented with comments accordingly.<br /> Non-interface methods should be prefixed with the &lt;tt&gt;private&lt;/tt&gt; keyword. Do not leave out the access specifier. The keyword &lt;tt&gt;protected&lt;/tt&gt; is deprecated.<br /> <br /> ====Comments and Documentation====<br /> * especially for library objects or objects with an interface used by other objects, write an introductory comment including title, author(s) and a description<br /> * please comment your script where it is necessary for other scripters to understand what you've done<br /> * please use Javadoc-like syntax when documenting your code so that a reference can be automatically created from it later<br /> <br /> ====Naming prefixes for IDs====<br /> * for libraries, icons and GUI elements: &lt;tt&gt;Library_*&lt;/tt&gt;, &lt;tt&gt;Icon_*&lt;/tt&gt;, &lt;tt&gt;GUI_*&lt;/tt&gt;<br /> * for goals, rules and environment objects: &lt;tt&gt;Goal_*&lt;/tt&gt;, &lt;tt&gt;Rule_*&lt;/code&gt;, &lt;tt&gt;Environment_*&lt;/tt&gt;<br /> * for spells: &lt;tt&gt;Magic_*&lt;/tt&gt;<br /> * objects which are exclusively used by their parent objects should prefix their parent object name. e.g. &lt;tt&gt;ParkourCheckpoint&lt;/tt&gt; for a checkpoint of the parkour goal<br /> <br /> ====Misc====<br /> * For C4Script veterans: You don't need to write &lt;code&gt;#strict 2&lt;/code&gt; at the start of each script. All scripts are considered to be in ''strict 2'' style<br /> * If you need multiple statements in a block, use one (&lt;tt&gt;if (...) { foo(); bar(); }&lt;/tt&gt;)! Avoid constructs like &lt;tt&gt;if (...) foo() &amp;&amp; bar();&lt;/tt&gt; or &lt;tt&gt;if (...) Or(foo(), bar());&lt;/tt&gt;</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1800 2016-09-19T18:56:09Z

<p>Maikel: </p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Download &amp; Play ===<br /> There currently is no stable version of Tower of Despair. You can play the latest version by downloading the repository and running the python script which creates the tower.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1799 2016-09-19T11:55:55Z

<p>Maikel: /* Editing &amp; Saving */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> Now you can start the real editing of the room, by drawing the landscape, adding objects, sequences, NPC's to construct a riddle.<br /> <br /> One important object is the PlayerStart object, with this object you can control what the clonk gets when he/she leaves the room entrance to start the room. Just create this object, select it and edit its properties to give the clonk HP, inventory slots, items, knowledge, etc.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1798 2016-09-19T11:50:37Z

<p>Maikel: </p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for one last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> Moreover you can test some of the basic room properties by executing the script TestRoom(). This will give your some information about your room and warns about possible problems.<br /> <br /> ==== Creating A Room Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1797 2016-09-19T11:39:34Z

<p>Maikel: /* Editing &amp; Saving */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save automatically to the new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for a last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> ==== Creating Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1796 2016-09-19T11:39:08Z

<p>Maikel: /* Editing &amp; Saving */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs using Save scenario as... (Ctrl + Shift + S). From then on you can save the progress easily using Save scenario (Ctrl + S) and save to this new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for a last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> ==== Creating Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1795 2016-09-19T11:37:41Z

<p>Maikel: </p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs. From then on you can save the progress easily using Ctrl + S and save to this new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> ==== Room Properties ====<br /> The room is control is handled by a control object of which certain properties must be adjusted for each room. The control object is named RoomTemplate.ocd and must be renamed to Room&lt;InsertName&gt;.ocd for this object you also need to modify its id in the DefCore.txt to Room&lt;InsertName&gt; but leave the rest unchanged. The main part is the room control script which will look like [https://github.com/MDT-Maikel/OCTower/blob/master/RoomTemplate.ocs/RoomTemplate.ocd/Script.c this Script.c] when first saving the rule. All of the basic room properties must be modified to the corresponding room.<br /> <br /> ==== Testing the Room ====<br /> Once the room is done save it for a last time. Then reopen the room in editor mode with a single player active. Your clonk will start at the room entrance and you can play the room. Do not save the room any more and press F12 to go back to the last save in case you failed and want to retry the room.<br /> <br /> ==== Creating Together ====<br /> The OpenClonk editor mode also works in online network games with multiple players. This also allows to together design a room. Currently on the side of the room template there is no official support for this, however it is certainly possible to design together. It may involve restarting editor mode several times because some properties must be edited outside of editing, especially the room control object.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1794 2016-09-19T11:24:47Z

<p>Maikel: /* Development */</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Development ===<br /> The tower is open-source and is developed using [https://github.com/MDT-Maikel/OCTower GitHub repository].<br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs. From then on you can save the progress easily using Ctrl + S and save to this new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> <br /> ==== Room Properties ====</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1793 2016-09-19T11:16:38Z

<p>Maikel: </p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> === Development ===<br /> The tower is open-source and is developed on [https://github.com/MDT-Maikel/OCTower GitHub].<br /> <br /> <br /> === Creating a Room ===<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room.<br /> <br /> ==== Cloning the Tower Repository ====<br /> First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> ==== Editing &amp; Saving ====<br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs. From then on you can save the progress easily using Ctrl + S and save to this new location. Your room is now in principle playable with the given entrance and exit.<br /> <br /> <br /> ==== Room Properties ====</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1792 2016-09-19T10:34:20Z

<p>Maikel: </p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle of various difficulty.<br /> <br /> ==Development==<br /> The tower is open-source and is developed on [https://github.com/MDT-Maikel/OCTower GitHub].<br /> <br /> <br /> ==Creating a Room==<br /> Creating a room is very easy using the build-in editor mode of OpenClonk. Here you will be guided through the basic steps of making a room. First you need a copy of the tower git repository which you can get from [https://github.com/MDT-Maikel/OCTower GitHub]. Place the repository in your /planet folder so that you can run scenarios easily.<br /> <br /> Now you start the room template scenario called RoomTemplate.ocs with the openclonk editor mode. Run the command<br /> ./openclonk --editor OCTower.ocs/RoomTemplate.ocs<br /> or similar on non-unix systems.<br /> <br /> Once you have started this scenario in editor mode, the first thing to do is to place a room entrance and room exit into the almost empty map (this is the typical look for a room). Do this and directly save the scenario under a new name of the form Room*.ocs. From then on you can save the progress easily using Ctrl + S and save to this new location. Your room is now in principle playable with the given entrance and exit.</div>

Maikel https://wiki.openclonk.org/index.php?title=Tower_of_Despair&diff=1791 2016-09-19T10:24:56Z

<p>Maikel: Created page with &quot;Tower of Despair is a tower with tons of rooms, each posing a riddle.&quot;</p> <hr /> <div>Tower of Despair is a tower with tons of rooms, each posing a riddle.</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1770 2016-01-29T16:57:48Z

<p>Maikel: /* Table of Kills */</p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts. There is a test scenario which checks all kinds of kills and returns whether the correct killer has been found.<br /> <br /> <br /> === Table of Kills ===<br /> <br /> This table contains all the tests in ''Tests.ocf/KillTracing.ocs'', you can launch each test with LaunchTest(nr) where nr is the number indicated in the first column. The second column contains the description of the test. For each test there is a ''killer'' (K) which should be the killer from the game play point of view. Then there is a ''victim'' (V) which dies in every test, and there is a ''fake killer'' (F) which sometimes plays a role. In the third column it is then registered if the correct ''killer'' (K) has been identified as the killer of the ''victim'' (V) by the engine.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |-<br /> ! #<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | 1<br /> | K throws object on V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 2<br /> | K throws lantern to V (V dies of lantern fire)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 3<br /> | K shoots object with cannon at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 4<br /> | K placed wallkit on V (V dies of asphyxiation)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 5<br /> | K strikes V with a sword<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 6<br /> | K strikes V with a club<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 7<br /> | K strikes V with an axe<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 8<br /> | K throws firestone at V (V dies of explosion)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 9<br /> | K shoots object with club at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 10<br /> | K throw firestone at object, object moves to V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 11<br /> | K explodes firestone material, one of the cascading firestones kills V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 12<br /> | K shoots a normal arrow at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 13<br /> | K shoots a fire arrow at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 14<br /> | K shoots a bomb arrow at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 15<br /> | K shoots with the musket at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 16<br /> | K throws a javelin at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 17<br /> | K shoots a grenade (with launcher) at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 18<br /> | K throws an activated iron bomb at V (no collection by V)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 19<br /> | K ignites powder keg (musket shot) near V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 20<br /> | K throws a fusing dynamite at V (no collection by V)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 21<br /> | F puts himself on fire, K is incinerated by F and then incinerates V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 22<br /> | K dumps object from a lorry onto V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 23<br /> | K destroys a lorry with objects next to V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 24<br /> | K shoots an object with the catapult at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 25<br /> | K lets lava move onto V (trigger: explosion)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 26<br /> | K lets acid move onto V (trigger: explosion)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 27<br /> | K uses windbag to shoot object at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 28<br /> | K shoots at V hanging on a balloon (V tumbles out of map)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 29<br /> | K shoots at balloon on which V hangs (V tumbles out of map)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 30<br /> | K uses windbag to shoot V out of map<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 31<br /> | K launches a boompack at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 32<br /> | F places a dynamite box, K takes igniter and blasts V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 33<br /> | K uses teleglove to drop object onto V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 34<br /> | K blasts object from material which drops on V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 35<br /> | K throws an activated iron bomb at V (then collected by V)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 36<br /> | K throws a fusing dynamite at V (V tries to collect but can't)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 37<br /> | K ignites boompack (musket shot) which shoots at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 38<br /> | K ignites a battery of boompacks which shoot down V flying an airplane<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 39<br /> | K shoots at airship which carries V (V tumbles out of map)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 40<br /> | K creates a fire which fuses a dynamite box, the explosion kills V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 41<br /> | K digs out a piece of coal which kills V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 42<br /> | K hacks out (with the pickaxe) a piece of ore which kills V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 43<br /> | K digs and moves a piece of rock (controlled by F) which kills V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 44<br /> | K pushes a tree into the sawmill, the sawn wood kills V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 45<br /> | K produces metal in the foundry which falls down and kills V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 46<br /> | K throws snow on V (V dies of asphyxiation)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 47<br /> | K pushed the container (lorry) holding V out of landscape<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 48<br /> | K blasts the container (wooden cabin) holding V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 49<br /> | K blasts V into lava where V dies<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 50<br /> | K blasts V into acid where V dies<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 51<br /> | K uses windbag to shoot V into lava where V dies<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 52<br /> | K uses windbag to shoot V into acid where V dies<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 53<br /> | K uses club to fling V into lava where V dies<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 54<br /> | K uses club to fling V into acid where V dies<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 55<br /> | K blasts a compensator and its explosion kills V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 56<br /> | K blasts a bridge and a rock drops which kills V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Release_Steps&diff=1758 2016-01-15T19:23:09Z

<p>Maikel: /* Release */</p> <hr /> <div>__NOTOC__<br /> 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.<br /> <br /> === Pre Release ===<br /> <br /> Steps to do before the release, and after the feature freeze.<br /> <br /> * If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.<br /> * Fix all bugs related to this release, which can be found in the bugtracker's [http://bugs.openclonk.org/roadmap_page.php roadmap].<br /> * Go the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and perform a dry release to create a release candidate.<br /> * Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.<br /> <br /> === Release ===<br /> <br /> 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.<br /> <br /> * Update all Version.txt files in planet/ to the new version number and commit/push.<br /> * Update the Version.txt to the new version number and commit/push.<br /> * Set the extra version in Version.txt to nothing [SET(C4VERSIONEXTRA FALSE)]<br /> * Then go to the [http://londeroth.org/~ck/oc-release/oc-release.cgi release button] and release from the correct branch.<br /> <br /> === Post Release ===<br /> <br /> After the release has been uploaded do the following:<br /> * Tag the released changeset with the vX.Y tag (leightweight: git tag vX.Y).<br /> * Create a stable branch named stable-X for bugfix releases.<br /> * Check if installers for all operating systems are existing (contact Mortimer for Mac).<br /> * Basic tests: download, check installer content, run game, play game, play network game.<br /> * Make announcements in our blog and in our forum.<br /> * Update external game portals: [http://www.desura.com/games/publish/openclonk/execute Desura], [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt].<br /> * 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.<br /> * Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.<br /> * Update [http://en.wikipedia.org/wiki/OpenClonk wikipedia article].<br /> <br /> === Optional ===<br /> <br /> Optional steps:<br /> * Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].<br /> * Spread the word! More advertisement!</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1756 2016-01-04T19:19:20Z

<p>Maikel: </p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts. There is a test scenario which checks all kinds of kills and returns whether the correct killer has been found.<br /> <br /> <br /> === Table of Kills ===<br /> <br /> This table contains all the tests in ''Tests.ocf/KillTracing.ocs'', you can launch each test with LaunchTest(nr) where nr is the number indicated in the first column. The second column contains the description of the test. For each test there is a ''killer'' (K) which should be the killer from the game play point of view. Then there is a ''victim'' (V) which dies in every test, and there is a ''fake killer'' (F) which sometimes plays a role. In the third column it is then registered if the correct ''killer'' (K) has been identified as the killer of the ''victim'' (V) by the engine.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |-<br /> ! #<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | 1<br /> | K throws object on V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 2<br /> | K throws lantern to V (V dies of lantern fire)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 3<br /> | K shoots object with cannon at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 4<br /> | K placed wallkit on V (V dies of asphyxiation)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 5<br /> | K strikes V with a sword<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 6<br /> | K strikes V with a club<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 7<br /> | K strikes V with an axe<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 8<br /> | K throws firestone at V (V dies of explosion)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 9<br /> | K shoots object with club at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 10<br /> | K throw firestone at object, object moves to V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 11<br /> | K explodes firestone material, one of the cascade firestones kills V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 12<br /> | K shoots a normal arrow at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 13<br /> | K shoots a fire arrow at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 14<br /> | K shoots a bomb arrow at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 15<br /> | K shoots with the musket at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 16<br /> | K throws a javelin at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 17<br /> | K shoots a grenade (with launcher) at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 18<br /> | K throws an activated iron bomb at V (no collection by V)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 19<br /> | K ignites powder keg (musket shot) near V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 20<br /> | K throws a fusing dynamite at V (no collection by V)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 21<br /> | F put himself on fire, K is incinerated by F and then incinerates V<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 22<br /> | K dumps object from a lorry onto V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 23<br /> | K destroys a lorry with objects next to V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 24<br /> | K shoots an object with the catapult at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 25<br /> | K lets lava move onto V (trigger: explosion)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 26<br /> | K lets acid move onto V (trigger: explosion)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 27<br /> | K uses windbag to shoot object at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 28<br /> | K shoots at V hanging on a balloon (V tumbles out of map)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 29<br /> | K shoots at balloon on which V hangs (V tumbles out of map)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 30<br /> | K uses windbag to shoot V out of map<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 31<br /> | K launches a boompack at V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 32<br /> | F places a dynamite box, K takes igniter and blasts V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 33<br /> | K uses teleglove to drop object onto V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 34<br /> | K blasts object from material which drops on V<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 35<br /> | K throws an activated iron bomb at V (then collected by V)<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 36<br /> | K throws a fusing dynamite at V (V tries to collect but can't)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1755 2016-01-03T22:46:43Z

<p>Maikel: </p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts. There is a test scenario which checks all kinds of kills and returns whether the correct killer has been found. This scenario can be found in the repository under Tests.ocf/KillTracing.ocs. The results of this scenario are summarized in the table below. In order to see what the test exactly does, you can run a test with LaunchTest(nr) where nr is the number indicated in the first column.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |-<br /> ! #<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | 1<br /> | Object throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 2<br /> | Lantern fire<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 3<br /> | Cannon shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 4<br /> | Wallkit asphyxiation<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 5<br /> | Sword strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 6<br /> | Club strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 7<br /> | Axe strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 8<br /> | Firestone explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 9<br /> | Club object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 10<br /> | Object moved by explosion<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 11<br /> | Firestone material cascade<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 12<br /> | Bow shot (arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 13<br /> | Bow shot (fire arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 14<br /> | Bow shot (bomb arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 15<br /> | Musket shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 16<br /> | Javelin throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 17<br /> | Grenade launcher shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 18<br /> | Iron bomb explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 19<br /> | Powder keg (shot by musket)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 20<br /> | Dynamite explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 21<br /> | Incineration by burning clonk<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 22<br /> | Lorry dump<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 23<br /> | Lorry destruction<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 24<br /> | Catapult shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 25<br /> | Moving lava<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 26<br /> | Moving acid<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 27<br /> | Windbag object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 28<br /> | Balloon tumble out of map (hit rider)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 29<br /> | Balloon tumble out of map (hit balloon)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 30<br /> | Windbag shot out of map<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 31<br /> | Boompack hit<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 32<br /> | Dynamite box (placed by other)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 33<br /> | Teleglove drop<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1754 2016-01-03T19:17:09Z

<p>Maikel: </p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts. There is a test scenario which checks all kinds of kills and returns whether the correct killer has been found. This scenario can be found in the repository under Tests.ocf/KillTracing.ocs. The results of this scenario are summarized in the table below. In order to see what the test exactly does, you can run a test with LaunchTest(nr) where nr is the number indicated in the first columns.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |-<br /> ! #<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | 1<br /> | Object throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 2<br /> | Lantern fire<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 3<br /> | Cannon shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 4<br /> | Wallkit asphyxiation<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 5<br /> | Sword strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 6<br /> | Club strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 7<br /> | Axe strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 8<br /> | Firestone explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 9<br /> | Club object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 10<br /> | Object moved by explosion<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 11<br /> | Firestone material cascade<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 12<br /> | Bow shot (arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 13<br /> | Bow shot (fire arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 14<br /> | Bow shot (bomb arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 15<br /> | Musket shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 16<br /> | Javelin throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 17<br /> | Grenade launcher shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 18<br /> | Iron bomb explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 19<br /> | Powder keg (shot by musket)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 20<br /> | Dynamite explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 21<br /> | Incineration by burning clonk<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 22<br /> | Lorry dump<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 23<br /> | Lorry destruction<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 24<br /> | Catapult shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 25<br /> | Moving lava<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 26<br /> | Moving acid<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 27<br /> | Windbag object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 28<br /> | Balloon tumble out of map (hit rider)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 29<br /> | Balloon tumble out of map (hit balloon)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 30<br /> | Windbag shot out of map<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 31<br /> | Boompack hit<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 32<br /> | Dynamite box (placed by other)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 33<br /> | Teleglove drop<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1753 2016-01-03T17:39:49Z

<p>Maikel: </p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts. There is a test scenario which checks all kinds of kills and returns whether the correct killer has been found. This scenario can be found in the repository under Tests.ocf/KillTracing.ocs. The results of this scenario are summarized in the table below. In order to see what the test exactly does, you can run a test with LaunchTest(nr) where nr is the number indicated in the first columns.<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |-<br /> ! #<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | 1<br /> | Object throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 2<br /> | Lantern fire<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 3<br /> | Cannon shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 4<br /> | Wallkit asphyxiation<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 5<br /> | Sword strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 6<br /> | Club strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 7<br /> | Axe strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 8<br /> | Firestone explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 9<br /> | Club object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 10<br /> | Object moved by explosion<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 11<br /> | Firestone material cascade<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 12<br /> | Bow shot (arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 13<br /> | Bow shot (fire arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 14<br /> | Bow shot (bomb arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 15<br /> | Musket shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 16<br /> | Javelin throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 17<br /> | Grenade launcher shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 18<br /> | Iron bomb explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 19<br /> | Powder keg (shot by musket)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 20<br /> | Dynamite explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 21<br /> | Incineration by burning clonk<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 22<br /> | Lorry dump<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 23<br /> | Lorry destruction<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 24<br /> | Catapult shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 25<br /> | Moving lava<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 26<br /> | Moving acid<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 27<br /> | Windbag object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 28<br /> | Balloon tumble out of map (hit rider)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 29<br /> | Balloon tumble out of map (hit balloon)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 30<br /> | Windbag shot out of map<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1752 2016-01-03T17:31:50Z

<p>Maikel: </p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts. There is a test scenario which checks all kinds of kills and returns whether the correct killer has been found. This scenario can be found in the repository under Tests.ocf/KillTracing.ocs. The results of this scenario are summarized in the table below. In order to see what the test exactly does, you can run a test with LaunchTest(nr) where nr is the number indicated in the first columns.<br /> <br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! #<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | 1<br /> | Object throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 2<br /> | Lantern fire<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 3<br /> | Cannon shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 4<br /> | Wallkit asphyxiation<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 5<br /> | Sword strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 6<br /> | Club strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 7<br /> | Axe strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 8<br /> | Firestone explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 9<br /> | Club object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 10<br /> | Object moved by explosion<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 11<br /> | Firestone material cascade<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 12<br /> | Bow shot (arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 13<br /> | Bow shot (fire arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 14<br /> | Bow shot (bomb arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 15<br /> | Musket shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 16<br /> | Javelin throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 17<br /> | Grenade launcher shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 18<br /> | Iron bomb explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 19<br /> | Powder keg (shot by musket)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 20<br /> | Dynamite explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 21<br /> | Incineration by burning clonk<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 22<br /> | Lorry dump<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 23<br /> | Lorry destruction<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 24<br /> | Catapult shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 25<br /> | Moving lava<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 26<br /> | Moving acid<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 27<br /> | Windbag object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 28<br /> | Balloon tumble out of map (hit rider)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 29<br /> | Balloon tumble out of map (hit balloon)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 30<br /> | Windbag shot out of map<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1751 2016-01-03T14:50:28Z

<p>Maikel: </p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts. There is a test scenario which checks all kinds of kills and returns whether the correct killer has been found. This scenario can be found in the repository under Tests.ocf/KillTracing.ocs. The results of this scenario are summarized in the table below. In order to see what the test exactly does, you can run a test with LaunchTest(nr) where nr is the number indicated in the first columns.<br /> <br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! #<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | 1<br /> | Object throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 2<br /> | Lantern fire<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 3<br /> | Cannon shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 4<br /> | Wallkit asphyxiation<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 5<br /> | Sword strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 6<br /> | Club strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 7<br /> | Axe strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 8<br /> | Firestone explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 9<br /> | Club object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 10<br /> | Object moved by explosion<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 11<br /> | Firestone material cascade<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 12<br /> | Bow shot (arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 13<br /> | Bow shot (fire arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 14<br /> | Bow shot (bomb arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 15<br /> | Musket shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 16<br /> | Javelin throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 17<br /> | Grenade launcher shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 18<br /> | Iron bomb explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 19<br /> | Powder keg (shot by musket)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 20<br /> | Dynamite explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 21<br /> | Incineration by burning clonk<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 22<br /> | Lorry dump<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 23<br /> | Lorry destruction<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 24<br /> | Catapult shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> | 25<br /> | Moving lava<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 26<br /> | Moving acid<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;no&lt;/span&gt;<br /> |-<br /> | 27<br /> | Windbag object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;yes&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel https://wiki.openclonk.org/index.php?title=Kill_Tracing&diff=1750 2016-01-03T13:36:30Z

<p>Maikel: </p> <hr /> <div>This page keeps track of which types of kills in OpenClonk are currently correctly traced by the engine and the object scripts.<br /> <br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! Kill Description<br /> ! Traced?<br /> |-<br /> | Object throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Lantern fire<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Cannon shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Wallkit asphyxiation<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;false&lt;/span&gt;<br /> |-<br /> | Sword strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Club strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Axe strike<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Firestone explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Club object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Object moved by explosion<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Firestone material cascade<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Bow shot (arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Bow shot (fire arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Bow shot (bomb arrow)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Musket shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Javelin throw<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Grenade launcher shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Iron bomb explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Powder keg (shot by musket)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Dynamite explosion (thrown)<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Incineration by burning clonk<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;false&lt;/span&gt;<br /> |-<br /> | Lorry dump<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Lorry destruction<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Catapult shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> | Moving lava<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;false&lt;/span&gt;<br /> |-<br /> | Moving acid<br /> | &lt;span style=&quot;color:#FF0000&quot;&gt;false&lt;/span&gt;<br /> |-<br /> | Windbag object shot<br /> | &lt;span style=&quot;color:#00CC00&quot;&gt;true&lt;/span&gt;<br /> |-<br /> |}</div>

Maikel