Minecraft Forums

Quote from Mumfrey

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.

---- 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)

 

Quote from Mumfrey

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.

Quote from Mumfrey

It does install, it just can't delete the stuff in TEMP on some platforms for some reason, but the modpack should work fine. The "temporary resources" in question are how the installer creates the custom mcpatcher setup based on your selections - I basically copy the minecraft jar to the system temp dir, run mcpatcher on it with the options you choose in the installer, and then use that to build a small jar containing only the mcpatcher-patched classes which gets copied back to the real minecraft folder and injected at runtime.

I think that what happens is that sometimes when it does that "diff" to work out what changed and copy it, on some platforms (notably, on mac, but I don't have a mac so I can't actually test it) it doesn't seem to want to delete the temporary jars afterwards.

If you really want to get rid of the "temporary resources" in question, go into your system's temp folder and look for a folder called "mcpatchertemp_abcdef123" and delete it by hand.