.myvenom
How many times the bot's own DNA writes to .strvenom, the command to make attack venom; unlike the other my* sysvars, it has no ref* partner.
Facts
- Address
- 731
- Name
.myvenom- Kind
- Sense: the engine writes it for the DNA to read
- Group
- Its own signature (my*)
- Written by
- The engine, when the DNA changes (on load, at birth, through a virus or a mutation), counting the writes to
.strvenom. Not every cycle. - Cleared
- Never. Your DNA can overwrite it; the engine recalculates it the next time the DNA changes.
- Range
- 0 to about 16000; in practice, a few dozen.
- Mutations
- picked as a read (
*)
A counter taken from the bot's own DNA: how many writes to .strvenom there are in the genome, that is, how many times its address (824) appears immediately followed by a write word, as in 100 .strvenom store or .strvenom inc. Just as with .myup, it counts what is written, whether it runs or not.
It is useful to the bot itself, though, for knowing whether its genome makes attack venom:
' if my DNA makes venom and I have none, make a little
cond
*.myvenom 0 >
*.venom 0 =
start
50 .strvenom store
stopIn this example the gene itself already makes .myvenom at least 1.
The engine computes it when the DNA changes (on load, at birth, through a virus or a mutation; see Its own signature (my*)), not every cycle. For the venom the bot has stored, look at .venom. More about these counters in Its own signature (my*).