Lord Ptolemy

Your forge file is named wrong. It is suppose to be modpack.jar not modpack.jar.jar Enable file extensions in Windows then fix the file name. https://support.microsoft.com/en-us/help/865219/how-to-show-or-hide-file-name-extensions-in-windows-explorer

Your Java install is corrupted. To reinstall it please go to the link below and download the version for your computer. If you're using Windows, please use the version Windows Offline (64-Bit). After downloading the updated version of Java. Please click on the installer to install it. http://java.com/en/download/manual.jsp

1.) In the Windows search bar in the bottom left of the screen type "command prompt" 2.) Once the command prompt has opened type "java -version" 3.) Show the results here.

1.) In the Windows search bar in the bottom left of the screen type "command prompt" 2.) Once the command prompt has opened type "java -version" 3.) Show the results here.

Complain to the modpack author. Their server is misconfigured. On top of that they're violating the Modpack Terms by using the name of an official modpack which could lead to deletion in the future.

Please use pastebin. We cannot view uploads on the forum.

It appears you're running an Intel iGPU that has issues with Java 8 past version 60. You will need to downgrade your current Java install. Please follow the instructions below. 1.) Completely close the Technic launcher DO NOT skip this step. 2.) Download: http://cdn.lemonmc.com/jre-8u25-windows-x64.exe 3.) Run the Java installer called: jre-8u25-windows-x64.exe that you just downloaded 4.) Follow the on screen instructions of the Java installer. Stick with the default settings. Click next or accept for each screen. 5.) After the Java installer has finished installing Java. Start up the Technic launcher again. 6.) Click on the tab called MODPACKS at the top of the window. 7.) Click on the button that says Launcher options in the top right of the window 8.) Click on the tab called Java settings 9.) Click on the dropdown called Minecraft Java Version 10.) Click on the option called 1.8.0_25 64-Bit 11.) Change Memory to a value between 2 GB and 4 GB. DO NOT allocate more than 4gb. 12.) Attempt to launch a modpack. DO NOT update Java 8 again as updates past the one you were just provided will not work with your system and cause crashes.

This is a bug with Java 8 on Windows 10 Anniversary that's apparently fixed in Java 9. Not entirely sure if this will fix your issue as I haven't been able to get anyone to test it and give feedback. 1.) Download this version of the Technic launcher: http://launcher.technicpack.net/launcher4/349/TechnicLauncher.jar 2.) After downloading place that jar file on your desktop 3.) In the "Search Windows" bar type in "command prompt" 4.) Copy and paste this into the command prompt: java -Dswing.defaultlaf=javax.swing.plaf.nimbus.NimbusLookAndFeel -jar %USERPROFILE%\Desktop\TechnicLauncher.jar 5.) Try navigating to the "Mod Options" tab in the Technic launcher again. You can read up more on this issue along with what that command is doing by looking at these links: https://bugs.openjdk.java.net/browse/JDK-8179014 https://bugs.openjdk.java.net/browse/JDK-8178873 http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8178873 https://docs.oracle.com/javase/tutorial/uiswing/lookandfeel/plaf.html#commandLine EDIT: I was able to get a confirmation that the above does not work. However the fix for this issue was back-ported to Java 8. Update your Java from this link: https://www.java.com/en/download/manual.jsp Get the one that says Windows Offline (64-bit)

It indeed does not apply any user submitted java arguments in the options menu. From what I understand it was purposely done so people don't go copying random things into there and then complain something broke.

That has nothing to do with the Technic launcher. That's you forgetting your password or your account was already compromised. However if you don't believe me you can view the entirety of the launcher's source code at these locations: https://github.com/TechnicPack/LauncherV3 https://github.com/TechnicPack/LauncherCore https://github.com/TechnicPack/LauncherUICore https://github.com/TechnicPack/MinecraftCore More specifically you can view the code related to logging in here: https://github.com/TechnicPack/MinecraftCore/blob/master/src/main/java/net/technicpack/minecraftcore/mojang/auth/AuthenticationService.java#L97:L111

Also take a look at these for various tutorials: http://www.minecraftforge.net/forum/forum/111-user-submitted-tutorials/ http://www.minecraftforum.net/forums/mapping-and-modding/mapping-and-modding-tutorials You can ask for modding support here as well: http://www.minecraftforge.net/forum/forum/116-mod-developer-central/

Your launcher is extremely outdated. Please allow it to update. If it doesn't update then download a fresh copy using this link: http://launcher.technicpack.net/launcher4/349/TechnicLauncher.exe

Instead of posting this giant wall of text again. Look at the solution I posted here:

You appear to be having an issue with an unsupported Intel Graphics device and windows 10. This issue is common for older computers and windows 10. If your computer is a desktop, we recommend getting a dedicated graphics card, as it is a better option. If that is not possible, there is a fix: Java 8: 1.) Close the launcher. Make sure it isn't running! 2.) Download and install: https://download.uskarian.net/java/jre-8u25-windows-x64.exe 3.) Start up the launcher 4.) Launcher options -> Java settings -> Minecraft Java Version -> pick 1.8.0_25 64-Bit 5.) Attempt to launch a modpack. DO NOT update Java 8 as versions past this one do not work. OR Java 7: 1.) Close the launcher. Make sure it isn't running! 2.) Download and install: https://download.uskarian.net/java/jre-7u80-windows-x64.exe 3.) Start up the launcher 4.) Launcher options -> Java settings -> Minecraft Java Version -> pick 1.7.0_80 64-Bit 5.) Attempt to launch a modpack.

From the Discord ~30 mins ago:

API caches information. It can take up to an hour before it updates. It is usually instant.

