From: Marcus A. <maa...@ab...> - 2004-04-20 08:45:45
|
On Tue, 20 Apr 2004, Jan Ekholm wrote: > > Hi, > > After some playtesting I discovered that somehow orders to units were > often "forgot" somewhere and execution of them wasn't started until at a > much later time. This turned out to be a few bugs in the way data was read > from the sockets and should be more or less fixed now. I cleaned up some > of the stuff in event_loop.py and it is now a bit simpler and less error > prone. Cool, I've been seeing something similar, but didn't find the error (didn't have time to try very hard either.. :( ) Somehow units also _seem_ (before your patch) to start "one after the other", i.e. ordering three cavallery units to move the same offset seems to make one start first, then the next update the second, then the third. ? |