The Meaning of Life, the Universe, and Everything.
Location:
Miami
Join Date:
4/27/2013
Posts:
57
Minecraft:
Knight_Warrior7
Member Details
If you're telling me that the error doesn't have an affect, it does, some mods aren't working properly, the game menu is default, light loader doesn't work, there are lots of effects to having this error, I've experienced these myself.
Rollback Post to RevisionRollBack
AnimeCraft1 is where we take Anime and Minecraft to a new level!!! For all Anime lovers <3
If you're telling me that the error doesn't have an affect, it does, some mods aren't working properly, the game menu is default, light loader doesn't work, there are lots of effects to having this error, I've experienced these myself.
Yes, I'm telling you the error doesn't have any effect, it does not affect anything, and nothing is affected by it. Whatsoever. End of story.
The problem is that because people see that warning, they just come and report that instead of thinking, "oh look this other error I'm seeing is likely the cause". Did you do as I suggested in the first place and read back a few posts? Did you try the IPv6 fix like I suggested?
The Meaning of Life, the Universe, and Everything.
Location:
Miami
Join Date:
4/27/2013
Posts:
57
Minecraft:
Knight_Warrior7
Member Details
Would you like me take print my screen to show you the affects of this error, I honestly don't want to argue, you're the expert, I'm telling you what I see, there are affects from this error, but there's nothing I can do but tell you, if you refuse to believe me then this conversation is done, but I greatly appreciate your help, thanks!
Rollback Post to RevisionRollBack
AnimeCraft1 is where we take Anime and Minecraft to a new level!!! For all Anime lovers <3
Would you like me take print my screen to show you the affects of this error, I honestly don't want to argue, you're the expert, I'm telling you what I see, there are affects from this error, but there's nothing I can do but tell you, if you refuse to believe me then this conversation is done, but I greatly appreciate your help, thanks!
Oh good grief. No, look, I'm not "refusing to believe you" and never have refused. This is what I've been trying to tell you all along:
Yes, I acknowledge that you see the error
The error is not related to the problems you're seeing, please let go of that idea.
The "effects" you're seeing are not related to it in the slightest.
Try the IPv6 fix, it's the most likely cause of the problem
If the IPv6 fix doesn't fix it, then there are other things to try, but please, please, please, please just accept my word that the temp file clean up is not related, has never been related, won't ever become related, and just plain isn't related to the issues you're having with the pack.
The Meaning of Life, the Universe, and Everything.
Location:
Miami
Join Date:
4/27/2013
Posts:
57
Minecraft:
Knight_Warrior7
Member Details
Ah I see, some misconceptions then, thank you for clearing it up. How would I try the IPV6, what are the steps, I looked through the previous post and I didn't find instructions on the IPV6 fix.
Rollback Post to RevisionRollBack
AnimeCraft1 is where we take Anime and Minecraft to a new level!!! For all Anime lovers <3
Ah I see, some misconceptions then, thank you for clearing it up. How would I try the IPV6, what are the steps, I looked through the previous post and I didn't find instructions on the IPV6 fix.
I've been trying to help you all along. The IPv6 fix is literally at the top of this page, like 2 posts above where you originally posted.
Just remove VoxelBoards and VoxelTextures. I initially thought it would be a simple fix but FML doesn't even provide a vanilla-compatible method to call to register TE's, so the only way around it is a complex process involving reflection. We're busy working on 1.7.10 updates as we speak and have developed that work-around for the 1.7.10 release in order to deal with running alongside FML.
We do our best to be as compatible as possible but when another mod or subsystem introduces a breaking change (in this case actually completely changing vanilla behaviour) it's not always straightforward to deal with. Since compatibility with other mods is provided for convenience only, we usually have to dedicate what little dev time is available to working on updates (honestly we can't win, we get accused of being "slow" to update all the time). We'd never release a modpack knowingly being incompatible with FML, but if that changes mid-cycle there's only so much that can be done. If it's a simple fix we can dedicate the time to fixing it but in this situation that's just not the case, so the fix gets pushed into the next release.
If I have time then once the 1.7.10 pack is ready I might look at back-porting the changes to 1.7.2, but they involve changes to LiteLoader as well which means I can't just push the update out via the modpack's automatic updater.
tl;dr This isn't a simple problem to fix but will be fixed in 1.7.10. If it's bugging you just remove VoxelBoards and VoxelTextures from the pack.
I'd use this as a reference but last time I did that it ended up being the wrong thing, though my mc does crash, and I do have voxel with forge.
I'd use this as a reference but last time I did that it ended up being the wrong thing, though my mc does crash, and I do have voxel with forge.
Then you need to post a crash report and preferably a developer log as well. Change the modpack profile to "keep the launcher open" then when it crashes copy the whole log to pastebin or something.
Normally I'd insist that you post this as a support ticket but this has been dragging on in the forum for so long I don't see any point in sending you over there since I'd be the one having to deal with it either way.
Anytime i download the mod only liteloader works none of the other mods do what could be the cause of this problem.(fyi. I have tried re-downloading but it stays the same.)
I hope you can help me
Hint, whenever you post in a thread about a problem, try reading the last few posts in case someone else is having the same problem as you.
The Meaning of Life, the Universe, and Everything.
Location:
Miami
Join Date:
4/27/2013
Posts:
57
Minecraft:
Knight_Warrior7
Member Details
---- Minecraft Crash Report ----
// This is a token for 1 free hug. Redeem at your nearest Mojangsta: [~~HUG~~]
Time: 7/17/14 11:47 PM
Description: Unexpected error
java.lang.NullPointerException: Unexpected error
at com.thevoxelbox.voxelboards.LiteModVoxelBoards.onTick(LiteModVoxelBoards.java:639)
at com.mumfrey.liteloader.core.Events.onTick(Events.java:709)
at com.mumfrey.liteloader.core.transformers.InjectedCallbackProxy.onTick(InjectedCallbackProxy.java:148)
at net.minecraft.client.Minecraft.func_71411_J(MinecraftOverlay.java:946)
at net.minecraft.client.Minecraft.func_99999_d(MinecraftOverlay.java:835)
at net.minecraft.client.main.Main.main(SourceFile:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at java.lang.reflect.Method.invoke(Method.java:597)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 1.7.2
Operating System: Mac OS X (x86_64) version 10.9.3
Java Version: 1.6.0_65, Apple Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Apple Inc.
Memory: 25694928 bytes (24 MB) / 129957888 bytes (123 MB) up to 129957888 bytes (123 MB)
JVM Flags: 0 total;
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML: MCP v9.03 FML v7.2.217.1147 Minecraft Forge 10.12.2.1147 3 mods loaded, 3 mods active
mcp{9.03} [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
FML{7.2.217.1147} [Forge Mod Loader] (forge-1.7.2-10.12.2.1147.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
Forge{10.12.2.1147} [Minecraft Forge] (forge-1.7.2-10.12.2.1147.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
Launched Version: 1.7.2
LWJGL: 2.9.1
OpenGL: NVIDIA GeForce 320M OpenGL Engine GL version 2.1 NVIDIA-8.24.13 310.90.9.05f01, NVIDIA Corporation
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
Anisotropic Filtering: Off (1)
Well here it is
Rollback Post to RevisionRollBack
AnimeCraft1 is where we take Anime and Minecraft to a new level!!! For all Anime lovers <3
Again this could have been solved by just reading the thread, and you even quoted the appropriate post above, VoxelBoards is not currently compatible with Forge because Forge introduced a breaking change to the tile entity registry. If you want to use Forge you must not install VoxelBoards.
Again this could have been solved by just reading the thread, and you even quoted the appropriate post above, VoxelBoards is not currently compatible with Forge because Forge introduced a breaking change to the tile entity registry. If you want to use Forge you must not install VoxelBoards.
So can I just delete voxelboards or do I reinstall VMP without Voxelboards?
Rollback Post to RevisionRollBack
AnimeCraft1 is where we take Anime and Minecraft to a new level!!! For all Anime lovers <3
Yes, I'm telling you the error doesn't have any effect, it does not affect anything, and nothing is affected by it. Whatsoever. End of story.
The problem is that because people see that warning, they just come and report that instead of thinking, "oh look this other error I'm seeing is likely the cause". Did you do as I suggested in the first place and read back a few posts? Did you try the IPv6 fix like I suggested?
Oh good grief. No, look, I'm not "refusing to believe you" and never have refused. This is what I've been trying to tell you all along:
Thanks
I've been trying to help you all along. The IPv6 fix is literally at the top of this page, like 2 posts above where you originally posted.
I'd use this as a reference but last time I did that it ended up being the wrong thing, though my mc does crash, and I do have voxel with forge.
Then you need to post a crash report and preferably a developer log as well. Change the modpack profile to "keep the launcher open" then when it crashes copy the whole log to pastebin or something.
Normally I'd insist that you post this as a support ticket but this has been dragging on in the forum for so long I don't see any point in sending you over there since I'd be the one having to deal with it either way.
Hint, whenever you post in a thread about a problem, try reading the last few posts in case someone else is having the same problem as you.
Well here it is
Again this could have been solved by just reading the thread, and you even quoted the appropriate post above, VoxelBoards is not currently compatible with Forge because Forge introduced a breaking change to the tile entity registry. If you want to use Forge you must not install VoxelBoards.
Since the modpack for 1.7.10 isn't released yet, no.
So can I just delete voxelboards or do I reinstall VMP without Voxelboards?