Search results

Matter overdrive requires java 8.

Start by giving us full log: In the launcher's options tab, check the boxes "Show Console" and "Reopen launcher when Minecraft exits". Then launch your pack again and when the crash/error/other problem occurs, click the "upload log" button in console window and give us the link. Forge's log...

Reintall java. Certificate store is probably somehow broken.

Just no. That particular problem has been fixed in 1.4.4 version of the launcher. There is no need to download JRE which is already at EOL.

Nobody communicated. It would have been easy task to add loop and some kind of control structure into server startup script template. Feedback and request(s) should be entered into issue tracker, not here.

Are you sure? IIRC it's "Loading - Contstructing mods" not "Downloading". Screenshot? Log?

Lemme guess: by vanilla working you mean you are using vanilla lancher and its bundled JRE? Try downgrading your java. See: https://bugs.mojang.com/browse/MC-297

Workaround: http://ftb.cursecdn.com/FTB2/modpacks/FTBDeparted/1_4_0/FTBDepartedServer.zip

http://minecraft.curseforge.com/projects/ftb-utilities/issues/5

Bigger packs won't work with 32-bit java.

http://support.feed-the-beast.com/t/ftb-infinitiy-crash/10438/4?u=jikuja

Is there FTBServer-1.7.10-1448.jar in your mods folder?

That is probably full log provided by the multicraft console. That thing just screws your log:/

Known issue: http://minecraft.curseforge.com/projects/ftb-utilities/issues/5

On the launcher go to options then click the force update button, then launch the modpack.

Next rant: links to mods in the http://www.feed-the-beast.com/projects/ftb-infinity-evolved/relations/dependencies are broken

Crash in the GPU driver. Try updating GPU drivers.

No log => no support. Other rant in the "problem description": answer for launcher part: NO, won't gonna happen. If you weree criticiting the fact that MC uses java you should direct your complain to mojhsang, not here. Even if we decide to rewrite launcher with <insert your language here> it...

IIRC the file could be unzipped but JVM could not open the file with classloader/JarFile => checksum found real problem.

TBH I mostly blame users and AV/firewall vendors for this problem: Logs are well-hidden. Documentation for getting logs? Does users check to logs if requested? Will they find the logs? Does product X even log its actions? Do we need to write guide for log checking? Notifications can be easily...