Ryan Ledvina

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!

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.

I currently have no framed maps on the server I am testing with, though I did at one point frame a map and since removed it. I created a second test server, where the only thing I did was to create a map (with the give command) and test this bug, and the issue still happens. Also please note that a server restart alone will not fix the issue for me, so that's not the same as MC-3416 either. I have to restart both the client and the server to fix the issue. I can't explain the difference you and I are seeing in the fix, but the description of the issue sounds to be the exact same.

I've had different experiences with fixing the issue. In my testing, it requires both a server and a client restart to fix. I have tried restarting just the client or just the server, but the map issue persists.

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.

I've found Savanna Plateau M in multiple seeds now, and they're all around 200 high in height. I'm not sure it's intended, but I really hope they keep it, as it looks awesome and certainly worthy of being a rare variation.

However, it's not the case that it's being affected by the amplified code, as this biome attempts to be much higher when you do an amplified version of the same seed, except that the build height limit prevents it from going above 256. You end up with a very flat top of stone at 250. Raising the build height limit does not change this. If the Savanna Plateau M height is intended to top out at about 200, then they need to fix it so it can generate above 250 on amplified when the building height is raised above the default.

One of the seeds I've been using: -1236150180
Coordinates: x:10700, z: 11600

I encountered the bug in 1.5.2 just now. Restarting the server does indeed bring back the white cursor. However the problem comes back not long after restart. I first saw the issue right after I created my second map. The first map lost the cursor, but the second map worked fine. I had the first map in an item frame in my base, and that may be part of the bug. I also noticed that the green cursor did not disappear when I removed the map from the item frame until I reset the server.