Distributed Core Wars
Multiple RedCode VM's (MARS, see pMARS) with ability to interconnect and communicate.
Connecting to VM's requires exploiting (unlocking) the VM with a magic sequence (varying randomly) to send and start a process. Abstracts exploiting real world software.
Thoughts:- Evolutionary development of programs.
- Manual competative development/evolution seeding
- Random generator in Redcode to crack VMs with brute force
- Long term goal - nearby VMs would cooperate.
- What does one VM need from another?
- See VM resets - cooperation = reinfection without overloading to trigger reset
- Nearby VM's act like cells in singular organism
- What does one VM need from another?
- VM's that run too many processes are reset - abstract outside intervention re: exploited systems
- Give player method of interacting with running/exploited systems.
- Player has "home" node that remains constant and they can modify/seed programs
- Arrange VM's in 3D, voxel style display.
- Activity of VM indicated by solidness of display