WikiManual - User contributions [en]

Multibot

2005-09-18T01:30:01Z

66.91.138.35:

==Multibots==
Multibots are organisms that are made up of more than one bot. In a MB (MultiBot) the bots are connected by ties . The first multibot was in the form of a triangle where each bot worked independently, but all three coordinated their movement in order to obtain food.

[[Image:Triangulus_P.jpg|frame|right|This is one of the first and simpliest Multibots there is]]

This is a picture of the Triangulus_P bot, the first MB ever created.

--------------------------------------------------------------------------------

'''MB Commands'''

The bots in the MB must be connected with each other, and for that they use ties . The bots within a MB can share information, energy and protective layers with each other. Bots can learn whether they are a part of MB using the .multi command, which returns 1 when the bot is a part of a MB(intentially or not), and 0 when it is not.

The presence of a tie alone does not make the bot a multibot. The tie must first harden.

--------------------------------------------------------------------------------

'''MB Advantages'''

The MBs have several advantages over a normal [[Single Bot]](SB). Most of these are in the form of cheaper actions (costs of actions divided by number of other bots the current cell is connected to).

--------------------------------------------------------------------------------

'''MB Problems'''

Many MBs have difficulty when it comes time to reproducing. Coordinating motion in one direction amongst the bots can also prove difficult. With good coding, however, any problem can be solved. Helios is a good example of a MB that is stronger than most SB.

Single Bot

2005-09-18T01:29:10Z

66.91.138.35: /* Singlebot Advantages */

A singlebot, sometimes abbreviated as SB, is any bot made of a single cell unconnected to other cells by permanent ties.

[[Image:SB1.jpg|frame|right|This is a typical Singlebot. Note the lack of permanent connective ties. It eats, lives, reproduces and dies entirely independantly (or mostly independantly) of other cells.]]
----
===Singlebot Advantages===

Singlebots are much simpler to program than multibots. They are also significantly more maneuverable. An SB that uses ties does so primarily to feed from other bots. While feeding SBs can become [[Multibots]] but revert to SB status once feeding is complete.

Single Bot

2005-09-18T01:28:56Z

66.91.138.35:

A singlebot, sometimes abbreviated as SB, is any bot made of a single cell unconnected to other cells by permanent ties.

[[Image:SB1.jpg|frame|right|This is a typical Singlebot. Note the lack of permanent connective ties. It eats, lives, reproduces and dies entirely independantly (or mostly independantly) of other cells.]]
----
===Singlebot Advantages===

Singlebots are much simpler to program than multibots. They are also significantly more maneuverable. An SB that uses ties does so primarily to feed from other bots. While feeding SBs can become [Multibots] but revert to SB status once feeding is complete.

Cannibot

2005-09-18T01:26:40Z

66.91.138.35:

Cannibots, or Canni's for short, is a bot that has turned cannibalistic. It typically attacks everything within range, often including it's own children. Many dislike Canni's and typically try to avoid them in sims. Quite often once cannibotism becomes established, one single bot will take over wiping out the population and subsequently dying without leaving any descendents.

'''Ways to avoid Canni's'''

One of the better ways to fight cannibotism is to decrease birth nrg, typical values are 10-100. Another method is to ensure that bots are forced to work together either due to enviromental circumstances or internal feeding methods.

A favorite feeding method is sharing nrg equally at 50%. Any bot not particpating is guaranteed to die off since offspring are unable to feed without a Sharer's help.

'''Accepting Canni's or If you can't beat them join them.'''

Considering that often Canni's are a part of life in EvoSims it is an even better strategy to plan for them from the outset. Genes that allow a bot to fight or flight if attacked are guaranteed to help. Other ways to help ease the transition from normal to Canni is with genes fireing only when refage is 20 >; at this stage a child will have likely been able to get away, leaving the parent free to feed from nearby bots.

Div

2005-09-18T01:15:28Z

66.91.138.35:

To divide in DB you must use inverse polish notation. For example:

Ordinarily you would write: 10/5=2
Now write: 10 5 div

The result left on top of the stack is 2.

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

Mult

2005-09-18T01:14:05Z

66.91.138.35:

To multiply in DB you must use inverse polish notation. For example:

Ordinarily you would write: 5x2=10
Now write: 5 2 mult

The result left on top of the stack is 10.

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

Sub

2005-09-18T01:13:18Z

66.91.138.35:

To subtract in DB you must use inverse polish notation. For example:

Ordinarily you would write: 5-2=3
Now write: 5 2 sub

The result left on top of the stack is 3.

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

Add

2005-09-18T01:12:15Z

66.91.138.35:

To add in DB you must use inverse polish notation. For example:

Ordinarily you would write: 1+2=3
Now write: 1 2 add

