Code center > Suggestions

Bot Recognition

(1/2) > >>

Numsgil:
Actually, Endy, that was/is the best competitive strategy.

They did an AI expo a while ago with the prisoner's dilema.  The computer program that wins (apparently even against programs specifically designed to hurt it) stays loyal to friends and destroys betrayers.

If you can find a way to reliable and consistantly identify robots beyond just what species they are, you can easily implement such a system.  The only problem of course is there isn't a way to identify another robot reliably (the other robot can play chameleon.)

What we probably need to create is something that is unique to a bot that the bot can't change mid life.  Perhaps a set of memory locations that are set by the bot at birth but can't be changed, representing unique look/smell/pheremone signal/etc.

PurpleYouko:

--- Quote ---If you can find a way to reliable and consistantly identify robots beyond just what species they are, you can easily implement such a system. The only problem of course is there isn't a way to identify another robot reliably (the other robot can play chameleon.)
--- End quote ---

Robots aleady have such an attribute but they just can't see it.

COLOR

The trouble is that DBs are color-blind for the reason that the color attribute is way too long to fit into a robot's integer memory locations.
Changing all memlocs to longs (where have we heard that before?) would enable direct reading of a robot's color with the eyes. Using this along with the "%=" operator will allow robots to identify conspecs and near conspecs during mutations.

Unless robots are also able to change their color (possibly temporarily and at a certain expense) then this will be a foolproof conspec detection system. I see great uses for this in sexual reproduction and mate finding. Possibly with color cycling displays or such like.  :D

Numsgil:
Well, color is composed of 3 attributes, the red, green, and blue components.  Each is itself an integer.

Just let the color readback read to .mygreen, .myred, .myblue, .refblue, .refgreen, and .refred

Could be alot of fun.  I also like the idea of color changing, but I'm not sure how we'd implement it.

PurpleYouko:
Implementing it should be very easy. Use something like

255 .chameleonblue store

to add 255 to blue

Obviously using a shorter sysvar if possible

Then you just have either a timer to return it back to normal or just keep it that way as long as the gene keeps operating.
Maybe even have another zyzvar such as .colortimer into which a value can be stored.

Numsgil:
Color changing ability should probably cost something to maintain.  Perhaps like 1 nrg a cycle per color compnent or something along those lines.

Navigation

[0] Message Index

[#] Next page