Posted by William D McQuain on April 19, 2001 at 17:36:57:
In Reply to: Creature moves then... posted by Lane Martin on April 19, 2001 at 01:40:44:
: Within one loop, should the tick increment apply to one creature then a move, then it looks to see if there is anything to eat. Then move to the next creature in the list, incriment the SAME tick# for it, then have it look to see if there is anything to eat. and so on...
Yep. Each creature gets one update call per "tick" and on that call the creature does everything it will do on this "tick".
: because if this is true, then it seems to me that the ordering of the creatures in the list would matter.
Yep. That's why the spec says creatures should be updated as follows:
- plants first, in the order created
- animals, in the order created
Also this tick would not simulate true time, which occurs for all creatures at the same time, not creature by creature.
True. We can solve that problem by moving execution to a massively parallel machine, like a Paragon, and mapping each creature to its own processor.
: In other words, do we do the clock for each creature, then move each creature, then have them interact? Or is it more like do the clock tick for a single creature, move the creature, interact, then repeat for all creatures?
: does any of this make sense to anyone else? or is it just me?
Post a Followup