The result left on top of the stack is 3.

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

Add

2005-09-18T01:11:51Z

66.91.138.35:

To add in DB you must use inverse polish notation. For example:

Ordinarily you would write: 1+2=3
Now write: 1 2 add

The result left on top of the stack is 3.

Rnd

2005-09-18T01:10:18Z

66.91.138.35:

'''Overview'''

The operator generates a random number.

'''Use'''

State the maximal desired number. The operator will generate a random number between 0 and the specified maximal desired number. The random number is placed on the top of the stack.

Example:

10 rnd 50 store

This stores a random number from 0 -10 in memory location 50.

This is most often used in combat sims to:

*generate different actions per cycle (1 rnd)
*randomize turning radius
*randomize number stored into .tie

'''Uses in Evolution'''

Several bots have been observed using the rnd operator in evolution sims. Presumably this allows the bot access to more memory locations and therefore a wider range of behaviors with little additional code.

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

Rnd

2005-09-18T01:09:56Z

66.91.138.35:

'''Overview'''
The operator generates a random number.

'''Use'''
State the maximal desired number. The operator will generate a random number between 0 and the specified maximal desired number. The random number is placed on the top of the stack.

Example:

10 rnd 50 store

This stores a random number from 0 -10 in memory location 50.

This is most often used in combat sims to:

*generate different actions per cycle (1 rnd)
*randomize turning radius
*randomize number stored into .tie

'''Uses in Evolution'''
Several bots have been observed using the rnd operator in evolution sims. Presumably this allows the bot access to more memory locations and therefore a wider range of behaviors with little additional code.

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

Rnd

2005-09-18T01:09:31Z

66.91.138.35:

'''Overview'''
The operator generates a random number.

'''Use'''
State the maximal desired number. The operator will generate a random number between 0 and the specified maximal desired number. The random number is placed on the top of the stack.

Example:

10 rnd 50 store

This stores a random number from 0 -10 in memory location 50.

This is most often used in combat sims to:

*generate different actions per cycle (1 rnd)
*randomize turning radius
*randomize number stored into .tie

'''Uses in Evolution'''
Several bots have been observed using the rnd operator in evolution sims. Presumably this allows the bot access to more memory locations and therefore a wider range of behaviors with little additional code.

Store

2005-09-18T01:06:03Z

66.91.138.35:

'''Overview'''

Stores the second value on the stack into the memory location specified by the top value.

Syntax
*x y store

Where 'x' is the value to be stored, and 'y' is the memory location.

or

store

Compared to the first, the lonely store-command works on the numbers on the stack, what ever they are.

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

Shooting

2005-09-18T00:59:48Z

66.91.138.35:

The .shoot command is one of the most vital in DB. With it a bot can feed, dispose of waste, shoot poison or venom, and affect another bots memory.

