DarwinBotsManual
Open the app EspañolES

Parameters: Death and decay

What is left of a bot that dies and how it rots, whether energy gifts and waste wear off in flight, and how much waste it takes for a bot to get poisoned.

This group decides what happens to what is left over: dead bots, shots that stay in flight and waste that piles up. There are three topics:

Together they control how much gets recycled. With corpses that do not rot, the energy of the dead stays in the world until someone eats it; without corpses, it is lost. In Experiment's basic mode, the first one appears as Corpses.

Corpses

Dead bots remain as food.

Default
yes
Usual range
yes / no
Variable
CorpseEnabled
Key
opt:50
Live
can be changed while the simulation runs
Mode
basic and advanced

If it is on (as the app starts), a bot whose energy drops below 15 turns into a corpse: it keeps its body, which others can eat with −6 shots or through a tie, and it stops running its DNA. With it off, the bot holds on until its energy drops below 0.5 and then disappears, leaving nothing. The F1 league turns it off.

It only affects those that die of hunger or from a shock: those emptied by a shot and those left without a body never leave a corpse. The full table is in the causes of death, and what a corpse is, in corpses.

Body decay per cycle

At each decay step, a corpse loses a tenth of this value in body.

Default
0
Usual range
0 to 1000
Variable
Decay
Key
opt:51
Live
can be changed while the simulation runs
Mode
advanced only

How much a corpse rots at each step: it loses a tenth of this value in body. With 0, the app's value, corpses never rot and stay in the world until someone eats them.

In one test, with 1000 and a step every 2 cycles, a corpse with 1040 body lost 100 every two cycles and disappeared after twenty-some cycles. Fast rotting clears the field of corpses that block the light and get in the way; slow rotting feeds the scavengers. See decay.

Decay delay (cycles)

Cycles between two decay steps.

Default
100
Usual range
1 to 32000
Variable
Decaydelay
Key
opt:52
Live
can be changed while the simulation runs
Mode
advanced only

How many cycles pass between decay steps. The app starts with 100: with that, even with Body decay per cycle other than 0, a corpse lasts a long time. With 1 it rots every cycle. It only counts if Body decay per cycle is not 0.

Decay type

What the corpse releases as it decays.

Default
0
Values
0 = no shot · 2 = waste shot · 3 = energy shot
Variable
DecayType
Key
opt:53
Live
can be changed while the simulation runs
Mode
advanced only

Whether the corpse releases something at each decay step, in a random direction:

  • no shot (the app's value): it only loses body.
  • waste shot: it releases a waste shot (−4), which fouls whichever neighbor it hits.
  • energy shot: it releases an energy gift (−2), a small ration for whoever passes nearby.

The shot goes out with the value of Body decay per cycle as long as more than a tenth of that is left in the body; on the last step it goes out with whatever body is left. Since body is worth 10 energy, in the normal steps what it releases equals what it loses. It only counts if Body decay per cycle is not 0. See what each shot does.

Energy shots do not decay

Energy gifts (.shoot −2) neither lose value nor age: they fly until they hit someone.

Default
no
Usual range
yes / no
Variable
NoShotDecay
Key
opt:54
Live
can be changed while the simulation runs
Mode
advanced only

Energy gifts (−2 shots) do not lose strength in flight or age: they fly with their full value until they hit someone. That includes the energy that every −1 or −6 shot returns to the shooter: if it does not reach them, it keeps flying and someone else can eat it. Off in the app and in the F1 league.

With this parameter on, no energy is lost in the air, but in a world with walls the lost gifts bounce endlessly until someone crosses their path.

Waste shots do not decay

Waste shots neither lose value nor age: they fly until they hit someone.

Default
no
Usual range
yes / no
Variable
NoWShotDecay
Key
opt:55
Live
can be changed while the simulation runs
Mode
advanced only

The same for waste shots (−4): they do not lose strength or age, and they keep flying until they hit someone. A bot that throws out its waste to clean itself can no longer count on it vanishing: sooner or later it reaches someone else. Off in the app and in the F1 league.

Waste is toxic from

Accumulated waste from which it hurts. 0 is taken as 400.

Default
400
Usual range
0 to 2147483647
Variable
BadWastelevel
Key
opt:56
Live
can be changed while the simulation runs
Mode
advanced only

How much waste it takes for a bot to get poisoned. If .waste plus the permanent waste (.pwaste) go over this value, every cycle the engine writes random numbers to random memory addresses, once for every 4 units of excess. Any address from 1 to 1000 can be hit, including commands such as .repro or .shoot; only .mkchlr and .rmchlr are spared.

The app starts with 400 and the F1 league raises it to 10000. In one test, a bot that made shell without throwing out its waste had clean memory with the level at 5000 and memory full of garbage within a few cycles with 400. If you set 0, the engine takes it as 400; a negative value turns poisoning off.