Jump to content
  • 0

Launcher doesn't open modpack when launch button is pressed.


Kaniva

Question

Launcher Version: 285 - 322

Operating System: Windows 7 64-bit

Java Version: Version 7 Update 45

Antivirus Program: avast! antivirus

Description of Problem:

When I press the launch button after logging into the launcher, it tries to extract or something (progress bar seems to do something), but abruptly stops and does nothing. Repeated tries, as well as multiple clean installs of the launcher, java, Minecraft, and antivirus has done nothing. Antivirus and firewalls have been turned off. Tried different memory amounts, different versions of modpack and launcher, as well as logging in with a Mojang email account as well as a Minecraft username account. I also have both the 32 and 64-bit versions of java installed.

The packs seem to install fine, but afterwards never lets me launch them. The only pack I have noticed that lets me launch is Tekkit Classic.

It's also worth noting that last time I used the launcher (Summer 2013) it worked flawlessly, problem has arisen since then.

Error Messages:

No error messages given, just doesn't do anything after launch is pressed.

Technic Launcher Console:


Analytics Response [installModpack]: 200



Starting download of http://mirror.technicpack.net/Technic/version/1.5.2/1.5.2.json, with 3 tries remaining



 

 

Error Log:



2013/10/30 00:37:00 [iNFO] ------------------------------------------

2013/10/30 00:37:00 [iNFO] Technic Launcher is starting....

2013/10/30 00:37:00 [iNFO] Launcher Build: 322

2013/10/30 00:37:00 [iNFO] ------------ Startup Parameters ------------

2013/10/30 00:37:00 [iNFO] --------- End of Startup Parameters ---------

2013/10/30 00:37:00 [iNFO] Analytics Response [runLauncher]: 200

2013/10/30 00:37:02 [iNFO] Starting download of http://skins.technicpack.net/helm/Kaniva/100, with 3 tries remaining

2013/10/30 00:37:02 [iNFO] Valid:

2013/10/30 00:37:02 [iNFO] {"accessToken":"e2c46c727ed24518a25feb4ea86f8c6e","clientToken":"a15f8fbb-e0d9-49bf-9a9a-c27de580d07b","selectedProfile":{"id":"f203f9a1566c41739ad346a64a6eb629","name":"Kaniva"}}

2013/10/30 00:37:02 [iNFO] Launcher took: 3476ms to start

2013/10/30 00:37:05 [iNFO] Analytics Response [installModpack]: 200

2013/10/30 00:37:07 [WARNING] File version.json not found in C:\Users\Windows\AppData\Roaming\.technic\modpacks\hexxit\bin\modpack.jar

2013/10/30 00:37:07 [iNFO] Starting download of http://mirror.technicpack.net/Technic/version/1.5.2/1.5.2.json, with 3 tries remaining

2013/10/30 00:37:07 [sEVERE] Unhandled Exception in Thread[installThread,6,main]

com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1

at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)

at com.google.gson.Gson.fromJson(Gson.java:803)

at com.google.gson.Gson.fromJson(Gson.java:768)

at com.google.gson.Gson.fromJson(Gson.java:717)

at com.google.gson.Gson.fromJson(Gson.java:689)

at net.technicpack.launchercore.install.ModpackInstaller.getMinecraftVersion(ModpackInstaller.java:186)

at net.technicpack.launchercore.install.ModpackInstaller.installPack(ModpackInstaller.java:80)

at org.spoutcraft.launcher.InstallThread.run(InstallThread.java:54)

Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1

at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:374)

at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:165)

... 7 more

Link to comment
Share on other sites

16 answers to this question

Recommended Posts

  • 0

Actually kaniva, it looks like your local network is providing a situation where when your router receives a 404 from a remote webpage, it serves you a search page instead. This sucks for us, because we check to see if the technic site has a version.json before we try to use the mojang one. What's going on is your router tells the launcher that there IS a version.json at the remote site, and then we download the search page your router serves up and try to parse it as json. We'll probably need to make some changes to the way we do things to work around this, but it'd be better if you could get your router to stop doing this craziness.

Link to comment
Share on other sites

  • 0

It turns out with my specific router this feature cannot be turned off. Is there a version.json that I could download and add manually? Or does my computer specifically need to generate it?

Either that or I buy a new router.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...