3
Getting, Identifying, and Reporting Errors Logs.
Your Minecraft Crashes or something? Did you see a error screen in a blink of a eye? Then follow this Guide. Carefully read all of this and you'll be able to solve your problem and identify your what your error report is.
Works with all Operating Systems. The screenshot shows that it is on Mac but it works for all OSes.
If you don't understand this, Read it all over again until you know it.
This thread is meant to tell:- How to get error logs
- Identifying error logs/ Types of error
- How to correctly report a error onto threads
Please give this a + and reply to this thread if you got any problems. (please the post error logs here as well as your installed mods)
Before you argue read this guide all over again.
Or
If you hate this thread or this fucks you up or you feel i am a smartass just don't read this or reply. Don't complain if this is ugly too.
If you're a modder that would like to link this thread, go ahead.
But first off make sure you
!!!DELETE META-INF!!!
Troubleshooting crash:
1. Make sure you have deleted Meta-INF!
2. Have the right version of mod to Minecraft. I.E MC 1.1 mod do not work with weekly build so do no ask the modder. This includes future weekly builds.
3. Reading the error report. You could get a solution if you do read the report. Read below for info. Don't post errors that have a solution listed here.
1. How to get error logs
go to top
If you're suddenly getting a saving chunks in game and a error report showing for a nano seconds or hang in the mojang screen and then Black Screen. Do this so modders know what's your error.
Method 1:(MCPatcher)
This is works for all OSes and pretty much easy to do.
First off. You need to download the tool MCPatcher.
Download the version that is suitable version for your OS and run it.
Once you run it you should see a screen like this:(this is on mac)
Click the test minecraft button and do not press anything than that button.
If you got a error it should look like this:
Copy the whole error log(or the error at the bottom) and post it into the thread.
Before you post the error logs make sure you READ IT FIRST!
FOLLOW the "how to correctly post error logs into threads" to correctly post one without getting the page longer.
Method 2:(The magic way)
Download a launcher created by sp614x located here
Once you log in you should see a logging window as well as a crash report if it crashes.
The logging window is different but the crash report screen is the same as above.
Method 3:(Batch or Command lines)
This uses the power of Batch files of your windows so it pretty much works only for windows and if you don't want MCPatcher.
Download and run this Error test by mDiyo or Run this command at the Command Prompt
java -Xms512m -Xmx1024m -cp "%APPDATA%\.minecraft\bin\*" -Djava.library.path="%APPDATA%\.minecraft\bin\natives" net.minecraft.client.Minecraft
Same as above if you see the error.
Method 4:(modloader.txt)
This is works for all OSes but only if you got Modloader installed.
First off go into your minecraft directory and find the file named Modloader.txt
Use your text editor's 'find' to find the error by finding the word "java." (without quotes or the ")
Or if the author of the mod actually needs you to post the whole modloader.txt then do that.
Example. Inside the modloader.txt:
Spoiler:
Before you post the error logs make sure you READ IT FIRST! and FOLLOW the "how to correctly post error logs into threads" to correctly post one without getting the page longer and getting yourself look stupid.
Method 5:(Sudden crash without saving chunks)
This method only works if you're suddenly getting minecraft to close immediately without the saving chunks screen a hs_err_pidxxx.log appears on the directory where minecraft is installed into.
Usually this is a Out Of memory error which does not show the out of memory screen.
So do assign more RAM into minecraft. Search the thread to get more RAM in MCF to get the guide.
2. Identifying error logs
go to top
There are some types of errors. Such as:
1. Block ID Conflict or java.lang.IllegalArgumentException: Slot XXX is already occupied by *insert block name here* when adding *insert other block name here*
Now Block ID Conflict is the thing that most people sometime doesn't know about. Example of them:
java.lang.IllegalArgumentException: Slot 209 is already occupied by forestry.BlockSoil@519549e when adding forestry.BlockSoil@420253af at yy.<init>(Block.java:212) at forestry.BlockSoil.<init>(BlockSoil.java:23) at forestry.config.ForestryBlock.initialize(ForestryBlock.java:31) at forestry.config.Config.load(Config.java:126) at forestry.ForestryCore.load(ForestryCore.java:44) at forestry.ForestryClient.load(ForestryClient.java:71) at mod_Forestry.load(mod_Forestry.java:42) at ModLoader.init(ModLoader.java:830) at ModLoader.AddAllRenderers(ModLoader.java:186) at wb.<init>(wb.java:76) at wb.<clinit>(wb.java:9) at net.minecraft.client.Minecraft.a(SourceFile:265) at net.minecraft.client.Minecraft.run(SourceFile:644) at java.lang.Thread.run(Unknown Source)
Sometimes this type of error starts with a ExceptionInInitializerError and followed by a Block ID Conflict error.
How to solve:
Method 1
1. READ IT FIRST
2. Find the mod related to the Block ID Conflict
3. Find the mod's Config. If both of the mod doesn't have a config then you have to use method 2
4. Change the block ID located in the Config
5. Run the game again and repeat this process until the conflict are gone
Method 2
1. Download the mod named ID Resolver and it's requirements by ShaRose and install it
2. Follow the conflict screen and ID Resolver will try to assign it to another ID
Method 2 is easier than method 1 but i recommend method 1 because method 2 will sometimes crash certain mods such as Pam's Mods.
2. java.lang.ArrayIndexOutOfBoundsException: XXXXX
Info from java docs:
Quote
Thrown to indicate that an array has been accessed with an illegal index. The index is either negative or greater than or equal to the size of the array.
There are certain types of this error:
1. Out of Bounds Block ID
Out of Bounds block id is usually caused by user error when assigning block IDs such as when they set it above 255.
It looks like this:
java.lang.ExceptionInInitializerError at forestry.ForestryClient.initialize(ForestryClient.java:63) at mod_Forestry.<init>(mod_Forestry.java:29) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at ModLoader.addMod(ModLoader.java:275) at ModLoader.readFromModFolder(ModLoader.java:1179) at ModLoader.init(ModLoader.java:824) at ModLoader.AddAllRenderers(ModLoader.java:186) at aam.<init>(aam.java:61) at aam.<clinit>(aam.java:10) at net.minecraft.client.Minecraft.a(SourceFile:259) at net.minecraft.client.Minecraft.run(SourceFile:629) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ArrayIndexOutOfBoundsException: 2017 at forge.Configuration.getOrCreateBlockIdProperty(Configuration.java:66) at forestry.ForestryCore.<clinit>(ForestryCore.java:207) ... 17 more
It can start without the ExceptionInInitializerError.
2. Modder's fault
Sometimes they may do a user error when coding:
But it usually says like
java.lang.ArrayIndexOutOfBoundsException: -1 at zx.a(Chunk.java:387) at ry.b(World.java:489) at ry.d(World.java:602) at xie.Xie.setBlockAndMeta(Xie.java:708) at xie.blocks.XieBlockFurnace.onDestroyed(XieBlockFurnace.java:182) at xie.blocks.XieBlockFurnace.e(XieBlockFurnace.java:313) at aes.a(PlayerController.java:46) at dm.a(PlayerControllerSP.java:58) at dm.b(PlayerControllerSP.java:91) at net.minecraft.client.Minecraft.c(SourceFile:1211) at net.minecraft.client.Minecraft.k(SourceFile:1537) at net.minecraft.client.Minecraft.x(SourceFile:705) at net.minecraft.client.Minecraft.run(SourceFile:658) at java.lang.Thread.run(Unknown Source)
DO REPORT THIS SUCH ERROR NOT THE OUT OF BOUNDS BLOCK ID!
3. java.lang.NoClassDefFoundError: *insert class name here*
Info from java docs:
Quote
Thrown if the Java Virtual Machine or a ClassLoader instance tries to load in the definition of a class (as part of a normal method call or as part of creating a new instance using the new expression) and no definition of the class could be found.
The searched-for class definition existed when the currently executing class was compiled, but the definition can no longer be found.
The searched-for class definition existed when the currently executing class was compiled, but the definition can no longer be found.
This usually happens when you did not install certain required mods
Here is the referring classes that i've found is popular:
BaseMod (Modloader)
BaseModMp (ModloaderMp)
ITextureProvider(MCForge)
But before you post this error make sure you INSTALLED THE MOD'S REQUIRED APIs
Otherwise it is modder's packaging stupidity.
4. java.lang.NoSuchMethodError: *insert text here* or NoSuchFieldError: *insert text here*
Info from java docs:
Quote
Thrown if an application tries to call a specified method of a class (either static or instance), and that class no longer has a definition of that method.
Normally, this error is caught by the compiler; this error can only occur at run time if the definition of a class has incompatibly changed.
Normally, this error is caught by the compiler; this error can only occur at run time if the definition of a class has incompatibly changed.
This usually happens when you got a base class conflict, Wrong Minecraft Version etc.
So make sure you:
1. Have the correct version for minecraft's version
2. Have merge for conflicting classes
3. Install from clean jar
4. Re-install the mod
Just don't report this error. MCP Compiler never actually allows wrong named Methods.
5. RedPowerCore: BlockID XXX exists, autoAssign is disabled.
This is RedPower Related error. Usually happens just like Block ID errors.
How to solve:
Delete .minecraft/redpower/redpower.cfg. that way red power will re-assign the block IDs
6. java.lang.VerifyError: (class: *insert mod class here*, method: *insert method here* signature: (*insert signature here*;)V) Incompatible argument to function
Info from java docs:
Quote
Thrown when the "verifier" detects that a class file, though well formed, contains some sort of internal inconsistency or security problem.
Most likely you have not used the fixed version of a API or Some user error when installing.
How to solve:
Make sure you have updated to the lastest Related mods.
7. java.lang.NullPointerException
Info from java docs:
Quote
Thrown when an application attempts to use null in a case where an object is required. These include:
Applications should throw instances of this class to indicate other illegal uses of the null object.
- Calling the instance method of a null object.
- Accessing or modifying the field of a null object.
- Taking the length of null as if it were an array.
- Accessing or modifying the slots of null as if it were an array.
- Throwing null as if it were a Throwable value.
Applications should throw instances of this class to indicate other illegal uses of the null object.
Happens when modders accidently made a method or other stuff that points into a null. Such as a unhandled method or field.
Report this.
8. java.lang.ExceptionInInitializerError
Info from java docs:
Quote
Signals that an unexpected exception has occurred in a static initializer. An ExceptionInInitializerError is thrown to indicate that an exception occurred during evaluation of a static initializer or the initializer for a static variable.
Usually followed by another type of error. Read the bottom one instead.
9. java.lang.IndexOutOfBoundsException
Info from java docs:
Quote
Thrown to indicate that an index of some sort (such as to an array, to a string, or to a vector) is out of range.
Usually followed by a ArrayIndexOutOfBoundsException but usually not Out of Bounds block ID.
10. java.lang.reflect.InvocationTargetException
Info from java docs:
Quote
InvocationTargetException is a checked exception that wraps an exception thrown by an invoked method or constructor.
Before you report this error make sure you got the lastest version of the mod.
11. java.lang.NoSuchMethodError: buildcraft.api.LiquidData.<init>(IILyq;)V
Another mod related error. Usually when you guys trying to install forestry with BC 2.1.12 or other mods that require BC 3.1.x
Other types of error that i have not yet shown needs to be reported.
3. How to Correctly Report a Error log into modder's thread
go to top
This is will prevent yourself from getting the page longer and prevents people from thinking that you're stupid.
First off open all spoilers on mod author's page and open your find feature in your browser. Find any text related to the bug/crash you have encountered. If it finds one then the author already know that. This will prevent you from looking stupid. If there's one, then the author didn't know/wrote about your bug/crash then report it.
Use this code to post your error logs:
[spoiler]*insert error logs here*[/spoiler]
And thats about it about error logs.
But the most important stuff is MAKE SURE YOU READ THE ERROR LOG and DELETE META-INF!
