BunnRee wrote:Hi Lack, I have one of those games 10174858 that keeps trying to load scripts.
lackattack wrote:Unfortunately the game log stopped recording information for turns taken during a period of 4 hours last night, from CC Time: 2011-11-30 19:20:00 to CC Time: 2011-11-30 23:20:00. The game log data is gone for good and cannot be recovered. The problem stemmed from the fact that we recorded the 2,147,483,647th log entry last night and that is a magic number for computers - the maximum size of an integer in some cases.
The good news is that attacks, point exchanges etc. were all calculated and processed correctly. Your games were not corrupted even though the logs might seem to indicate something is fishy.
After the recording of game logs had been restored there was still a bug that sometimes caused game log entries to repeat themselves over and over. This is now fixed as well.
Please note that some community scripts may produce errors or miscalculations when used with games that are missing game log entries.
Thank you and best of luck with your conquest!
Elmo9199 wrote:well, hope this is the last of this kind of bug.
ever heard of the Unix 2038 bug?
*EDIT: after some web searching about the Unix 2038, the same integer that crashed the game logs will also reset the time from 03:14:07 UTC on Tuesday, 19 January 2038 to some time in 1901 in computers. it WILL crash computers. kinda like Y2K.
it WILL crash computers. kinda like Y2K.
drunkmonkey wrote:I'm filing a C&A report right now. Its nice because they have a drop-down for "jefjef".
I don't much remember comps doing the Y2K crash.
Elmo9199 wrote:jefjef wrote:
I don't much remember comps doing the Y2K crash.
That's because the bugs were FIXED. In the Unix 2038 problem, 32-bit computers will run out of integers. In Y2K, the computers simply misread the year 2000 as 1900.
I'm not scared of my comp crashing, I'm scared of old, Cold War era comps that haven't been updated capable of launching missiles. Like the following:
Mertvaya Ruka is a old Soviet computer that can launch nukes. From Cracked.com:
In America, that might be the name of a horror movie or a masturbation technique. In Russia, it is the name given to the giant border-wide robot installed around the city of Moscow whose only job is to kill you and everyone you've ever loved. The robot detected that a nuke had just been dropped. Ol' Dead Hand would run signals up to the silos to double check that nobody was responding. Upon confirming that the people with their finger on the doomsday button were dead (or on a piss break, whatever), the system automatically launched all the Soviet weapons at the United States. No talk. No getting permission. Not even engaging Jimmy Carter in a stern dressing down to see if you could get him to give you New York City. Mertvaya Ruka launched immediately, and cut out the middleman. And the first guy. And the last guy. It was a doomsday robot, is what we're saying here.
While the Russians are unsettlingly quiet on the matter today, the mysterious UVB-76 radio transmission is believed to be part of Mertvaya Ruka, so it is generally believed to still be active in Moscow.
See that? a doomsday robot might malfunction.
king sam wrote:quit facebook stalking me... and Im a sailor all I do is drunk, cuss and make illegitimate kids when Im away from CC
dont sig that
Elmo9199 wrote:guys, i found out that now all data from that time period was deleted.
Evidence - http://www.conquerclub.com/game.php?game=10137571
look for 2011-11-30 and you'll see data from 21:05:47 - 22:49:17, at the time the bug was in effect.
esiemer wrote:this glitch has ruined one of my most enjoyable games ever. we've been playing for over a year, and it has been tense, close, back-and-forth with none of the final 3 players able to gain advantage. then the glitch occurs in Round 163. we try to each skip a turn so that it is fair for the person we thought got skipped. this doesn't work, and then we learn the player was never skipped, but we can't see the log to determine what happened, and one player has come out strong enough to win now, after over a year of strategizing and near perfect gameplay, game 8284929 is going to end soon because of this glitch.
the only fair solution would be if there is some way to roll it back to the beginning of round 163.
i know there are bigger problems and injustices in the world, but this sucks.
esiemer wrote:this glitch has ruined one of my most enjoyable games ever. we've been playing for over a year, and it has been tense, close, back-and-forth with none of the final 3 players able to gain advantage. then the glitch occurs in Round 163. we try to each skip a turn so that it is fair for the person we thought got skipped. this doesn't work, and then we learn the player was never skipped
Users browsing this forum: No registered users