Hi. I've run into an annoying problem. I've solved it, but I didn't see any mention of it here, so I'm starting this post to warn others.
The symptom is simple: Minecraft (1.6.4 with Forge 965) will fail to launch with no error report whatsoever. The problem appeared suddenly after many successful runs.
If I configure the (standard) launcher to hang around, it thinks the game ran perfectly and I must have just quit immediately. The Launcher log says "Game ended with no troubles detected (exit code 0)", and the game output shows nothing helpful. There are plenty of log files in the .minecraft directory, but all of them date before the problem first occurred.
Hiding the old .minecraft directory, and re-installing Minecraft and Forge into a fresh one solved the problem for the moment, but I was still curious.
I compared the working and broken .minecraft directories. I found a few differences in a .json file and two .jar files, but copying the "good" files over the "bad" ones did not heal the "bad" directory. After that, the biggest difference was that the "bad" directory had more log files. I deleted them, just trying to simplify further comparisons, but surprisingly that alone fixed the problem!
It looks like the problem is that Forge keeps creating new logfiles of the form "ForgeModLoader-client-0.log.N" on every startup. In the bad .minecraft directory, N had hit 100, and apparently after that Forge can no longer think up unique names and just throws up its hands.
If I just delete log #100, then the game will launch precisely one more time before failing. I can see the logs starting to pile in the good directory.
So it seems this version of Forge has a "time bomb" flaw. Unless you know what is going on, it will only work 101 times per install...
The symptom is simple: Minecraft (1.6.4 with Forge 965) will fail to launch with no error report whatsoever. The problem appeared suddenly after many successful runs.
If I configure the (standard) launcher to hang around, it thinks the game ran perfectly and I must have just quit immediately. The Launcher log says "Game ended with no troubles detected (exit code 0)", and the game output shows nothing helpful. There are plenty of log files in the .minecraft directory, but all of them date before the problem first occurred.
Hiding the old .minecraft directory, and re-installing Minecraft and Forge into a fresh one solved the problem for the moment, but I was still curious.
I compared the working and broken .minecraft directories. I found a few differences in a .json file and two .jar files, but copying the "good" files over the "bad" ones did not heal the "bad" directory. After that, the biggest difference was that the "bad" directory had more log files. I deleted them, just trying to simplify further comparisons, but surprisingly that alone fixed the problem!
It looks like the problem is that Forge keeps creating new logfiles of the form "ForgeModLoader-client-0.log.N" on every startup. In the bad .minecraft directory, N had hit 100, and apparently after that Forge can no longer think up unique names and just throws up its hands.
If I just delete log #100, then the game will launch precisely one more time before failing. I can see the logs starting to pile in the good directory.
So it seems this version of Forge has a "time bomb" flaw. Unless you know what is going on, it will only work 101 times per install...
-
View User Profile
-
View Posts
-
Send Message
Retired Staff