Memloc and Memval
Memval reads the value of a location in another bot using the value that was already in or put into Memloc on the last cycle to define the location. Memloc holds its value until changed. Memval will not change if eye5 = 0 These allow the bots to readback another bot's memory locations.
Sysvars:
Memloc & Memval:
|
Syntax:
Example:
cond *.robage 0 = start 67 .memloc store 101 67 store stop cond *.eye5 40 > *.memval *67 != start -1 .shoot store stop
This will cause the bot to attack bots that don't have the same number as it does in memory location 67.
A slight problem, is that any bot can determine the location being referenced by simply checking in memloc with it's own memloc/memval. This is simply a more complex version of the problems facing bots using In and Out for secure information exhchange.
Example:
def foundmemloc 51 def reqmemval 52 cond *.eye5 0 > *.refshoot *.myshoot != *.foundmemloc 0 = start .memloc .memloc store *.memval .foundmemloc store stop cond *.eye5 0 > *.refshoot *.myshoot != *.foundmemloc 0 != start *.foundmemloc .memloc store *.memval .reqmemval store stop cond *.reqmemval 0 != *.foundmemloc 0 != start *.reqmemval *.foundmemloc store stop
These genes will fool memloc/memval based conspec recognition.
A more complex method would be to randomly vary the locations checked per cycle, but most bots simply make do with the refeye/myeye combination.
To use the commands tmemval and tmemloc the procedure is similar, but requires the tie number to be stored in tienum.
