Adrian Deutscher-Bishop
- BCNOFNeNaMg
- bcnofnenamg
- America/Los_Angeles
- Yes
- No
MC-99441![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg){kind=small}
Normal![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava, the item lands in the hopper but will
catch on fire andplay the burning sound. When you face other directions, the item is burned. It does not matter what Y coordinate you're at.When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at.
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at.
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will sometms work in survival
PC
Windows 8.1
Java 8
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will somet
ms work in survivalWhen you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava.
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava. I have tested this in 1.6.4 and the bug was there.
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will sometimes work in survival, when you're facing other directions, or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there.
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will sometimes work in survival,
when you're facing other directions,or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there.
When you face west and throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will sometimes work in survival
,or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there.
When you
face west andthrow an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. When you face other directions, the item is burned. It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there.
When you throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce.
When you face other directions, the item is burned.It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there.When you throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there. This usually happens when you're facing west, but it also happens when you're facing other directions.
When you throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there. This usually happens when you're facing west, but it also happens when you're facing other directions.
As of 1.21
When you throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there. This usually happens when you're facing west, but it also happens when you're facing other directions.
As of 1.21
When you throw an item into the lowest level of lava from 1 block away and place a hopper underneath the lava and hoppers next to the lava, the item lands in the hopper but will play the burning sound and will bounce. It does not matter what Y coordinate you're at. This will sometimes work in survival or on the not-lowest block of lava. This will only sometimes work. I have tested this in 1.6.4 and the bug was there. This usually happens when you're facing west, but it also happens when you're facing other directions.
As of 1.21.2 Pre-Release 2, the bug is still there, but due to hopper changes, it requires lava between 1 and 2 blocks thick with a hopper underneath to occur.
If you shoot an arrow at full speed toward the bottom of a lava block, the arrow won't be set on fire. This will not happen every time. [Note: A lot harder to do after 1.9.3pre-2.
If you shoot an arrow at full speed toward the bottom of a lava block, the arrow won't be set on fire. This will not happen every time. [Note: A lot harder to do after 1.9.3pre
-2.If you shoot an arrow at full speed toward the bottom of a lava block, the arrow won't be set on fire. This will not happen every time. [Note: A lot harder to do after 1.9.3-pre2.
Placing a redstone source in different locations changes which piston recieves the signal firstPlacing a redstone source in different locations changes which piston receives the signal first
If you connect a clock circuit that alternates really fast to an upwards-facing piston with a slime block on top and then jump onto the slime block, the contraption acts crazily.
First, sometimes the screen will automatically look in a certain direction for no reason, and Second: The slime block will (most of the time) not bounce you up.If you connect a clock circuit that alternates really fast to an upwards-facing piston with a slime block on top and then jump onto the slime block, the contraption acts crazily. Sometimes the screen will automatically look in a certain direction for no reason.
If you connect a clock circuit that alternates really fast to an upwards-facing piston with a slime block on top and then jump onto the slime block, the contraption acts crazily. Sometimes the screen will automatically look in a certain direction for no reason. This only happens on superflat worlds.
If you have lava near you and pause the game, you will hear the lava sound after you pause the game, even after all the other sounds have stopped. I found this also with pistons.
After pausing the game you hearlavaAfter pausing the game you hear sounds
If you have lava near you and pause the game, you will hear
the lavasound afteryou pause the game, even after all the other sounds have stopped. I found this also with pistons.If you have lava near you and pause the game, you will hear sounds after the game is paused.
If you have a custom item which gives you -19 Max Health your health will become 1 heart (2 health) when you die instead of 1/2 a heart (1 health).
If you have a custom item which gives you -19 Max Health your health will become 1 heart (2 health) when you die instead of 1/2 a heart (1 health). Use the command
{AttributeName:"generic.maxHealth",Name:"Test",Amount:-19.5,Operation:0,UUIDLeast:1l,UUIDMost:1l,Slot:"chest"}
/give @p minecraft:diamond_chestplate 1 0 {AttributeModifiers:[]}
If you have a custom item which gives you -19 Max Health your health will become 1 heart (2 health) when you die instead of 1/2 a heart (1 health). Use the command
{AttributeName:"generic.maxHealth",Name:"Test",Amount:-19.5,Operation:0,UUIDLeast:1l,UUIDMost:1l,Slot:"chest"}
/give @p minecraft:diamond_chestplate 1 0 {AttributeModifiers:[]}
If you have a custom item which gives you -19 Max Health your health will become 1 heart (2 health) when you die instead of 1/2 a heart (1 health). Use the command
{AttributeName:"generic.maxHealth",Name:"Test",Amount:-19.5,Operation:0,UUIDLeast:1l,UUIDMost:1l,Slot:"chest"}
/give @p minecraft:diamond_chestplate 1 0 {AttributeModifiers:[]}
I have also found this works with any item giving/making you lose an odd amount of health (a.k.a. health where you get halves of hearts.
If you have a custom item which gives you -19 Max Health your health will become 1 heart (2 health) when you die instead of 1/2 a heart (1 health). Use the command
{AttributeName:"generic.maxHealth",Name:"Test",Amount:-19.5,Operation:0,UUIDLeast:1l,UUIDMost:1l,Slot:"chest"}
/give @p minecraft:diamond_chestplate 1 0 {AttributeModifiers:[]}
I have also found this works with any item giving/making you lose an odd amount of health (a.k.a. health where you get halves of hearts).
When they added the Wither Skeleton Spawn Egg in 16w20a, I thought the skeleton spawn egg would not spawn Wither Skeletons anymore. But instead, the Skeleton Spawn Egg still spawns Wither Skeletons 80% of the time in the Nether. This is also the case with Zombie/Husks, Skeleton/Stray, and
When they added the Wither Skeleton Spawn Egg in 16w20a, I thought the skeleton spawn egg would not spawn Wither Skeletons anymore. But instead, the Skeleton Spawn Egg still spawns Wither Skeletons 80% of the time in the Nether. This is also the case with Zombie/Husk
s,Skeleton/Stray, andWhen they added the Wither Skeleton Spawn Egg in 16w20a, I thought the skeleton spawn egg would not spawn Wither Skeletons anymore. But instead, the Skeleton Spawn Egg still spawns Wither Skeletons 80% of the time in the Nether. This is also the case with Zombie/Husk and Skeleton/Stray.
If you finish fishing but double-click instead of single-clicking, the line
and the fishing rod in your inventorywill be reeled out again but the item in your hand will show that you are not fishing, even if you really are.If you finish fishing but double-click instead of single-clicking, the line will be reeled out again but the item in your hand and the item in your inventory will show that you are not fishing, even if you really are.
HP Split x2
Windows 8.1
Java 8
Intel i3
HP Split x2
Windows 8.1
Java 8
Intel Core i3
I spawned a zombie with this command:
{NoAI:1}
/summon Zombie ~ ~ ~and the zombie floated in the air, like NoGravity was set to 1.
Next, I tried /summon Zombie ~ ~ ~
{NoAI:1, NoGravity:0}
.
The zombie still floated in the air.I spawned a zombie with this command:
{NoAI:1}
/summon Zombie ~ ~ ~and the zombie floated in the air, like NoGravity was set to 1.
Next, I tried /summon Zombie ~ ~ ~
{NoAI:1, NoGravity:0}, and
the zombie still floated in the air.
I tried giving myself an item with negative durability with this command:
/give @p minecraft:golden_hoe 1 50In previous versions, this has given me an item with negative durability. When I tried it in the new snapshot, it just crashed the game. It then corrupted the world, so I could not use it again.
Boat on top of slime blocks hover over block
The bug
When a boat is falling while over a slime block, once it gets to about 5 blocks on top of the slime block, the boat will start rising and falling very slowly.
How to reproduce
Video demonstrating the issue: https://gfycat.com/PrestigiousDistantGardensnake
Code analysis
Code analysis by FX - PR0CESS can be found in this comment.
The bug
When a boat is falling while over a slime block, once it gets to about 5 blocks on top of the slime block, the boat will start rising and falling very slowly. As of 22w12a, this also occurs with boats with chests.
How to reproduce
Video demonstrating the issue: https://gfycat.com/PrestigiousDistantGardensnake
Code analysis
Code analysis by FX - PR0CESS can be found in this comment.
The bug
When a boat is falling while over a slime block, once it gets to about 5 blocks on top of the slime block, the boat will start rising and falling very slowly. As of 22w12a, this also occurs with boats with chests. As of 1.21.2 Pre-Release 2, the effect is not as large and does not occur with every bounce, but still happens.
How to reproduce
Video demonstrating the issue: https://gfycat.com/PrestigiousDistantGardensnake
Code analysis
Code analysis by FX - PR0CESS can be found in this comment.
If you summon Falling Sand Inside the block (Summoning a log falling sand inside a log block) will cause an invisible glitchy barrier which you cannot pass through. The only way to destroy it is with /setblock or /fill or by placing another block inside it.
You can give yourself more than one nonstackable items.You can give yourself more than one nonstackable item at once.
When I pushed white concrete powder upward onto a block next to water, the game suddenly crashed. I reloaded the world and it had saved. I tried it again and the game didn't crash. However, I tried it again and it did.
---- Minecraft Crash Report ---- // Why is it breaking :( Time: 12/6/17 9:20 PM Description: Ticking block entity java.lang.NullPointerException: Ticking block entity at bat.f(SourceFile:108) at bat.P_(SourceFile:317) at aqr.k(SourceFile:1469) at bmx.m(SourceFile:1253) at bmx.b(SourceFile:791) at bmx.a(SourceFile:380) at net.minecraft.client.main.Main.main(SourceFile:140) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Client thread Stacktrace: at bat.f(SourceFile:108) at bat.P_(SourceFile:317) -- Block entity being ticked -- Details: Name: minecraft:piston // bat Block: minecraft:sandstone Block location: World: (1352,66,-874), Chunk: (at 8,4,6 in 84,-55; contains blocks 1344,0,-880 to 1359,255,-865), Region: (2,-2; contains chunks 64,-64 to 95,-33, blocks 1024,0,-1024 to 1535,255,-513) Block: minecraft:sandstone Block location: World: (1352,66,-874), Chunk: (at 8,4,6 in 84,-55; contains blocks 1344,0,-880 to 1359,255,-865), Region: (2,-2; contains chunks 64,-64 to 95,-33, blocks 1024,0,-1024 to 1535,255,-513) Stacktrace: at aqr.k(SourceFile:1469) -- Affected level -- Details: Level name: MpServer All players: 1 total; [bzd['BCNOFNeNaMg'/0, l='MpServer', x=1344.06, y=56.00, z=-876.62]] Chunk stats: MultiplayerChunkCache: 81, 81 Level seed: 0 Level generator: ID 01 - flat, ver 0. Features enabled: false Level generator options: Level spawn location: World: (1389,4,-872), Chunk: (at 13,0,8 in 86,-55; contains blocks 1376,0,-880 to 1391,255,-865), Region: (2,-2; contains chunks 64,-64 to 95,-33, blocks 1024,0,-1024 to 1535,255,-513) Level time: 2005381 game time, 6000 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: creative (ID 1). Hardcore: false. Cheats: false Forced entities: 1 total; [bzd['BCNOFNeNaMg'/0, l='MpServer', x=1344.06, y=56.00, z=-876.62]] Retry entities: 0 total; [] Server brand: vanilla Server type: Integrated singleplayer server Stacktrace: at bxe.a(SourceFile:356) at bmx.b(SourceFile:1838) at bmx.a(SourceFile:389) at net.minecraft.client.main.Main.main(SourceFile:140) -- System Details -- Details: Minecraft Version: 17w49a Operating System: Windows 8.1 (amd64) version 6.3 Java Version: 1.8.0_25, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 128933192 bytes (122 MB) / 251658240 bytes (240 MB) up to 1073741824 bytes (1024 MB) JVM Flags: 8 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 Launched Version: 17w49a LWJGL: 3.1.2 build 29 OpenGL: Intel(R) HD Graphics 4200 GL version 4.2.0 - Build 10.18.10.3621, Intel GL Caps: Using GL 1.3 multitexturing. Using GL 1.3 texture combiners. Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported. Shaders are available because OpenGL 2.1 is supported. VBOs are available because OpenGL 1.5 is supported. Using VBOs: No Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Packs: Current Language: ~~ERROR~~ NullPointerException: null Profiler Position: N/A (disabled) CPU: 4x Intel(R) Core(TM) i3-4012Y CPU @ 1.50GHz #@!@# Game crashed! Crash report saved to: #@!@# C:\Users\BoronCarbon\AppData\Roaming\.minecraft\crash-reports\crash-2017-12-06_21.20.59-client.txt <log4j:Event logger="rd" timestamp="1512624059154" level="INFO" thread="Server thread"> <log4j:Message><![CDATA[Stopping singleplayer server as player logged out]]></log4j:Message> </log4j:Event>
When the gamerule randomTickSpeed is set to a high number (e.g. 50000), crops such as sugarcane and cacti grow so quickly that when a the middle block of a 3-block tall crop is broken, the top block (which would break in the next tick) is able to grow a new block above it. Since this suspended plant is not 3 blocks tall anymore, it can keep growing (potentially up to the height limit, as shown in one of the videos), all while the bottom blocks of the floating plants keep breaking every tick. In rare cases (such as the one shown in one of the videos), these crops grow so quickly that the broken block is replaced before the top block can be destroyed. This can occur simultaneously with the previous effect, allowing for 4-block tall grown plants.
This could theoretically occur when the tick speed is not high, but it would be hard to reproduce.
How to Reproduce:
- Set the gamerule randomTickSpeed to a high number (>40000).
- Plant a cactus or sugarcane.
- Keep breaking the middle block of the plant until a cascade effect occurs.
How do you do that?
Mobs with the NoAI tag can still enter boats if their collision collides with the boat's.
Note: The strange behavior when entering the boat in the video is due to
MC-167299
How to Reproduce:
- Summon a NoAI mob.
- Summon a boat on top of the mob.
- Get in the boat. If you do not start slowly moving downwards, get out of the boat and try again. This may take a few attempts.
- Get out of the boat. The mob should now be in the boat.
Big Dripleaves, when powered by redstone, still tilt down when a projectile is thrown at them. This is intended. However, when it is then updated by a block, it immediately tilts back up again.
Throwing Projectiles at Powered Big DripleavesCauses them to Tilt Down, Only toTilt Up withUpdatedThrowing Projectiles at Powered Big Dripleaves Hit By Projectiles Tilt Up when Updated
I disagree that this is a duplicate. The bug here is that they immediately tilt upward when updated.
Big Dripleaves, when powered by redstone, still tilt down when a projectile is thrown at them.
This is intended.However, when it is then updated by a block, it immediately tilts back up again.
Throwing Projectiles at Powered Big DripleavesHit By ProjectilesTiltUp when UpdatedThrowing Projectiles at Powered Big Dripleaves Tilt Down, then Tilt up when Updated
When teleporting a Y-Level of 0.00001 below the top of a block (For most blocks, at the Y-Level of an Integer + 0.99999), the player is unable to move or look around. Attempting to sprint or fly does nothing, although sprinting will create footstep particles and play the walking sound.
To reproduce, use the command /tp @p ~ ~-0.00001 ~
At a Y-Level of 0.00002 or more below a block, the player will fall through the block (which I believe is the intended behavior.
Yes, this is an issue in 1.9.1-pre3 but it works less often.
I have spawned lots of zombies and none of them broke down the door.
Confirmed for 1.9.1-pre1, pre2, and pre3
I have found this bug a lot with clock circuits and pistons.
Fixed.
The screen moves for no apparent reason. I don't know how to supply a video.
You need to build this and stand on the slime block.
/give @p minecraft:diamond_chestplate 1 0 {AttributeModifiers:[
{AttributeName:"generic.maxHealth",Name:"Test",Amount:-19.5,Operation:0,UUIDLeast:1l,UUIDMost:1l,Slot:"chest"}]}
I suggest that if you want to stop the corruption if your world got corrupted, go into the previous snapshot and delete any items with negative durability.
If you try enough times, you can reproduce it.
No, it doesn't happen in 16w44a. I think this is due to the piston translocation bug being fixed.
Although said to be fixed in 17w49b, this still happens for me.
The game still crashes in 17w50a. I have attached a crash log.
I couldn't find the swamp on the original seed, so here's a new one.
Seed: 774267198341012260
Coordinates: 635 128 -816
Ok. This is a duplicate.
Confirmed for 19w34a.
Confirmed for 19w34a.
This bug has been fixed.
Yes, but placing another block on top of that block doesn't make the mob clip through.
I have attached a screenshot.
This bug has been fixed at some point.
@Avoma I disagree that this is a duplicate.
MC-214804refers to the sound that dripleaves make when powered, while mine refers to the dripleaves lifting immediately after being block updated.