Search results

It sounds like the dimension table/list has been corrupted (especially dimension 0 - the overworld and dimension -1, the nether). I'm not sure how this could be fixed, though.

As has been pointed out many times already, this is a limitation of 32-bit Java. If you can, upgrade to 64-bit Java. But do bear in mind that this is a large modpack, running 140+ mods. It is going to take a fair amount of memory to run.

You are running 32-bit Java on a 32-bit operating system. This means that Java cannot allocate more than 1.5GB (Approximately) of RAM. Large modpacks like DireWolf20 require a lot of RAM, generally at least 2GB for Java (4GB total), to run. You need to upgrade your OS to a 64-bit version and...

You are running a 32-bit version of Java on a computer with 4GB RAM (2 of which is free). As you are only running the 32-bit version of Java, you are only allocating 1GB of RAM to minecraft, which will cause out of memory issues in fairly short order. Even upgrading to 64-bit (which it seems...

There's a v1.0.18? 'cause I only see 1.0.17. Though it seems that the launcher is having problems connecting to the repo (Or, indeed, anywhere), as it's getting "Connection refused:

Well, it looks like those mobs are from the Moo Moo Farm. It looks like the spawning rules for whatever world you're in (I'm going to hazard a guess and say the overworld) have been scrambled with those of other dimensions. Only thing I can think of is to delete the world and start from scratch.

If you are Morphed, WAILA can/will misread what you are looking at, as it is attempting to work out what your "Head" is looking at, and your head isn't where WAILA thinks it is. This is unfortunately a cross-mod problem, and I'm not entirely sure how it could be fixed. The same thing happens...

Press "N" to switch minimap mode (and re-enable the minimap)

You have an AMD graphics card, and you're using the Mantle beta driver. The Mantle driver has broken OpenGL. Please uninstall it and roll back to a previous AMD driver, or try the following temporary fix: http://forums.guru3d.com/showthread.php?t=386289

Yes, server and client have to have the same configs. If they don't, breakage can/will occur. This is part of Modded Minecraft, and is the same for every single pack out there. So not a bug.

In theory, every kind of ore should work, thanks to the Ore Dictionary. IIRC, IC2 ore configuration is "All or nothing", whereas TE ores can be customized with frequency and size, which makes them preferable. Also IIRC, the IC2e Scanner/Pattern Storage and Replicator are broken in current builds.

I certainly can. But this was playing on a server. Server didn't crash, it was client-side only. Could be a sync issue, as I was breaking down the HP boiler pretty fast, and the fluiducts didn't appear to be keeping up with the connected state of the boiler blocks.

What Mod Pack: Direwolf 20 v1.6 v1.0.14 Pastebin link: http://pastebin.com/gXxb7SYD Reproducible: Yes (Second pastebin: http://pastebin.com/UcxNU3Ur ) What happened: Was breaking a HP boiler (With covers on the sides covering the TE Fluiducts that removed the steam) when the above crash happened.

Mod Pack: Direwolf20 Mod & Version: 1.0.14 Pastebin link to crash log: N/A Whats the bug? AE storage bus isn't recognizing Factorization barrels. It works fine with MFR Deep Storage Units. Can it be repeated? Yes Known Fix: Unknown

This was a DireWolf20 1.0.12 server. It has been updated to 1.0.14 and it's still doing it. There is no DragonAPI installed in this modpack/server. Anyone else?

Java is reporting: Caused by: java.lang.ClassNotFoundException: org.lwjgl.LWJGLException Something is wrong with the lwjgl files. If you have another, working, Minecraft installation, I'd suggest copying the lwjgl and natives folders over from there, see if that helps.

I have no idea what's causing it, but I keep getting: 2014-01-29 07:34:55 [INFO] [STDERR] java.util.ConcurrentModificationException 2014-01-29 07:34:55 [INFO] [STDERR] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) 2014-01-29 07:34:55 [INFO] [STDERR] at...

Yes. It's crashing because you don't have enough available RAM. This has already been explained to you, and there is absolutely nothing that any of us can do about it.

You're in Adventure mode. Switch to Survival mode.