Minecraft Wiki talk:Issues/1.3.2

Page Redirect
Why is "Known Bugs/Version 1.3.2" being redirected to "Issues"? Also, the page formatting since the redirect is wonky and the links to in-line images are broken. -- KADC - &#34;Be unreasonable.&#34; 10:07, 31 August 2012 (UTC)

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)? --Denney 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)
 * I only report bugs for full releases and not snapshots because I don't really play snapshots so I guess reporting the bugs for each version is probably best for me. --Denney 05:43, 19 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)

{{bl|!} you cannot destroy blocks, you can only kill mobs and action things like doors, its like if i was punching air no matter what block i am looking at the only way to destroy blocks again is if you are in creative gamemode. i believe the bug started when i re-opened my single player world after i had opened it for an LAN game however the bug was not immediate. i think the bug is related to changing the gamemode of players but im not entirely sure. im sure if you test it you will get similar results.
 * Are you certain you're entering gamemode 0? (survival) In 1.3, gamemode 2 (adventure) will not allow you to break or place blocks
 * oh wow i am such a fool, thank you that fixed it.
 * Deleted from the bug report and moved here to discussion in case someone else experiences this "problem" and will find the "solution". --Be unreasonable. 13:39, 18 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)


 * The code that checks for mods is fairly simple, and it's not always correct; I've had it say 'probably not' with mods installed. However, it's just about impossible to get the 'very likely' message if you haven't modified minecraft.jar somehow, so that's essentially a 'yes'. There's also a 'definitely' message, which I've seen when a Bukkit server crashed. -- Orthotope 12:06, 21 August 2012 (UTC)


 * Probably not appears when the client/server brand is vanilla and meta-inf is still there. Very likely appears when meta-inf is deleted but the client/server brand is still vanilla. Definitely + (client brand) appears when the client brand is not vanilla.Minecraft5025 15:30, 28 August 2012 (UTC)

Talk
"Discussion" moved from "Items - Book Recipe Minor Annoyance" per comment rules and replaced with less argumentative summary. --KADC - &#34;Be unreasonable.&#34; 10:15, 21 August 2012 (UTC)
 * Where's the problem of raising cows ? You just need two cows, a lot of wheat and a Sword with "looting " enchantment ! --Kumasasa 06:05, 21 August 2012 (UTC)
 * This is a huge problem when your spawn starts you in an ocean biome and you decide you want to build there. Have you ever tried to transport 2 cows in Minecraft over several thousand tiles of ocean biome? This all assumes you want to try this in survival mode on any difficulty without cheats enabled. If they had not nerfed ocean animal spawns into oblivion with the recent biome-specific changes this never would have been a problem, but unless Mojang decide to make it possible for ocean biomes to spawn even minimal quantities of animals or some new ocean content that has leather drops I don't see a viable alternative to leading around a pair of animals over several thousand tiles of ocean or taking a lot of time to build some sort of transportation system which can get really time-consuming depending on which system you choose to go with. While one can search for villagers which have bookshelves as a trade option, or for any structure which has bookshelves naturally generated in it, the rarity of villages which actually have such a villager with such a trade or such structures generated in a particular seed means that if going this route one has to set up a villager mass breeding system to get a villager with the desired trade or find such a structure in the first place, meaning yet more expense and time wasted on villager trading setup or searching in some biome other than the ocean, which really makes surviving in ocean biomes really tough to do without finding a large enough village-generating biome for a village to be generated in. BrickVoid 09:32, 21 August 2012 (UTC)
 * I wonder if the whole animal spawn discussion should be moved over to to a separate bug or annoyance report? They have introduced oceans and made changes that seriously affect the viability of trying to stay in an ocean biome and live off the sea without providing any sort of game balancing that compensates the user for having to transport any kind of animal to an island in an ocean. While they've stated that they plan to add ocean content in the future I still do not see this as a fix for how the game is currently structured. I quite like to build in ocean biomes and one thing I want to see is that they help the player get going in ocean biomes with at least basic supplies like wood and food needs, and most certainly some sort of alternate means of crafting bookshelves from some new ocean content would be good if only they'd implement it by 1.4! I don't think swimming around for the first few game days is a viable alternative to getting a foothold on an island with some easy to get food and wood resources, it shouldn't matter to the player whether they can get wood or food in the usual way straight away they should still be able to come across spawns that will give them something better than spider eyes or zombie flesh to eat, and which will provide wood resources they can easily access. While they have provided cheat and creative modes for those that want to just get on with building something pretty those modes don't solve anything for the player who wants to survive in and develop an ocean biome and just leaves ocean biomes seriously unbalanced when it comes to their viability. Abandoned Mineshafts and Strongholds may provide wood blocks and bookshelves, respectively, and can be generated with openings to them under the ocean but they still don't generate saplings or any renewable resources, and don't always generate where the player can find them easily, so I don't consider them viable when it comes to getting started in an ocean. BrickVoid 06:47, 22 August 2012 (UTC)
 * It's still better than a shaped recipe, and can't you dig and make a big flat of grass and wait for cows to spawn. Minecraft5025 15:33, 28 August 2012 (UTC)
 * Animals only spawn in predetermined chunks, so that would be very hit-or-miss, not to mention the time spent waiting for grass to migrate to a new region. However, that's part of the challenge one accepts if you choose to play in an ocean world. -- KADC - &#34;Be unreasonable.&#34; 19:42, 28 August 2012 (UTC)
 * Also, abandoned mineshafts do provide wood and string for a fishing rod. Agreed that oceans need better balance, though -- even a few grassy islands (with associated spawns) would help.  So would a sea-creature that provides meat (calamari?  squid are pretty useless right now.).  However, AIUI, farm animals do sometimes spawn after generation, it's just rare.  So if you can build a grassy island and hang out within its update radius, you should get something eventually. --Mental Mouse 20:33, 28 August 2012 (UTC)
 * Now that bookshelves provide two enchantment levels each instead of one, the number of books required has been effectively halved so there really isn't a reason to increase the number of books created per recipe. That doesn't address the issue of getting animals into regions where they don't spawn, but neither would changing the crafting recipe for books. Perhaps if mob eggs were randomly found in chests could be a solution. This might take quite a bit of exploring, but if you choose to play in an ocean world you are clearly interested in accepting an increased gameplay challenge. -- KADC - &#34;Be unreasonable.&#34; 19:42, 28 August 2012 (UTC)

