-
cleka committed revision 4627 to the Colossus SVN repository, changing 1 files.
2009-12-03 21:22:46 UTC in Colossus
-
cleka committed revision 4626 to the Colossus SVN repository, changing 1 files.
2009-12-03 21:12:01 UTC in Colossus
-
cleka committed revision 4625 to the Colossus SVN repository, changing 1 files.
2009-12-03 20:53:53 UTC in Colossus
-
cleka committed revision 4624 to the Colossus SVN repository, changing 2 files.
2009-12-03 20:15:43 UTC in Colossus
-
cleka committed revision 4623 to the Colossus SVN repository, changing 1 files.
2009-12-03 19:55:37 UTC in Colossus
-
I agree with Bruno; sounds like the "uncertain content" case and you did not notice that there are question marks overlayed over the Titan/Angel (and other creatures) ... they are really sometimes difficult to see... - Next time look carefully... probably they are there?
In "Game Setup" window, "Options" tab, You could set a different "Viewable legion content", e.g. "True content for all...
2009-11-30 10:09:53 UTC in Colossus
-
The user who reported this problem has informed me that it might have been
caused by his PC, lots of other problems as well, now reinstalling the
computer and problem did not appear any more.
If nobody else ever reports similar issue, this can be closed when next
release is done.
2009-11-30 09:38:22 UTC in Colossus
-
Reverting previous comment. This case here is still unsolved.
The "player can't reproduce becuase PC under reinstallation" was another case :-(.
2009-11-30 09:37:38 UTC in Colossus
-
The user who reported this problem has informed me that it might have been caused by his PC, lots of other problems as well, now reinstalling the computer and problem did not appear any more.
If nobody else ever reports similar issue, this can be closed when next release is done.
2009-11-30 09:33:29 UTC in Colossus
-
Corrected in r4622.
There was used getEngagement().toString() in an else case where it might (in theory) reach also if there is no engagement ongoing. In practice it is somehow questionable how this could happen, because it means someone had clicked on a hex to engage but there were no opposing legions. Perhaps an AI caching from begin of Engagements phase all engagements and now one was not...
2009-11-29 11:53:15 UTC in Colossus
