Code center > Darwinbots3

Anyone out there?

<< < (4/5) > >>

abyaly:
That's fine if the groupings are configurable. Then there is room to play with it and see what types of groupings lead to interesting results. Consistent groupings matter less than interesting results, and we don't know which will yield those until we try them.

Numsgil:
Oh, so you mean like user configurable for the groupings?

bacillus:
maybe mutations should be split up into two categories: smooth mutation, where advances are made in small, progressive steps, and sudden mutation, where the changes are totally random. Changing add to sub or sgn to cond for example is a sudden mutation, as changing operators/operator types completely alters the function of the code, as opposed to changing 50 .repro to 55 .repro or .aimdx to .aimsx, where the changes are subtle, yet still noticeable.
...well, relatively speaking.  

bacillus:
Is the new shape of bots still two semi-circles and a connecting polygon? Because I had a good idea for a new kind of bot tie: instead of having the bots stick on the surface of other bots, or being connected by 'string', the endpoint circles are used as 'hinges', so the circles' centers are at the same point. A force on either one of the circles would loosen this connection, so chunks could be 'bitten off' other multibots without the prey slipping out due to gaps in the MB.

Numsgil:
Hmm, sounds like a good idea XD

The pivot point will probably be at the end points instead of the center of the circle.  I'll just half-disable collision code between joined shapes so that the pivot joined parts don't self collide, but the other end points can.

Navigation

[0] Message Index

[#] Next page

[*] Previous page