Adam Ekstrom

Thanks for posting the screenshots, FVbico. That'll do in place of a Youtube video, sure. Thank you.

To Anon Ymus: Yes, I am aware of the fact that the radius centers on the command block. Well, what am I doing wrong then, if I am doing it wrong? Please help. I have no trouble with it in 1.7.4, but it won't work in the 1.8 snapshots. Why would that be?

I would be grateful if anyone else CAN confirm this bug. It sure seems to be the result of a bug, not user error. I checked the commands, and they work for me in 1.7.4, but they don't work in the 14w02a snapshot or above, up to and including snapshot 14w26c, the most current snapshot as of today, June 30th.

Reply to FVbico's comment:

Are you in one of the snapshots between 14w02a and 14w26c? Also, if you can't confirm it, please record your attempt and post it as a Youtube video, and put the link to it in the comments for this bug report, so I can see what I might be doing wrong if you are doing it the right way. Thank you!!!

I suppose it's possible that Mojang changed the argument format in the snapshots, and that resulted in me doing it wrong, but until I see what you were doing, I won't know for sure.

I have the same problem using almost any command, and any arguement. They worked in the older versions, but this bug impairs players' ability to use commands in the snapshots. I can hardly do anything involving arguments. The only thing I found that works is if I just write the coordinates, followed by the radius, without actually labeling the arguments, like so:

@p[682,10,43,r=1]

And sometimes even that won't work either. Relative coordinates don't work at all. The same result happens every time I try to specify arguments, the last output in the command block is "The entity UUID provided is in an invalid format," even though I have it perfectly written, and I've checked it for accuracy. This happens almost every time, and with almost every command. It makes command block work almost impossible. Please fix this bug soon, Mojang.

These are the screenshots I took. The ones that don't have the messed up hitbox visible are the ones that were in between the flashes of abnormality in the pattern of the glitch. That pattern is:
normal...messed up... normal... messed up..., etc.

Thank you! I was able to fix that part of the resource pack, and now it works perfectly!

This is what Item frames look like that have maps in them in 14w04b. It renders them without the actual map being visible.

This bug is a pain! Confirmed in 14w04b. The maps are invisible in item frames.

Confirmed for 14w04a!!!!! It's rather annoying.

Actually, I can't reproduce it myself, and I'm the one who posted this bug. It must have just been a temporary glitch. Now when I try it, the "Blocks" volume can turn off Fire's sounds. Huh. Sorry for the false alarm, it seems.

Still present in 1.8's snapshot # 14w02c I don't know to add that to the "affects versions:" list.

To Dakotah Intriglia:
Many of the people who commented on this issue here suggested the exact same solution as you did, myself included. Unfortunately, Mojang usually has a "we'll do it in our own sweet time" attitude.

Why is it intended to stop background music when gamemodes are changed? It makes sense to pause the music when the game is paused, but I can't think of a reason why gamemode changing would need music ending as part of it. I'm not trying to be mad or rude, I was just curious as to the motivation for saying that this works as intended in that regard.

Sorry. I searched for a duplicate of this issue before creating it, but I must have used the wrong keywords, instead of the ones for the duplicate of this. I know that over 50% of issues are resolved as duplicates, but I wasn't able to find it, as I said.

This is the crash report that was made when I most recently attempted to trade with villagers in 1.7. It may or may not detail the actual bug of trades with villagers failing. I am not sure because the crash report is steeped in programming language of which I have little to no comprehension.

Confirmed for 13w42b snapshot. This bug happens far less often when I use 1.6.4 than when I use any of the 1.7 snapshots. It crashes any time when I try to trade with a villager in 1.7 snapshots. This cripples the snapshots, in my opinion, because I use trading so often.

Confirmed.

Confirmed for 13w24b. It's annoying to have your most recently played worldsaves at the bottom of the list!

I can confirm this bug. I ran into the same problem myself in 13w24b. I converted six 1.5 texture packs from the 1.5 version by using the Texture Ender, and then tried to load them in 13w24b, expecting them to load as normal. They didn't load at all, but they did make a few things like grass and torches look weird. I tried to select the resource pack on the selection screen, but it just lagged like it used to when loading the old texturepacks, but then the the default was still shown as selected (had the white box around it.) The resource packs really don't seem to be as ready to be released as Mojang thought. This bug makes me hesitate to play this snapshot. Default textures get sooooo boring to look at, and in 13w24b, that's the only textures that will load because of this bug! I've tested this in 13w24a as well. It loads resource packs fine (other than the fact that the menu for them is labeled "Texture packs" rather than "Resource packs", but that doesn't affect their loading), but 13w24b doesn't load them at all!!!

I can confirm this bug. I ran into the same problem myself in 13w24b. I converted six 1.5 texture packs from the 1.5 version by using the Texture Ender, and then tried to load them in 13w24b, expecting them to load as normal. They didn't load at all, but they did make a few things like grass and torches look weird. I tried to select the resource pack on the selection screen, but it just lagged like it used to when loading the old texturepacks, but then the the default was still shown as selected (had the white box around it.) The resource packs really don't seem to be as ready to be released as Mojang thought. This bug makes me hesitate to play this snapshot. Default textures get sooooo boring to look at, and in 13w24b, that's the only textures that will load because of this bug! I've tested this in 13w24a as well. It loads resource packs fine (other than the fact that the menu for them is labeled "Texture packs" rather than "Resource packs", but that doesn't affect their loading), but 13w24b doesn't load them at all!!!