.slime
How much slime the bot has: it prevents the bot from being tied and stops viruses; it evaporates 2% per cycle.
Facts
- Address
- 821
- Name
.slime- Kind
- Sense: the engine writes it for the DNA to read
- Group
- Defenses
- Written by
- The engine: in the forces and collisions phase, after evaporating 2%; and in the actions phase, when you make slime. You read it in the next cycle.
- Cleared
- The engine recalculates it every cycle; writing to it changes nothing.
- Range
- 0 to 32000
- Mutations
- picked as a read (
*)
Slime protects against two things that another bot can do to you:
- Ties. Every time someone tries to tie you with
.tie, the engine draws a number between 2 and 92; if your slime is greater, the tie doesn't form. With more than 92 no tie can catch you. Each attempt, whether it succeeds or not, takes 20 slime from you. - Viruses. A virus shot first has to get through the slime. If its strength isn't enough, the slime absorbs it (and is used up); if it gets through, it leaves the slime at 0 and the virus infects anyway. Viruses are covered in DNA and viruses.
The engine publishes it every cycle after evaporating 2%, so the value goes down on its own even if you do nothing. It is made with .mkslime and in a multicellular organism it is shared with .shareslime.
Note that slime also stops you from receiving friendly ties: a child can't tie with .tie to a parent that has more than 92 slime, and every attempt eats 20 slime from the parent. The tie that parent and child are born with does form, because the one receiving that tie is the child, which is born without slime.
' top up slime only if it dropped below 100
cond
*.slime 100 <
start
20 .mkslime store
stop