Code center > Suggestions
.sexrepro reimplemented in 2.43.1
Numsgil:
I would be careful with DNA replacement. Rape is one thing, but outright forcing another bot to mingle its DNA with your own is something even more brutish. I would ask that a bot destined to be an egg be produced specifically for that cause. Use -16001 to -32000 in sexrepro to mean to produce an egg: it would have all the DNA of the parent, like a normal .repro, but would be available for DNA replacement. Otherwise it could function like a normal bot. DNA replacement would occur either automatically after fertilization or by calling sexrepro (any value), depending on you thoughts.
EricL:
--- Quote from: Numsgil ---Use -16001 to -32000 in sexrepro to mean to produce an egg: it would have all the DNA of the parent, like a normal .repro, but would be available for DNA replacement. Otherwise it could function like a normal bot. DNA replacement would occur either automatically after fertilization or by calling sexrepro (any value), depending on you thoughts.
--- End quote ---
Sounds good to me. It will be a few weeks before I get to this (vacation coming up).
JossiRossi:
I'm sure this is because there is more going on but 2.43.1 goes about half as fast as version 2.43z. Is the sex stuff responsible for this alone?
EricL:
--- Quote from: JossiRossi ---I'm sure this is because there is more going on but 2.43.1 goes about half as fast as version 2.43z. Is the sex stuff responsible for this alone?
--- End quote ---
Shouldn't be directly, but I did make a change to the shot array compact routine to handle -8 shots. That may be it.
I'll do some profiling shortly. It's time. The next drop will have some perf work.
rsucoop:
Is there a way to push information into memory locations of an egg? Through a tie or info shot?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version