Chunk Glitches In SSP
I have been getting moments when the game will lag and certain areas in chunks will become invisible then return to normal with a block update. I find this confusing and very annoying and have been wondering why this happens to me, and whether it can be fixed or not. the chunk glitch shown below.

A link to the screenshot: [[Media:ChunkGlitch.png]]
 * This was happening to me very frequently in 1.3.1, but it hasn't happened to me since 1.3.2; however, in 1.3.1 I was exploring previously ungenerated chunks whereas since 1.3.2 I have mostly stayed put, so I'm wondering if this is some kind of rendering lag when entirely new chunks are being created as opposed to new chunks simply being loaded. --KADC - &#34;Be unreasonable.&#34; 20:04, 20 August 2012 (UTC)
 * That is not a glitch, your computer is slow.Minecraft5025 15:34, 28 August 2012 (UTC)
 * No, my computer isn't slow, it's definitely a memory use and/or rendering issue. -- KADC - &#34;Be unreasonable.&#34; 19:43, 28 August 2012 (UTC)
 * I'm seeing it too -- quite dramatically in new areas (I came out of a new nether portal to the Overworld, and half the landscape was invisible down to lava, and stayed that way until daybreak). But, also in specific old areas: there are particular places in well-known caves where for a few steps I can see down to lava.  --Mental Mouse 21:27, 28 August 2012 (UTC)

Chunk Redstoning Glitch? (SSP)
When ever I take any sort of redstone device, and activate it, the chunk errors until I a. Place a block b. Break a block

Snow
undefined Snow isn't melted correctly by torches at biome borders. See image. Torches are there for at least a game week. --Gizmo2342 12:39, 19 August 2012 (UTC)


 * Not a bug, so removed it from bug page. Seems I got confused by "... and it won't regrow 2 additional blocks away." --Gizmo2342 07:36, 24 August 2012 (UTC)