Basics
Whenever a non zero value is stored in .shoot, a shot is produced. This shot by default fires directly along the bot's eye's vector (that is, which direction it's looking). The shot's basic strength and range are determined by a bot's body.

'''Shot Types:'''

'''Feeding Shots'''
*-1 - [[Energy]] Shots
*-2 - Give energy Shoot, bread and butter feeding type
*-6 - Body Shots

'''Waste Poison and Venom'''
*? - Poison Shots(fired automatically at attacker provided defender has poison, cannot be fired manually through the DNA)
*-3? - Venom Shots(can be fired at other bot provided venom stored)
*-4 - Waste Shots(coupled with .shootval to determine waste size)

'''Memory shots'''
By storing positive numbers in .shoot another bot's memory can be overwritten by what's written in .shootval. This can be used to either mess up another bot or to exchange some vital information between bots.

Here's how you'd make another bot turn. Light's Icarus used this to dominate F2 league for a while.

cond 
'you figure it out 
'Icarus fires if: <nowiki>
*.shup</nowiki> -2 != 
start 
.aimdx .shoot store 
314 .shootval store 
stop 

This will make any bot that you hit turn 90 degrees to the right.

--------------------------------------------------------------------------------

Defenses and Attacking
For 2.36 and later, check out [[How defenses and attacks work]]

Advanced Uses of Shootval
As of 2.36, you may 'power up' a shot's strength and range.

Storing a negative value in .shootval will make body shots (-6) and energy shots (-2) have a longer range.

Storing positive values in .shootval will make body shots (-6) and energy shots (-2) become more powerful.

The multiplier is roughly log2(.shootval). That's log base 2. So spend 4 energy in .shootval and you'll double your shot strength or range, but spend 8 energy and you only triple shot strength or range.

This will also work in a way with venom and waste shots. The increase is linear instead of logarithmic though, and you spend venom amount instead of energy. See venom and waste. Note that storing negative numbers for venom or waste shots has no effect, the shootval must be positive. (I think)

Advanced Shooting Commands
.backshot and .aimshoot allow for more control over how the shot is produced.

Storing a positive number in .backshoot or increasing .backshoot by one, will instruct the bot to fire backwards if a non zero value is stored in .shoot.

Saving energy by using the increase operator:

.backshoot inc 
-6 .shoot store 

.aimshoot follows .backshot's syntax, but allows you to specify an angle to shoot at. The number stored here represents the angle from the bot's eye vector (direction it's facing) running counter-clockwise.

Example

314 .aimshoot store 
-2 .shoot store 

will fire a shot directly 90 degrees to the left of the bot's eye.

Shooting

2005-09-18T00:58:59Z

66.91.138.35:

The .shoot command is one of the most vital in DB. With it a bot can feed, dispose of waste, shoot poison or venom, and affect another bots memory.

Basics
Whenever a non zero value is stored in .shoot, a shot is produced. This shot by default fires directly along the bot's eye's vector (that is, which direction it's looking). The shot's basic strength and range are determined by a bot's body.

'''Shot Types:'''

'''Feeding Shots'''
*-1 - [[Energy]] Shots
*-2 - Give energy Shoot, bread and butter feeding type
*-6 - Body Shots

'''Waste Poison and Venom'''
*? - Poison Shots(fired automatically at attacker provided defender has poison, cannot be fired manually through the DNA)
*-3? - Venom Shots(can be fired at other bot provided venom stored)
*-4 - Waste Shots(coupled with .shootval to determine waste size)

'''Memory shots'''
By storing positive numbers in .shoot another bot's memory can be overwritten by what's written in .shootval. This can be used to either mess up another bot or to exchange some vital information between bots.

Here's how you'd make another bot turn. Light's Icarus used this to dominate F2 league for a while.

cond 
'you figure it out 
'Icarus fires if: <nowiki>
*.shup -2 != </nowiki>
start 
.aimdx .shoot store 
314 .shootval store 
stop 

This will make any bot that you hit turn 90 degrees to the right.

--------------------------------------------------------------------------------

Defenses and Attacking
For 2.36 and later, check out [[How defenses and attacks work]]

Advanced Uses of Shootval
As of 2.36, you may 'power up' a shot's strength and range.

Storing a negative value in .shootval will make body shots (-6) and energy shots (-2) have a longer range.

Storing positive values in .shootval will make body shots (-6) and energy shots (-2) become more powerful.

The multiplier is roughly log2(.shootval). That's log base 2. So spend 4 energy in .shootval and you'll double your shot strength or range, but spend 8 energy and you only triple shot strength or range.

This will also work in a way with venom and waste shots. The increase is linear instead of logarithmic though, and you spend venom amount instead of energy. See venom and waste. Note that storing negative numbers for venom or waste shots has no effect, the shootval must be positive. (I think)

Advanced Shooting Commands
.backshot and .aimshoot allow for more control over how the shot is produced.

Storing a positive number in .backshoot or increasing .backshoot by one, will instruct the bot to fire backwards if a non zero value is stored in .shoot.

Saving energy by using the increase operator:

.backshoot inc 
-6 .shoot store 

.aimshoot follows .backshot's syntax, but allows you to specify an angle to shoot at. The number stored here represents the angle from the bot's eye vector (direction it's facing) running counter-clockwise.

Example

314 .aimshoot store 
-2 .shoot store 

will fire a shot directly 90 degrees to the left of the bot's eye.

Shooting

2005-09-18T00:58:09Z

66.91.138.35:

The .shoot command is one of the most vital in DB. With it a bot can feed, dispose of waste, shoot poison or venom, and affect another bots memory.

Basics
Whenever a non zero value is stored in .shoot, a shot is produced. This shot by default fires directly along the bot's eye's vector (that is, which direction it's looking). The shot's basic strength and range are determined by a bot's body.

'''Shot Types:'''

'''Feeding Shots'''
*-1 - [[Energy]] Shots
*-2 - Give energy Shoot, bread and butter feeding type
*-6 - Body Shots

'''Waste Poison and Venom'''
*? - Poison Shots(fired automatically at attacker provided defender has poison, cannot be fired manually through the DNA)
*-3? - Venom Shots(can be fired at other bot provided venom stored)
*-4 - Waste Shots(coupled with .shootval to determine waste size)

'''Memory shots'''
By storing positive numbers in .shoot another bot's memory can be overwritten by what's written in .shootval. This can be used to either mess up another bot or to exchange some vital information between bots.

Here's how you'd make another bot turn. Light's Icarus used this to dominate F2 league for a while.

cond 
'you figure it out 
'Icarus fires if: 
*.shup -2 != 
start 
.aimdx .shoot store 
314 .shootval store 
stop 

This will make any bot that you hit turn 90 degrees to the right.

--------------------------------------------------------------------------------

Defenses and Attacking
For 2.36 and later, check out [[How defenses and attacks work]]

Advanced Uses of Shootval
As of 2.36, you may 'power up' a shot's strength and range.

Storing a negative value in .shootval will make body shots (-6) and energy shots (-2) have a longer range.

Storing positive values in .shootval will make body shots (-6) and energy shots (-2) become more powerful.

The multiplier is roughly log2(.shootval). That's log base 2. So spend 4 energy in .shootval and you'll double your shot strength or range, but spend 8 energy and you only triple shot strength or range.

This will also work in a way with venom and waste shots. The increase is linear instead of logarithmic though, and you spend venom amount instead of energy. See venom and waste. Note that storing negative numbers for venom or waste shots has no effect, the shootval must be positive. (I think)

Advanced Shooting Commands
.backshot and .aimshoot allow for more control over how the shot is produced.

Storing a positive number in .backshoot or increasing .backshoot by one, will instruct the bot to fire backwards if a non zero value is stored in .shoot.

Saving energy by using the increase operator:

.backshoot inc 
-6 .shoot store 

.aimshoot follows .backshot's syntax, but allows you to specify an angle to shoot at. The number stored here represents the angle from the bot's eye vector (direction it's facing) running counter-clockwise.

Example

314 .aimshoot store 
-2 .shoot store 

will fire a shot directly 90 degrees to the left of the bot's eye.

Shooting

2005-09-18T00:51:56Z

66.91.138.35:

The .shoot command is one of the most vital in DB. With it a bot can feed, dispose of waste, shoot poison or venom, and affect another bots memory.

Basics
Whenever a non zero value is stored in .shoot, a shot is produced. This shot by default fires directly along the bot's eye's vector (that is, which direction it's looking). The shot's basic strength and range are determined by a bot's body.

Shot Types
Feeding Shots
*-1 - Energy Shots
*-2 - Give energy Shoot, bread and butter feeding type
*-6 - Body Shots
Waste Poison and Venom
X - Poison Shots(fired automatically at attacker provided defender has poison, cannot be fired manually through the DNA)
? - Venom Shots(can be fired at other bot provided venom stored)
-4 - Waste Shots(coupled with .shootval to determine waste size)
Memory shots
By storing positive numbers in .shoot another bot's memory can be overwritten by what's written in .shootval. This can be used to either mess up another bot or to exchange some vital information between bots.

Here's how you'd make another bot turn. Light's Icarus used this to dominate F2 league for a while.

cond
'you figure it out
'Icarus fires if:
*.shup -2 !=
start
.aimdx .shoot store
314 .shootval store
stop

This will make any bot that you hit turn 90 degrees to the right.

--------------------------------------------------------------------------------

Defenses and Attacking
For 2.36 and later, check out How defenses and attacks work ?

Advanced Uses of Shootval
As of 2.36, you may 'power up' a shot's strength and range.

Storing a negative value in .shootval will make body shots (-6) and energy shots (-2) have a longer range.

Storing positive values in .shootval will make body shots (-6) and energy shots (-2) become more powerful.

The multiplier is roughly log2(.shootval). That's log base 2. So spend 4 energy in .shootval and you'll double your shot strength or range, but spend 8 energy and you only triple shot strength or range.

This will also work in a way with venom and waste shots. The increase is linear instead of logarithmic though, and you spend venom amount instead of energy. See venom and waste. Note that storing negative numbers for venom or waste shots has no effect, the shootval must be positive. (I think)

Advanced Shooting Commands
.backshot and .aimshoot allow for more control over how the shot is produced.

storing 1 in .backshoot, will instruct the bot to fire backwards if a non zero value is stored in .shoot.

Note that this:

-2 .backshoot store

will NOT work. You must do:

1 .backshoot store
-6 .shoot store

or to save energy use the increase operator:

.backshoot inc
-6 .shoot store

.aimshoot follows .backshot's syntax, but allows you to specify an angle to shoot at. The number stored here represents the angle from the bot's eye vector (direction it's facing) running counter-clockwise.

So

314 .aimshoot store
-2 .shoot store

will fire a shot directly 90 degrees to the left of the bot's eye.

Shooting

2005-09-18T00:50:57Z

66.91.138.35:

The .shoot command is one of the most vital in DB. With it a bot can feed, dispose of waste, shoot poison or venom, and affect another bots memory.

Basics
Whenever a non zero value is stored in .shoot, a shot is produced. This shot by default fires directly along the bot's eye's vector (that is, which direction it's looking). The shot's basic strength and range are determined by a bot's body.

Shot Types
Feeding Shots
-1 - Energy Shots
-2 - Give energy Shoot, bread and butter feeding type
-6 - Body Shots
Waste Poison and Venom
X - Poison Shots(fired automatically at attacker provided defender has poison, cannot be fired manually through the DNA)
? - Venom Shots(can be fired at other bot provided venom stored)
-4 - Waste Shots(coupled with .shootval to determine waste size)
Memory shots
By storing positive numbers in .shoot another bot's memory can be overwritten by what's written in .shootval. This can be used to either mess up another bot or to exchange some vital information between bots.

Here's how you'd make another bot turn. Light's Icarus used this to dominate F2 league for a while.

cond
'you figure it out
'Icarus fires if:
*.shup -2 !=
start
.aimdx .shoot store
314 .shootval store
stop

This will make any bot that you hit turn 90 degrees to the right.

--------------------------------------------------------------------------------

Defenses and Attacking
For 2.36 and later, check out How defenses and attacks work ?

Advanced Uses of Shootval
As of 2.36, you may 'power up' a shot's strength and range.

Storing a negative value in .shootval will make body shots (-6) and energy shots (-2) have a longer range.

Storing positive values in .shootval will make body shots (-6) and energy shots (-2) become more powerful.

The multiplier is roughly log2(.shootval). That's log base 2. So spend 4 energy in .shootval and you'll double your shot strength or range, but spend 8 energy and you only triple shot strength or range.

This will also work in a way with venom and waste shots. The increase is linear instead of logarithmic though, and you spend venom amount instead of energy. See venom and waste. Note that storing negative numbers for venom or waste shots has no effect, the shootval must be positive. (I think)

Advanced Shooting Commands
.backshot and .aimshoot allow for more control over how the shot is produced.

storing 1 in .backshoot, will instruct the bot to fire backwards if a non zero value is stored in .shoot.

Note that this:

-2 .backshoot store

will NOT work. You must do:

1 .backshoot store
-6 .shoot store

or to save energy use the increase operator:

.backshoot inc
-6 .shoot store

.aimshoot follows .backshot's syntax, but allows you to specify an angle to shoot at. The number stored here represents the angle from the bot's eye vector (direction it's facing) running counter-clockwise.

So

314 .aimshoot store
-2 .shoot store

will fire a shot directly 90 degrees to the left of the bot's eye.

.aimdx

2005-09-18T00:48:18Z

66.91.138.35:

Less than

2005-09-18T00:43:29Z

66.91.138.35:

Takes the two top values on the stack, and checks whether the first value is less than the second.

Examples:

10 5 <
Is false

10 25 <
Is true

10 10 <
Is false, as 10 is equal to 10, not less.

=== Logical Comparison Operators===
* [[=]]
* [[!=]]
* [[Greater than|>]]
* [[Less than|<]]
* [[%=]]
* [[!%=]]

Greater than

2005-09-18T00:42:25Z

66.91.138.35:

Takes the two top values on the stack, and checks whether the first value is greater then the second.

Examples:

10 5 >
Is true

10 25 >
Is false

10 10 >
Is false, as 10 is equal to 10, not greater.

=== Logical Comparison Operators===
* [[=]]
* [[!=]]
* [[Greater than|>]]
* [[Less than|<]]
* [[%=]]
* [[!%=]]

Greater than

2005-09-18T00:42:00Z

66.91.138.35:

!=

2005-09-18T00:41:00Z

66.91.138.35:

Not Equals takes the top two values on the regular stack, and places true on the conditions stack if the two values were not equal, false otherwise.

For instance:

50 50 !=

Will place false on the conditions stack. The two 50s are removed from the regular stack.

50 60 !=

Will place true on the conditions stack. The 50 and 60 are still removed from the regular stack.

=== Logical Comparison Operators===
* [[=]]
* [[!=]]
* [[Greater than|>]]
* [[Less than|<]]
* [[%=]]
* [[!%=]]

=

2005-09-18T00:39:39Z

66.91.138.35:

Equals takes the top two values on the regular stack, and places true on the conditions stack if the two values were equal, false otherwise.

For instance:

50 50 =

Will place true on the conditions stack. The two 50s are removed from the regular stack.

50 60 =

Will place false on the conditions stack. The 50 and 60 are still removed from the regular stack.

=== Logical Comparison Operators===
* [[=]]
* [[!=]]
* [[Greater than|>]]
* [[Less than|<]]
* [[%=]]
* [[!%=]]

=

2005-09-18T00:39:02Z

66.91.138.35:

Inc/dec

2005-09-18T00:35:23Z

66.91.138.35:

Increase/Decrease
These operators, inc(increase) and dec(decrease), are some of the most useful but are infrequently used. They work by either decreasing or increasing a memory location by 1.

For example:

50 inc

adds 1 to *50. When more are used simultaneously the effects are cumulative.

For Example:

50 dec 
50 dec 
50 dec 

Subtracts 3 from *50.
One of the more popular uses of this is for birth tie removal.

cond 
start 
.tie *.robage 1000 mult add inc 
.deltie *.robage 1 sub 1000 mult add inc 
stop 

It has also been used effectivly as an inter-gene signal and method to "freeze" values.

Not all locations can be handled with them, memlocs 1-8(more?) can not be inc/dec. This is to ensure that the bots are required to expend some energy. (Note: being changed in new version)

'''Value freezing using inc/dec'''

This technique allows you to "freeze" values or to raise/lower a number to a value and then keep it there. This is best used for when you need a value at a constant number, but without the cost of continously storing it.

' Basic method to demonstrate freezing 
' Will keep .tieloc at -1 permanently 
cond 
start 
.tieloc *.tieloc dup div mult inc 
.tieloc dec 
stop' More complex method demonstrates freezing 
' at a value with .ploc=7 
cond 
start 
' When *.ploc = 7 dec by 1 
.ploc *.ploc 7 sub 1000 mult add dec 
.ploc inc 
stop

Inc/dec

2005-09-18T00:32:09Z

66.91.138.35:

Increase/Decrease
These operators, inc(increase) and dec(decrease), are some of the most useful but are infrequently used. They work by either decreasing or increasing a memory location by 1.

For example:

50 inc

adds 1 to 50. When more are used simultaneously the effects are cumulative.

For Example:

50 inc
50 inc
50 inc

Adds 3 to 50.
One of the more popular uses of this is for birth tie removal.

<nowiki>
cond
start
.tie *.robage 1000 mult add inc
.deltie *.robage 1 sub 1000 mult add inc
stop
</nowiki>
It has also been used effectivly as an inter-gene signal and method to "freeze" values.

Not all locations can be handled with them, memlocs 1-8(more?) can not be inc/dec. This is to ensure that the bots are required to expend some energy.

'''Value freezing using inc/dec'''

This technique allows you to "freeze" values or to raise/lower a number to a value and then keep it there. This is best used for when you need a value at a constant number, but without the cost of continously storing it.

<nowiki>
' Basic method to demonstrate freezing
' Will keep .tieloc at -1 permanently
cond
start
.tieloc *.tieloc dup div mult inc
.tieloc dec
stop' More complex method demonstrates freezing
' at a value with .ploc=7
cond
start
' When *.ploc = 7 dec by 1
.ploc *.ploc 7 sub 1000 mult add dec
.ploc inc
stop
</nowiki>

Inc/dec

2005-09-18T00:31:49Z

66.91.138.35:

Increase/Decrease
These operators, inc(increase) and dec(decrease), are some of the most useful but are infrequently used. They work by either decreasing or increasing a memory location by 1.

For example:

50 inc

adds 1 to 50. When more are used simultaneously the effects are cumulative.

For Example:

50 inc
50 inc
50 inc

Adds 3 to 50.
One of the more popular uses of this is for birth tie removal.

<nowiki>
cond
start
.tie *.robage 1000 mult add inc
.deltie *.robage 1 sub 1000 mult add inc
stop
</nowiki>
It has also been used effectivly as an inter-gene signal and method to "freeze" values.

Not all locations can be handled with them, memlocs 1-8(more?) can not be inc/dec. This is to ensure that the bots are required to expend some energy.

'''Value freezing using inc/dec'''

This technique allows you to "freeze" values or to raise/lower a number to a value and then keep it there. This is best used for when you need a value at a constant number, but without the cost of continously storing it.

<math>nowiki>
' Basic method to demonstrate freezing
' Will keep .tieloc at -1 permanently
cond
start
.tieloc *.tieloc dup div mult inc
.tieloc dec
stop' More complex method demonstrates freezing
' at a value with .ploc=7
cond
start
' When *.ploc = 7 dec by 1
.ploc *.ploc 7 sub 1000 mult add dec
.ploc inc
stop
</nowiki>
</math><

End

2005-09-18T00:30:18Z

66.91.138.35: /* Flow Commands */

The most important of all even if it is only written once in a file, End tells the program when to stop reading the DNA. If it is not there the program will add (random?) numbers, largly consisting of zeros until another bot's DNA(that does contain end) is added to the end(normally a veggie). Often errors can occur due to lack of a proper end statement.

=== Flow Commands===
* [[cond]]
* [[start]]
* [[stop]]
* [[end]]
* [[Robot DNA]]

End

2005-09-18T00:29:56Z

66.91.138.35:

Stop

2005-09-18T00:29:44Z

66.91.138.35:

Stop marks the end of a gene.

=== Flow Commands===
* [[cond]]
* [[start]]
* [[stop]]
* [[end]]

Start

2005-09-18T00:29:29Z

66.91.138.35:

Start Flow Operator

Start marks the action step of a gene. This is where logical operators, [[store]] and [[inc/dec]] can be used. It will only execute if the boolean value in from conditions stack is true.

=== Flow Commands===
* [[cond]]
* [[start]]
* [[stop]]
* [[end]]

Cond

2005-09-18T00:29:10Z

66.91.138.35: /* Condition */

=Condition=

'''cond''' marks the start of a gene in the DNA. Everything from cond to [[start]] is evaulated. Once the program reaches start, any values still on the conditions stack are anded together. If the resulting boolean value is true, every [[action]] after start to the next stop command is executed.

Otherwise, the program continues to the next cond statement, or stops reading the DNA if the [[end]] is found instead.

The condition is the part of the gene that tells if should happen or not. Many action commands can be used in here but not all.

=== Flow Commands===
* [[cond]]
* [[start]]
* [[stop]]
* [[end]]

End

2005-09-18T00:28:21Z

66.91.138.35:

Stop

2005-09-18T00:26:42Z

66.91.138.35:

Stop marks the end of a gene.

Start

2005-09-18T00:25:59Z

66.91.138.35:

Cond

2005-09-18T00:24:46Z

66.91.138.35: /* Condition */

Cond

2005-09-18T00:24:37Z

66.91.138.35: /* Condition */

=Condition=

'''cond''' marks the start of a gene in the DNA. Everything from cond to [[start]] is evaulated. Once the program reaches start, any values still on the conditions stack are anded together. If the resulting boolean value is true, every [[action]] after start to the next stop command is executed.

Otherwise, the program continues to the next cond statement, or stops reading the DNA if the[[end]] is found instead.

The condition is the part of the gene that tells if should happen or not. Many action commands can be used in here but not all.

Cond

2005-09-18T00:24:22Z

66.91.138.35: /* Condition */

=Condition=

'''cond''' marks the start of a gene in the DNA. Everything from cond to [[start]] is evaulated. Once the program reaches start, any values still on the conditions stack are anded together. If the resulting boolean value is true, every [[action]] after start to the next stop command is executed.

Otherwise, the program continues to the next cond statement, or stops reading the DNA if the end[[end]] is found instead.

The condition is the part of the gene that tells if should happen or not. Many action commands can be used in here but not all.

Other Resources

2005-06-04T03:49:12Z

66.91.138.35:

==Links to other areas related to DB==

* [http://www.darwinbots.com/ Darwinbots' New Home]
* [http://s9.invisionfree.com/DarwinBots_Forum/index.php?act=idx/index.php?act=site New Forum]

* [http://darwinbots.xwiki.com/ Xwiki vers of Manual (Retired)]
* [http://darwinbots.proboards20.com/index.cgi Old Forum (Dead Feb 05)]
* [http://digilander.libero.it/darwinbots/ Old DB Homepage (No longer updated)]
* [http://www.sodev.free-speicher.de/dbdb/ Database]

Other Resources

2005-06-04T03:48:46Z

66.91.138.35:

==Links to other areas related to DB==

[http://www.darwinbots.com/ Darwinbots' New Home]
[http://s9.invisionfree.com/DarwinBots_Forum/index.php?act=idx/index.php?act=site New Forum]

[http://darwinbots.xwiki.com/ Xwiki vers of Manual (Retired)]
[http://darwinbots.proboards20.com/index.cgi Old Forum (Dead Feb 05)]
[http://digilander.libero.it/darwinbots/ Old DB Homepage (No longer updated)]
[http://www.sodev.free-speicher.de/dbdb/ Database]

Advanced Stack

2005-06-04T03:41:11Z

66.91.138.35:

'''Saving Values into the Stack'''
The Stack can be used as a means to save a value than retrieve it whenever necessary. The new dup operator allows the number to stay in the Stack continously

{code}
cond
*.robage 0 =
start
998 rnd 1 add
stopcond
*.refeye *.myeye !=
*.eye5 50 >
start
dup .tie store
stop
{code}

This will duplicate the value and also use it to tie. The same value can then be kept and re-used forever. To use it as part of a condition statement requires a solo "dup" gene.

'''Timing Actions with the Stack'''
Another more advanced use is to store a whole series of actions into the stack and then unstacking them in the following cycles.

{code}
cond
*.robage 0 =
start
50 .repro
314 .aimdx
10 .up
stop

cond
start
dup
stop

cond
0 >
' dup gene and 0 > not really needed in this case but helps to
' demo ability to sense the stack without destroying the information
start
store
stop
{code}

This will cause the bot to perform the above actions from bottom to top.
This could also be used for anything from MB reproduction to more accurate aiming.

--------------------------------------------------------------------------------

[[Stack]]

MB Sharing

2005-06-04T03:37:28Z

66.91.138.35:

Share commands

A bot can share things with another bot if they are connected through tie. There are DNA commands that allow sharing of energy, slime, shell, and waste.

--------------------------------------------------------------------------------

Share commands Command Effect
sharenrg This lets bot share energy. There is no need to address a specific tie reference number. The number stored in here becomes the percentage of total energy that I receive.
sharewaste This lets bot share waste.
shareshell This lets bot share shell. Individual bots within multibots are allowed to have twice as much shell as singlebots.
shareslime This lets bot share slime. Individual bots within multibots are allowed to have twice as much shell as singlebots.

Example

Suppose there are two bots connected by a tie. First bot has 40 waste (or any other shared material) and the second one has 60. If first bot executes command

10 .sharewaste store
then the total amount of waste (100) will be redistributed so that the first bot receives 10% of that total. The final outcome is that the first bot will have 10 waste and the second bot will have 90 waste.
Uses

A useful way to use these with combat bots is shown below.

cond
*.multi 1 =
start
99 .sharenrg store
.sharewaste inc
stop

In this gene 99% of the total energy is taken by a bot. This is useful to feed in case a bot accidently becomes a MB while tie feeding.

The code ".sharewaste inc" forces the enemy to take 99% of the attacker's waste. Useful to dump waste without having to shoot it away, also plants will convert this waste to energy allowing the bot to recoup some energy.

Epigenetic Memory Locations

2005-06-04T03:35:15Z

66.91.138.35:

During the birthing cycle, baby robots copy certain information from the memory of the parent. Copying is done through the birth tie . The copied locations are 971 through 990 and one location is copied each cycle for 20 cycles. Robots who cut their gestation periods short will miss out on the valuable opportunity to pass on vital information to their offspring.

Epigenetic Memory Locations

2005-06-04T03:35:04Z

66.91.138.35:

==Racial memory==

During the birthing cycle, baby robots copy certain information from the memory of the parent. Copying is done through the birth tie . The copied locations are 971 through 990 and one location is copied each cycle for 20 cycles. Robots who cut their gestation periods short will miss out on the valuable opportunity to pass on vital information to their offspring.

Birth tie

2005-06-04T03:33:38Z

66.91.138.35:

A thick tie seen at birth connecting both parent and offspring. Lasts for 20 cycles, plus number of cycles required to transfer Epigenic Memory, from parent to child. Can reduce time by means of creating permanent tie and then deleting said tie. Normally this is done to reduce motion penalties imposed by attached bot.

Other methods include:

* limit motion when tied to child
* limit child's motion.

Birth tie

2005-06-04T03:33:15Z

66.91.138.35:

==The Birth Tie==

--------------------------------------------------------------------------------

A thick tie seen at birth connecting both parent and offspring. Lasts for 20 cycles, plus number of cycles required to transfer Epigenic Memory, from parent to child. Can reduce time by means of creating permanent tie and then deleting said tie. Normally this is done to reduce motion penalties imposed by attached bot.

Other methods include:

* limit motion when tied to child
* limit child's motion.

Organism

2005-06-04T03:31:47Z

66.91.138.35:

An Organism is a either a single bot or a group of bots connected by ties.

Also see:

[[Save entire organism]]

Organism

2005-06-04T03:31:14Z

66.91.138.35:

==Organism==
An Organism is a either a single bot or a group of bots connected by ties.

Also see:

[[Save entire organism]]

Multibot

2005-06-04T03:29:08Z

66.91.138.35:

==Multibots==
Multibots are organisms that are made up of more than one bot. In a MB (MultiBot) the bots are connected by ties . The first multibot was in the form of a triangle where each bot worked independently, but all three coordinated their movement in order to obtain food.

"No image currently here"

This is a picture of the Triangulus_P bot, the first MB ever created.

--------------------------------------------------------------------------------

'''MB Commands'''

The bots in the MB must be connected with each other, and for that they use ties . The bots within a MB can share information, energy and protective layers with each other. Bots can learn whether they are a part of MB using the .multi command, which returns 1 when the bot is a part of a MB(intentially or not), and 0 when it is not.

--------------------------------------------------------------------------------

'''MB Advantages'''

The MBs have some advantages over a normal Single Bot(SB) . Each bot in a MB can carry more slime and shell. They can share the work between them. Some bots do work that others don't. And they dont suffer ShockDeath.

--------------------------------------------------------------------------------

'''MB Problems'''

Many MBs have difficulty when it comes time to reproduce. Co-ordinating motion in one direction amongst the bots can also prove difficult. With good coding, however, any problem can be solved.