.myaimsx
How many times the bot's own DNA writes to .aimsx (the command to turn left): part of the signature used to recognize its own species.
Facts
- Address
- 726
- Name
.myaimsx- 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
.aimsx. Not every cycle. - Cleared
- Never. Your DNA can overwrite it, but everyone else still sees the engine's count.
- 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 times a write to .aimsx appears, that is, the number 6 (the address of .aimsx) immediately followed by a word from the store family, such as store, inc or addstore. 35 .aimsx store and .aimsx inc both count; a computed address doesn't, and neither does a .aimsx that isn't right before the write. Since what gets checked is the number, it also counts if you write the address by hand (6 instead of .aimsx).
It doesn't say whether those writes run: it counts what is written in the genome, whether it runs or not.
Its partner is .refaimsx, which gives the same count but for the DNA of the bot being looked at. Comparing them is one way to recognize members of your own species (see Its own signature (my*)):
' what I see writes to .aimsx a different number of times than I do
cond
*.eye5 0 >
*.refaimsx *.myaimsx !=
start
1 60 store
stopThe 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. If the bot writes to it, its value changes for the bot, but everyone else keeps seeing the original count.