AJ Ruckman
- ajthemacboy
- ajthemacboy
- America/Havana
- Yes
- No
When a cake is placed near the edge of the world, it's hitbox is doubled. You can also place another cake in the side of the hitbox that isn't occupied, without a problem like you normally would have placing a block inside another block's hitbox. Sometimes, a cake's hitbox will only render on one side, and a few pixels off. It's all very weird, I'm sure theres more, you will have to play around with it yourself. I know a similar issue was fixed recently, https://bugs.mojang.com/browse/MC-45346 , this is different.
When a cake is placed near the edge of the world, it's hitbox is doubled. You can also place another cake in the side of the hitbox that isn't occupied, without a problem like you normally would have placing a block inside another block's hitbox. Sometimes, a cake's hitbox will only render on one side, and a few pixels off. It's all very weird, I'm sure theres more, you will have to play around with it yourself. I know a similar issue was fixed recently, https://bugs.mojang.com/browse/MC-45346 , this is different. Also, sometimes you can walk straight into the cake. Some of the hitbox issues seem to be directional.
When summoning a falling and entity, or any other entity, riding an item frame with /summon, an internal error occurs. This is the text from console, with one of the bugged commands:
[11:25:39 INFO]: Client> [11:25:39] [Server thread/ERROR]: Couldn't process command: 'summon FallingSand ~ ~10 ~ {TileID:66,Riding:{id:ItemFrame}}'
[11:25:39 INFO]: Client> s: Loading entity NBT
[11:25:39 INFO]: Client> at tu.f(SourceFile:1159) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ua.a(SourceFile:158) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at cm.b(SourceFile:94) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at z.a(SourceFile:65) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.d(SourceFile:606) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.a(SourceFile:593) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:37) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:9) [14w19a.jar:?]
[11:25:39 INFO]: Client> at fp.a(SourceFile:163) [14w19a.jar:?]
[11:25:39 INFO]: Client> at os.c(SourceFile:134) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.w(SourceFile:580) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.v(SourceFile:496) [14w19a.jar:?]
[11:25:39 INFO]: Client> at clf.v(SourceFile:132) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.run(SourceFile:412) [14w19a.jar:?]
[11:25:39 INFO]: Client> at mz.run(SourceFile:682) [14w19a.jar:?]
[11:25:39 INFO]: Client> Caused by: java.lang.NullPointerException: The validated object is null
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:222) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:203) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at ul.a(SourceFile:39) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ul.a(SourceFile:212) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at um.a(SourceFile:169) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at tu.f(SourceFile:1150) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> ... 14 more
[11:25:39 INFO]: Client> [11:25:39] [Client thread/INFO]: [CHAT] An unknown error occurred while attempting to perform this commandIt also occurs with any other sand variant riding an item frame, including sand with a tile id, time set to 0 and 1, etc.
When summoning a falling and entity, or any other entity, riding an item frame with /summon, an internal error occurs. This is the text from console, with one of the bugged commands:
[11:25:39 INFO]: Client> [11:25:39] [Server thread/ERROR]: Couldn't process command: 'summon FallingSand ~ ~10 ~ {TileID:66,Riding:{id:ItemFrame}}'
[11:25:39 INFO]: Client> s: Loading entity NBT
[11:25:39 INFO]: Client> at tu.f(SourceFile:1159) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ua.a(SourceFile:158) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at cm.b(SourceFile:94) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at z.a(SourceFile:65) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.d(SourceFile:606) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.a(SourceFile:593) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:37) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:9) [14w19a.jar:?]
[11:25:39 INFO]: Client> at fp.a(SourceFile:163) [14w19a.jar:?]
[11:25:39 INFO]: Client> at os.c(SourceFile:134) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.w(SourceFile:580) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.v(SourceFile:496) [14w19a.jar:?]
[11:25:39 INFO]: Client> at clf.v(SourceFile:132) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.run(SourceFile:412) [14w19a.jar:?]
[11:25:39 INFO]: Client> at mz.run(SourceFile:682) [14w19a.jar:?]
[11:25:39 INFO]: Client> Caused by: java.lang.NullPointerException: The validated object is null
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:222) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:203) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at ul.a(SourceFile:39) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ul.a(SourceFile:212) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at um.a(SourceFile:169) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at tu.f(SourceFile:1150) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> ... 14 more
[11:25:39 INFO]: Client> [11:25:39] [Client thread/INFO]: [CHAT] An unknown error occurred while attempting to perform this commandIt also occurs with any other sand variant riding an item frame, including sand with a tile id, time set to 0 and 1, etc.
When summoning a falling and entity, or any other entity, riding an item frame with /summon, an internal error occurs. This is the text from console, with one of the bugged commands:
[11:25:39 INFO]: Client> [11:25:39] [Server thread/ERROR]: Couldn't process command: 'summon FallingSand ~ ~10 ~ {TileID:66,Riding:{id:ItemFrame}}'
[11:25:39 INFO]: Client> s: Loading entity NBT
[11:25:39 INFO]: Client> at tu.f(SourceFile:1159) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ua.a(SourceFile:158) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at cm.b(SourceFile:94) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at z.a(SourceFile:65) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.d(SourceFile:606) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.a(SourceFile:593) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:37) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:9) [14w19a.jar:?]
[11:25:39 INFO]: Client> at fp.a(SourceFile:163) [14w19a.jar:?]
[11:25:39 INFO]: Client> at os.c(SourceFile:134) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.w(SourceFile:580) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.v(SourceFile:496) [14w19a.jar:?]
[11:25:39 INFO]: Client> at clf.v(SourceFile:132) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.run(SourceFile:412) [14w19a.jar:?]
[11:25:39 INFO]: Client> at mz.run(SourceFile:682) [14w19a.jar:?]
[11:25:39 INFO]: Client> Caused by: java.lang.NullPointerException: The validated object is null
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:222) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:203) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at ul.a(SourceFile:39) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ul.a(SourceFile:212) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at um.a(SourceFile:169) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at tu.f(SourceFile:1150) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> ... 14 more
[11:25:39 INFO]: Client> [11:25:39] [Client thread/INFO]: [CHAT] An unknown error occurred while attempting to perform this commandIt also occurs with any other sand variant riding an item frame, including sand with a tile id, time set to 0 and 1, etc, as well as any entity riding an item frame or painting. Happens with the entity being ridden in quotations and not in quotations. (Riding:{id:"Bat"}}
ORRiding:{id:Bat}})
When summoning a falling and entity, or any other entity, riding an item frame with /summon, an internal error occurs. This is the text from console, with one of the bugged commands:
[11:25:39 INFO]: Client> [11:25:39] [Server thread/ERROR]: Couldn't process command: 'summon FallingSand ~ ~10 ~ {TileID:66,Riding:{id:ItemFrame}}'
[11:25:39 INFO]: Client> s: Loading entity NBT
[11:25:39 INFO]: Client> at tu.f(SourceFile:1159) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ua.a(SourceFile:158) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at cm.b(SourceFile:94) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at z.a(SourceFile:65) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.d(SourceFile:606) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.a(SourceFile:593) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:37) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:9) [14w19a.jar:?]
[11:25:39 INFO]: Client> at fp.a(SourceFile:163) [14w19a.jar:?]
[11:25:39 INFO]: Client> at os.c(SourceFile:134) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.w(SourceFile:580) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.v(SourceFile:496) [14w19a.jar:?]
[11:25:39 INFO]: Client> at clf.v(SourceFile:132) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.run(SourceFile:412) [14w19a.jar:?]
[11:25:39 INFO]: Client> at mz.run(SourceFile:682) [14w19a.jar:?]
[11:25:39 INFO]: Client> Caused by: java.lang.NullPointerException: The validated object is null
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:222) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:203) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at ul.a(SourceFile:39) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ul.a(SourceFile:212) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at um.a(SourceFile:169) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at tu.f(SourceFile:1150) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> ... 14 more
[11:25:39 INFO]: Client> [11:25:39] [Client thread/INFO]: [CHAT] An unknown error occurred while attempting to perform this commandIt also occurs with any other sand variant riding an item frame, including sand with a tile id, time set to 0 and 1, etc, as well as any entity riding an item frame or painting. Happens with the entity being ridden in quotations and not in quotations. (Riding:{id:"
Bat"}}ORRiding:{id:Bat}})When summoning a falling and entity, or any other entity, riding an item frame with /summon, an internal error occurs. This is the text from console, with one of the bugged commands:
[11:25:39 INFO]: Client> [11:25:39] [Server thread/ERROR]: Couldn't process command: 'summon FallingSand ~ ~10 ~ {TileID:66,Riding:{id:ItemFrame}}'
[11:25:39 INFO]: Client> s: Loading entity NBT
[11:25:39 INFO]: Client> at tu.f(SourceFile:1159) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ua.a(SourceFile:158) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at cm.b(SourceFile:94) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at z.a(SourceFile:65) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.d(SourceFile:606) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.a(SourceFile:593) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:37) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:9) [14w19a.jar:?]
[11:25:39 INFO]: Client> at fp.a(SourceFile:163) [14w19a.jar:?]
[11:25:39 INFO]: Client> at os.c(SourceFile:134) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.w(SourceFile:580) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.v(SourceFile:496) [14w19a.jar:?]
[11:25:39 INFO]: Client> at clf.v(SourceFile:132) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.run(SourceFile:412) [14w19a.jar:?]
[11:25:39 INFO]: Client> at mz.run(SourceFile:682) [14w19a.jar:?]
[11:25:39 INFO]: Client> Caused by: java.lang.NullPointerException: The validated object is null
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:222) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:203) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at ul.a(SourceFile:39) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ul.a(SourceFile:212) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at um.a(SourceFile:169) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at tu.f(SourceFile:1150) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> ... 14 more
[11:25:39 INFO]: Client> [11:25:39] [Client thread/INFO]: [CHAT] An unknown error occurred while attempting to perform this commandIt also occurs with any other sand variant riding an item frame, including sand with a tile id, time set to 0 and 1, etc, as well as any entity riding an item frame or painting. Happens with the entity being ridden in quotations and not in quotations. (Riding:{id:"ItemFrame"}}
ORRiding:{id:ItemFrame}})
When summoning a falling and entity, or any other entity, riding an item frame with /summon, an internal error occurs. This is the text from console, with one of the bugged commands:
[11:25:39 INFO]: Client> [11:25:39] [Server thread/ERROR]: Couldn't process command: 'summon FallingSand ~ ~10 ~ {TileID:66,Riding:{id:ItemFrame}}'
[11:25:39 INFO]: Client> s: Loading entity NBT
[11:25:39 INFO]: Client> at tu.f(SourceFile:1159) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ua.a(SourceFile:158) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at cm.b(SourceFile:94) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at z.a(SourceFile:65) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.d(SourceFile:606) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.a(SourceFile:593) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:37) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:9) [14w19a.jar:?]
[11:25:39 INFO]: Client> at fp.a(SourceFile:163) [14w19a.jar:?]
[11:25:39 INFO]: Client> at os.c(SourceFile:134) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.w(SourceFile:580) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.v(SourceFile:496) [14w19a.jar:?]
[11:25:39 INFO]: Client> at clf.v(SourceFile:132) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.run(SourceFile:412) [14w19a.jar:?]
[11:25:39 INFO]: Client> at mz.run(SourceFile:682) [14w19a.jar:?]
[11:25:39 INFO]: Client> Caused by: java.lang.NullPointerException: The validated object is null
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:222) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:203) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at ul.a(SourceFile:39) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ul.a(SourceFile:212) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at um.a(SourceFile:169) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at tu.f(SourceFile:1150) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> ... 14 more
[11:25:39 INFO]: Client> [11:25:39] [Client thread/INFO]: [CHAT] An unknown error occurred while attempting to perform this commandIt also occurs with any other sand variant riding an item frame, including sand with a tile id, time set to 0 and 1, etc, as well as any entity riding an item frame or painting. Happens with the entity being ridden in quotations and not in quotations. (Riding:{id:"ItemFrame"}}
ORRiding:{id:ItemFrame}})When summoning a falling and entity, or any other entity, riding an item frame with /summon, an internal error occurs. This is the text from console, with one of the bugged commands:
[11:25:39 INFO]: Client> [11:25:39] [Server thread/ERROR]: Couldn't process command: 'summon FallingSand ~ ~10 ~ {TileID:66,Riding:{id:ItemFrame}}'
[11:25:39 INFO]: Client> s: Loading entity NBT
[11:25:39 INFO]: Client> at tu.f(SourceFile:1159) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ua.a(SourceFile:158) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at cm.b(SourceFile:94) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at z.a(SourceFile:65) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.d(SourceFile:606) [14w19a.jar:?]
[11:25:39 INFO]: Client> at ox.a(SourceFile:593) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:37) [14w19a.jar:?]
[11:25:39 INFO]: Client> at kb.a(SourceFile:9) [14w19a.jar:?]
[11:25:39 INFO]: Client> at fp.a(SourceFile:163) [14w19a.jar:?]
[11:25:39 INFO]: Client> at os.c(SourceFile:134) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.w(SourceFile:580) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.v(SourceFile:496) [14w19a.jar:?]
[11:25:39 INFO]: Client> at clf.v(SourceFile:132) [14w19a.jar:?]
[11:25:39 INFO]: Client> at net.minecraft.server.MinecraftServer.run(SourceFile:412) [14w19a.jar:?]
[11:25:39 INFO]: Client> at mz.run(SourceFile:682) [14w19a.jar:?]
[11:25:39 INFO]: Client> Caused by: java.lang.NullPointerException: The validated object is null
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:222) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at org.apache.commons.lang3.Validate.notNull(Validate.java:203) ~[commons-lang3-3.2.1.jar:3.2.1]
[11:25:39 INFO]: Client> at ul.a(SourceFile:39) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at ul.a(SourceFile:212) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at um.a(SourceFile:169) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> at tu.f(SourceFile:1150) ~[14w19a.jar:?]
[11:25:39 INFO]: Client> ... 14 more
[11:25:39 INFO]: Client> [11:25:39] [Client thread/INFO]: [CHAT] An unknown error occurred while attempting to perform this commandIt also occurs with any other sand variant riding an item frame, including sand with a tile id, time set to 0 and 1, etc, as well as any entity riding an item frame or painting. Happens with the entity being ridden in quotations and not in quotations. (Riding:{id:"ItemFrame"}} OR Riding:{id:ItemFrame}})
I agree, this is a bug. OP, maybe re-post so mojang will see this.
When I join a singleplayer world, my screen turns black. When I hit escape, I can click till I hit the 'save and quit' button and I'm taken back to the main menu.
Black screen when joiningSPworld on 15w31a
When I join a
singleplayerworld, my screen turns black. When I hit escape, I can click till I hit the 'save and quit' button and I'm taken back to the main menu.
When I join a world, my screen turns black. When I hit escape, I can click till I hit the 'save and quit' button and I'm taken back to the main menu.
Update: It occurs with VBOs on and off. Sometimes I can see the world for a second before the screen goes black; other times, it is instantaneous.
Windows 10, Java 8 update 51, Minecraft 15w31a, Nvidia GTX 765M, Graphics driver 353.54 & 353.62 (Windows 10 Driver)
When I join a world, my screen turns black. When I hit escape, I can click till I hit the 'save and quit' button and I'm taken back to the main menu.
Update: It occurs with VBOs on and off. Sometimes I can see the world for a second before the screen goes black; other times, it is instantaneous.
Update 2: Updated to the Windows 10 Nvidia driver, no change.
When I join a world, my screen turns black. When I hit escape, I can click till I hit the 'save and quit' button and I'm taken back to the main menu.
Update: It occurs with VBOs on and off. Sometimes I can see the world for a second before the screen goes black; other times, it is instantaneous.
Update 2: Updated to the Windows 10 Nvidia driver 353.62, no change.
When I join a world, my screen turns black. When I hit escape, I can click till I hit the 'save and quit' button and I'm taken back to the main menu.
Update: It occurs with VBOs on and off. Sometimes I can see the world for a second before the screen goes black; other times, it is instantaneous.
Update 2: Updated to the Windows 10 Nvidia driver 353.62, no change.
Update 3: Added a video
I think the new end gateways look cool, but since you cannot place them manually, I attempted to set up a fill clock with this command:
`execute ajthemacboy ~ ~ ~ fill ~-5 ~-5 ~-5 ~5 ~5 ~5 end_gateway 0 replace wool 11`
So every time I placed a blue wool block, it would be replaced by an end gateway. However, it simply doesn't work; the command block says 'Failed to execute' and when I try the command in chat, I get this:
[Client thread/INFO]: [CHAT] Data tag parsing failed: Invalid tag encountered, expected '{' as first char.
I believe this to be because of added support for NBT data in block commands, but since the help menu for /fill still doesn't include its usage, this is a bug.
I think the new end gateways look cool, but since you cannot place them manually, I attempted to set up a fill clock with this command:
`execute ajthemacboy ~ ~ ~ fill ~-5 ~-5 ~-5 ~5 ~5 ~5 end_gateway 0 replace wool 11`
So every time I placed a blue wool block, it would be replaced by an end gateway. However, it simply doesn't work; the command block says 'Failed to execute' and when I try the command in chat, I get this:
`[Client thread/INFO]: [CHAT] Data tag parsing failed: Invalid tag encountered, expected '{' as first char.`
I believe this to be because of added support for NBT data in block commands, but since the help menu for /fill still doesn't include its usage, this is a bug.
Hitboxes don't rotate with entities. This causes lots of inaccuracies, especially with entity collision re-added:
- Shooting arrows near a mob will hit it if it's incorrectly rotated
- Attacking near a mob while rotated will hit the mob
- Walking near the edge of a rotated mob will cause you to collide with it
- The Elytra may collide with blocks when the player is rotated
The first screenshot depicts the hitbox while rotated.
The second shows how the player collides with the sheep, even from the edge.
Hitboxes don't rotate with entities. This causes lots of inaccuracies, especially with entity collision re-added:
- Shooting arrows near a mob will hit it
if it'sincorrectly rotated- Attacking near a mob while rotated will hit the mob
- Walking near the edge of a rotated mob will cause you to collide with it
- The Elytra may collide with blocks when the player is rotated
The first screenshot depicts the hitbox while rotated.
The second shows how the player collides with the sheep, even from the edge.
Hitboxes don't rotate with entities. This causes lots of inaccuracies, especially with entity collision re-added:
- Shooting arrows near a mob will hit it incorrectly if it's rotated
- Attacking near a mob while rotated will hit the mob
- Walking near the edge of a rotated mob will cause you to collide with it
- The Elytra may collide with blocks when the player is rotated
The first screenshot depicts the hitbox while rotated.
The second shows how the player collides with the sheep, even from the edge.
Villagers inconsistently don't run from Zombies
Villagers don't run from zombies.
The next mob I'd think to try to see if the AI is broken is a snowman, but when I spawn one it dies on the ground.Villagers often don't run from zombies.
Sometimes they will start running and never stop, sometimes they will just stand and let the zombie kill them.
@AJ Ruckman: Yes, create a new ticket. Please attach screenshots of your setup there.













