Difference between revisions of "Memloc and Memval"
(Modified by Elite) |
m |
||
Line 10: | Line 10: | ||
67 .memloc store | 67 .memloc store | ||
stop | stop | ||
− | + | ||
cond | cond | ||
*.eye5 40 > | *.eye5 40 > | ||
Line 26: | Line 26: | ||
def foundmemloc 51 | def foundmemloc 51 | ||
def reqmemval 52 | def reqmemval 52 | ||
− | + | ||
cond | cond | ||
*.eye5 0 > | *.eye5 0 > | ||
Line 35: | Line 35: | ||
*.memval .foundmemloc store | *.memval .foundmemloc store | ||
stop | stop | ||
− | + | ||
cond | cond | ||
*.eye5 0 > | *.eye5 0 > | ||
Line 44: | Line 44: | ||
*.memval .reqmemval store | *.memval .reqmemval store | ||
stop | stop | ||
− | + | ||
cond | cond | ||
*.reqmemval 0 != | *.reqmemval 0 != |
Revision as of 10:12, 19 February 2006
These allow the bots to readback another bot's memory locations. To do this simply specify the location you'd like to reference in memloc and the bot will receive the information in memval.
Sysvars:
Memloc & Memval:
|
Syntax:
Example:
cond start 67 .memloc 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.