Videogamer555

That's absolutely correct. Sadly, I think MS sees the collection of data as a benefit to their company and probably thinks that as a massive company their expensive lawyers can find loopholes in the law, basically making them untouchable. In fact, I believe that MS actually KNOWS what they are doing is illegal, but literally doesn't care, because they think they are too big to lose in court. They disabled the snooper function only until they felt they could be sneaky enough to bring it back without notice, or until their hubris finally got strong enough they finally thought they were truly untouchable. So I hope you actually do follow through and file the report though, and hopefully the courts in the EU will sue MS and win. Until MS changes it back to being GDPR compatible, I'm just going to not play the latest version of Minecraft anymore. I don't want personal information to be on servers. Even servers of big corps like MS's internal servers where the data is held are not unhackable. A smart enough hacker could eventually hack them and steal the data. And if all that player data does get leaked to the dark web, then all the players are screwed. Well I wont be one of them. I'll not play any version of Minecraft that either has it permanently enabled or that has it enabled by default (even if switching it off is possible). Because all it takes is ONE TRANSMISSION of telemetry data to be sent, for MS to now have a HUGE trove of personally identifiable information on you, that you can only get rid of by literally buying a new computer (so the telemetry data about your computer is now obsolete).

UPDATE:
I finally found how to post there, but it wasn't easy to find.

ORIGINAL POST:
I looked there, and there's no place to add new feedback. It just gives me 2 buttons to go to either the help center or the bug reporting. The bug reporting is where I am now. The help center is just an FAQ with a bunch of answers to various specific questions that people might ask. I can't find any place to submit actual feedback.

It's not a duplicate. It provides more context. It explains that it is, and why it is, a violation of the laws of at least 2 separate jurisdictions (the European Union and the US state of Califorina). I'm simply posting here to notify Mojang/Microsoft that the current state of the game is one in which a crime is being committed, literally.

I'm also posting here to notify them that I do not consent to be tracked, and therefore I am a VICTIM of the crime they are committing.

"Also, did you just admit to a 'feature' breaking the rules of GDPR?"

Yes. That's exactly what they did. Not only is the snooper reactivated an intended thing, it seems that also the inability to disable it is intended. Since being unable to disable it is a blatant GDPR violation, it appears that Microsoft is literally BRAGGING ABOUT COMMITTING A CRIME!

Does this mean that the snooper feature has been removed completely from current versions of Minecraft?
What about older versions that still have the feature in the game? Can they still connect to the snooper URL http://snoop.minecraft.net ?
In the web browser, I can't access this URL, but maybe that's because the browser is using GET, while that server is expecting POST as the request type.
Can you confirm if the snooper server itself has been taken offline?

I don't remember this glitch on previous versions of the launcher. I think it's just in the current version.
One possible solution would be to set go into the JSON files and set the releaseTime field of the newer version (higher version number) to one second after the releaseTime of the older version (lower version number).
Alternatively, use 7Zip to open the JAR file itself (do this for each JAR file who's date is the same but time is different), and then look inside its META-INF folder. Look at the "modified" dates/times of the files in META-INF, and notice the time (accurate down to the minute). This is the date and time that that version of the game was compiled. Use that date and time for the date and time info for the release time field in the JSON file for that version. Do that for both of these JSON files (the one for 1.4.5 and the one for 1.4.6). These changes may also need to be made to the main version_manifest.json file.

Unfortunately, this is not something I can do, as any changes to JSON files done by the user are automatically overwritten by the launcher when starting the launcher, and the versions_manifest.json file is never present on the user's computer when accessed by the launcher (only present on Mojang's server). Therefore, I can't do any JSON fixes. That's something that Mojang will need to fix.

Yep Gofri. That is correct. It doesn't work at all. No launcher works now with the sound. The reason is the game itself looks in .minecraft\resources, while the actual resources get downloaded to .minecraft\assets\virtual\legacy which is not where the game is looking for them. Also the folder structure that the game is expecting is slightly different than the one provided in the virtual\legacy folder. Also some of the sound files have been renamed (new versions of some files using an underscore, while the old versions of the same files used a space, in their filename). I only wish that whoever is in charge of running the Minecraft resources server took more interest in fixing this.

Interesting that the LaunchWrapper could supposedly fix this. I thought that the URL for downloading resources for the game was hardcoded in the Java class files in the game. This means that the game itself makes a direct connection to minecraft.net rather than telling the launcher to make this connection.

As far as I know, there's no way for the launchwrapper (or any other Java application) to be able to intercept such a direct connection and redirect it to any other location.

I don't think that you can redirect Minecraft to look for new resources, without actually modifying the game's code. From my understanding the resource URL http://s3.amazonaws.com/MinecraftResources/ is hardcoded into the game's class files (at least in older versions). I would like game's code to remain intact, so that it is the same as it was when it was released, so that it can be seen as a museum of old versions. To alter that game's code would put a blemish on the originalness of these old versions. It would be like an artist trying to fix a famous painting by painting details into it that they thought the original artist should have put in. That would destroy the originalness of the artwork. And yes, Minecraft is artwork. I believe the best fix is to simply reactivate all the files pointed to by the URLs in the resource index http://s3.amazonaws.com/MinecraftResources/

@Petr_Mrazek is it not possible to simply re-activate the old links? That way the old versions of Minecraft can work again while you migrate your resources, instead of leaving old versions of the game without sound while you migrate your resources.

I mean the index http://s3.amazonaws.com/MinecraftResources/ does exist. There should be no reason for the links referenced by that index to not work. Only thing I can think of is that the actual files listed there have been deactivated (but hopefully not removed). The easiest fix is to just reenable those files, while you copy them to the new server.

Why hasn't that been done yet?

Despite reports here that the bug still exists in version 15w49a, I've discovered that on my PC that it was resolved in 15w47c, and has not come back in 15w49a. Of those who report that it's still not been resolved, I'm not sure what version of Java you are using (1.7 or 1.8, or something even newer), or what version of Windows you are using (XP, Vista, 7, 8, 8.1, or 10). I have Windows 7 Home Premium with SP1. It is the 64bit version of Windows. I'm using Java 1.8.0_51, and it's the 64bit version of Java. Double-tall grass no longer flashes the top segment as a flower when it is destroyed for me.

I've just updated the description of the issue, because the bug wasn't triggered by what I originally thought it was. But it still appears that a bug is present, just that what triggers it is different that what I thought originally.

It's only a PARTIAL duplicate. Notice where I said that I believe it may have been partially fixed, but not completely fixed. The intermediate state of it being partially fixed, constitutes its own bug, which deserves to be reported separately, I believe.