Map is freezing after logging out and back in to a game

Duplicate of MC-31731, please use the search function to see if your bug has already been submitted. Currently over 47% of tickets are being resolved as duplicate.

This is not a duplicate of MC-31731. This has nothing to do with item frames. Please use the "reading comprehension function" to see if the bug you're viewing is the same as another bug before commenting (see how condescending that sounds?). Hastily labeling reports as duplicates does not help to serve the wellbeing of Minecraft. From my time searching this issue, I see I am not the first one to complain about this behavior from mods.

I did use the search function before posting this bug. The problem is that people use different terminology to describe issues. The solution to this is not to reply with a condescending comment saying please search before posting. The correct solution is to better manage the summaries of bug reports so that they are easier to search. It's likely a large portion of these 47% duplicates is due to crappy summaries and search perameters, and not because users didn't search.

Also MC-32480 is a duplicate of this bug. But since that one was not erroneously closed, let's just say this is a duplicate of 32480 and combine our efforts there.

Insulting the mods will not get you anywhere, and neither will your frustration. People complain about the mods anywhere you go, no matter what. If they don't like a resolution, they think things should be different, or they are simply frustrated by the issue before them. If you want to provide appropriate information about issues you run across please do. Just because your ticket is resolved as duplicate does not mean the issue will not be addressed in the parent ticket.

This ticket was not resolved "hastily" but was resolved as duplicate as the core issue is the same. MC-32480 I linked as RELATED as one was referring to SMP only the other to single player only, the item frame is not the core issue, but others have been linked to it as it was the first to be opened and subsequent related tickets may be closed as fixed once the parent ticket is, all duplicate tickets are searchable and lead back to the parent ticket. Your ticket related to both SMP and single-player, therefore one of them had to be picked. Since both SMP and single-player have been reported, then your complaint is a non-issue as a ticket is still open regarding the exact same thing your report does.

I am also one of the mods handled MC-32480 and related tickets. A simple search for the word "map" found all of the duplicates. Yes different terminology is used, and yes we do update summaries so they can be found easier, but it is up to the end user to search for the correct search terms, or the ticket is closed as a duplicate.

A simple search for the word "map" comes up with 4784 responses. Filtering out the closed and resolved bug reports leaves 1416 bug reports, none of which was actually a duplicate of the SMP issue I reported at the time, not that I was going to take the time to parse through them all. It's a completely valid stance if you believe people should parse through that many bug reports to find a duplicate, but I think you're being entirely unrealistic. I did try other searches for word combinations, and found no duplicates either. I don't know if you get paid or not, and I hope you do, but at some point there gets to be far too many bug reports around to realisticly expect users to manage duplicates, and it becomes the job of the mods to handle it, as you're obviously far more familiar with the currently open bugs than any single bug reporter.

And thanks to your latest response, I now understand why you closed mine and kept open a newer bug, but unfortunately that took a second response from you. If you would have explained that there were two other duplicate issues open, one dealing with single player and one with SMP, and that you wanted them seprarted so you kept those open instead of mine, that would have worked nicely. Instead I received a condescending canned response about using the search function. This is why I became a frustrated user. I hope you keep this in mind when responding to future bug reports.

You said it yourself, there are many bugs reported on a daily basis, many of them duplicate. Submitting a custom reply to every single ticket is unrealistic if valid issues are to be found among the garbage. Hence our standard responses.

All you had to do is ask why it was closed as it was, or provide additional information showing why it was not a duplicate instead of becoming enraged. We as mods are not perfect, and I myself have reopened tickets, that once additional information was provided showing a valid, non-duplicate issue.

We too are human beings and enjoy playing Minecraft, that's why the mods are here; to help resolve issues and provide valid tickets to the devs so they don't have to wade through every ticket.

Well I would like to recommend that you revise your canned response. I too love Minecraft and I want to help it anyway I can, and I really think this might alleviate some of the frustration on this site, hopefully saving you time from responding to such people. I appreciate you taking the time to respond to me. I think we can leave it at this.

Example Response:
Duplicate of MC-31731. Please review the Issue Links to see the duplicate/related tickets. Currently over 47% of tickets are being resolved as duplicate. If you did not use the search function before posting, please make sure to do so in the future to help cut down on the clutter. If you have reviewed the duplicate/related tickets and have additional information as to why this is not a duplicate, please comment and it will be reviewed. We appreciate your help!

Actually I like how you worded some of that. I don't believe we will use the entire line, as nobody will read it (we try to keep it short) but I will look into rewording it. We realize not everyone doesn't search, it's more of an informational message for those who haven't.

As my final word I would like to say...

Duplicate of MC-32480 and MC-31731 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.