In investigating that out-of-sync problem I was seeing with my new
builds and older ones, I discovered that the problem isn't with my new
build - it was with the particular sequence of steps I was using in my
Try this (probably in any version - I've verified it in both the recent
Carbon release and in my own Windows SDL private build):
Use the Moo stuff.
Command+option+Begin New Game (Control+Shift+Begin New Game in SDL).
Choose level 40, House of Pain.
See how the little droney things fly around and shoot green goo at you?
Nothing exciting, right?
Quit House of Pain, but do NOT quit the A1 application.
Command+option+Begin New Game on level 2, Rise Robot Rise.
Once you're on the platform rising up, you can quit RRR, but again, do
NOT quit A1 proper.
Command+option+Begin New Game on level 40, House of Pain, again.
Notice anything strange about the drones? Anything at all?
If you don't want to actually do this, I'll describe what happens.
The second time on House of Pain, well first off either you or the
drones start off in different places than you did the first time. That
may or may not be significant. But what definitely IS significant is
that the drones don't emit projectiles! They open their little mouths
and play the "shoot" sound effect, but nothing comes out. BUT, try
letting one get up next to you. When it attacks you now, it's in range
and you are effectively hit by a Pfhor shock-staff! The screen flashes
white, it plays the familiar shock staff "hit" sound, and the damage
taken is shock-staff-like.
It seems as though a level sets a custom physics model, but then the
default model isn't automatically restored when you quit and choose a
Anyway I may be looking into this; if I can't figure it out readily, I
might just submit my resume-netgame code as-is since the problems I am
having are unrelated to my new code (and are sufficient to set the game
out-of-sync from tick 0 if only one machine follows this sequence of
events). The resume-netgame stuff seems to work just fine otherwise...
actually so well, if I may say, that I'm already kind of taking it for
granted, like it's just always been there and always worked. :)
It would be interesting to know whether Moo proper (not A1) exhibits
this behavior too, if anyone has a copy set up and ready to try...