Well for one don't allocate 16gb. Allocate half your ram or 4gb. Which ever is the lowest. Not entirely sure what is going on. I passed it around and one person thought it may be because of spaces in your filepath. So instead of: D:\Minecraft\Technic Launcher\modpacks\ D:\Minecraft\Technic Launcher\modpacks\ To something like: D:\Minecraft\Technic_Launcher\modpacks\ I think you should reinstall your Java and Technic install (please try using the default install and not portable): I see you're using Java 8 u25 and you can get it directly here: https://download.uskarian.net/java/jre-8u25-windows-x64.exe or Get it from Oracle: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html Completely remove your Technic install. This includes the executable you downloaded along with your custom directory. Then redownload the exe from: http://launcher.technicpack.net/launcher4/347/TechnicLauncher.exe EDIT: and I just realized you tried clean installs of both the launcher and Java already :/

Use pastebin.com to upload your techniclog.

You appear to be having an issue with an unsupported Intel Graphics device and windows 10. This issue is common for older computers and windows 10. If your computer is a desktop, we recommend getting a dedicated graphics card, as it is a better option. If that is not possible, there is a fix: Java 8: 1.) Close the launcher. Make sure it isn't running! 2.) Download and install: https://download.uskarian.net/java/jre-8u25-windows-x64.exe 3.) Start up the launcher 4.) Launcher options -> Java settings -> Minecraft Java Version -> pick 1.8.0_25 64-Bit 5.) Attempt to launch a modpack. DO NOT update Java 8 as versions past this one do not work. OR Java 7: 1.) Close the launcher. Make sure it isn't running! 2.) Download and install: https://download.uskarian.net/java/jre-7u80-windows-x64.exe 3.) Start up the launcher 4.) Launcher options -> Java settings -> Minecraft Java Version -> pick 1.7.0_80 64-Bit 5.) Attempt to launch a modpack.

Your log shows no crashes. Can you please make sure you're uploading the correct log. Make sure you've attempted to launch a modpack today.

Pastebin the log. We cannot view attachments.

[B#347] 2016/10/30 09:49:35 [INFO] [09:49:35] [main/ERROR] [FML]: There is a binary discrepency between the expected input class ahu (ahu) and the actual class. Checksum on disk is 782b2e42, in patch 746fe971. Things are probably about to go very wrong. Did you put something into the jar file? [B#347] 2016/10/30 09:49:35 [INFO] [09:49:35] [main/ERROR] [FML]: The game is going to exit, because this is a critical error, and it is very improbable that the modded game will work, please obtain clean jar files. Download your mods from reputable sites like Curse or straight from the mod author's website.

Easiest way is to just reinstall the modpacks. This shouldn't touch your saves. Another way is to reconstruct the installedPacks json file located at the root of the technic install directory. Basically open it up in a text editor. Copy and paste the first object in "installedPack" a few times. Now open up your modpack directory in your file browser. Copy each of their names into seperate objects that you just copied to replace the info in there. Set all the builds to "recommended", set each "name" key to the name of the folder. Change the "directory" key to "%MODPACKS%\\<modpack-folder-name-here". Then skip down to the "byIndex" array. Add a new string to the array for each folder name. Examples: Broken installedPacks: { "installedPacks": { "hexxit": { "name": "hexxit", "build": "2.0.1c", "directory": "%MODPACKS%\\hexxit" }, "some-modpack": { "name": "some-modpack", "build": "recommended", "directory": "%MODPACKS%\\some-modpack" } }, "byIndex": [ "hexxit", "some-modpack", ], "selected": "hexxit" } Copied the first installed pack object to create a few placeholders: { "installedPacks": { "hexxit": { "name": "hexxit", "build": "2.0.1c", "directory": "%MODPACKS%\\hexxit" }, "some-modpack": { "name": "some-modpack", "build": "recommended", "directory": "%MODPACKS%\\some-modpack" }, "hexxit": { "name": "hexxit", "build": "2.0.1c", "directory": "%MODPACKS%\\hexxit" }, "hexxit": { "name": "hexxit", "build": "2.0.1c", "directory": "%MODPACKS%\\hexxit" }, "hexxit": { "name": "hexxit", "build": "2.0.1c", "directory": "%MODPACKS%\\hexxit" }, "hexxit": { "name": "hexxit", "build": "2.0.1c", "directory": "%MODPACKS%\\hexxit" }, }, "byIndex": [ "hexxit", "some-modpack", ], "selected": "hexxit" } Modpack folders: hexxit, some-modpack, testing-1-2-3, my-awesome-modpack, tekkit-legends, to-the-moon-and-back Fixed installedPacks file: { "installedPacks": { "hexxit": { "name": "hexxit", "build": "2.0.1c", "directory": "%MODPACKS%\\hexxit" }, "some-modpack": { "name": "some-modpack", "build": "recommended", "directory": "%MODPACKS%\\some-modpack" }, "testing-1-2-3": { "name": "testing-1-2-3", "build": "recommended", "directory": "%MODPACKS%\\testing-1-2-3" }, "my-awesome-modpack": { "name": "my-awesome-modpack", "build": "recommended", "directory": "%MODPACKS%\\my-awesome-modpack" }, "tekkit-legends": { "name": "tekkit-legends", "build": "recommended", "directory": "%MODPACKS%\\tekkit-legends" }, "to-the-moon-and-back": { "name": "to-the-moon-and-back", "build": "recommended", "directory": "%MODPACKS%\\to-the-moon-and-back" }, }, "byIndex": [ "hexxit", "some-modpack", "testing-1-2-3", "my-awesome-modpack", "tekkit-legends", "to-the-moon-and-back" ], "selected": "hexxit" }

Please upload your techniclog to pastebin.com

For all the other people who stumble upon this thread with this same predicament. Press F1 on your keyboard. It will hide/unhide the GUI.