Jump to content

Iasumonecara

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by Iasumonecara

  1. Amaxter: Symptoms? How far do you get? What happens? Log?
  2. It appears that older versions of forge do not have the version.json in the universal jar. To acquire this and remedy the situation, install forge into your 1.6+ vanilla minecraft launcher. Navigate to .minecraft/versions/YOUR_FORGE_VERSION/ and you will find a .jar and a .json Rename the .json to version.json Add that version.json to your modpack.jar in your /bin/ folder. You *should* boot up correctly. This is version specific, so don't do mix&match on them
  3. Unfortunately, .789 is as high as I can go without learning to update the mod. It is looking for a new maintainer and is otherwise abandoned. I'm waiting for 1.7 before putting in requests with folks who update out of kindness. Believe me, I wish I could just run the top versions, but I can't. I've sacrificed some rather enjoyable mods by being trapped in this version. :/
  4. The most up to date forge version for 1.6.2 works just fine (generates working json). Version x.789 does not. If you can make that specific version generate, then dandy. I'd love to know how. I'm locked into this version, unfortunately. Recommended builds seem to be available for use, but not all of the versions... Then again, this belongs on this thread about the 1.6.2 forge x.789 not here about the 1.6.4
  5. With further testing, the most up to date forge version for MC 1.6.2 (forge version 9.10.1.871) appears to work flawlessly. My current best bet is the recommended versions were prepared for this change while the vast majority were not. Unfortunately, this places those using less common versions of forge out of service. I continue seeking a solution....
  6. Further information leaning towards this being a bug rather than something on the user end continues to develop. Bug report has been established here.
  7. Launcher Version: 290 Operating System: 7 x64 Java Version: 1.7.0_07 Antivirus Program: AVG (which I'm suspecting is irrelevant, but whatever....) Description of Problem: A modpack that was previously functional on Launcher Build 189 in no longer functioning when loaded by Build 290. Forge version 9.10.0.789 is in use (and must be used due to mod requirements). It appears that the launcher normally checks what version of forge is in use and then acquires/generates the necessary version.json. There are 3 failed attempts to download and then a successful attempt to download. This successful attempt downloads a vanilla 1.6.2 version.json that does not load forge. A new version.json is downloaded at every launch even if replaced with what was once a working version.json. Error Messages: None. Error is displayed by not loading forge. Error Log: 2013/10/18 11:39:24 [iNFO] ------------------------------------------ 2013/10/18 11:39:24 [iNFO] Technic Launcher is starting.... 2013/10/18 11:39:24 [iNFO] Launcher Build: 290 2013/10/18 11:39:24 [iNFO] ------------ Startup Parameters ------------ 2013/10/18 11:39:24 [iNFO] --------- End of Startup Parameters --------- 2013/10/18 11:39:25 [iNFO] Loaded face 2013/10/18 11:39:27 [iNFO] Starting download of http://skins.technicpack.net/helm/Iasumonecara/100, with 3 tries remaining 2013/10/18 11:39:27 [iNFO] Launcher took: 5244ms to start 2013/10/18 11:39:29 [iNFO] InstalledPack{info=PlatformPackInfo{name='chaoschism', displayName='Chaoschism', url='http://www.iharemehn.com/chaoschism/Chaoschism_1.0/1.0/gah3.05.zip', icon=null, logo=net.technicpack.launchercore.restful.Resource@1dfb2c2e, background=net.technicpack.launchercore.restful.Resource@55118f62, minecraft='1.6.2', forge='null', version='3.05', solder='', forceDir=false}, name='chaoschism', platform=true, build='recommended', directory='%MODPACKS%\chaoschism'} 2013/10/18 11:39:32 [iNFO] Valid: {"error":"ForbiddenOperationException","errorMessage":"Invalid token"} 2013/10/18 11:39:32 [iNFO] {"error":"ForbiddenOperationException","errorMessage":"Invalid token."} 2013/10/18 11:39:54 [iNFO] ------------------------------------------ 2013/10/18 11:39:54 [iNFO] Technic Launcher is starting.... 2013/10/18 11:39:54 [iNFO] Launcher Build: 290 2013/10/18 11:39:54 [iNFO] ------------ Startup Parameters ------------ 2013/10/18 11:39:54 [iNFO] --------- End of Startup Parameters --------- 2013/10/18 11:39:56 [iNFO] Launcher took: 3347ms to start 2013/10/18 11:40:08 [WARNING] File version.json not found in C:\Users\Iasu\AppData\Roaming\.technic\modpacks\chaoschism\bin\modpack.jar 2013/10/18 11:40:08 [iNFO] Starting download of http://mirror.technicpack.net/Technic/version/1.6.2/1.6.2.json, with 3 tries remaining 2013/10/18 11:40:08 [sEVERE] Download of http://mirror.technicpack.net/Technic/version/1.6.2/1.6.2.json Failed! 2013/10/18 11:40:08 [iNFO] Starting download of http://mirror.technicpack.net/Technic/version/1.6.2/1.6.2.json, with 2 tries remaining 2013/10/18 11:40:08 [sEVERE] Download of http://mirror.technicpack.net/Technic/version/1.6.2/1.6.2.json Failed! 2013/10/18 11:40:08 [iNFO] Starting download of http://mirror.technicpack.net/Technic/version/1.6.2/1.6.2.json, with 1 tries remaining 2013/10/18 11:40:08 [sEVERE] Download of http://mirror.technicpack.net/Technic/version/1.6.2/1.6.2.json Failed! 2013/10/18 11:40:08 [iNFO] Starting download of https://s3.amazonaws.com/Minecraft.Download/versions/1.6.2/1.6.2.json, with 3 tries remaining 2013/10/18 11:40:09 [iNFO] CompleteVersion{id='1.6.2', time=Tue Aug 06 06:00:00 CDT 2013, releaseTime=Fri Jul 05 08:09:02 CDT 2013, type=RELEASE, minecraftArguments='--username ${auth_player_name} --session ${auth_session} --version ${version_name} --gameDir ${game_directory} --assetsDir ${game_assets}', libraries=[net.technicpack.launchercore.minecraft.Library@44385f8c, net.technicpack.launchercore.minecraft.Library@51090351, net.technicpack.launchercore.minecraft.Library@26b8e467, net.technicpack.launchercore.minecraft.Library@349b3a0d, net.technicpack.launchercore.minecraft.Library@3b004676, net.technicpack.launchercore.minecraft.Library@f120b3d, net.technicpack.launchercore.minecraft.Library@699fd985, net.technicpack.launchercore.minecraft.Library@7d81e0ef, net.technicpack.launchercore.minecraft.Library@59d6ab48, net.technicpack.launchercore.minecraft.Library@1c87320c, net.technicpack.launchercore.minecraft.Library@6fe6c075, net.technicpack.launchercore.minecraft.Library@16657ab8, net.technicpack.launchercore.minecraft.Library@605bd184, net.technicpack.launchercore.minecraft.Library@2c186288, net.technicpack.launchercore.minecraft.Library@74ece555, net.technicpack.launchercore.minecraft.Library@6cc46b6b, net.technicpack.launchercore.minecraft.Library@53687596, net.technicpack.launchercore.minecraft.Library@6efff5a1, net.technicpack.launchercore.minecraft.Library@665755f5, net.technicpack.launchercore.minecraft.Library@6fcc7c50, net.technicpack.launchercore.minecraft.Library@59f5a187], mainClass='net.minecraft.client.main.Main', minimumLauncherVersion=4, incompatibilityReason='null', rules=null} 2013/10/18 11:40:15 [iNFO] Running C:\Program Files\Java\jre7\bin\javaw.exe -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2048m -XX:MaxPermSize=256m -Djava.library.path=C:\Users\Iasu\AppData\Roaming\.technic\modpacks\chaoschism\bin\natives -Dminecraft.applet.TargetDirectory=C:\Users\Iasu\AppData\Roaming\.technic\modpacks\chaoschism -cp C:\Users\Iasu\AppData\Roaming\.technic\cache\net\sf\jopt-simple\jopt-simple\4.5\jopt-simple-4.5.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\com\paulscode\codecjorbis\20101023\codecjorbis-20101023.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\com\paulscode\codecwav\20101023\codecwav-20101023.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\com\paulscode\libraryjavasound\20101123\libraryjavasound-20101123.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\com\paulscode\librarylwjglopenal\20100824\librarylwjglopenal-20100824.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\com\paulscode\soundsystem\20120107\soundsystem-20120107.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\argo\argo\2.25_fixed\argo-2.25_fixed.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\org\bouncycastle\bcprov-jdk15on\1.47\bcprov-jdk15on-1.47.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\com\google\guava\guava\14.0\guava-14.0.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\org\apache\commons\commons-lang3\3.1\commons-lang3-3.1.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\commons-io\commons-io\2.4\commons-io-2.4.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\net\java\jinput\jinput\2.0.5\jinput-2.0.5.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\net\java\jutils\jutils\1.0.0\jutils-1.0.0.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\com\google\code\gson\gson\2.2.2\gson-2.2.2.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\org\lwjgl\lwjgl\lwjgl\2.9.0\lwjgl-2.9.0.jar;C:\Users\Iasu\AppData\Roaming\.technic\cache\org\lwjgl\lwjgl\lwjgl_util\2.9.0\lwjgl_util-2.9.0.jar;C:\Users\Iasu\AppData\Roaming\.technic\modpacks\chaoschism\bin\modpack.jar;C:\Users\Iasu\AppData\Roaming\.technic\modpacks\chaoschism\bin\minecraft.jar net.minecraft.client.main.Main --username Iasumonecara --session token:5987a3edcd33441f9f2bb8baf4a329b1:e6e1ae79ab974d7b8a47d2c2f37d0f0c --version 1.6.2 --gameDir C:\Users\Iasu\AppData\Roaming\.technic\modpacks\chaoschism --assetsDir C:\Users\Iasu\AppData\Roaming\.technic\assets 2013/10/18 11:40:16 [iNFO] 2013-10-18 11:40:16 [CLIENT] [iNFO] Setting user: Iasumonecara 2013/10/18 11:40:16 [iNFO] 2013-10-18 11:40:16 [CLIENT] [iNFO] (Session ID is token:5987a3edcd33441f9f2bb8baf4a329b1:e6e1ae79ab974d7b8a47d2c2f37d0f0c) 2013/10/18 11:40:17 [iNFO] 2013-10-18 11:40:17 [CLIENT] [iNFO] LWJGL Version: 2.9.0 2013/10/18 11:40:17 [iNFO] 2013-10-18 11:40:17 [CLIENT] [iNFO] Reloading ResourceManager: Default 2013/10/18 11:40:17 [iNFO] 2013/10/18 11:40:17 [iNFO] Starting up SoundSystem... 2013/10/18 11:40:17 [iNFO] Initializing LWJGL OpenAL 2013/10/18 11:40:17 [iNFO] (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) 2013/10/18 11:40:18 [iNFO] OpenAL initialized. 2013/10/18 11:40:18 [iNFO] 2013/10/18 11:40:19 [iNFO] 2013-10-18 11:40:19 [CLIENT] [iNFO] Stopping! 2013/10/18 11:40:19 [iNFO] 2013/10/18 11:40:19 [iNFO] SoundSystem shutting down... 2013/10/18 11:40:20 [iNFO] Author: Paul Lamb, www.paulscode.com 2013/10/18 11:40:20 [iNFO]
  8. http://files.minecraftforge.net/maven/net/minecraftforge/minecraftforge/9.11.1.916/minecraftforge-9.11.1.916.jar

  9. Skuli and I worked and tinkered with this a bit. This issue doesn't seem present in 1.6.4 but does exist for at least this version of forge in 1.6.2... It seems that the launcher checks your forge version (via checksum or some file within) and downloads an appropriate version.json for you. This does not seem to be a recognized version or the appropriate version.json is not available to download in the first place. Confirmation (and resolution ) would be greatly appreciated and bring merriment to the masses.
  10. Here's hoping. Though I don't expect it to magic the modpack.jar into place (where.. it should have already been placed by the launcher >.<)
  11. If it DLs any of the files, you DL should be fine (open to public, etc)... why it doesn't DL your modpack.jar? I... am at a complete loss, really. I assume coremods/ and cache/ are relics and harmless artifacts. Continuing to fight for progress... I'll let you know if I get it runnin' :/
  12. Launcher Build - 290 Minecraft Version - 1.6.2 Forge Version - 9.10.0.789 A modpack that was fully functional in Launcher Build 289 is now failing to load anything other than vanilla. Upon launching the pack, my version.json that I ship with the pack to let forge make magic is overwritten by a version downloaded from Mojang after 3 failed attempts to get it from technicpack.net. The new one appears (and functions) as a vanilla 1.6.2 version.json. Unless someone can enlighten me, I've no clue how to launch the client with forge without the forge version.json intact. I can't imagine that this is intentional, as I do not see this happening with 1.6.4 packs. Any assistance of advice would be delicious.
  13. That's.... odd? To me anyways. I'm still getting to know the launcher (more intimately than I had hoped), but that kind of behavior is not surprising anymore. I've found the log file to be nearly useless in diagnosing launcher issues thus far... I do remember having those issues you describe and I am trying to recall how I resolved them. Does the pack arrive intact in the correct locations? PM regarding further attempts sent. :/
  14. That's shoddy :/ I'm starting to think this is a 1.6.2 issue. After trying working packs for 1.6.4 (through launcher), my files line up just fine and all appears well. When you try to launch the pack with the console open, does it give anything at all about downloading version.json? You say it just stops.... I've no clue how to move forward if it is that upset with you. Strangling a cat sounds.... accurate.
  15. I had a working pack that worked dandy with build 289. When the launcher updated to 290, I'm now launching vanilla without any attempt to fire up forge as it downloads a clean vanilla 1.6.2 version.json on startup. Awaiting any head's up on what changes we need to make to packs to make them work again. Like you, Nox13last, I have folks waiting. The packed worked flawlessly last night and now won't even load. Quite a bummer of an update. Anyone have a clue on a technic launcher changelog? Even the tiniest bit might clarify this mess. Also, Nox13last, your pack would have likely been well off a day or two ago.... I can't find any info on how to get forge fired up for us in 290.
×
×
  • Create New...