Minecraft Wiki talk:Issues/Weekly 12w38b

Sound quibbles
I'm not flagging this as an annoyance just yet, but the new sound for skeletons taking damage makes it sound like they're made of plastic. It also isn't likely to 'work' convincingly when a skeleton takes damage from lava or drowning, unless there's different SFX in those cases which I haven't heard yet. Is it just me that doesn't like this change? --Simons Mith[82.69.54.207] 01:41, 21 September 2012 (UTC)
 * Neither the sounds nor the new sound engine are finished yet. It won't stay like this. Also C418 accidentally swapped some wromg sound files. --☺ Sven ? ! 12:47, 21 September 2012 (UTC)

Calling the latest weekly 'Weekly' is a Mistake
Unless the admins are reliably able to create the new page for the weekly build within 5-10 minutes of it appearing, it's highly likely you'll get a bug or two from the newest weekly unknowingly reported on the old weekly page. And it's very easy to overlook the fact that you aren't reporting a bug on the right page. Can we change things to consistently call the weekly 12w##a or whatever, and have the weekly as the alias, rather than the other way round. That way you can tell from the URL whether the issues page is the right one. I know this isn't a perfect solution either, but it is a little better than the other way round, which is even more error-prone.--82.69.54.207 18:46, 21 September 2012 (UTC)

Where to report bugs discussion
Cut from bug 'undefined Pistons still don't have their complete push ability back...'. this has no bearing on that particular bug, so I've moved the whole off-topic part of the discussion below:--82.69.54.207 22:45, 26 September 2012 (UTC)


 * Wrong section. This should be in the issues page (1.3.2), Not a snapshot.
 * if it isn't fixed in this snapshot and it's a bug occuring in this snapshot. please clarify why it shouldn't be here--League 19:46, 22 September 2012 (UTC)
 * Yes, a cardinal rule of bug reporting is that you always report a bug where you encountered it, not in some other version that may or may not have the same problem. For this reason I'm striking through the several cases where the GP has put in this incorrect info.--82.69.54.207 17:00, 23 September 2012 (UTC)
 * he is actually right, posting a bug that is in game since 1.3.2 in every snapshot doesn't make any sense.
 * Why? The bugs page should be a comprehensive list of bugs in the version it's for. There is usually absolutely no indication of whether bugs have been fixed in a previous version, as Mojang don't have the time to respond to each and every bug posted. If you didn't include a long-standing bug in future versions where it still exists, then there's no way to tell whether that was the last version to have the bug. More importantly, Mojang probably only checks the most recent version's bug page for things to correct - if we started excluding bugs just because they're old, they may simply never get fixed. --WolfieMario 19:21, 26 September 2012 (UTC)
 * Grandparent poster, no, he or she isn't right. The bug reporting guideleines are clear. The very first instruction on the top of all issues pages says "This page is for issues that: 1. Are found in the version of the game specified in the article's title."--82.69.54.207 22:45, 26 September 2012 (UTC)