OpenClonk Wiki - User contributions [en]

Missing sounds

2014-08-13T17:08:05Z

Sven2:

The acoustic parts of our game are pretty shabby. Here are some ideas for sound polishing. Feel free to contribute sounds from the list or to contribute your own ideas to this list by editing this page.

== Environmental sounds ==
* Forest: Tree leaves, birds, cicadas
* Night sounds: Howling wolves at midnight/full moon
* Ocean: Sea waves, seagulls
* Underwater: Bubbles, fish sonar echoes
* Caves: Dripping water

== Object sounds ==
* Construction site: Hammering, sawing, ...
* Large explosion sound
* Item construction sounds for tools workshop, chemical lab [boiling.ogg?], inventor's lab - could also be used for NPC village ambience sounds
* Destruction sounds for collapsing buildings
* Put/Hit sounds for barrel and bucket

== Engine sounds ==
* Game start sound in the lobby (currently Blast3 I think)

== General Objects ==
* The music controller object should also do sounds (forest/village/underwater/etc. ambience) (Better performance if sound search is done per player)

== Engine features ==
* Automatic frequency adjustment when player is underwater
* Fix left/right pan
* Echo for caves

Missing sounds

2014-08-07T21:30:53Z

Sven2:

Missing sounds

2014-08-07T21:29:03Z

Sven2: /* Event sounds */

The acoustic parts of our game are pretty shabby. Here are some ideas for sound polishing. Feel free to contribute sounds from the list or to contribute your own ideas to this list by editing this page.

== Environemental sounds ==
* Forest: Tree leaves, birds, cicadas
* Night sounds: Howling wolves at midnight/full moon
* Ocean: Sea waves, seagulls
* Underwater: Bubbles, fish sonar echoes
* Caves: Dripping water

== Event sounds ==
* Construction site: Hammering, sawing, ...
* Large explosion sound
* Item construction sounds for tools workshop, chemical lab [boiling.ogg?], inventor's lab - could also be used for NPC village ambience sounds
* Destruction sounds for collapsing buildings

== General Objects ==
* The music controller object should also do sounds (forest/village/underwater/etc. ambience) (Better performance if sound search is done per player)

== Engine features ==
* Automatic frequency adjustment when player is underwater
* Fix left/right pan

Missing sounds

2014-08-07T21:28:01Z

Sven2:

The acoustic parts of our game are pretty shabby. Here are some ideas for sound polishing. Feel free to contribute sounds from the list or to contribute your own ideas to this list by editing this page.

== Environemental sounds ==
* Forest: Tree leaves, birds, cicadas
* Night sounds: Howling wolves at midnight/full moon
* Ocean: Sea waves, seagulls
* Underwater: Bubbles, fish sonar echoes
* Caves: Dripping water

== Event sounds ==
* Construction site: Hammering, sawing, ...
* Large explosion sound
* Item construction sounds for tools workshop, chemical lab [boiling.ogg?], inventor's lab
* Destruction sounds for collapsing buildings

== General Objects ==
* The music controller object should also do sounds (forest/village/underwater/etc. ambience) (Better performance if sound search is done per player)

== Engine features ==
* Automatic frequency adjustment when player is underwater
* Fix left/right pan

Missing sounds

2014-08-07T21:25:41Z

Sven2: /* Sounds */

The acoustic parts of our game are pretty shabby. Here are some ideas for sound polishing:

== Objects ==
* The music controller object should also do sounds (forest/village/underwater/etc. ambience) (Better performance if sound search is done per player)

== Environemental sounds ==
* Forest: Tree leaves, birds, cicadas
* Night sounds: Howling wolves at midnight/full moon
* Ocean: Sea waves, seagulls
* Underwater: Bubbles, fish sonar echoes
* Caves: Dripping water

== Event sounds ==
* Construction site: Hammering, sawing, ...
* Large explosion sound
* Item construction sounds for tools workshop, chemical lab [boiling.ogg?], inventor's lab
* Destruction sounds for collapsing buildings

