.fertilized
Signals that the bot received sperm: greater than 0 while the fertilization is in effect, counting down from 9.
Facts
- Address
- 303
- Name
.fertilized- Kind
- Sense: the engine writes it for the DNA to read
- Group
- Reproduction
- Written by
- The engine sets it to 10 when a sperm arrives, in the shots phase, and lowers it by 1 in the actions phase.
- Cleared
- The engine, when the fertilization expires and after a sexual birth. If the bot rejects the sperm, it stays frozen.
- Range
- 0 to 10; in practice you read 9 the cycle after the sperm and then it counts down to 0.
- Note
- Writing it does not fertilize the bot. Outside a fertilization the engine does not touch it: whatever you write stays there.
- Mutations
- picked as a read (
*)
When a sperm shot reaches a bot (another bot wrote -8 .shoot store aiming at it), it is fertilized for about ten cycles. .fertilized shows the countdown: in the cycle after the impact it reads 9, then 8, and so on down to 0. If another sperm arrives before that, the count starts over with the new DNA.
While it is greater than 0, the bot can have a child by writing to .sexrepro. After the birth it goes back to 0 right away: each sperm gives only one child.
' If fertilized and it has the means, it has the child
cond
*.fertilized 0 >
*.nrg 2000 >
start
50 .sexrepro store
stop*.fertilized 0 > matches the window exactly: the cycle in which the DNA reads 0 is already too late. You can also write .sexrepro beforehand: the command stays written and is used as soon as a sperm arrives.
Writing to .fertilized does not fertilize the bot. And outside a fertilization the engine does not touch it, so the number you write stays there and fools your own conditions: use another cell for your counts. More in Reproduction.