quartz

Sonic: what version were you using when you [partially] confirmed?

More playing around and testing stuff. I've updated the description with a second edit. I don't know what the right procedure is in this case.

The attached resource pack has two textures in it. "beacon_beam.png" is the rainbow one that doesn't show up at all, whereas "beacon_beam_slices.png" is the white one.

OK, well, at the time Kumasasa responded with "Fixed in 1.8.1-pre1" MC-1279 was listed as being fixed in pre1, not future-1.8.2, so I'm not sure what's going on there.

As far as confirmation goes, I forgot to attach a resource pack with the cut up texture I was using (the problem is still there with the vanilla texture, but hard to see). I'll attach that now and maybe it'll be more obvious (it's worth mentioning that the flickering garbled-ness is much more apparent when actually playing the game, you can't really capture how bad it looks in a screenshot).

Also, being a texture/rendering issue, there's a good chance it might be hardware specific.

Still present in 1.8.0

Note: All of my worlds that feature this are far too large to upload here, so I had to do some more digging. After reading MC-1279 in more detail, it mentions that the beacon slow rotate issue is due to the world's time. I realized that in my worlds there was a correlation between world age and how garbled the texture got. After some more investigation and testing with NBTExplorer, I confirmed that high values on the 'time' parameter caused the problem. For the purposes of this bug, I created a superflat world and manually set 'time' to 19999999 (and took a screenshot).

As far as dupes go, MC-1279 is about how beacon beams' rotation animation gets progressively slower and more choppy with world age. I have never seen slow or choppy beams in any of my worlds, instead the beam texture gets progressively more distorted. Whatever fix was put in for MC-1279 didn't resolve my issue. While these two bugs are definitely closely related, they're not exactly the same thing, however if you want to reopen MC-1279 and then roll this bug into it, I'd be fine with that.

OK, I've uploaded a pic showing that this still affects pre2, and attached a world. Please reopen.

This is NOT fixed in pre1 or pre2, nor is it a dupe of 1279, please reopen.

This bug should be updated to reflect that it still applies to 1.8

It's definitely related, but not sure about a dupe. 65040 says that that bug requires 'constantly loaded chunks', except I'm not sure that's been the case for me. I'm pretty sure I got this to happen a couple times on superflat worlds where I had teleported away from the initial spawn point to [0,100,0] on a fresh world with nothing else in it besides a few inert blocks with a map on it. I'm not sure what would be keeping those chunks loaded in such a situation.

Ok, so if things are messed up when opening in 1.7.x as well then we can say this is a bug that's been around for a while and not new to 1.8 at least.

If you have the time, make a bunch of copies of the pre-converted world (from backups) and try opening them with progressively older major versions (1.6.x, 1.5.x, 1.4.x, etc) and see how far back you have to go before it loads up correctly. That will probably help them narrow down what code changes were going on that started the problem. (It's probably worth trying 1.0 or 1.1 first though just to make sure it isn't a beta vs official thing).

Well, because I have no idea what the intended behavior is here. In MC-69399, Ely Golden states that command+pickblock doesn't do anything on his machine. I'd rather someone from Mojang make a statement either directly or implied based on how they fix things. People have a responsibility to only add things to a wiki they believe to be correct, so I'm not going to write up something based on a half-assed guess.

I'm well aware of Reddit thanks. A warning that you're going to lose information isn't exactly a "feature request".

If you have a backup of the world you can open in 1.7.x, you could try adding and removing an item in each chest to see if it 'rewrites' their NBT data into something 1.8 can deal with.

Do you still have a backup of that one? Can you copy it and open it in 1.8 again and see if the problem is reproducible? You're probably going to have include a link to download the world save before anyone will be able to figure out what went wrong. It's probably also worth generating a forced crash report and attaching it here too.

When you say "beta", do you mean BETA beta from like three or four years ago, or one of the 1.8 pre-release snapshots from a month ago?

If you mean the former, 1.8 has a completely different method for handling world data (specifically tile entities). Worlds saved in 1.8 aren't even backwards compatible with 1.7.X. It's quite possible that the new code doesn't even understand a world save from that far back and may have corrupted something. If you have backups of the worlds frome before you opened them in 1.8, try instead opening them in several older versions in order up through 1.7.x before finally trying 1.8 again.

If you're instead referring to a pre-release snapshot, one or two of those had a major bug that corrupted tile entities. Again, restoring a 1.7.x world from backups and opening it in 1.8-release should be fine.

@Ely
This bug wasn't technically a duplicate when you reported it, the mods just decided to roll up all of the different Mac keyboard bugs into one place so it's easier to deal with. Jira doesn't have a way to mark bugs as being merged together, so they had to pick one bug as the parent and mark all the others as duplicates.

FWIW, after reading the other bugs referenced here I got and idea and tested; I discovered that command and control are swapped on my Mac. Control+pickblock does nothing, but command+pickblock gives me the NBT data. There's a discussion worth having about if this is the correct behavior or not, which I wrote up in MC-72697

So, after reading some of the stuff referenced in the other bugs, it looks like it's actually COMMAND+pickblock on my machine, not control+pickblock

Hey Kumasasa (or any other mod):
If you're going to roll up these issues into one entry, it would be beneficial to merge the description as well as the title so whoever tries to fix this doesn't have to read five six+ other bugs to see everything that's broken.

I also think the title should be changed to something cleaner, like "Modifier keys on Mac glitchy or swapped", since it looks like it's an issue with the bucky keys in general and not copy/paste/pickblock specifically.