@Quantech what Wipyman is saying is that the cell has to have two functions: read and write. The cell would first read the preexisting data in its genome, and carry out those instructions. The cell would then check its surroundings, and write that data to the genome when it detected something. It wouldn't use the data it collected, it would just save it for the next generation of cells.
I've managed to make a rudimentary duplication system, but it has to be manually operated until I can rig up a SPRK counter ID:2010551
but irl, the code is inside the cell. So far, i have 4 nucleotide bases, a basic "read" wire, and a heat sensor. The sensor codes the first nucleotide base to a "1", so that when the code is read, it will send a signal to the GEL system to release some GEL. I have trouble undertsanding what wipyman is trying to say, once i do understand, i'll try your idea!
We should also make it so that a cell has to gather a certain amount of energy (like from light, head, PLNT, or YEST) before it can replicate. And yeah, I like Wipyman's system more.
If not, you could keep the genetic code and timer extraneous, as a representation of the microbiology, as the cell itself, in locomotion, reacting to stimuli and dying is a representation of the macrobiology of the cell.
I am going to add a "clock" so that in every tick, it reads the code and does whatever it needs to do!
you might have to increase the planned cell size a bit.
do you think we can fit the timer, genetic code, and everything else in the planned cell size?
Don't you think my system is more streamlined? Solving overpopulation, easier implementation of expressing genes as adapations to phenotypes as a result of genetic evolution and making the removal of redundancy easier to implement, as it doesn't involve editing the 'parent' cell directly, rather simply relying on it turning the gene(s) off when the requirement for them isn't met?