.vloc
The memory cell that your venom will overwrite in the victim on every cycle of the paralysis.
Facts
- Address
- 835
- Name
.vloc- Kind
- Command: the bot writes it and the engine reads it and usually consumes it
- Group
- Defenses
- Written by
- Your DNA.
- Read by
- The engine, when you fire venom or pass it along a tie: it is the victim's cell where your
.venvalwill be written while the paralysis lasts. - Cleared
- Nobody: it is configuration. A child is born with 0.
- Range
- −32000 to 32000; 1 to 1000 work (a larger value is brought down to that range, 0 or negative picks at random and address 340 is left alone)
- Mutations
- picked as a store target
It is configuration: you write it once and the engine reads it every time you shoot venom (-3 in .shoot) or pass it through a tie (.tieloc -3). The engine never clears it. Together with .venval it decides what happens to the victim: while it is paralyzed, the engine writes .venval into its .vloc cell every cycle, after its DNA runs, so the victim can't correct it.
The most used targets are commands the victim doesn't want to carry out: .shoot with -2 (gives away energy), .up (moves forward), .aimdx (turns).
Three details:
- A value outside 1…1000 is brought into that range the same way as a memory address (1050 is 50).
- With 0 or a negative, each hit picks a random cell.
- Cell 340 (
.delgene) is protected: if you aim there, nothing happens.
Since a newborn's memory starts at 0, each child has to set it again; otherwise its venom hits random cells.
' at birth: the venom makes the victim move forward
cond
*.robage 0 =
start
.up .vloc store
40 .venval store
stop