Code center > Darwinbots3
Viruses (Re: Programming task (DNA editor))
Panda:
The DarwinBots2 "virus" wasn't particularly virus like; it was simply a way to transfer a gene using a shot, which inserted the gene into another robot.
The cost of a "virus" (if DB3 using the same idea as in DB2) will probably a community decision, depending on how powerful the concept is.
Numsgil:
I'm not really sure how I want to handle viruses in DB3 just yet. A lot of it I won't know until I have bots in the simulation and I'm happy with how they physically work. Either something like shots, but more bound to floating around in the fluid, and bots are vulnerable to them when they're pinocytosis-ing, or larger bot-like structures that bots are vulnerable to when they phagocytosis-ing.
Peter:
I'm not sure if I want viruses. Genes running around can mess up stuff.
Panda:
I think viruses were overpowered. Just compiled a quick list with their problems:
* genes injected (no or little incubation time)
* artificial protection
* changes original bots execution
* little ability for bots to modify or "view" own code (e.g. no checksum for individual genes to identify )
Numsgil:
In terms of how they work in the bot, I think they'd be separate chromosomes. That is, their code would be isolated from the rest of the genome and the results of all chromosomes' stores would get combined in some way that doesn't favor plurality. Something like a simple max. That's the same mechanism that I want to use to do diploid, so we can mimic the lifecycles of some fungi that have haploid and diploid alternating generations. A diploid cell would have two "brains" controlling it, and dominant/recessive genes work just by how large of numbers they're storing to sysvars. An infected cell would likewise be controlled by multiple programs, but the programs are largely ignorant of each other and can't directly interfere with each other.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version