-
There was a misleading typo in previous post:
> Colossus writes now own specific log files.
Colossus writes NO own specific log files.
2009-11-15 19:37:10 UTC by cleka
-
Saving alone does (should ;-) not harm. Saving and loading and saving and loading I would rather suspect might effect something.
So, do you sometimes save, and at some point (because you were killed, or noticed you made a bad decision, or had to stop playing for some reason), load such a game to continue. And that two times.
(i.e., that the previous save&reload to continue introduces some...
2009-11-15 19:08:55 UTC by cleka
-
Fixed in 4618.
Since this was just introduced in recent refactoring (=not visible in any release) closing it immediately.
2009-11-15 18:50:41 UTC by cleka
-
cleka committed revision 4619 to the Colossus SVN repository, changing 1 files.
2009-11-15 18:48:41 UTC by cleka
-
Hiya,
Java web start has always confused me, which is ironic because I support one of those at work ;-). In any case, I launch it by clicking on the downloaded JNLP file.
In this game I saved a lot. I use the file->save operation. I probably saved and reloaded in this game using file-save rather than autosave.
Thanks for attaching the corrected xml file, but that's alright, no big deal...
2009-11-14 23:39:33 UTC by nobody
-
cleka committed revision 4618 to the Colossus SVN repository, changing 1 files.
2009-11-14 20:23:16 UTC by cleka
-
ALl right, this is a harmless case.
// OK. This can happen if game was saved with a split that is
// now recombined by the server because the legions didn't have
// valid moves. Now it was loaded in move phase, but replay
// does (at least for now) NOT replay the actual event, it just
// re-sends the add/remove info so that clients get the split
// predict info right. Thus there is no...
2009-11-14 20:20:38 UTC by cleka
-
The point worth mentioning is, I reloaded the AUTO-save game (from split phase) file that stresstest had produced.
(Perhaps, is there some problem / difference between normal save and autosave ? See also the other bug with load game, was that also loaded from an autosave game?
https://sourceforge.net/tracker/?func=detail&atid=101939&aid=2897542&group_id=1939 )
2009-11-14 18:18:24 UTC by cleka
-
After refactoring of the Movement(Client|Server)Side to Movement, now it does not handle the "could spin but what if just did split there so other own legion is there" case properly any more; if one loads the attached save game, Coward1 continues to play and produces NAKs forever:
D:\katzer\stuff\trunk1>java -Dnet.sf.colossus.forceViewBoard=true -Djava.util.logging.config.file=logging.propert.
2009-11-14 18:12:33 UTC by cleka
-
D:\katzer\stuff\trunk5>java -Dnet.sf.colossus.forceViewBoard=true -Djava.util.logging.config.file=logging.properties -Xmx128M -jar C
olossus.jar --load CantMoveSplittedLegions6.xml
SEVERE: Requested '0' EVENT to undo (Gd06, Gd04, turn 19) not found
D:\katzer\stuff\trunk5>
Happens in r4615, as well already in Release 0.9.3.
Save Game file attached.
What has happened: A stresstest ga.
2009-11-14 18:05:44 UTC by cleka
