John Distler
- deepicness12345
- deepicness12345
- Europe/Stockholm
- Yes
- No
MC-8980![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
Low
In older versions, TNT was moved by water. It wasn't documented as a change. I consider it a bug.
Primed TNT does not travel through Nether Portals. In the screenshot, the TNT is sitting in the Nether Portal
not going through the portal.Primed TNT does not travel through Nether Portals. In the screenshot, the TNT is sitting in the Nether Portal without going through the portal.
I put around 30,000 creepers through an end portal. I jumped in. I was getting about 0.1 fps. After a couple minutes, I heard a explosion. I got the out of memory screen. Then, I crashed:
Minecraft has crashed!
----------------------Minecraft has stopped running because it encountered a problem; Ticking entity
A full error report has been saved to C:\Users\John\AppData\Roaming\.minecraft\crash-reports\crash-2013-03-09_22.55.43-server.txt - Please include a copy of that file (Not this screen!) if you report this crash to anyone; without it, they will not be able to help fix the crash
— BEGIN ERROR REPORT 9d472e94 --------
Full report at:
C:\Users\John\AppData\Roaming\.minecraft\crash-reports\crash-2013-03-09_22.55.43-server.txt
Please show that file to Mojang, NOT just this screen!Generated 3/9/13 10:55 PM
– Head –
Stacktrace:
at aqt.a(SourceFile:23)
at aou.b(SourceFile:567)
at aou.a(SourceFile:562)
at zv.a(SourceFile:935)
at mp.d(SourceFile:481)
at ng.e(SourceFile:977)
at ng.c(SourceFile:1185)
at rv.c(SourceFile:26)
at ng.l_(SourceFile:551)
at rv.l_(SourceFile:31)
at ro.l_(SourceFile:108)
at zv.a(SourceFile:1336)
at iz.a(SourceFile:508)
at zv.g(SourceFile:1314)– Entity being ticked –
Details:
Entity Type: Creeper (ro)
Entity ID: 2528962
Entity Name: Creeper
Entity's Exact location: 99.64, 50.36, 0.33
Entity's Block location: World: (99,50,0), Chunk: (at 3,3,0 in 6,0; contains blocks 96,0,0 to 111,255,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Entity's Momentum: -227.52, 1.26, 210.87
Stacktrace:
at zv.h(SourceFile:1221)
at iz.h(SourceFile:390)– Affected level –
Details:
Level name: Test World (Non Mob Spawners)
All players: 1 total; [jc['DeEpicness123'/730264, l='Test World (Non Mob Spawners)', x=100.00, y=49.00, z=0.00]]
Chunk stats: ServerChunkCache: 442 Drop: 0
Level seed: 516595084
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: World: (0,0,0), Chunk: (at 0,0,0 in 0,0; contains blocks 0,0,0 to 15,255,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 0 game time, 0 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: ~ERROR~ NullPointerException: null
Stacktrace:
at net.minecraft.server.MinecraftServer.r(SourceFile:462)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at bja.q(SourceFile:122)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)– System Details –
Details:
Minecraft Version: 1.5
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.6.0_31, Sun Microsystems Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Sun Microsystems Inc.
Memory: 56849664 bytes (54 MB) / 1041694720 bytes (993 MB) up to 1041694720 bytes (993 MB)
JVM Flags: 2 total; -Xms512m -Xmx1024m
AABB Pool Size: 8835157 (494768792 bytes; 471 MB) allocated, 8835157 (494768792 bytes; 471 MB) used
Suspicious classes: No suspicious classes found.
IntCache: cache: 0, tcache: 0, allocated: 1, tallocated: 63
Profiler Position: N/A (disabled)
Vec3 Pool Size: 33 (1848 bytes; 0 MB) allocated, 17 (952 bytes; 0 MB) used
Player Count: 1 / 8; [jc['DeEpicness123'/730264, l='Test World (Non Mob Spawners)', x=100.00, y=49.00, z=0.00]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.java.lang.OutOfMemoryError: Java heap space
at aqt.a(SourceFile:23)
at aou.b(SourceFile:567)
at aou.a(SourceFile:562)
at zv.a(SourceFile:935)
at mp.d(SourceFile:481)
at ng.e(SourceFile:977)
at ng.c(SourceFile:1185)
at rv.c(SourceFile:26)
at ng.l_(SourceFile:551)
at rv.l_(SourceFile:31)
at ro.l_(SourceFile:108)
at zv.a(SourceFile:1336)
at iz.a(SourceFile:508)
at zv.g(SourceFile:1314)
at zv.h(SourceFile:1221)
at iz.h(SourceFile:390)
at net.minecraft.server.MinecraftServer.r(SourceFile:462)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at bja.q(SourceFile:122)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)
— END ERROR REPORT 31ba3297 ----------
Mining an AnvilMakes No SoundMining an Anvil Plays No Sound
Mining anAnvilPlaysNoSoundMining an anvil plays no sound!
The visual box (not hitbox: you can't bump into it) around corner fences is wrongly displayed, for it shouldn't be a box.
Thevisual box (not hitbox: you can't bump into it) around corner fences is wrongly displayed, for it shouldn't be a box.The hitbox of corner fences isn't the same as the
The hitbox of corner fences isn't the same as the collision box since 1.5!
What I expect to see:
The visual box (not hit-box: you can't bump into) curve around thecornerfenceWhat I actually saw:
The visual box (not hit-box: you can't bump into) is square shapedHow to recreate:
screenshot belowWhat I expect to see:
When the collision box of cornerWhat I actually saw:
The visual box (not hit-box: you can't bump into) is square shapedHow to recreate:
screenshot below
The hitbox of corner fences isn't the same as the collision boxsince 1.5!
What I expect to see:
When the collision box of corner fences was fixed I expected for the hitboxWhat I actually saw:
The visual box (not hit-box: you can't bump into) is square shapedHow to recreate:
screenshot below
The hitbox of corner fences isn't the same as the collisionbox!The hit-box of corner fences isn't the same as the collision-box!
What I expect to see:
When the collision box of corner fences was fixed I expected for the hitboxWhat I actually saw:
The visual box (not hit-box: you can't bump into) is square shapedHow to recreate:
screenshot belowWhat I expect to see:
When the collision-box of corner fences was fixed I expected for the hit-box to conform to the new collision box.
What I actually saw:How to recreate:
screenshot below
What I expect to see:
When the collision-box of corner fences was fixed I expected for the hit-box to conform to the new collision box.
What I actually saw:How to recreate
:
screenshot belowWhat I expect to see
When the collision-box of corner fences was fixed I expected for the hit-box to conform to the new collision box.
What I actually saw
The hit-box of corner fences isn't the same as the collision-box!
How to recreate
screenshot below
What I expect to see
When the collision-box of corner fences was fixed, I expected for the hit-box to conform to the new collision box.
What I actually saw
The hit-box of corner fences isn't the same as the collision-box!
How to recreate
screenshot below
What I expect to see
When the collision-box of corner fences was fixed, I expected for the hit-box to conform to the new collision box.
What I actually saw
The hit-box of corner fences isn't the same as the collision-box!
How to recreatescreenshot belowWhat I expect to see
When the collision-box of corner fences was fixed, I expected for the hit-box to conform to the new collision box.
What I actually saw
The hit-box of corner fences isn't the same as the collision-box!
How to recreate
screenshot below*
What I expect to see
When the collision-box of corner fences was fixed, I expected for the hit-box to conform to the new collision box.
What I actually saw
The hit-box of corner fences isn't the same as the collision-box!
How to recreate
screenshot below*What I expect to see
When the collision-box of corner fences was fixed, I expected for the hit-box to conform to the new collision box.
What I actually saw
The hit-box of corner fences isn't the same as the collision-box!
How to recreate
Replicate the conditions of the screenshot below.
What I expect to see:
When the collision-box of corner fences was fixed, I expected for the hit-box to conform to the new collision box.
What I actually saw:
The hit-box of corner fences isn't the same as the collision-box!
How to recreate:
Replicate the conditions of the screenshot below.
I expected
if ashoot a TNT minecart with a flame bow, the TNT minecart would explode.Instead, the arrow destroyed the minecart. If you shoot it with a short pull-back time, the minecart catches fire. The minecart gets destroyed if you are in creative mode regardless of the pull-back time.
I expected I shoot a TNT minecart with a flame bow, the TNT minecart would explode.
Instead, the arrow destroyed the minecart. If you shoot it with a short pull-back time, the minecart catches fire. The minecart gets destroyed if you are in creative mode regardless of the pull-back time.
FlameBows don'tActivate TNTMinecartsFlame enchanted bows bows don't activate TNT minecarts!
I expected I shoot a TNT minecart with a flame bow, the TNT minecart would explode.
Instead, the arrow destroyed the minecart. If you shoot it with a short pull-back time, the minecart catches fire. The minecart gets destroyed if you are in creative mode regardless of the pull-back time.
What I expected to happen:*
What I expected to happen:*
What I expected to happen:
I expected
What I expected to happen:
Iexpected
What I expect
edto happen:
IWhat I expect to happen:
I expect for TNT
What I expect to happen:
I expect for TNTWhat I expect to happen:
I expect for TNT minecarts to activate when hit with a flame bow.
Flame enchanted bowsbowsdon't activate TNT minecarts!
Flameenchanted bows don't activate TNT minecarts!Flame-enchanted bows don't activate TNT minecarts!
What I expect to happen:
I expect for TNT minecarts to activate when hit with a flame-enchanted bow.
What actually happens:
TNT minecar
What I expect to happen:
I expect for TNT minecarts to activate when hit with a flame-enchanted bow.
What actually happens:
TNT minecarWhat I expect to happen:
I expect for TNT minecarts to activate when hit with a flame-enchanted bow.
What actually happens:
TNT minecarts don't activate when hit with a flame-enchanted bow. If you hit it using high power, it destroys the minecart. If you use low power, it sets the minecart on fire.
What I expect to happen:
I expect for TNT minecarts to activate when hit with a flame-enchanted bow.
What actually happens:
TNT minecarts don't activate when hit with a flame-enchanted bow. If youhit it usinghigh power,it destroysthe minecart. If you use low power,it setsthe minecart on fire.What I expect to happen:
I expect for TNT minecarts to activate when hit with a flame-enchanted bow.
What actually happens:
TNT minecarts don't activate when hit with a flame-enchanted bow. If you use high power, the minecart is destroyed. If you use low power, the minecart is set on fire.
Redstone wire running through a piston extends under certain circumstances. (see screenshots)
What I expect to happen:
I expect the piston to never extend just from having redstone running through it.What actually happens:
The piston extends under certain circumstances (see screenshots)How to recreate:
Build the devices shown in the screenshots.This is true with sticky pistons as well. This is not directional. (In terms of north, west, etc)
Quite quirky behavior as you can see in the screenshots.
Personally, I believe in all of these situations, the piston should extend.I'm not go
nnaeven try to explain all of these. Just look at the screenshots.What I expect to happen:
I expect the piston to never extend just from having redstone running through it.What actually happens:
The piston extends under certain circumstances. (see screenshots)How to recreate:
Build the devices shown in the screenshots.This is true with sticky pistons as well. This is not directional. (In terms of north, west, etc)
Quite quirky behavior as you can see in the screenshots.
Personally, I believe in all of these situations, the piston should extend.I'm not going to even try to explain all of these. Just look at the screenshots.
The base of farms in desert NPC villages are composed of dirt!
Description:
Falling into a shallow lava pool doesn't break your fall.What I expected to happen:
I expected a shallow lava pool to break your fall.What actually happened:
Falling into a shallow lava pool doesn't break your fall.Steps to reproduce:
1. Dig a one meter deep hole.
2. Fill it with lava.
3. Drink a fire resistance potion.
4. Fall from a great height into it.Summary:
Falling into a shallow lava pool doesn't break your fall.What I expected to happen:
I expected a shallow lava pool to break your fall.What actually happened:
Falling into a shallow lava pool doesn't break your fall.Steps to reproduce:
1. Dig a one meter deep hole.
2. Fill it with lava.
3. Drink a fire resistance potion.
4. Fall from a great height into it.
Falling into a shallow lava pool doesn't break your fall!Unlike water, falling into a shallow lava pool doesn't break your fall!
When destroying *non-blocks that are destroyed by fluids* ex. levers (besides air), by placing water or lava in the block, a breaking sound, and particles result.
Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
This bug is defiantly not intended
When destroying *non-blocks that are destroyed by fluids* ex. levers (besides air), by placing water or lava in the block, a breaking sound, and particles result unlike when fluids flow into the non-solid block that is destroyed by fluids..
When destroying *non-blocks that are destroyed by fluids* ex. levers (besides air), by placing water or lava in the block, a breaking sound, and particles result unlike when fluids flow into the non-solid block that is destroyed by fluids..
When destroying*non-blocks that are destroyed by fluids* ex. levers (besides air), by placing water or lava in the block, a breaking sound, and particles result unlike when fluids flow into the non-solid block that is destroyed by fluids.
When destroying non-blocks that are destroyed by fluids* ex. levers (besides air),by placing water or lava in the block, a breaking sound, and particles result unlike when fluids flow into the non-solid block thatis destroyed by fluids.*Destroying non-blocks that are destroyed by fluids besides air (ex. levers), by placing water or lava in the same block, a breaking sound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids.*
*Destroying non-blocks that are destroyed by fluids besides air (ex. levers), by placingwater or lavain the same block, a breaking sound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids.**Destroying non-blocks that are destroyed by fluids besides air (ex. levers), by placing a fluid in the same block space, a breaking sound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids.*
*Destroying non-blocks that are destroyed by fluids besides air (ex. levers), by placing a fluid in the same block space, a breaking sound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids.**Breaking non-blocks that are destroyed by fluids besides air (ex. levers), by placing a fluid in the same block space, a breaking sound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids.*
*Breaking non-blocks that are destroyed by fluids besides air (ex. levers), by placing a fluid in the same block space, a breaking sound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids.*
Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
This bug is defiantly not intended
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug may be related to
Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug may be related to
Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!
MC-18342IS ABOUT THE AN ITEM!Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!
MC-18342IS ABOUT THE AN ITEM!Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!
MC-18342IS ABOUT THE AN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you placeSteps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
Breaking non-blocks that are destroyed by fluids besides air (ex. levers), by placing a fluid in the same block space, a breakingsound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!
MC-18342IS ABOUT THE AN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you placeSteps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the *NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!*
MC-18342IS ABOUT THE AN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you place fluids in the same block space as a not-block that is destroyed by water besides air, a break sound, and particles result.Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the *NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!*
MC-18342IS ABOUT THE AN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you place fluids in the same block space as a not-block that is destroyed by water besides air, a break sound, and particles result.Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!
MC-18342IS ABOUT THE AN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you place fluids in the same block space as a not-block that is destroyed by water besides air, a break sound, and particles result.Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
Why would that be true?
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!
MC-18342IS ABOUTTHEAN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you place fluids in the same block space as a not-block that is destroyed by water besides air, a break sound, and particles result.Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT the fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!
MC-18342IS ABOUT AN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you place fluids in the same block space as a not-block that is destroyed by water besides air, a break sound, and particles result.Steps to reproduce:
1. Place down a non-solid block that is destroyed by fluids (ex. levers).
2. Place down water or lava in the same block space the block is in.
3. A breaking sound, and particles should result.
This bug is probably related to the bug of placing fluids inside each other.
TNT used to be pushed by water. Now it doesn't. It wasn't documented as a change. I consider it a bug.
TNT passing through portals should keep their momentum. Wouldn't it be really cool to shoot TNT through portals.
Please don't capitalize every word in a sentence. It is really annoying to look at. :~S
Hoppers are stone-type blocks even though they make wood-type noises while breaking them. This really is about the misleading noise hoppers make while breaking them.
I believe the noise hoppers make while you break them is a bug.
Confirmed.
Confirmed. I experienced this in the default texture pack. I doubt this is an intended feature. It is extremely confusing and misleading.
Confirmed in 13w18c.
My dog won't stop growling!
Confirmed in 13w19a.
Very annoying behavior. Not very usable in redstone contraptions. Should be fixed ASAP!
Device to replicate this:
! = Door/Trapdoor/Fence Gate
O = Redstone
+ = Block
8 = Button
!
+
OOOOOOO+8
Open the door/trapdoor/fence gate and press the button.
This bug is not fixed in the latest snapshot! I tested this and the item still disappears.
This bug is obviously causing much anxiety. Please fix this!
This bug is so awesome! I love watching the items bounce, bounce, bounce, bounce, bounce, bounce, bounce, bounce, bounce, bounce, BOUNCE!
There should be something that achieves this affect legitimately.
Confirmed in 13w19a.
However, I think we should be able to enchant horse armor and enchantments on the horse armor would function properly when equipped on a horse.
Confirmed.
They also graze underlava (This totally should be a real word).
BTW, don't you think the horses should generally graze less commonly? It makes leading horse(s) very difficult. The horse stops to graze and the lead breaks.
This 'feature' makes villages a total eyesore! I saw villages spawn over ravines. It totally messes up the paths and the buildings spawn with a base that stretches to the bottom of the ravine. It's stupid how many villages spawn that are totally, unrealistically, messed up!
It should!
This is a bug? I thought it was a feature to make our lives easier! LOL XD
O rly? I thought it was a feature to make our lives easier! LOL XD
Confirmed in 13w22a.
Perhaps a fix could be the addition of a specific tool for attaching leads to fences.
Confirmed in 13w22a
One randomly appeared in my survival world today.
Deleting the chunk via mcedit seems to fix it.
This bug somehow duplicates chickens. (This is a serious statement.)
Confirmed in 13w22a
Seems like a very obnoxious bug. I have probably a couple of those phony chunks in my world.
Very annoying behavior. It makes copying survival maps less ideal.
This entry is reporting more than one bug. I'm not sure if it is valid.
When this gets fixed, it needs to be publicized like crazy! Right now, people are accustomed to the water-fall safety this bug provides. If it isn't publicly known when it is fixed, so many people will die.
I think when you break them, you should get the wheat back as well.
This only happens under non-superflat world generation. This bug can occur in all three gamemodes, not just survival.
Confirmed in 1.5.2
@Treydun
Me too. <3
I've been experiencing this since forever.
You need to not be able to break item frames and paintings in creative mode with a sword since the functionality of not being able to break blocks in creative mode carries over to not being able to break item frames and paintings.
@Dylan Rivers
Your wrong. You can break blocks with improper tools in creative mode. Heck, you can use your fists!
(This isn't meant to make you feel bad at all.)
Confirmed in 1.6
Why would you have to break paintings or item frames with swords in creative mode? When you would be using swords in creative mode, you would be killing mobs, not destroying blocks, or entities like item frames or paintings.
First, the particles aren't always dirt particles. I did some testing and, it seems to depend on what block is underneath the block you broke. In the second screenshot, the extra particles seem to be stone particles.
Second, the block you're breaking doesn't need to be a coal block. Other blocks like gravel do the same thing.
Third, I believe those extra particles are for effect. If my statement is correct, this behavior works as intended.
Lastly, you are soooooooooo observant to notice this.
It's not doing it for me under normal conditions.
What are the steps to reproduce?
The mods are not reading this bug correctly. It is the opposite of
MC-9568! Not a duplicate.@Phillip Leon
What are the steps to reproduce? I couldn't get this to happen occur under normal conditions.
You are not reading this bug correctly. The bug is that particles and a breaking sound results from placing water or lava in the same block as the non-solid block that is destroyed by water.
BE SURE TO READ THE BUG VERY VERY CAREFULLY.
This bug is the NOT fix of
MC-18342. ITS ABOUT THE PARTICLES AND THE SOUND EFFECT!MC-18342IS ABOUT THE AN ITEM!This bug is definitely not intended since fluids flowing into the non-solid block that is destroyed by fluids results in no sound effect and no particles.
This bug is when you place fluids in the same block space as a not-block that is destroyed by water besides air, a break sound, and particles result.
Breaking non-blocks that are destroyed by fluids besides air (ex. levers), by placing a fluid in the same block space, a breaking sound, and particles result unlike when fluids flow into the non-solid block that's destroyed by fluids. Defiantly some weird behavior.
@Chip Seraphine
I don't think many people who built a mob grinder that depends on this bug not existing before 1.4.3 wouldn't fix their mob grinder to accompany this bug after a year of this bug not getting fixed, unless they gave quit playing Minecraft.
Confirmed in 1.6.2
In 13w41b, the seed, "13" has this problem.
Confirmed in 13w41b.
I cannot reproduce this in a flat swampland world with one layer of water.
@Johnathan
Most likely, slimes are jumping into the water and getting trapped since they can't jump. If you destroy all the dry land in your swamp, the problem will resolve likely resolve.
I believe this is intended.
@Markku
I agree that
MC-7294is probably a major cause for this issue.MC-31380is an example of how villages that are naturally generated are useless to villagers commonly.@raz
christian? :3