Also, when leaving a world while sand is falling, the sand disappears until it finishes falling.
Nevermind, this is a duplicate.
If you look in the launcher console, this may be the result of the generator crashing. This has happened to me, and is reproducible by setting all sliders to max. The minecraft window stays open even after the generator crashes, so there's no way for you to know that it has broken.
This isn't actually a chunk error by definition; this is a render error. A chunk error would slow you when you fly over it, and have sides of whatever block was around them, just darker. These render errors have clear sides and render correctly when you get near them. This has been an issue in Minecraft for ages, but they are much more frequent in 14w17a. This is especially visible when in gamemode 3, flying around at max speed.
Not a bug; a feature!
Could you attach a screenshot? If there is no endermite at all, that's a problem, but if it is a little 'blob' that spins and has a red bar for eyes, that's its new model.
Having this problem too, almost every time I try to create a world with any custom settings. This didn't happen when I first started creating custom worlds, but now I can't create any without a crash. Very annoying. I understand that I may be changing multiple settings that can't work together, maybe Mojang could add some kindof slider lock, if you have one setting that can't work another, it dithers or locks the scroll bar?
Has this happened more than once? Does it happen every time you close a world, or only with a specific world?
I hope this is a feature and not a bug. It would be really nice to be able to get these blocks in survival.
If this issue is closed, it needs to be reopened. Please see here:
MC-53584There are errors in console and debug profiles. This is a problem that can be reproduced, and slows my 3.7 GHz 8 core cpu to much more than a crawl, as you say.
Confirmed in OS X. If this issue is closed, it needs to be reopened. This is a reproducible problem.
Steps to reproduce:
1. Create a new customized world with this preset:
{"coordinateScale":6000.0,"heightScale":684.412,"lowerLimitScale":2007.6409,"upperLimitScale":2007.6409,"depthNoiseScaleX":200.0,"depthNoiseScaleZ":200.0,"depthNoiseScaleExponent":20.0,"mainNoiseScaleX":5000.0,"mainNoiseScaleY":2570.9084,"mainNoiseScaleZ":5000.0,"baseSize":18.239437,"stretchY":4.2345076,"biomeDepthWeight":10.098592,"biomeDepthOffset":0.0,"biomeScaleWeight":10.098592,"biomeScaleOffset":0.0,"seaLevel":63,"useCaves":true,"useDungeons":true,"dungeonChance":8,"useStrongholds":true,"useVillages":true,"useMineShafts":true,"useTemples":true,"useRavines":true,"useWaterLakes":true,"waterLakeChance":4,"useLavaLakes":true,"lavaLakeChance":80,"useLavaOceans":false,"fixedBiome":-1,"biomeSize":4,"riverSize":4,"dirtSize":33,"dirtCount":10,"dirtMinHeight":0,"dirtMaxHeight":256,"gravelSize":33,"gravelCount":8,"gravelMinHeight":0,"gravelMaxHeight":256,"graniteSize":33,"graniteCount":10,"graniteMinHeight":0,"graniteMaxHeight":80,"dioriteSize":33,"dioriteCount":10,"dioriteMinHeight":0,"dioriteMaxHeight":80,"andesiteSize":33,"andesiteCount":10,"andesiteMinHeight":0,"andesiteMaxHeight":80,"coalSize":17,"coalCount":20,"coalMinHeight":0,"coalMaxHeight":128,"ironSize":9,"ironCount":20,"ironMinHeight":0,"ironMaxHeight":64,"goldSize":9,"goldCount":2,"goldMinHeight":0,"goldMaxHeight":32,"redstoneSize":8,"redstoneCount":8,"redstoneMinHeight":0,"redstoneMaxHeight":16,"diamondSize":8,"diamondCount":1,"diamondMinHeight":0,"diamondMaxHeight":16,"lapisSize":7,"lapisCount":1,"lapisCenterHeight":16,"lapisSpread":16}2. When in the world, with console open, type /debug start.
3. Start flying around (loading new chunks). Notice the spam in console. See debug profile attached.
This issue is not resolved in 14w18a.
You may also want to open the world and type /debug start, that will give you some information in the minecraft/debug folder, as well as in console.
This happens for me all the time in 14w19a.
Cannot test now, but before you were able to summon item frames and paintings without specifying coordinates. (See this video: https://www.youtube.com/watch?v=36rIqGnXrcE ) Also, 49835 gives a different error: "Unable to summon object", while this issue gives the error "An internal error occurred while attempting to perform this command."
Try reinstalling minecraft, or delete the versions folder in the minecraft folder.
For me it happens with and without Advanced openGL on, and I have a fast computer.
Still not fixed in 14w20b.
Big bug. I really wish mojang would fix this, this seems like the kindof bug they miss in the snapshot and never fix.
"barely a big bug" is still a bug.
I never said anything about this one being more important than the others, but as this issue has been open for 6 months and still isn't fixed, perhaps it is time for further action (such as a repost.) No need to be rude.
Present in 34b
The opposite of this is also true. There is grass in the bottom of lakes and rivers when you set the sea level higher.
This also happens when walking on half slabs in a certain way.
1. Make a 3x3 slab of ONE half slab, so that you stand 0.5 blocks higher.
2. Place another 3x3 half slab 'slab' AS LOW as you can when you are on the first slabs.
3. On top place a 3x3 slab of solid blocks.
The end configuration should look like this, and each layer should be 3x3:
Solid Block
Upper Half Slab
Air
Lower Half Slab
Standing in the middle causes items to darken.
Should I create a separate issue for the bug I reported above, on 29/August/14?
No; the errors are gone in pre3. Don't have time to test in other versions.
Still in 1.8.1 pre 5.
This is still an issue in 1.8.1.
Here's how you can set things up to test.
Command block 1: summon ArmorStand ~ ~1 ~
{Invulnerable:1,NoGravity:1,CustomName:"StandTeleported"}Command block 2: execute @e[name=StandTeleported] ~ ~ ~ spreadplayers ~ ~ 0 1 false @e[name=StandTeleported,c=1]
Run command block 1 a few times, then command block 2 on a clock. Watch as the armor stands head northwest.
Still an issue in 1.8.2 pre 3
Ya, this is a serious issue. On vanilla, when a player logs in, even on a very capable server with 3+gbs ram allocated, there is a huge lagspike.
It was not nearly as bad before 1.8.
Perhaps this is a BUD switch? I can't really tell what's happening.
Both. I made a new world, but old worlds don't work either.
Duplicate: https://bugs.mojang.com/browse/MC-82839?jql=text%20~%20%22black%20screen%2015w31a%22
Another duplicate of https://bugs.mojang.com/browse/MC-82839
If it's relevant, my screen also turns black when using super secret settings in 1.7 & 1.8.
I will post a crash in the morning. However, seeing as the new launcher comes bundled with Java 8, it would be both abnormal and counterintuitive to backdate to 7.
Debug crash:
Here's a video. You can see the world for a second before it goes black.
Completely different card and OS version... What...
It is! I switched to to true and no more black screen! But I never turned off fboEnable, so this is still a bug.
Why is an end gateway a tile entity, and can't you fill chests? Aren't they tile entities?
Do you know how difficult it would be to code?
You're using a resource pack; try disabling it and see what happens.
Can you explain in what way this is by design? How does it benefit the game? All I see it creating is anomalies.
Please don't take this as rude, but all bugs are coded like they are. I can't imagine that something as simple as rotating hitboxes would cause any noticeable performance loss.
I hope you'll consider un-marking this as works as intended, because there is no real advantage to the current system, and improving it will only make the game better.
XP is fixed in 15w51b, didn't test items.
I've had this happen to me several times as well. (My screenshot shows OptiFine, but it occurs without it as well.)
VSync does not fix the issue and my graphics drivers are always up to date.
Edit: Looking at the pictures on my laptop now I see that my bug is different, my apologies.
I can no longer confirm whether this is an issue. I've since switched to a new computer and it no long occurs. If anyone is still experiencing this please update the issue.