Minecraft Forums

Ok so I recently installed this mod (or rather re-installed) and I noticed a mod conflict. I'm not sure exactly where it is coming from but OpenEye seems to think it is either in LiteLoader or in Mod Macros and I only need to disable the latter to clear it up.

OpenEye Report: http://openeye.openmods.info/crashes/1249626db5c99eef1273a101af9929f1

When Mod Macros is installed the game crashes when I hit the O key on the Options screen. It appears to be a conflict with iChunUtils which adds the menu to the Options screen. I attempted to disable Mod Dismemberment and the issue persists.

The good news is it just prevents me from getting to that screen. However I would like to hopefully see this cleared up.

If you need me to do anything just let me know. I'll try to check back on this thread and forum for troubleshooting steps.

I'm running Minecraft 1.7.10 here but I noticed Optifine is giving the update available alert. I'm not planning to update to 1.8.x yet since some of the plugins are not updated yet.

No problem.

For some reason 1.7.10 version of Gammabright is showing that the 3.2.2 release version is available even though that one is only for 1.8.

For some reason the Waila version isn't working for me. It shows up in Waila as a module but it doesn't seem to do anything else beyond that. All the information that seems to be present is what Waila provides directly already. Help?

P.S. - I get an option that says "Show Body". Not sure what that does at all.

Quote from UniblueMedia

• Make sure you have installed Sonic Ether's Unbelievable Shaders.
• Make sure you place the R3D.CRAFT shader resourcepack above the original R3D.CRAFT resourpack.
• Should work with newer versions of SEUS, but not the old ones.

Shaders: Check (SEUS 10.1)
Resource Packs: Check (using 256x ones)

Any before/after screenshots so I have something to compare?

Is there bump mapping setup for the shaders? I'm having trouble determining if the shaders addon pack is doing anything.

Quote from SpaghettiNinja

I found out that it happens every time I change my Resource pack, It just crashes.

Your pack has connected textures and it is broke in Optifine. If you are not running A9 already though I would give it a shot. I reported it earlier.

Optifine is choking on Connected Texture files in DokuCraft 1.7. Check Doku Light (not the Mega or Mini versions although they may have the error as well). Tested using "installed" Optifine (no other mods present)

http://www.minecraft...saga-continues/

Same texture pack works with MCPatcher

Log:

---- Minecraft Crash Report ----
// Why is it breaking 

Time: 1/5/14 3:12 AM
Description: Initializing game

java.lang.IllegalArgumentException: Name cannot contain slashes!
at bpr.a(TextureMap.java:544)
at ConnectedProperties.registerIcons(ConnectedProperties.java:883)
at ConnectedProperties.updateIcons(ConnectedProperties.java:847)
at ConnectedTextures.updateIcons(ConnectedTextures.java:926)
at bpr.g(TextureMap.java:422)
at bpr.<init>(TextureMap.java:85)
at azd.Z(SourceFile:452)
at azd.e(SourceFile:689)
at net.minecraft.client.main.Main.main(SourceFile:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
at bpr.a(TextureMap.java:544)
at ConnectedProperties.registerIcons(ConnectedProperties.java:883)
at ConnectedProperties.updateIcons(ConnectedProperties.java:847)
at ConnectedTextures.updateIcons(ConnectedTextures.java:926)
at bpr.g(TextureMap.java:422)
at bpr.<init>(TextureMap.java:85)
at azd.Z(SourceFile:452)

-- Initialization --
Details:
Stacktrace:
at azd.e(SourceFile:689)
at net.minecraft.client.main.Main.main(SourceFile:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)

-- System Details --
Details:
Minecraft Version: 1.7.2
Operating System: Windows 8 (amd64) version 6.2
Java Version: 1.7.0_45, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 382075152 bytes (364 MB) / 513802240 bytes (490 MB) up to 954728448 bytes (910 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.7.2-OptiFine_HD_U_A7
LWJGL: 2.9.0
OpenGL: AMD Radeon HD 7970M GL version 4.3.12614 Compatibility Profile Context 13.250.18.0, ATI Technologies Inc.
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Resource Packs: [[1.7]Dokucraft_TSC_Light.zip]
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
Anisotropic Filtering: Off (1)

Couldn't they of left 32x32 as a valid size for the image for all those server operators that already did a smaller icon?

The author posted an updated version here: http://forum.minecraftuser.jp/viewtopic.php?f=13&t=153

Already mentioned a few times. It's in japanese (the op native language) however I think you should be able to find the download link easy enough.

Thanks Mumfrey. That took care of the issue for me.

Quote from munomario777

Anyone have a non-installer download? I intend to use this with Magic Launcher

When you run the installer there is an option to extract it instead of installing. You should be able to use the extracted version with Magic Launcher if you want.

Quote from hexk

Are you 100% sure about that? Granted, this thread is the only one that comes up when you google the bug, however, I experience the problem with liteloader removed. So the problem may in fact be FML 898 , that you've only installed recently to get it to work with liteloader, making a false correlation on the cause of the problem.

Remove Liteloaded from your .json, put the broken mods in your mod/ folder, try repeat the problem.

Ok. I retested but it still points at LiteLoader. Removing the (afaik) 2 entries related to LiteLoader results in the same crash however a clean Forge specific profile loads fine. I'm gonna dig into the json a bit.

Looks like issue is in the json only. I went and experimented a bit (because just removing LiteLoader and having the issue doesn't make sense). I stripped the LiteLoader json and duplicated the library list from the Forge copy to LiteLoader. I left the arguments alone and left the library reference for Liteloader present. After that it loads fine.

So... we got 2 possibilities.
1) Load order matters
2) There is a version discrepancy somewhere.

Note: I thought about the LaunchWrapper bit. All by itself isn't enough although LiteLoader is loading with 1.7 and Forge is loading with 1.8.

Update (during edit): Finished digging. Version numbers up and down except for LaunchWrapper is the same. In the end I found though that LaunchWrapper plus load order is what the issue is.

These must be true:
1) For Forge #898 LaunchWrapper must be 1.8 or it won't work.
2) LiteLoader but be listed BEFORE Forge. It can't load after or it will fail with jar mods.

Don't ask why but it was how I got it fixed.

EDIT: This is a ticket I opened up previously.

https://www.assembla.com/spaces/liteloader/tickets/6#/activity/ticket:

In it I have attached 2 files. If you know how to use patch (eg on linux) then you can just patch the LiteLoader1.6.4.json file using the diff file. Or you can replace it fully using the json attached as well. Either way works. In the meantime it's up to the op work on making a final fix.

Quote from megagiy2

Are you sure?

I know I'm sure. I checked it myself and it works fine.