java.lang.NullPointerException: Rendering Block Entity
at net.malisis.doors.tileentity.DoorTileEntity.isHingeLeft(DoorTileEntity.java:152)
at net.malisis.doors.renderer.DoorRenderer.setTileEntity(DoorRenderer.java:193)
at net.malisis.doors.renderer.CustomDoorRenderer.setTileEntity(CustomDoorRenderer.java:154)
at net.malisis.doors.renderer.DoorRenderer.render(DoorRenderer.java:153)
at net.malisis.core.renderer.MalisisRenderer.func_180535_a(MalisisRenderer.java:406)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_178469_a(TileEntityRendererDispatcher.java:147)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_180546_a(TileEntityRendererDispatcher.java:125)
at net.minecraft.client.renderer.RenderGlobal.func_180446_a(RenderGlobal.java:989)
at net.minecraft.client.renderer.EntityRenderer.func_175068_a(EntityRenderer.java:1727)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1556)
at net.minecraft.client.renderer.EntityRenderer.func_181560_a(EntityRenderer.java:1335)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1076)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:371)
at net.minecraft.client.main.Main.main(SourceFile:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
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:
---------------------------------------------------------------------------------------
-- Head --
Thread: Client thread
Stacktrace:
at net.malisis.doors.tileentity.DoorTileEntity.isHingeLeft(DoorTileEntity.java:152)
at net.malisis.doors.renderer.DoorRenderer.setTileEntity(DoorRenderer.java:193)
at net.malisis.doors.renderer.CustomDoorRenderer.setTileEntity(CustomDoorRenderer.java:154)
at net.malisis.doors.renderer.DoorRenderer.render(DoorRenderer.java:153)
at net.malisis.core.renderer.MalisisRenderer.func_180535_a(MalisisRenderer.java:406)
-- Block Entity Details --
Details:
Name: customDoorTileEntity // net.malisis.doors.tileentity.CustomDoorTileEntity
Block type: ID #769 (tile.customDoor // net.malisis.doors.block.CustomDoor)
Block data value: 1 / 0x1 / 0b0001
Block location: World: (2127,70,2178), Chunk: (at 15,4,2 in 132,136; contains blocks 2112,0,2176 to 2127,255,2191), Region: (4,4; contains chunks 128,128 to 159,159, blocks 2048,0,2048 to 2559,255,2559)
Actual block type: ID #699 (tile.blockLightNode // crazypants.enderio.machine.light.BlockLightNode)
Actual block data value: 1 / 0x1 / 0b0001
Stacktrace:
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_178469_a(TileEntityRendererDispatcher.java:147)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_180546_a(TileEntityRendererDispatcher.java:125)
at net.minecraft.client.renderer.RenderGlobal.func_180446_a(RenderGlobal.java:989)
at net.minecraft.client.renderer.EntityRenderer.func_175068_a(EntityRenderer.java:1727)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1556)
-- Affected level --
Details:
Level name: MpServer
All players: 1 total; [EntityPlayerSP['BlockBust2016'/140, l='MpServer', x=2127.26, y=70.00, z=2179.81]]
Chunk stats: MultiplayerChunkCache: 441, 441
Level seed: 0
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: World: (-56,64,-161), Chunk: (at 8,4,15 in -4,-11; contains blocks -64,0,-176 to -49,255,-161), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 20956317 game time, 26287771 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
im lacking textures from vanilla doors (basemetals fault) im also getting 2 doors every time i break one no errors/crashes minecraft 1.10.2
Upgrade to the latest version of Malisis Doors for 1.10.2. Fixes the 2 doors glitch.
Rollback Post to RevisionRollBack
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out https://minecraftnoobtest.com/test.php
No, I think it's the latest version that reintroduced the bug.
Dang, that sucks. Hopefully a new fix can be implemented.
Rollback Post to RevisionRollBack
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out https://minecraftnoobtest.com/test.php
Would you accept a PR on your 1.7.10 (master) branch for a new "Team Sensor"? If not, or until you do accept it either way, do I have permission to use it in a Modpack until that time (as long as I clearly mark it as an Unofficial in the filename and version string)?
It would be functionally identical to the PlayerSensor, with the following changes:
1) When placed by a player, the Player name (or UUID is probably best) is stored in a non-ticking TileEntity;
2) When the block update is triggered, it instead checks for EntityLivingBase followed by a Scoreboard#getPlayersTeam() on any found, instead of just checking for an EntityPlayer. I thought about caching the team in the tile entity but that's prone to errors.
The main reason for this change is not necessarily for PvP, though it could be used for that - but so the sensors work for non-player yet still-team-assigned entities - for example the NPC's from Ancient Warfare.
Would you accept a PR on your 1.7.10 (master) branch for a new "Team Sensor"? If not, or until you do accept it either way, do I have permission to use it in a Modpack until that time (as long as I clearly mark it as an Unofficial in the filename and version string)?
It would be functionally identical to the PlayerSensor, with the following changes:
1) When placed by a player, the Player name (or UUID is probably best) is stored in a non-ticking TileEntity;
2) When the block update is triggered, it instead checks for EntityLivingBase followed by a Scoreboard#getPlayersTeam() on any found, instead of just checking for an EntityPlayer. I thought about caching the team in the tile entity but that's prone to errors.
The main reason for this change is not necessarily for PvP, though it could be used for that - but so the sensors work for non-player yet still-team-assigned entities - for example the NPC's from Ancient Warfare.
Thanks!
If I might consider pulling that kind of PR for 1.9.4/1.10.2, the development for 1.7.10 has ended a long time ago. So I would strongly suggest that you update to a version that is not 2 years old. There is no good reason to stay behind.
If you really can't, or don't want, you seem you have enough knowledge to make the block into a separate mod, without needing to modify and rebuild MalisisDoors. The code is MIT so you can copy the code for yourself if you want.
I have the "break one door get two doors"-bug as mentioned some posts above. I'm using Malisiscore 4.1.1 and Malisisdoors 5.0.4.
The doors I break also get renamed to whatever their name is, plus "rotating" below. That makes them non-stackable with newly crafted doors.
And a question/request, is is possibel to get the dobble opening door function to work with non-vanilla doors added by other mods?(Biomes O Plenty etc)?
If I might consider pulling that kind of PR for 1.9.4/1.10.2, the development for 1.7.10 has ended a long time ago. So I would strongly suggest that you update to a version that is not 2 years old. There is no good reason to stay behind.
If you really can't, or don't want, you seem you have enough knowledge to make the block into a separate mod, without needing to modify and rebuild MalisisDoors. The code is MIT so you can copy the code for yourself if you want.
If I might consider pulling that kind of PR for 1.9.4/1.10.2, the development for 1.7.10 has ended a long time ago. So I would strongly suggest that you update to a version that is not 2 years old. There is no good reason to stay behind.
If you really can't, or don't want, you seem you have enough knowledge to make the block into a separate mod, without needing to modify and rebuild MalisisDoors. The code is MIT so you can copy the code for yourself if you want.
So someone else can maintain the 1.7.10 branch, so you don't have to?
Rollback Post to RevisionRollBack
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out https://minecraftnoobtest.com/test.php
When I try to use the block mixer the block that comes out is really buggy. I saw someone playing with this mod and when they mixed blocks it looked like each side of the block was fading into the other, when I try to do his there is a clear half-and-half with the 2 blocks used. Also, when I move around the block it kind of changes??? cant really describe it but one side of the block disappears and the other side shows through.
When I try to use the block mixer the block that comes out is really buggy. I saw someone playing with this mod and when they mixed blocks it looked like each side of the block was fading into the other, when I try to do his there is a clear half-and-half with the 2 blocks used. Also, when I move around the block it kind of changes??? cant really describe it but one side of the block disappears and the other side shows through.
Try unchecking the simple rendering box in the block mixer
WHY I CANNOT LOAD MALISIS' CORE AND MALISIS' DOORS VITHOUT JAVA 8 BUT WITH JAVA 8 IT CRASHES. LOGS
First off, don't spam capital letters, it's against the forum rules. Secondly, you need to open your launcher, click the edit profile button next to your profile (make sure you selected the forge profile), then go to the java target text box. In that box, replace the path you see with the one leading to your Java 8 installation (if on Windows x64: C:/Program Files/Java/jre1.8.0_xxx/bin/javaw.exe, if on x86 C:/Program Files (x86)/Java/jre1.8.0_xxx). Then click save, run Minecraft and have fun.
Rollback Post to RevisionRollBack
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out https://minecraftnoobtest.com/test.php
When I try to use the block mixer the block that comes out is really buggy. I saw someone playing with this mod and when they mixed blocks it looked like each side of the block was fading into the other, when I try to do his there is a clear half-and-half with the 2 blocks used. Also, when I move around the block it kind of changes??? cant really describe it but one side of the block disappears and the other side shows through.
WHY I CANNOT LOAD MALISIS' CORE AND MALISIS' DOORS VITHOUT JAVA 8 BUT WITH JAVA 8 IT CRASHES. LOGS
Full caps doesn't really incentivsize us to help you. When you install Java 8, the crash has nothing to do with MalisisCore/Doors because you didn't even use it.
But I bet that shitty X-ray mod you're using is the reason for the crash.
Hello there, just dropping by to say that the "Double sliding right" option in the Door Factory makes the door slide 2 blocks to the side instead of one
Kind of problematic if you set the door to only open by hand...
Got the following while breaking a custom door.
---- Minecraft Crash Report ----
WARNING: coremods are present:
EnderCorePlugin (EnderCore-1.10.2-0.4.1.53-beta.jar)
LoadingPluginBuildingBricks (BuildingBricks-1.10.2-2.0.12.jar)
MalisisCorePlugin (malisiscore-1.9.4-4.1.1.jar)
Contact their authors BEFORE contacting forge
// Shall we play a game?
Time: 9/5/16 7:49 PM
XRay version: 38
Description: Rendering Block Entity
java.lang.NullPointerException: Rendering Block Entity
at net.malisis.doors.tileentity.DoorTileEntity.isHingeLeft(DoorTileEntity.java:152)
at net.malisis.doors.renderer.DoorRenderer.setTileEntity(DoorRenderer.java:193)
at net.malisis.doors.renderer.CustomDoorRenderer.setTileEntity(CustomDoorRenderer.java:154)
at net.malisis.doors.renderer.DoorRenderer.render(DoorRenderer.java:153)
at net.malisis.core.renderer.MalisisRenderer.func_180535_a(MalisisRenderer.java:406)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_178469_a(TileEntityRendererDispatcher.java:147)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_180546_a(TileEntityRendererDispatcher.java:125)
at net.minecraft.client.renderer.RenderGlobal.func_180446_a(RenderGlobal.java:989)
at net.minecraft.client.renderer.EntityRenderer.func_175068_a(EntityRenderer.java:1727)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1556)
at net.minecraft.client.renderer.EntityRenderer.func_181560_a(EntityRenderer.java:1335)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1076)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:371)
at net.minecraft.client.main.Main.main(SourceFile:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
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:
---------------------------------------------------------------------------------------
-- Head --
Thread: Client thread
Stacktrace:
at net.malisis.doors.tileentity.DoorTileEntity.isHingeLeft(DoorTileEntity.java:152)
at net.malisis.doors.renderer.DoorRenderer.setTileEntity(DoorRenderer.java:193)
at net.malisis.doors.renderer.CustomDoorRenderer.setTileEntity(CustomDoorRenderer.java:154)
at net.malisis.doors.renderer.DoorRenderer.render(DoorRenderer.java:153)
at net.malisis.core.renderer.MalisisRenderer.func_180535_a(MalisisRenderer.java:406)
-- Block Entity Details --
Details:
Name: customDoorTileEntity // net.malisis.doors.tileentity.CustomDoorTileEntity
Block type: ID #769 (tile.customDoor // net.malisis.doors.block.CustomDoor)
Block data value: 1 / 0x1 / 0b0001
Block location: World: (2127,70,2178), Chunk: (at 15,4,2 in 132,136; contains blocks 2112,0,2176 to 2127,255,2191), Region: (4,4; contains chunks 128,128 to 159,159, blocks 2048,0,2048 to 2559,255,2559)
Actual block type: ID #699 (tile.blockLightNode // crazypants.enderio.machine.light.BlockLightNode)
Actual block data value: 1 / 0x1 / 0b0001
Stacktrace:
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_178469_a(TileEntityRendererDispatcher.java:147)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_180546_a(TileEntityRendererDispatcher.java:125)
at net.minecraft.client.renderer.RenderGlobal.func_180446_a(RenderGlobal.java:989)
at net.minecraft.client.renderer.EntityRenderer.func_175068_a(EntityRenderer.java:1727)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1556)
-- Affected level --
Details:
Level name: MpServer
All players: 1 total; [EntityPlayerSP['BlockBust2016'/140, l='MpServer', x=2127.26, y=70.00, z=2179.81]]
Chunk stats: MultiplayerChunkCache: 441, 441
Level seed: 0
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: World: (-56,64,-161), Chunk: (at 8,4,15 in -4,-11; contains blocks -64,0,-176 to -49,255,-161), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 20956317 game time, 26287771 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
b
i've tried on D6, nothing changes :c
well, i don't really care about this, since it's not basic mod function
im lacking textures from vanilla doors (basemetals fault) im also getting 2 doors every time i break one no errors/crashes minecraft 1.10.2
Upgrade to the latest version of Malisis Doors for 1.10.2. Fixes the 2 doors glitch.
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out
https://minecraftnoobtest.com/test.php
Don't click this link, HE is haunting it...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNo, I think it's the latest version that reintroduced the bug.
Mods for Minecraft :
MalisisDoors
MalisisBlocks
MalisisAdvert
MalisisSwitches
Do It Yourself Decorative Blocks
Dang, that sucks. Hopefully a new fix can be implemented.
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out
https://minecraftnoobtest.com/test.php
Don't click this link, HE is haunting it...
Hi Ordinastie,
Would you accept a PR on your 1.7.10 (master) branch for a new "Team Sensor"? If not, or until you do accept it either way, do I have permission to use it in a Modpack until that time (as long as I clearly mark it as an Unofficial in the filename and version string)?
It would be functionally identical to the PlayerSensor, with the following changes:
1) When placed by a player, the Player name (or UUID is probably best) is stored in a non-ticking TileEntity;
2) When the block update is triggered, it instead checks for EntityLivingBase followed by a Scoreboard#getPlayersTeam() on any found, instead of just checking for an EntityPlayer. I thought about caching the team in the tile entity but that's prone to errors.
The main reason for this change is not necessarily for PvP, though it could be used for that - but so the sensors work for non-player yet still-team-assigned entities - for example the NPC's from Ancient Warfare.
Thanks!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIf I might consider pulling that kind of PR for 1.9.4/1.10.2, the development for 1.7.10 has ended a long time ago. So I would strongly suggest that you update to a version that is not 2 years old. There is no good reason to stay behind.
If you really can't, or don't want, you seem you have enough knowledge to make the block into a separate mod, without needing to modify and rebuild MalisisDoors. The code is MIT so you can copy the code for yourself if you want.
Mods for Minecraft :
MalisisDoors
MalisisBlocks
MalisisAdvert
MalisisSwitches
Do It Yourself Decorative Blocks
Hi,
Really great mod!
I have the "break one door get two doors"-bug as mentioned some posts above. I'm using Malisiscore 4.1.1 and Malisisdoors 5.0.4.
The doors I break also get renamed to whatever their name is, plus "rotating" below. That makes them non-stackable with newly crafted doors.
And a question/request, is is possibel to get the dobble opening door function to work with non-vanilla doors added by other mods?(Biomes O Plenty etc)?
-Morten
That's very fair enough. Cheers!
I love this mod!
So someone else can maintain the 1.7.10 branch, so you don't have to?
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out
https://minecraftnoobtest.com/test.php
Don't click this link, HE is haunting it...
My Game is not crashing . but door textures are missing when installed MalisisDoors MalisisCore and BaseMetals(
known issue.
But not fixed(
When I try to use the block mixer the block that comes out is really buggy. I saw someone playing with this mod and when they mixed blocks it looked like each side of the block was fading into the other, when I try to do his there is a clear half-and-half with the 2 blocks used. Also, when I move around the block it kind of changes??? cant really describe it but one side of the block disappears and the other side shows through.
Try unchecking the simple rendering box in the block mixer
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out
https://minecraftnoobtest.com/test.php
Don't click this link, HE is haunting it...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe fading is not available on Low Graphics.
Full caps doesn't really incentivsize us to help you. When you install Java 8, the crash has nothing to do with MalisisCore/Doors because you didn't even use it.
But I bet that shitty X-ray mod you're using is the reason for the crash.
Mods for Minecraft :
MalisisDoors
MalisisBlocks
MalisisAdvert
MalisisSwitches
Do It Yourself Decorative Blocks
Hello there, just dropping by to say that the "Double sliding right" option in the Door Factory makes the door slide 2 blocks to the side instead of one
Kind of problematic if you set the door to only open by hand...