Minecraft Wiki talk:Issues/Weekly 12w36a

Possible Duplication Bug
I would like some confirmation on this bug, just making sure other people can reproduce it.

Send a Minecart Chest with an item through an End Portal. The Minecart Chest will break and drop its items. If the player goes through the portal, The Minecart chest appears in the End, and has all of its items still in it. The items in the chest can somehow be duplicated infinitely, and in the case of blocks, can be placed and crafted. In some cases, tools will instantly break.

It is much easier to explain with a video, so here is a link: http://www.youtube.com/watch?v=Br4N-tZIFP8 --Lapppy 02:17, 7 September 2012 (UTC)

Blocks joining to other blocks inappropriately
Original bug+comment:

a Repeat of older bug, plus new info: Glass panes join to leaves, which is illogical in my view, but won't join to step blocks, which is a pain, especially when you're trying to put windows in a roof. Glass panes also join to bookshelves - also illogical. I don't think glass should join to dirt, sand or gravel either. How would you get a seal on such a join? Fences, OTOH, could be dug into the sand (or whatever) and could reasonably expect to find themselves placed next to sand, dirt etc. under normal circumstances. It seems that what joins to what needs to be hand-tweaked slightly; a simple 'joins to any full-sized block, transparent or not' algorithm (which is what glass currently seems to do) produces some odd results. --82.69.54.207 01:34, 7 September 2012 (UTC)
 * This isn't a bug, downgrading. If in your opinion the game shouldn't do something it is, that's an annoyance. I agree that it could be an inconvenience when putting glass next to steps, but it's the way the game is, and everything can't just be changed for what you feel glass should and shouldn't join to. Bookcases are whole, opaque blocks, so there's really no reason for it not to connect to them. --Keithicus420 14:53, 8 September 2012 (UTC)
 * I disagree with your downgrading this, for several reasons. The main one being that there is supposed to be a 'consensus' before a downgrade. One opinion for and one against isn't a consensus. If there is doubt about whether a bug really is a bug or not, the bug reporting guidelines say you should defer to the original poster's classification. I flagged it as a bug, so you should have left it as a bug, at least for the moment. Another reason I flagged it as a bug is that it gives Mojang a chance to flag it as N. In fact you have pretty much reversed what it says in the bug reporting guidelines: If in your opinion the game shouldn't do something it is, that's an annoyance. On the contrary, the reporting guidelines actually say When we talk about a 'bug', the term has two common meanings: either a computer program is doing something it shouldn't do, or it isn't doing something it should. Yes, there will always be opinions about what is and isn't a bug. And addressing wrong opinions about what is or isn't a bug is pretty much the main use of the N tag!--82.69.54.207 17:48, 8 September 2012 (UTC)
 * In my opinion a bug is something that does not work the way the developers of the game want it to work. Your "bug" is just a request for a new feature. --☺ Sven ? ! 19:22, 8 September 2012 (UTC)
 * If a bug is something that 'does not work the way the developers want it to work', then that report of mine should be tagged as a bug, because then a developer can look at it and say 'Nope, it really is supposed to do that. N'. Your definition is impractical, because you've got to be a Mojang dev or a mind reader to know how to class bugs correctly. Hence the pragmatic approach on the guidelines page for classifying issues. The basic principle is when in doubt, flag things as bugs; you should only flag things as annoyances when you're sure the game is doing what it's supposed to, but that correct behaviour is something you find annoying. I'm not sure glass should be joining to leaves, which was the initial issue, and I added some more related matters when I re-reported the problem. And that's why I flagged the problem as a bug. Okay? --82.69.54.207 19:40, 8 September 2012 (UTC)

Nether lag
--93.58.67.206 13:29, 9 September 2012 (UTC) In this update the nether lags a lot, crashing sometimes... I don't think it's becouse of my computer, since it's a quad core 2.6 GHz 8Gb Ram and 1024 MHz GPU...