The Meaning of Life, the Universe, and Everything.
Location:
Miami
Join Date:
4/27/2013
Posts:
57
Minecraft:
Knight_Warrior7
Member Details
Ok, I deleted Voxelboard, but now when I open the game, it's now giving me this error message saying that I've either run out of memory or there is a bug that is causing this issue...
Rollback Post to RevisionRollBack
AnimeCraft1 is where we take Anime and Minecraft to a new level!!! For all Anime lovers <3
What is VoxelVisualizer used for? Also, was VoxelTime originally part of VoxelWorld/VoxelVision?
VoxelVisualiser is a client-side region visualiser similar to WorldEditCUI but with an open API for bukkit plugins to display regions on the client. It is not currently used.
VoxelTime was originally built in to VoxelTextures, and from 1.7.10 will be included with VoxelVision instead of stand-alone.
VoxelVisualiser is a client-side region visualiser similar to WorldEditCUI but with an open API for bukkit plugins to display regions on the client. It is not currently used.
Has VoxelVisualizer ever been considered as a replacement or option for displaying WECUI regions? If I recall, the visuals were quite pleasant and a bit more polished looking than the current selection visuals.
Has VoxelVisualizer ever been considered as a replacement or option for displaying WECUI regions? If I recall, the visuals were quite pleasant and a bit more polished looking than the current selection visuals.
Yes, given that I'm the current maintainer of WECUI, I plan to merge the two mods eventually. WECUI's rendering needs a complete rewrite anyway.
java.lang.NullPointerException: Unexpected error
at com.voxelmodpack.voxelboards.LiteModVoxelBoards.onTick(LiteModVoxelBoards.java:735)
at com.mumfrey.liteloader.client.ClientEvents.onTick(ClientEvents.java:664)
at com.mumfrey.liteloader.client.CallbackProxyClient.onTick(CallbackProxyClient.java:146)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:991)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:887)
at net.minecraft.client.main.Main.main(SourceFile:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
at net.minecraft.launchwrapper.Launch.mai
Still has that conflict with Minecraft:
B#439] [13:21:55] [Client thread/INFO]: Calling late init for mod VoxelBoards
[B#439] java.lang.IllegalArgumentException: The name minecraft:standing_sign has been registered twice, for net.minecraft.block.BlockSign@34cf1067 and com.voxelmodpack.voxelboards.entity.VoxelBoardsBlockSign@49f91f50.
[B#439] at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:355)
[B#439] at cpw.mods.fml.common.registry.GameData.registerBlock(GameData.java:835)
[B#439] at cpw.mods.fml.common.registry.GameData.register(GameData.java:740)
[B#439] at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.func_148756_a(FMLControlledNamespacedRegistry.java:114)
[B#439] at com.mumfrey.liteloader.util.ModUtilities.addBlock(ModUtilities.java:137)
[B#439] at com.voxelmodpack.voxelboards.LiteModVoxelBoards.onInitCompleted(LiteModVoxelBoards.java:193)
[B#439] at com.mumfrey.liteloader.client.ClientEvents.onStartupComplete(ClientEvents.java:479)
[B#439] at com.mumfrey
.liteloader.client.CallbackProxyClient.onStartupComplete(CallbackProxyClient.java:129)
[B#439] at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:573)
[B#439] at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:867)
[B#439] at net.minecraft.client.main.Main.main(SourceFile:148)
[B#439] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[B#439] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[B#439] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[B#439] at java.lang.reflect.Method.invoke(Method.java:606)
[B#439] at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
[B#439] at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
java.lang.NullPointerException: Unexpected error
at com.voxelmodpack.voxelboards.LiteModVoxelBoards.onTick(LiteModVoxelBoards.java:735)
at com.mumfrey.liteloader.client.ClientEvents.onTick(ClientEvents.java:664)
at com.mumfrey.liteloader.client.CallbackProxyClient.onTick(CallbackProxyClient.java:146)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:991)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:887)
at net.minecraft.client.main.Main.main(SourceFile:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
at net.minecraft.launchwrapper.Launch.mai
Still has that conflict with Minecraft:
B#439] [13:21:55] [Client thread/INFO]: Calling late init for mod VoxelBoards
[B#439] java.lang.IllegalArgumentException: The name minecraft:standing_sign has been registered twice, for net.minecraft.block.BlockSign@34cf1067 and com.voxelmodpack.voxelboards.entity.VoxelBoardsBlockSign@49f91f50.
[B#439] at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:355)
[B#439] at cpw.mods.fml.common.registry.GameData.registerBlock(GameData.java:835)
[B#439] at cpw.mods.fml.common.registry.GameData.register(GameData.java:740)
[B#439] at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.func_148756_a(FMLControlledNamespacedRegistry.java:114)
[B#439] at com.mumfrey.liteloader.util.ModUtilities.addBlock(ModUtilities.java:137)
[B#439] at com.voxelmodpack.voxelboards.LiteModVoxelBoards.onInitCompleted(LiteModVoxelBoards.java:193)
[B#439] at com.mumfrey.liteloader.client.ClientEvents.onStartupComplete(ClientEvents.java:479)
[B#439] at com.mumfrey
.liteloader.client.CallbackProxyClient.onStartupComplete(CallbackProxyClient.java:129)
[B#439] at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:573)
[B#439] at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:867)
[B#439] at net.minecraft.client.main.Main.main(SourceFile:148)
[B#439] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[B#439] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[B#439] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[B#439] at java.lang.reflect.Method.invoke(Method.java:606)
[B#439] at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
[B#439] at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
Oh, believe me.. Your mod is THE reason I swapped over to 1.7.10.. Started out butt spankin new. Saw you guys released 1.7.10 and I used your installer on my minecraft folder, coopied the mods to my technic folder and set it up as per your manual setup for liteloader. NOT the first time It IS running 1.7.10 and it is runing lazy laptrap as well...
Ok then I'm not sure what broke, the fix is actually in liteloader not in the mod, and it's far from a straightforward fix. I'll investigate.
EDIT: Okay the best I can do for the moment is make it not crash. It's going to be pretty complicated to get VoxelBoards to play nicely with Forge so I'm going to need a lot more time to get a fix out. I'll push an update which will at least alleviate the crash.
Thank you Mumfrey. My apology on posting on the voxelmodpack support site and here. Used to posting on the forums for us users to keep up with current issues and help each other out. .. While your ticketing helps you keep track of issues seperately and orderly on a dedicated database... Didn't think it bothered anyone.
Does the HDSkin manager have any other methods of bringing up the menu? Also, seems to be calling out an error minecraft api after I choose my old HD skin.. or ANY skin... I have to quit to even get out of the HDSkin Manager.. No Errors on the log. Technic launcher using Forge Mod Loader 7.10.25.1199 Minecraft Forge 10.13.0.1199
Does the HDSkin manager have any other methods of bringing up the menu?
In VoxelMenu click the menu option. If VoxelMenu is not active then press F1 at the main menu. Those are the only ways of getting to the HD Skin manager.
Also, seems to be calling out an error minecraft api after I choose my old HD skin.. or ANY skin... I have to quit to even get out of the HDSkin Manager.. No Errors on the log. Technic launcher using Forge Mod Loader 7.10.25.1199 Minecraft Forge 10.13.0.1199
Argh... Thanks Mumfrey.. sorry to be a pain. I'm going to just chalk this up to forge again. .. no error about a api's or anything else or log errors that I can find. .. it let's you select a skin but after hitting the apply button nothing happens. .. you can close the screen. If you try and choose the skin again OR if you close it and immediately open the HD skin manager up again and go to the skin selection button; none of the buttons will work. You can't close it, cancel it. .. you have to quit entirely.
**EDIT
This is after the update to the latest by the way..
Argh... Thanks Mumfrey.. sorry to be a pain. I'm going to just chalk this up to forge again. .. no error about a api's or anything else or log errors that I can find. .. it let's you select a skin but after hitting the apply button nothing happens. .. you can close the screen. If you try and choose the skin again OR if you close it and immediately open the HD skin manager up again and go to the skin selection button; none of the buttons will work. You can't close it, cancel it. .. you have to quit entirely.
**EDIT
This is after the update to the latest by the way..
VoxelVisualiser is a client-side region visualiser similar to WorldEditCUI but with an open API for bukkit plugins to display regions on the client. It is not currently used.
VoxelTime was originally built in to VoxelTextures, and from 1.7.10 will be included with VoxelVision instead of stand-alone.
Has VoxelVisualizer ever been considered as a replacement or option for displaying WECUI regions? If I recall, the visuals were quite pleasant and a bit more polished looking than the current selection visuals.
Yes, given that I'm the current maintainer of WECUI, I plan to merge the two mods eventually. WECUI's rendering needs a complete rewrite anyway.
That's good to hear. I've been looking forward to seeing it implemented.
// You should try our sister game, Minceraft!
Time: 8/13/14 1:22 PM
Description: Unexpected error
java.lang.NullPointerException: Unexpected error
at com.voxelmodpack.voxelboards.LiteModVoxelBoards.onTick(LiteModVoxelBoards.java:735)
at com.mumfrey.liteloader.client.ClientEvents.onTick(ClientEvents.java:664)
at com.mumfrey.liteloader.client.CallbackProxyClient.onTick(CallbackProxyClient.java:146)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:991)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:887)
at net.minecraft.client.main.Main.main(SourceFile:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
at net.minecraft.launchwrapper.Launch.mai
B#439] [13:21:55] [Client thread/INFO]: Calling late init for mod VoxelBoards
[B#439] java.lang.IllegalArgumentException: The name minecraft:standing_sign has been registered twice, for net.minecraft.block.BlockSign@34cf1067 and com.voxelmodpack.voxelboards.entity.VoxelBoardsBlockSign@49f91f50.
[B#439] at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:355)
[B#439] at cpw.mods.fml.common.registry.GameData.registerBlock(GameData.java:835)
[B#439] at cpw.mods.fml.common.registry.GameData.register(GameData.java:740)
[B#439] at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.func_148756_a(FMLControlledNamespacedRegistry.java:114)
[B#439] at com.mumfrey.liteloader.util.ModUtilities.addBlock(ModUtilities.java:137)
[B#439] at com.voxelmodpack.voxelboards.LiteModVoxelBoards.onInitCompleted(LiteModVoxelBoards.java:193)
[B#439] at com.mumfrey.liteloader.client.ClientEvents.onStartupComplete(ClientEvents.java:479)
[B#439] at com.mumfrey
.liteloader.client.CallbackProxyClient.onStartupComplete(CallbackProxyClient.java:129)
[B#439] at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:573)
[B#439] at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:867)
[B#439] at net.minecraft.client.main.Main.main(SourceFile:148)
[B#439] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[B#439] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[B#439] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[B#439] at java.lang.reflect.Method.invoke(Method.java:606)
[B#439] at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
[B#439] at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
If I remove it, it all loads up fine.
Update to 1.7.10, this was fixed.
and
EDIT: Okay the best I can do for the moment is make it not crash. It's going to be pretty complicated to get VoxelBoards to play nicely with Forge so I'm going to need a lot more time to get a fix out. I'll push an update which will at least alleviate the crash.
In VoxelMenu click the menu option. If VoxelMenu is not active then press F1 at the main menu. Those are the only ways of getting to the HD Skin manager.
Update liteloader.
**EDIT
This is after the update to the latest by the way..
Is there a log for the litemods in particular?
This should be fixed now.