Difference between revisions of "In and Out"
From WikiManual
| Line 1: | Line 1: | ||
This refers to the in1, in2, out1, out2 sysvar locations. The number stored at out1 or out2 can be read by any robot viewing the bot, with the value arriving at out1 or out2 respectivly. These were in the past used for identification, and more recently in unique bot species not intended for battle. | This refers to the in1, in2, out1, out2 sysvar locations. The number stored at out1 or out2 can be read by any robot viewing the bot, with the value arriving at out1 or out2 respectivly. These were in the past used for identification, and more recently in unique bot species not intended for battle. | ||
| + | |||
| + | ID'ing non family with in/out: | ||
| + | |||
| + | *.in1 *.out1 != | ||
A problem similar to the one facing bots using [[Memloc and Memval |memloc/memval]] for identification is that with the simple code: | A problem similar to the one facing bots using [[Memloc and Memval |memloc/memval]] for identification is that with the simple code: | ||
Revision as of 01:24, 27 September 2005
This refers to the in1, in2, out1, out2 sysvar locations. The number stored at out1 or out2 can be read by any robot viewing the bot, with the value arriving at out1 or out2 respectivly. These were in the past used for identification, and more recently in unique bot species not intended for battle.
ID'ing non family with in/out:
*.in1 *.out1 !=
A problem similar to the one facing bots using memloc/memval for identification is that with the simple code:
*.in1 .out1 store
An enemy bot can seem like family. Of course with randomly(rnd) changing their value via inc/dec an enemy bot will waste Energy storing these.
