4 ms·
Thanks, these are very nice ideas, especially the API for agents. I'd like to build this sometime, as it should be really fun to play... There are some issues i
by project_idea 17y ago
Thanks, these are very nice ideas, especially the API for agents. I'd like to build this sometime, as it should be really fun to play...
There are some issues in gameplay that I couldn't figure out yet, though.
for example running until completion could be quite hard to detect, as there can be oscillators with a long period. Also, not sure if the board should be circular, to allow re-entry or not... I was thinking whether players can place their cells anywhere or just in their own restricted "corners" of the board. My main concern however is whether the whole thing would be predictable enough to allow some sort of strategy or it would just be too chaotic... I also sent you a private message if you'd like to discuss...
- jacquesm 17y agoNo cells live or die in x generations = end of game. Anywhere, one after the other.
- deleted 17y ago[deleted]
- project_idea 17y agoI meant one of these: http://en.wikipedia.org/wiki/Oscillator_(CA) http://en.wikipedia.org/wiki/Oscillator_(CA) So cells keep dying and being born forever, yet the game is stable.
- jacquesm 17y agoAh, good point! You'd have to keep quite a few digests of the 'state' to figure out that you're caught in a loop, the 'halting problem' in disguise. You could work out the size of the cycle by checking the lower and upper limit of the populations though, if the lower and upper limits have not changed for a number of cycles it could also be end-of-game.
- m_eiman 17y agoStore evey state, and if you ever get a state you've already stored you know you're in a loop. Should be possible to store it in very few bytes in "raw" form, and then compress it for good measure.
- jacquesm 17y agohash the state.. even then, if the period is very long it might be problematic