Bots and Simulations > Simulation Emporium

What do you make of this one?

<< < (2/2)

Testlund:
I'm guessing that putting a cond command before a start command is like a restrictive command; "don't do until the condition is met". Without that it's free to execute start commands at will, like reproducing at random.

Sprotiel:

--- Quote from: Testlund ---I'm guessing that putting a cond command before a start command is like a restrictive command; "don't do until the condition is met". Without that it's free to execute start commands at will, like reproducing at random.
--- End quote ---
Actually, you're right. So the part of the code which accomplishes something is between the first "start" and the first "cond".

Numsgil:
To be honest the code you give is really convoluted (as you would expect from evolution), and would take alot of effort to decode.

EricL:
FYI, for several reasons not the least of which because evolved DNA is so hard to decypher, I'm starting to add some features that should at least help make the actions of evolved bots easier to see.  Shot impact dots were the first of these, which makes it easy to see what kind of shots a bot is shooting.  The next is movemenet vectors, which makes it easy to see how a bot is using .up, .dn, .sx and .dx.   Will be in 2.42.8d or 2.42.9, whichever is first.

Navigation

[0] Message Index

[*] Previous page