.waste
The waste the bot has accumulated: in excess it writes random numbers into its memory; it is thrown away with a -4 shot.
Facts
- Address
- 828
- Name
.waste- Kind
- Sense: the engine writes it for the DNA to read
- Group
- Body, energy and state
- Written by
- The engine, in the actions phase; if they exceeded 32000, after expelling them. You read it in the next cycle.
- Cleared
- No: the engine rewrites it every cycle.
- Range
- 0 to 32000.
- Mutations
- picked as a read (
*)
Waste is a byproduct of activity. The main sources are:
- making defenses: the extra cost of building shell, slime, venom or poison (
.mkshell,.mkslime…) doesn't vanish, it becomes waste; - eating: 1% of what the bot takes from another, by shooting or through a tie;
- receiving other bots' waste: a −4 shot from another bot, or whatever is passed to it through a tie.
Why it matters. When the waste, added to the permanent waste in .pwaste, goes past the limit set by the option Waste is toxic from (400 if you haven't changed it), the bot suffers something like Alzheimer's: every cycle the engine writes random numbers into random addresses of its memory, and the more waste, the more writes. That breaks its variables, commands and counters.
How to get rid of it.
- By throwing it away with a −4 shot:
-4 .shoot storeshoots out the amount you put in.shootval(or 1/20 of the waste if it is 0). 1% of what is thrown stays in.wasteand another 1% goes to.pwaste. - With chloroplasts: a bot with
.chlrdigests its waste and turns it into energy and body. - By passing it to a partner in the same organism with
.sharewaste. - If it goes past 32000, the bot expels it on its own.
' Throws away the waste when it goes past 100
cond
*.waste 100 >
start
*.waste .shootval store
-4 .shoot store
stopIt's the pattern many Bestiary bots use, such as A. Praxidikae mk2. More in Energy, body and waste.