Documentation


Introduction

The "wesen" are creatures living in a torus-world (donut).
Their "life" consists of moving to the food and eating it.
It's your job to program the instincts of a species which
will be in a contest with others. The sourcecode of your
species ans therefore all species are simply called "source".
Advanced features of the wesen are reproducing, attacking and talking.
The one who survives all the others is the winner.
The key to good tactics is communication.
The better your algortihms are, the more likely you'll win.


Getting started

sorry, not available yet


More specific information

Quick Reference on Wesen/source interface

Methods the interface provides you:

Methods you should write (not necessary):

Config options explained

This is the default scheme of config options:

[section]
option1=value
option2=value
The names of options are usually also the names used in the infoObjects in your wesenSource.
If value is (1,yes,true) it is considered as True.
If value is (0,no,false) it is considered as False.
You must not add "" to the config options.
You can get some help by using the command-line config editor (wesen c).

[general]
logfile = /home/konrad/.wesen/log
guisource = gui
enablelog = True
enablegui = 1
In the general section, you should change nothing.
If you want to disable logging permanently, set
enablelog=No
You can read the logs at the path specified in "logfile".

[world]
length = 100
Worldlength*dimensions is the size of the world.
By default it is 100, so the size is 10,000.
Bigger values slow down the gui dramatically.

[wesen]
count = 10
energy = 100
maxage = 500
sources = DrunkenSailor,Nightwatch
In the wesen section you can choose which sources to use.
Count determines how many instances of each source are made during initialization.
Energy is the starting energy of every wesen.
The lower it is, the harder it is to survive at the beginning
when no food is near a wesen.


We highly recommend to not change the sections
[Time], [Range] and [Food]
because it could destroy the game balance.


Code conventions

Please look at Guido van Rossums code conventions
If you want to be conformistic: we use FirstLetterCapitalized()
for methods (simple calls without important results) and
x=firstLetterNotCapitalized() for functions (when the result is most important).


Writing a source

sorry, not available yet


Hints