Sadly, no. I wasn't prepared for this to happen at the time. When I saw (in the anvil) that there would be nothing different about my tools, I thought it was a graphical glitch..
At this point Java(w) doesn't even want to load up the game. I looked in task manager and sure enough, I find that it still exists. The only way I get it running Is by closing "Minecraft Launcher.exe" after is launches. (There is always two which are both for functions but they don't end their task once its supposed to be done. Also I have to end the one that's heavier on Kilobytes.)
Should I Use Pastebin or can I just paste it here?
I didn't mean that they'd be broken, i meant that they would get submerged.. but yeah if mojang wanted to remain consistent i guess they gotta keep it this way
I Got Really Lucky Using The Taskbar Getting A Modded Minecraft-Client up, But If I Try Any Other Version It Crashes
oh..
both in the latest snapshot
I said that on one world, the structures are there, and on the other, it wasnt there.
Wait how is mine a duplicate?
It kinda does, yeah. Except the enderman that chased me lost interest after about 200 blocks of running. But in both cases, time was most likely a factor.
probably less, because it went out in 3 seconds.
It almost looked like it went out at the speed of a wooden pickaxe
Notice I Said "Appears"
I gotta say, I'm happy it doesn't apply to stairs, otherwise my entire mine would've be flooded.
I should also mention i got the book from fishing.
You see the disconnection?
no, i talking about a graphical glitch at the corners
let me see if i can re-capture it.
I just realized I included Y cords. Man I'm a rookie :/
Ok Thank you.
Looking back at it, I don't see this much as a bug, but more so a minor inconvenience. Considering that most modern maps use resource packs to customize the game, it's a minimal flaw/side-effect from a design perspective and probably not worth the effort to bother fixing. In all honesty, having it cap off at .5 is more helpful in some cases, *such as when trying to increase a sound by an octave. Because of this, it almost feels to be intentional, or perhaps just a side-effect.
Revamping the playsound command would be a much better approach, as fixing this bug would break most sound-effects in projects regardless, which is a main concern when approaching these sorts of problems.
*Note that this works because of a 1:2 ratio.
Ex. Playing a pitch of .7 is an octave below the pitch of 1.4.