error 126
every time i open minecraft and log in it comes up with load library failed with error 126: the specified module could not be found. iv tried everything from uninstalling and re installing minecraft and the .bin file and even tried .dill but nothing works my computer is new and is fine, and i have been playing minecraft before this started only the 4th or 5th time i was playing with the latest update if anyone can help me please do.

this is totally guess, but have you updated your computer somehow? new graphics card.. maybe need to update drivers (to version that don't possibly exist yet). try to think what you have changed on your computer at time between last succesful play and this error. EDIT: you could also try lwjgl update. --188.238.55.115 20:30, 26 August 2012 (UTC)

My Minecraft is Not Working Right
Hi, My minecraft game is not working right. The game works fine until I try to go into my world. Here is what i do, I log in normally then go play in my browser. Then i go to Single Player and go to my world. When my world is loading it does the normal loading thing but after a couple seconds it goes back to the main page for a half second then to the dirt background it goes and doesn't go back. ( I have updated java, the drivers and, even tried it not on browser )PLEASE HELP ME.
 * First, please sign your comments on talk pages like this one, by ending them with --~ . That turns into a dated signature.  Now, about the problem:  World loading can take a lot of time anyway, but it also takes a lot of memory and CPU.  If your computer is not very powerful, having the browser open at the same time may be pushing it too far...  try exiting the browser (also mail and other big programs) before you enter your world, then be prepared to wait a minute or so. --Mental Mouse 21:50, 28 August 2012 (UTC)

Deja-vu issue.
Sometimes a part of older map appears in new map. I was playing in Creative and then lined a TNT all the way from village to spawn point (which took a while and with Rendering Distance at Short [ie. 2nd lowest] it wasn't visible) and then set it off [some holes weren't visible until I did something with them]. Then I deleted the world and generated new... just to see a sudden drop at northern (ie. upper on map; after that drop there was just a thin layer of ground, like in Superflat, except a difference). I went down to see the screen becoming darker, likely game was treating it as going underground since it was Default world not Superflat unlike the deleted one. I saw lava flowing out of stone into the Superflat layer, water, Emerald ore and abandoned Mineshaft. Then I ventured a bit further, only to see the things I did in previous map. Holes in ground, and village partially destroyed. It was Singleplayer on Windows XP Service Pack 3, though not sure if Minecraft's version was 1.3.1 or 1.3.2 159.255.184.22 16:08, 28 August 2012 (UTC)

Serious memory issue?
Whenever my friend crashes, or a server closes on him unexpectedly (I.E.: When he leaves a world without Save and Quit to Title or Disconnect), a ghost javaw.exe appears on his Task Manager. He can't quit it, and it consumes more and more memory until 1GB. Sometimes, he has multiple of these "ghosts" and his computer lags so much he can't do anything. This hasn't happened in 1.2.5, only in 1.3.

Also, I have a private server with my friends, and I play Minecraft at the same time on the same computer. I haven't ever had a problem with lagspikes on my server or anything in the past while I was playing, but lately whenever I open Minecraft and my server at the same time, everyone says they're lagging out and the little red spike goes way up through the roof.

I posted this here because I'm not sure if ever I should directly post it on the page, or what :P

AetherX 12:38, 29 August 2012 (UTC)

1.3.2 Glitch
I found in 1.3.2 that sometimes when a player is riding in a minecart on a lan server the other player couldnt see the player in the minecart. used when connected to the internet but tricked the game to be able to use multiplayer.

re-direct from list of current bugs
Why has this page turned into a technical help section?

It was originally for listing all the confirmed or documented bugs present in the current edition of rhe game.in this psges current dtate, it is basically useless for finding out about bugs, only if you encounter a bug and are not sure if its just you or not.

It's not written from a encyclopedic POV, its like a talk page or fourm. I suggest ethier all of it be moved here to the talk page, or be moved to a new page for REPORTING bugs. Whoever decided that this is how the page dhould be needs to seriously re-think what this site is for. It is an encyclopedia for amassing as much info about the game as possible that can be verified or documented, not for disscision about the game. Excuse my spelling, I am typing this from my pho.ne 173.132.111.242 14:05, 30 August 2012 (UTC)


 * The purpose of these pages isn't just for documenting issues, but for determining/discussing the specific issues so that the developers can fix them. If you have a problem with the system, you should have commented at the rename discussion, which was open for quite a while. The majority already decided on the move (and not based on majority, but on reasons). --M0rphzone 20:01, 31 August 2012 (UTC)

Single Player Mods affect SMP/Bukkit/LAN
Problem: If you install mods in a single player.jar, it works in LAN Worlds and MP Worlds. Bukkit and Vanilla included.

E.G. I install an armor mod. I go into a multiplayer server and craft it. It works, i place it on, and gain the armor points. No one else can see it unless they have the mod. All weapons and armor work fine for me.

04:28, 31 August 2012 (UTC)24.6.168.222 04:29, 31 August 2012 (UTC) Jdembo/Giraffestock

can't find out how to categorize bug
If a bug happens when you edit NBT tags, and bricks the level until you change it back, would it be an annoyance or a bug? Also, would it fall under the 'modded' category? Would it count as a loss of data? I found a bug like that, and i don't have any idea how to classify it.

Creative mode crash on exiting inventory
Has anyone else experienced Minecraft 1.3.2 crashing when escape key used to exit the inventory, but only in creative mode, survival mode fine.

Worlds used were created before 1.3.2. No mods installed.

First few lines of Java stacktrace are: java.lang.IndexOutOfBoundsException: -100 at java.nio.DirectByteBuffer.get(Unknown Source) at org.lwjgl.input.Keyboard.isKeyDown(Keyboard.java:399) at aqn.a(SourceFile:251) UncleLukibus 17:31, 1 September 2012 (UTC)

Lava Burning "non-flamable" blocks
I think this is a minor bug, and I read everything about bugs and issues, but I still think posting here first for reproduction would be prudent. In ver. 1.3.2 single player, cheat-activated mode I have lava in a moat beneath a stone-brick bridge (which I changed from a sandstone bridge which also had this problem). The lava catches the stone brick block above it on fire. The fire dies and doesn't spread unless a flammable block is directly adjacent (like a wooden fence). It did not burn up the door adjacent to the burning block. I believe it to be a bug because if I were standing on the bridge and it spontaneously caught fire, well that would be inconvenient. Maybe this is normal block behavior. I have never tried to make a bridge over a contained lava moat. It seems though, by all of my research that stone, cobblestone, stone brick, and sandstone should not catch fire. this photo shows a block that spontaneously caught fire and is NOT even directly over lava. See layout below. (N-nether fence, F-Fire, A-Air, S-Stone Brick, L-lava, C-cobblestone) JuliaStar 23:18, 1 September 2012 (UTC) N F A S L C


 * Actually, the lava is setting your wooden doors on fire. They are one of several blocks that can be ignited by lava, but are not destroyed and fire does not otherwise spread to them (more details here). Try moving them farther away from the moat, or replace them with iron doors. -- Orthotope 07:15, 2 September 2012 (UTC)
 * How can the fire in the picture be setting my doors on fire, when the doors aren't burning? How far away do you think the doors should be? Would putting them a block higher be enough? Or should the be a block further away from the lava? Stupid wooden doors. JuliaStar 19:47, 2 September 2012 (UTC)


 * The doors are considered flammable, so fire blocks can be created next to them. According to Fire, fire can be created up to four blocks above and one block to the side of the lava, so the doors will need to be farther away than that. -- Orthotope 05:40, 3 September 2012 (UTC)

Graphical Glitch
New bug I've never seen before. I'm using 1.3.2 and no mods. I have the faithful 32x32 texture pack on, but haven't updated the mcpatcher from 1.3.1. There are flames on the gold block (and item sprite) and flames and part of a portal on the brick block (and item sprite). Relogging does not change anything. Samwuzhere973 04:25, 3 September 2012 (UTC)


 * Probably the result of using a high-res texture pack without an appropriate patch installed. Update MCPatcher (the 1.3.2 version has been out for a while), see if that fixes it. -- Orthotope 05:40, 3 September 2012 (UTC)
 * On the download page for the texture pack is written in bold, red, big capital letters: YOU MUST INSTALL THESE TEXTURES WITH THE LATEST VERSION OF THE MCPATCHER OR OPTIFINE OR LOTS OF THINGS WILL BE BROKEN. --Kumasasa 06:18, 3 September 2012 (UTC)