A monster in the realm!
The internal i/o is a mess—the methods that allow the digital creatures to read and write to and from themselves and each other. I’ve always planned on changing it. Each figure, (one of the digital creatures I created) gets a turn, one after another, enough time to execute one instruction. But, no matter how much they are reading or writing, it all happens in one instruction.
That’s too fast!
If one figure is deleting another one, if it happens all at once, the one getting deleted doesn’t have a chance to react. There’s no defense.
I thought I’d test this out, so I did something like core war, and stuck in a figure that does nothing but empty out the memory of other figures. It’s a monster, and all it does is kill.
In the following output, each “n” stands for “null” A letter n means that there is nothing in that slot. Otherwise, you’ll see the size of the given figure. There are 4 slots, and a maximum population size of 3—if every slot is filled, the death object takes out the oldest figure. The figures that copy themselves, the replicators, are 9 numbers long. The monster is only 6. The replicators take three turns to make a new copy. The monster kills a figure every two turns.
Taking all bets!
…