Development

2014-08-07T21:16:44Z

Sven2: /* Contribute Scripts or Game Content */

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

=== Use Development Snapshots ===

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

* Development Snapshots - [http://www.openclonk.org/nightly-builds/ www.openclonk.org/nightly-builds/]
* Blog - [http://blog.openclonk.org blog.openclonk.org]
* Changelog - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]
* Browse source - [http://git.openclonk.org/openclonk.git/tree/refs/heads/master git.openclonk.org/openclonk.git/tree/refs/heads/master]

=== Report Bugs ===

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

Here's how you can reach us:

* IRC - [irc://irc.euirc.net/openclonk-dev/ #openclonk-dev] on irc.euirc.net (Problems connecting? Use irc.ham.de.euirc.net)
* Bugtracker - [http://bugs.openclonk.org bugs.openclonk.org]
* Forum - [http://forum.openclonk.org forum.openclonk.org]

=== Contribute Scripts or Game Content ===

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

* Developer Documentation [http://docs.openclonk.org/en/sdk/ docs.openclonk.org/en/sdk/]
* Forum - [http://forum.openclonk.org forum.openclonk.org]
* Style Guide - [http://wiki.openclonk.org/w/C4Script_Style_Guidelines wiki.openclonk.org/w/C4Script_Style_Guidelines]
* Contribute changes - [[Git Workflow]]
* [http://crucible.openclonk.org Crucible] for code review
* Are you a sound artist? Here is a list of [[missing sounds]] you can contribute.

=== Build OpenClonk Yourself ===

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

* Tutorial for Windows - [http://wiki.openclonk.org/w/Building_with_Windows wiki.openclonk.org/w/Building_with_Windows]
* General instructions - [http://wiki.openclonk.org/w/Build_OpenClonk wiki.openclonk.org/w/Build_OpenClonk]
* Git Workflow Guide - [http://wiki.openclonk.org/w/Git_Workflow wiki.openclonk.org/w/Git_Workflow]
* Git Repository - [http://git.openclonk.org/openclonk.git git.openclonk.org/openclonk.git]
* Source Code Structure - [http://wiki.openclonk.org/w/Source_code_structure wiki.openclonk.org/w/Source_code_structure]

=== Hack the OpenClonk Engine ===

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

* Wondering where to start? - [[GSoC2011Ideas|Ideas page]]
* Debugging synchronization losses - [http://wiki.openclonk.org/w/Sync_losses wiki.openclonk.org/w/Sync_Losses]
* Style Guide - [http://wiki.openclonk.org/w/Style_Guidelines wiki.openclonk.org/w/Style_Guidelines]
* Forum, developers' corner - [http://forum.openclonk.org/board_show.pl?bid=5 forum.openclonk.org]
* Contribute changes - [[Git Workflow]]

=== Internal Links ===

[http://londeroth.org/~ck/oc-release/oc-release.cgi The release button]

=== Legal Stuff ===

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

Missing sounds

2014-08-07T20:17:25Z

Sven2: /* Sounds */

2011-09-28T21:50:25Z

Sven2:

2010-02-08T19:25:28Z

Sven2: /* Scenarios */

Roadmap

2010-02-08T19:24:59Z

Sven2: /* Objects */

==Roadmap==

We have set us the goal to have a '''playable game''' for our next [http://forum.openclonk.org/topic_show.pl?tid=325 OpenClonk meeting] starting on March 21st 2010.

===Development goal===
The goal is to create some weapons, useful tools and other objects which can be used in small melees and parcours. We aim to have a few scenarios. Probably, we will go into the direction of settlement, mining and production lines after that, but we will decide on that when it's time. This is something we can work out at the OCM.

===Todos===
For this goal to reach, certain basic features have to be completed. That doesn't mean that we shouldn't do anything else or anything more. These are just the necessary features.
Much of this is (finally) work for the scripter and also for the graphic artists (render the objects, decoration textures?), sound and music makers.

====HUD====
...needs to be finished and bug-free engine-side. Related items in the bugtracker are: #66, #62, #67, #98, #99, #100, #72

====Basic controls and the clonk====

* Gamepad controls & the type of control needs to be chooseable in the frontend (Sven2)
* Finish animations (Randrian) and new control behaviour (Newton)
* Meshes of items must be attachable to the clonk for animations (ck?)

====Goals====

* Race(Parcour): Extend the goal with the possibility of checkpoints. The clonks have to come by the checkpoints in the (right) order to win. Option to respawn the clonk at the checkpoint. Checkpoint could be e.g. a flag pole. (Maikel)
* Melee: Last man (team) standing wins. If or how many relaunches each player gets, should be configurable (by script). The goal must work for teams, too.

====Objects====

# Items with which the clonk can overcome obstacles
#* Shovel (animation)
#* Loam
#* ...more items. Examples: Climbing hook, thrusters, staffs with certain effects, pickaxes, ropes, CX-like catapult. We didn't plan that out intentionally. If someone got solid ideas for this, he can implement it.
# Items with what one can fight
#* A (volcanic) flint to be found in the earth
#* A few melee weapons (e.g. also shield)
#* Bow (maybe with other arrow types too)
#* Musket
#* ... a few other ranged weapons or items

====Scenarios====
The Material.c4g needs to be ~complete. All typical materials from CR plus at least castle walls (stone/granite textures) and some other textures which might be useful in designing scenarios.
This will be the topic in some of the later meetings, when the objects have been scripted. During the meeting, nobody came up with concrete ideas for race scenarios.
Anyway, at this point at least this scenario should be done in any case:

* Tutorial scenario
o Would be nice to have a tutorial scenario that introduces each object/control mechanism one by one
o Could start out with simple movement left/right. Then you need to jump. Later, you find a shovel, then loam, etc.
o A message at every checkpoint, telling you what to do next

====Artwork====

* Main menu background / Loaders
* (Logo) / Upper board, Lower board

====Misc====
See bugtracker

Roadmap

2010-02-08T19:24:08Z

Sven2: /* Goals */

==Roadmap==

We have set us the goal to have a '''playable game''' for our next [http://forum.openclonk.org/topic_show.pl?tid=325 OpenClonk meeting] starting on March 21st 2010.

===Development goal===
The goal is to create some weapons, useful tools and other objects which can be used in small melees and parcours. We aim to have a few scenarios. Probably, we will go into the direction of settlement, mining and production lines after that, but we will decide on that when it's time. This is something we can work out at the OCM.

===Todos===
For this goal to reach, certain basic features have to be completed. That doesn't mean that we shouldn't do anything else or anything more. These are just the necessary features.
Much of this is (finally) work for the scripter and also for the graphic artists (render the objects, decoration textures?), sound and music makers.

====HUD====
...needs to be finished and bug-free engine-side. Related items in the bugtracker are: #66, #62, #67, #98, #99, #100, #72

====Basic controls and the clonk====

* Gamepad controls & the type of control needs to be chooseable in the frontend (Sven2)
* Finish animations (Randrian) and new control behaviour (Newton)
* Meshes of items must be attachable to the clonk for animations (ck?)

====Goals====

* Race(Parcour): Extend the goal with the possibility of checkpoints. The clonks have to come by the checkpoints in the (right) order to win. Option to respawn the clonk at the checkpoint. Checkpoint could be e.g. a flag pole. (Maikel)
* Melee: Last man (team) standing wins. If or how many relaunches each player gets, should be configurable (by script). The goal must work for teams, too.

====Objects====

1. Items with which the clonk can overcome obstacles
* Shovel (animation)
* Loam
* ...more items. Examples: Climbing hook, thrusters, staffs with certain effects, pickaxes, ropes, CX-like catapult. We didn't plan that out intentionally. If someone got solid ideas for this, he can implement it.
2. Items with what one can fight
* A (volcanic) flint to be found in the earth
* A few melee weapons (e.g. also shield)
* Bow (maybe with other arrow types too)
* Musket
* ... a few other ranged weapons or items

====Scenarios====
The Material.c4g needs to be ~complete. All typical materials from CR plus at least castle walls (stone/granite textures) and some other textures which might be useful in designing scenarios.
This will be the topic in some of the later meetings, when the objects have been scripted. During the meeting, nobody came up with concrete ideas for race scenarios.
Anyway, at this point at least this scenario should be done in any case:

* Tutorial scenario
o Would be nice to have a tutorial scenario that introduces each object/control mechanism one by one
o Could start out with simple movement left/right. Then you need to jump. Later, you find a shovel, then loam, etc.
o A message at every checkpoint, telling you what to do next

====Artwork====

* Main menu background / Loaders
* (Logo) / Upper board, Lower board

====Misc====
See bugtracker

Roadmap

2010-02-08T19:23:30Z

Sven2: /* Basic controls and the clonk */

==Roadmap==

We have set us the goal to have a '''playable game''' for our next [http://forum.openclonk.org/topic_show.pl?tid=325 OpenClonk meeting] starting on March 21st 2010.

===Development goal===
The goal is to create some weapons, useful tools and other objects which can be used in small melees and parcours. We aim to have a few scenarios. Probably, we will go into the direction of settlement, mining and production lines after that, but we will decide on that when it's time. This is something we can work out at the OCM.

===Todos===
For this goal to reach, certain basic features have to be completed. That doesn't mean that we shouldn't do anything else or anything more. These are just the necessary features.
Much of this is (finally) work for the scripter and also for the graphic artists (render the objects, decoration textures?), sound and music makers.

====HUD====
...needs to be finished and bug-free engine-side. Related items in the bugtracker are: #66, #62, #67, #98, #99, #100, #72

====Basic controls and the clonk====

* Gamepad controls & the type of control needs to be chooseable in the frontend (Sven2)
* Finish animations (Randrian) and new control behaviour (Newton)
* Meshes of items must be attachable to the clonk for animations (ck?)

====Goals====

* Race(Parcour): Extend the goal with the possibility of checkpoints. The clonks have to come by the checkpoints in the (right) order to win. Option to respawn the clonk at the checkpoint. Checkpoint could be e.g. a flag pole.
* Melee: Last man (team) standing wins. If or how many relaunches each player gets, should be configurable (by script). The goal must work for teams, too.

====Objects====

1. Items with which the clonk can overcome obstacles
* Shovel (animation)
* Loam
* ...more items. Examples: Climbing hook, thrusters, staffs with certain effects, pickaxes, ropes, CX-like catapult. We didn't plan that out intentionally. If someone got solid ideas for this, he can implement it.
2. Items with what one can fight
* A (volcanic) flint to be found in the earth
* A few melee weapons (e.g. also shield)
* Bow (maybe with other arrow types too)
* Musket
* ... a few other ranged weapons or items

====Scenarios====
The Material.c4g needs to be ~complete. All typical materials from CR plus at least castle walls (stone/granite textures) and some other textures which might be useful in designing scenarios.
This will be the topic in some of the later meetings, when the objects have been scripted. During the meeting, nobody came up with concrete ideas for race scenarios.
Anyway, at this point at least this scenario should be done in any case:

* Tutorial scenario
o Would be nice to have a tutorial scenario that introduces each object/control mechanism one by one
o Could start out with simple movement left/right. Then you need to jump. Later, you find a shovel, then loam, etc.
o A message at every checkpoint, telling you what to do next

====Artwork====

* Main menu background / Loaders
* (Logo) / Upper board, Lower board

====Misc====
See bugtracker