Crash when I first right click a new spell to assign a name and pick an icon.

[eastwood6510]

This crash happens 85% of the time I first open a new spell to assign a name and assign an icon. Curiously, on different crashes (which come from different new spells) the indexOutOfBoundsException is indexed at different locations.

The main description of the crash is: Exception in world tick

Here are a few of the crash logs:

http://pastebin.com/CiRZsvg3
http://pastebin.com/4wXqDABD
http://pastebin.com/rCDuJqPw

[Mithion]

This seems to be related to a custom minecraft launch location. Would you happen to be launching MC using a batch file from a different location?

[eastwood6510]

Actually, I'm not. The path to forge is: "C:\Users\MyUser\AppData\Roaming.minecraft\versions\1.6.4-Forge9.11.0.883"

The path to the game directory is default as well: "C:\Users\MyUser\AppData\Roaming.minecraft"

; /

[Mithion]

Are you playing on single player or multiplayer?

[eastwood6510]

Single player

[angelnc1989]

I have the same crash, but I'm playing Multiplayer and using a custom Minecraft launch location.

[angelnc1989]

FYI: Still crashing in 1.0.1

[Mithion]

Can you post your ForgeModLoader-client-0.log from 1.0.1 after reproducing this issue?

[eastwood6510]

Well well! The update to 1.0.1 seems to have fixed it for me! I've tried 4 spells with the update and they've all worked.

Before in 1.0.0 that would have been 4 crashes and 4 unnamed, no icon spells.

I can upload my ForgeModLoader-client-0.log still if you wish, though the problem seems fixed for me.

[Mithion]

If you're not having the issue, then it's fine. If it happens again, please post the ForgeModLoader-Client-0.log files.

[Jhary]

EDIT: upgrading forge from 916 before to 935 seems to fix this issue. Or I am just lucky. Created two spells without a crash. But the exception on startup with the GUI stays.

---

I get the same crash situation on multiplayer with Ars Magica 1.0.1 and forge 916 when rightclicking a new spell for the first time:

http://pastebin.com/yJF71pdR

Oh and this exception is thrown on every client startup, it does not crash the client, but it seems to be gui related, possibly the reason for this?

[WARNING] [Minecraft-Client] Failed to load texture: minecraft:textures/guis/
Client> java.io.FileNotFoundException: minecraft:textures/guis/
Client> at net.minecraft.client.resources.FallbackResourceManager.func_110536_a(SourceFile:52)
Client> at net.minecraft.client.resources.SimpleReloadableResourceManager.func_110536_a(SourceFile:50)
Client> at net.minecraft.client.renderer.texture.SimpleTexture.func_110551_a(SourceFile:26)
Client> at net.minecraft.client.renderer.texture.TextureManager.func_110579_a(SourceFile:69)
Client> at net.minecraft.client.renderer.texture.TextureManager.func_110577_a(SourceFile:37)
Client> at net.minecraft.client.gui.FontRenderer.(SourceFile:53)
Client> at am2.guis.AMGuiHelper.(AMGuiHelper.java:19)
Client> at am2.guis.AMGuiHelper.(AMGuiHelper.java:24)
Client> at am2.proxy.tick.ClientTickHandler.renderTick_Start(ClientTickHandler.java:116)
Client> at am2.proxy.tick.ClientTickHandler.tickStart(ClientTickHandler.java:140)
Client> at cpw.mods.fml.common.SingleIntervalHandler.tickStart(SingleIntervalHandler.java:28)
Client> at cpw.mods.fml.common.FMLCommonHandler.tickStart(FMLCommonHandler.java:122)
Client> at cpw.mods.fml.common.FMLCommonHandler.onRenderTickStart(FMLCommonHandler.java:372)
Client> at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:944)
Client> at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:838)
Client> at net.minecraft.client.main.Main.main(SourceFile:101)
Client> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Client> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
Client> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
Client> at java.lang.reflect.Method.invoke(Unknown Source)
Client> at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
Client> at net.minecraft.launchwrapper.Launch.main(Launch.java:27)

[Mithion]

This issue should be fixed as of 1.0.2