.mkslime
Command to make slime: each 1 of energy gives 10 of slime, up to 200 per cycle.
Facts
- Address
- 820
- Name
.mkslime- Kind
- Command: the bot writes it and the engine reads it and usually consumes it
- Group
- Defenses
- Written by
- Your DNA.
- Read by
- The engine, in the actions phase of the same cycle: makes up to 200 slime (or takes it apart, if negative) and charges 1 energy per 10, plus a surcharge that goes to waste (parameter Slime).
- Cleared
- The engine, after making. With energy at 0 or less, the command stays written without being carried out.
- Range
- −32000 to 32000; at most 200 per cycle are used in each direction
- Mutations
- picked as a store target
Write how much slime you want to add this cycle. The engine makes it at the end of the cycle, charges 1 energy for every 10 of slime and sets the command to 0. It is the only one of the four substances with a cap of 200 per cycle instead of 100.
Slime evaporates: it loses 2% per cycle. To keep a stable layer you have to replenish it every cycle, and the thicker the layer, the more is lost. With 200 per cycle the layer settles near 10000 (2% of 10000 is exactly 200).
As with .mkshell, a negative value takes slime apart but still charges energy, a transaction cost that goes to waste is added (in a multicellular bot, the part you pay in energy is divided by the number of ties plus one) and with energy at 0 or less the command stays written without running.
The result is read in .slime.
' a slime layer thick enough that nobody ties to me
cond
*.slime 150 <
start
50 .mkslime store
stop