.poison
How much poison the bot has: it punishes whoever bites it with an energy shot or steals from it through a tie; it evaporates 2% per cycle.
Facts
- Address
- 827
- Name
.poison- 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%; also when you make poison (actions) and when your poison goes out against an attacker (the shots phase or a tie). 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 (
*)
Poison is a passive defense: it isn't shot, it acts when you are attacked.
- Energy shots. If a
-1from.shoothits you and your poison exceeds the strength of the hit, you don't lose energy: the engine sends a poison shot back at the attacker and takes poison off you. - Memory shots. A shot that tries to write to your memory (positive type) doesn't write if your poison is enough to stop it: it also bounces back as poison.
- Ties. If a bot of another species sucks energy or body from you through a tie (
.tieloc-1or-6) and you have enough poison, instead of eating it gets poisoned.
Shots that steal body (-6) aren't stopped by poison: for those there is .shell.
Whoever gets poisoned is marked in its .poisoned and, for as long as it lasts, the engine writes your .pval into its .ploc cell every cycle. Those two cells are yours, the poisonous bot's.
Poison evaporates 2% per cycle and the engine publishes the new value every cycle. It is made with .strpoison. It doesn't poison one of your own species: if a shot of your poison reaches it, it adds it to its own.
' whoever bites me will spin without stopping
cond
*.robage 0 =
start
.aimdx .ploc store
50 .pval store
stop
cond
*.poison 500 <
start
100 .strpoison store
stopWith this bot, an attacker that shoots it a -1 ends up spinning 50 per cycle for as long as the poison lasts.