JaariAtmc

The guide tells people to rename the forge.jar to modpack.jar. However, as the file is already a .jar, it actually tells you to rename forge to modpack. People rename to modpack.jar instead, and that's where it breaks.

[B#347] Running C:\Program Files\Java\jre1.8.0_91\bin\javaw.exe [B#347] org.lwjgl.LWJGLException: Pixel format not accelerated Downgrade your Java to 8u25. Also, please don't use 7 GB of RAM, that is going to cause issues as well. The main rule is: Either half your system's RAM, or max. 4 GB, whichever is less.

Mind telling us what is wrong with your modpack, except for the modpack in modpack.zip being in a subfolder?

Modpack.jar is now actually called modpack.jar.jar (Just name it "modpack", but make sure it is still a .jar file).

Ask your friends to remove your player.dat file, I fear you've been doing something that causes your issue. Downside of this is that you lose anything in your inventory/statusses on your character.

"Haven't played for months" and upgraded to Windows 10 in the meantime?

If I remember correctly, the IP stated when you were portforwarding.

Forestry version?

What was the last thing you were doing? Trying to ride a dinosaur?

Please provide your launcher log so we can check what you are doing. Launcher Log can be found in %appdata%\roaming\.technic\logs\ Open the log file, copy the contents and paste it here, then give us the link.

Which pack are you downloading?

Please provide the full URL, I know I can paste stuff there

Ah, that bit of knowledge would've been nice to hear. Could you provide us with your launcher log? You can find it in %appdata%\Roaming\.technic\logs\ (get the one from the day you last tried, like probably today...), and upload the contents to paste.ubuntu.com. Also, there appears something to be wrong with one of the .jar files. Please download all the mods and forge again, and zip/upload the modpack again.

Update your forge to a more recent version for 1.7.10, and get your mods from the official source, not from modrepost sites. It is likely caused by some ancient mod that affects world generation. Otherwise, you'll have to remove Farseek + Streams.

It sure did: [B#347] 2016/06/10 13:02:51 [INFO] Error occurred during initialization of VM [B#347] 2016/06/10 13:02:51 [INFO] Incompatible minimum and maximum heap sizes specified [B#347] 2016/06/10 13:02:51 [INFO] Picked up _JAVA_OPTIONS: -Xmx512M You've got a Java Environment Variable that limits any java processes to 512MB max. So even if you try to allocate 3 GB, it will not allow the system to allocate more than 512 MB. Now for your fix: https://cdn.discordapp.com/attachments/96563656271093760/166334782450565121/clearJavaEnvVars.bat Download it, open it. Nothing will come up, but the variable is gone and you will be able to play modpacks.

All I needed to know. You'll have to downgrade your java to java8u25 (can be downloaded here), then restarting your launcher. This is caused by your graphics drivers not being fully supported by Windows 10.

Let's start with you providing a log. You can find the logs in %appdata%\Roaming\.technic\logs, and you can upload it to paste.ubuntu.com.

What I think you are doing (used Attack of the Bteam for my example): You zip the folders first, after that, you put these folders in another zip, which makes it look like this inside the new zip file. What you should be doing: Select these 3 folders, then zip them into one zip folder, which looks like this on the inside.

Please upload the contents of that crashreport to www.pastebin.com, as we cannot view attachments on here

Open the big map, default key is M (this conflicts with another key, change that in your controls).

The name of the world, does it have a dot in it?

Remove that one, it is a clientside only mod (means the server will crash if left in).

So you zipped the config/mods/bin folders seperately, then zipped the zipped folders? Just select bin/config/mods, then make one zip out of those three unzipped folders.

And the URL for your technic modpack page? Like, what is your modpack's name? Also, kick out LegacyJavaFixer, unless you are using a version of Forge before 1291 (which also means you should consider upgrading to a much later version of Forge...).