Bots and Simulations > DNA - General
Rape bots
Numsgil:
It only results in broken code if the two parents' DNA are mostly unrelated. If they are entirely unrelated, then it's just a 50/50 gamble on which DNA the child gets. Meaning that in such a union the child is not only not broken, but is actually just a clone of either parent.
gymsum:
--- Quote from: Numsgil ---It only results in broken code if the two parents' DNA are mostly unrelated. If they are entirely unrelated, then it's just a 50/50 gamble on which DNA the child gets. Meaning that in such a union the child is not only not broken, but is actually just a clone of either parent.
--- End quote ---
That shouldn't be hard to correct, just let the remaining unmatched pairs form broken codes, they'll only contain ethier side of the entire dna, so the parts combined will work, while the rest will fall apart.
Numsgil:
But if none of the code gets matched, then whichever DNA the child gets will be fully functional. This wouldn't be a problem if the DNA was that of the mother. But when it's the Father's DNA, it's unbalanced and unfair.
bacillus:
.sexrepro is powerful indeed, either you get a free copy of yourself, or some twisted offspring is produced, axing right through the parent's nrg and probably creating some twisted offspring that does nothing.
There's an idea; make a bot that forces 99 .sexrepro, and then feed on the weakened(likely, but not every time) offspring while the victim dies.
EricL:
I suggest we do the following simple, easily implimented fixes:
1) Disallow .sexrepro if the parents have 0 matching sub-sequences.
2) Allow bots to override .fertilized, allowing for the disposal of sperm it doesn't want or for keeping it longer if it does.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version