Minecraft Wiki talk:Issues/Weekly 12w15a

More pick block bugs

 * When you use pick block on tall grass and fern blocks it gives you the bead bush version of grass.
 * If you select a full block made of half slabs of any type(Wood, Brick, Cobble, etc.), it gives you a double half block of stone slabs.

And while i was at it a noticed a few of the previous pick block bugs were fixed(like selecting grass gives you grass and not dirt).

Feel free to add more pick blocks bugs here because i know i have only found a few things.Sickma 04:17, 13 April 2012 (UTC)

Unknown crash.
There is a chance when I use the seed 666 the game crashes after a few seconds, tested on 2 PCs, there is a error report found on .minecraft/crash-2012-04-14_12.05.13.txt, heres the error report. It appears to be something to do with falling blocks.

http://dl.dropbox.com/u/67688033/crash-2012-04-14_12.05.13.txt

Magmar452 13:11, 14 April 2012 (UTC)

Carrying bugs forward - Policy?
Some bugs and annoyances - such as the unbalanced enchantment system annoyance (which I quite agree with BTW) are being religiously carried forward to every new release to which thay apply. Others, some equally long-standing, are left behind on whichever release they were first reported in. Carrying all bugs forward would allow Mojang to just refer to the bug tracker for latest release, but would require someone on the Wiki to collate all the old unfixed bugs, deduplicate and repost them with each new release - quite a bit of work.

Another alternative might be to create a Frequently Reported Bugs and Annoyances page, or an Unfixed Bugs page and store the constantly-recurring ones there.

Which way's better? The current halfway house, with some bugs carried forward, others ignored and left behind, seems to be the worst of both worlds. You can't even say that if a bug keeps getting reported it must be annoying a lot of people, because some of the reported-once bugs are just as serious.

Do Mojang have an internal bug tracker, into which issues are copied so they don't get overlooked, or is this Wiki really their prime bug tracker? If so, EW!

Could we define a more consistent policy on how or whether bugs are carried forward from one release to the next? 82.69.54.207 14:12, 14 April 2012 (UTC)


 * I agree that bugs getting lost is a problem. I think we should keep a single known bugs page (or one for release and one for new-in-snapshot bugs), and institute a policy to cut down on the "this item is useless"-type "bugs", and otherwise generally keeping the list clean. Personally, I've archived my 'favorite' bugs on my user page so that I can copy them into new bug pages — but I don't get around to that promptly enough to get them noticed, so far. —kpreid 17:08, 14 April 2012 (UTC)


 * Hah, I personally believe Mojang should definitely set up a proper bug tracker, especially now that they have many more employess working on minecraft. However, since they are unwilling to do this, the next best thing is to keep a lovely clean list of currently known bugs on the wiki and hope that they still check them.... :/


 * Until now I have believed that the serious bugs will be carried forward simply due to more users thinking about it. To certain extent this is true, and I am happy to leave it like this


 * What I find slightly more aggravating is that many users have taken to copying over a long list of bugs without bothering to check that they still exist in the latest snapshot. These should AT LEAST be vetted on the talk page first. For example, in this snapshot Calinou has created the "Multi-player related" section from a long list of bugs that was present a few versions back. I know its pretty likely that most of these bugs still exist, but its still possible that some of these are bogus.


 * So, for my part, I would like to suggest rigorous use of the discussion for confirming the existence of old bugs. --Mattrition 10:48, 15 April 2012 (UTC)


 * Could we get a Wiki admin to officially ask Mojang if there are any changes or refinements to their bug-tracking preferences? And post their revised preferences, if any, here? For that matter, how do they make use of the present setup, and how could we improve it? This is an important enough area to be deserving of their direct input. I mean, surely the Bukkit guys had a saner bug-tracking system than a Wiki for heaven's sake - perhaps we could we adopt that? Only catch with tracking bugs in something like, say, Gna is that the bug list still needs curating, and probably by a Mojang employee at that.82.69.54.207 12:43, 15 April 2012 (UTC)


 * Is there a "Fixed Bug" page or list anywhere? If not, would it help to have one or have some sort of "Bug Checklist"? Or maybe a new snapshot page setup with 3 main sections like "New Bugs/Annoyances", "Pre-existing Bugs/Annoyances", and "Fixed Bugs/Annoyances" Sickma 19:49, 15 April 2012 (UTC)

Enchantment System
Another proposal: Possibly relocate the complaints about the Enchantment system to a new Issues\Enchantment System page?82.69.54.207 15:15, 14 April 2012 (UTC)