Minecraft Wiki talk:Issues/1.3.2

1.3.2 / 1.3.2 pre?
There's a 1.3.2 out? Yoshidude56 22:24, 14 August 2012 (UTC)

There's 1.3.2 pre, which presumably will be byte-for-byte identical to 1.3.2, (as happened for 1.3.1 and 1.3.1pre). Assuming that's true, perhaps 1.3.2pre ought to redirect to this page. That would save having to migrate the bugs across in a few days. --82.69.54.207 13:16, 15 August 2012 (UTC)


 * They are one and the same. In fact, I have no idea why anybody is waiting to update mods (Risugami in particular) thinking that somehow something is going to change between the pre-release and the full update when Mojang already made their intentions very clear.  For the purpose of this page, the bug reports should definitely be merged.  --Robert Horning 21:00, 16 August 2012 (UTC)


 * Oh, good. Nothing to merge then; 1.3.2 and 1.3.2pre both point to the same place already. --82.69.54.207 21:03, 16 August 2012 (UTC)

Old bugs
If there are bugs from previous versions of the game that aren't apparently fixed, should those bugs (after verification in the current version of course) be reported for the current version of the game? Should outstanding bugs that haven't been fixed over several versions be marked up in some way to note that they are perennial bugs that aren't getting fixed? --Robert Horning 21:06, 16 August 2012 (UTC)
 * I've just started reporting bugs and am wondering this as well. Should I go back through each version to try and find the bug I'm reporting or just report it against the current version (if the bug still exists of course)? --110.174.214.164 13:55, 17 August 2012 (UTC)
 * I tend to take an ad-hoc approach, re-reporting old bugs whenever they inconvenience me again sufficiently, but not every time I see them for every last weekly release. Too much hassle.
 * We pretty much have to take it on trust that the world's Jebs and Dinnerbones are familiar with all the bugs reported. Still, if a bug keeps getting reported, then clearly it's regularly affecting a lot of people and annoying them enough to take action. So the system is a bit of a mess, but it sort of self-regulates; recurrent, intrusive bugs regularly get re-reported, but rarer bugs are re-reported less often. Using a wiki as a bug tracker is a bad idea in the first place, and we've complained about that before too. I don't have the citations handy, but Mojang do know that using a wiki as a bug tracker is... let's just say sub-optimal, and there are supposed to be plans afoot to adopt a proper bug tracker at some point. Complaining on the relevant Mojang Twitter feeds might help prod them into action. It's some time past due IMV. --82.69.54.207 18:56, 17 August 2012 (UTC)

Resolved issue
So I play on a Mac, when I got 1.3 I went into creative mode in a new world to check out the new stuff, The Emerald Ore block was pink, the Emerald block was a wooden block basically, Emeralds were invisible, Tripwire hooks are a pink screen, and the new books you can write in are invisible too. Please fix this!!
 * Your texture pack is out of date. Update it to one that matches the current game version and you will be fine. DarkWolff 14:03, 17 August 2012 (UTC)
 * Moved from bug page because it's unnecessary, was in the wrong section, tagged incorrectly, and already solved. --Keithicus420 16:27, 17 August 2012 (UTC)

step sounds
my character stepping sounds doesn't play on sand, stone, cobble, planks (any type), logs (anytype), endstone, netherrack, +possibly more.

can anyone hear these sounds? --188.238.1.36 17:30, 17 August 2012 (UTC)

Modded: Very likely/Probably not?
Before I tag a crash report with a [MOD] tag, are 'Modded: Very likely' and 'Probably not' just cute versions of 'Yes' and 'No', or are definitive yeses and noes (or any other responses) also possible? If so, what are they? --82.69.54.207 22:59, 17 August 2012 (UTC)
 * Cannot confirm how they are, because I haven't got any crashes. --188.238.242.198 05:18, 18 August 2012 (UTC)