Add topic
From Minecraft Wiki

Template:Pending archive

Question about drops[edit source]

Is this to say that, if you die and drop a bunch of stuff, and respawn far away from it, it won't despawn until you go back and enter that chunk? How long after entering a chunk do mobs begin to spawn? Is it essentially pointless to plant trees in areas you don't regularly visit? Sorry for all the questions, this is just very different from how I perceived the game working. MrMatthew 20:55, 7 October 2010 (UTC)

Items despawn after about fifteen minutes (I think?) even if you're far away from them. I don't know the answer to the other questions. I think it's time for some experimenting! :D –Preceding unsigned comment was added by PurpleKiwi (Talk|Contribs) 8 October 2010. Please sign your posts with ~~~~
You are always in a 9x9 chunck square, with the chunk you're standing on, and 4 loaded infront, 4 loaded behind and 4 to either side of you. Monsters can spawn the second their chunk is activated (Within the 9x9 area around you) and trees and crops will only grow it you are within not 9, but 5 chunks away (As you're at the CENTER of the 9x9 square, not the edge), so anything further than 80 blocks away will never grow and monsters won't spawn, though I'm pretty sure it's the opposite with item decay. Only items further than 80 blocks/5 chunks will therefore decay so you will always have to run to get your items, unless your spawn is close to where you died. I could be wrong about the decay, and it may be the other way around... I forget =O.o= Reziah 07:15, 19 April 2011 (UTC)
I believe that dropped items don't get updated unless they are within your 9x9 chunk. Once I was exploring and got lost so I committed suicide by jumping off a mountain overhang. I had a lot of resources so I wanted to find where I died when I respawned. It probably took over half an hour of searching before I resorted to using map viewers to find where I died. My items were still there.--Lunt0er 22:03, 23 April 2011 (UTC)
I believe Notch himself said that there's a 5-minute timer on dropped items which pauses if they aren't within that 9x9 chunk box. My personal experience has confirmed this many times as well. -AlphapT~C 22:31, 23 April 2011 (UTC)

Chunk Load distance[edit source]

I know I've seen somewhere where someone said either the radius or diameter of chunks that are "nearby" enough to load. Does anyone have this information still? My Google-fu is weak tonight. Cjc343 11:21, 23 October 2010 (UTC)

128, I think. I read about that in the forum somewhere. PurpleKiwi 01:42, 24 October 2010 (CDT)
In Talk:Items, someone says the time is about 5 minutes. We’ll have to find out if we can get the chunk (on which some items are) to be saved to disk, then come back and see if the items still despawn. ‒ Flying sheep 13:14, 4 April 2011 (UTC)
9x9 Chunks around you. You being in the center with 4 chunks on all sides (Including diagonals). That means if you're in the center of a chunk, things are loaded 70 blocks around you (4 full chunks loaded plus half one chunk that you're in the center of, minus 2 as you'd be standing on the corners of 4 blocks). This also means the furthest away you can be from a block in memory (Not including height) is 80 blocks, on the very corner of a chunk. Reziah 07:25, 19 April 2011 (UTC)

Isn't it 17x17 chunks loaded around a player, not 9x9? Benjaminkc 20:31, 4 October 2011 (UTC)

Ah, the page has been updated to say that it's variable based on view distance and single/multiplayer. If someone knows the radius per fog setting, a little table would be nice. Benjaminkc 21:04, 5 October 2011 (UTC)

Chunk dimensious[edit source]


is a chunk really 16 x 128 x 16, which is suppose is X x Y x Z? From the picture i would say it's 16 x 16 x 128. –Preceding unsigned comment was added by Knochi (Talk|Contribs) 09:40, 17 November 2010. Please sign your posts with ~~~~

According to Minecraft_map_format_(NBT), the Y coordinate is height, not Z. --DannyF1966 03:43, 17 November 2010 (CST)
Yeah. Minecraft reverses the usual meanings of "Y" and "Z" for some damn reason. Phasma Felis 06:55, 25 December 2010 (UTC)
Actually, X and Y were always Length and Height. Think back to 2D games, they had X and Y, Width and Height. The third dimension was added, so Z is always depth. Reziah 07:06, 19 April 2011 (UTC)
X and Z is the flatland in which the player walks on. X is Length, Z is Depth. Y is the elevation from bedrock. Ah, I love number cubes. --Rocĸetor talk 07:12, 19 April 2011 (UTC)
It depends on the developer and most modern engines allow you to change it. X, Z, Y is the most conventional method though and most don't find it easier to move to a different order. –Preceding unsigned comment was added by (Talk) 12:57, 16 March 2012. Please sign your posts with ~~~~

Chunk activity question[edit source]

Is all activity stopping when not around ones 9x9 chunks? What about minecarts driving out of the active chunks? Do they continue or just when the inactive chunk they entered is reloaded (by getting into ones 9x9 area) or do they even just stop? I have experienced that neither a furnace works when nobody is around, nor grass is growing. Could also have been because nobody was logged in during this time. Don't know if it would have continued growing/smelting when another player had logged in, but further away than those 4/5 chunks. Enudoran 14:58, 19 May 2011 (UTC)

Dungeon=unlimted supply of hostile mob drops?[edit source]

I think this is what this does I found a creeper spawner and now I have a total of 70000 TNT's I don't really think this is fair because getting Gun-powder should be more difficult. –Preceding unsigned comment was added by Dusty01 (Talk|Contribs) 15:17, 19 May 2011. Please sign your posts with ~~~~

You should have put this up on either monster spawner or dungeon, creeper spawners do not happen naturally, but while it makes it easy to get a lot of bones or TNT, it also makes them very dangeris. Timberdoodle 16:03, 19 May 2011 (UTC)

First of all, the person above is correct. Creeper spawners do NOT happen naturally. Second, if we assume that they DID exist, and each dropped 1-2 for an average of 1.5, to get the 350,000 gunpowder needed for that many TNT, you would need to kill about 230,000 creepers. With a spawn rate of about 1 every 5 seconds, that would take almost one million seconds, which is almost two week in real life time. Just saying, but what you said most likely could never happen, even if there WERE creeper spawners. 18:31, 14 July 2012 (UTC)

Slimes[edit source]

Does anyone think slimes should spawn in all chunks, not just 10% of them? I need slimeballs. Jedi in, um, I forgot. 15:40, 12 July 2011 (UTC)

This site is for information, not for suggestions. Also, they spawn in somewhere around the 50% mark of chunks, but it doesn't appear to be entirely random, but instead working in groups. Shellface 15:50, 12 July 2011 (UTC)
That is completely wrong. There is exactly a 1 in 10 chance that a chunk spawns slimes. Escortkeel 10:03, 3 August 2012 (UTC)

Despawn[edit source]

How much blocks from a monster exactly must the player go away to cause the monster to despawn (horizontally and vertically)? Xeoxer 12:18, 1 August 2011 (UTC)

After a minecraft update, do new blocks generate in new chunks?[edit source]

this isn`t answered anywhere I can find, so I decided this would probaly be the best place to ask it.--Icecat can haz cool signature? 23:31, 25 September 2011 (UTC)

Yes. New chunks are generated using the terrain generation algorithm. Thus, chunks that have already been generated do not get new stuff, on account of not being regenerated, and new chunks do get new stuff, on account of being generated with the new terrain generator. Jaeil 00:00, 26 September 2011 (UTC)

A different Kind of Chunk Error[edit source]

So here I am playing with the TMI mod on, a 111 stack of boats in hand and a map (that I soon learned I couldn't view while riding a boat.) I'm trying to find a suitable place that's not in the midddle of the ocean to build. I'm traveling West (towards the sunset) at full speed on a boat. I'm noticing the chunks are having trouble keeping up with me, so I wanted to see if I could outrun the generator. I'm pretty close I have to say, but suddenly it catches up, but an odd formation is formed. I'm calling it the Inverted Chunk Error, and you'll see why. I have some screen shots:

  • chunkerror1.png - Note, this is the 'Back/West' wall of the Inverted Chunk Error, where I'm facing east. I did not come this way at this angle at all to meet the chunk.
  • chunkerror2.png
  • chunkerror3.png - This is the North side of the Chunk, and to the right is a single, tinier Chunk that was generated with the larger mountain chunk.
  • chunkerror4.png - At this angle, you can see the see floor. You can also see how the Inverted Chunk Error goes all the way down to the see floor, probably past that.
  • chunkerror5.png - Eastern side, facing West. I can now see that this is was obviously supposed to be an Extreme Mountain Biome, odd, yet funny, how the game generated this in the middle of an Ocean Biome. Also, in the bottom corner, you can see that there is a cave. The water wasn't flowing into that. I have another screenshot of another cave that shows it better.
  • - What is this, a Farlands Wannabe? This is the angle I came at this chunk, not the exact place, but this nearly-solid wall was the first thing I saw, followed by a 'Wow.'. Oddly enough, there are waterfalls carved into the sheer wall, but a water-spring in that cave over there (in the top, left corner) the water will not flow out.
  • chunkerror7.png - Hard to understand/believe that this was generated in the middle of nowhere. Game, our race has ended, you win. Obviously, mobs are able to walk on it, so it isn't a 'normal' Chunk Error.
  • chunkerror8.png Here is a cave that was carved into this chunk. You can clearly see in this picture that water isn't flowing into it.
  • chunkerror9.png On the other side again.
  • chunkerror10.png Well, I am able to walk inside this chunk. Here I am, inside another cave that was generated. Again, no water flow.
  • chunkerror11.png And here's the outside of it.

The onlything unusual about this is the generation. By all appearances, it's a completely different biome, but other than that, the land is normal, mob-spawning is normal, and I can even walk and build on it. Speaking of that, it appears the water will flow into the caves if a block around it is modified, which I expected. I put a ladder near one of them. Perhaps if I were to travel at high-speed across a Mountain Biome I'll suddenly run into a see Biome chunk strip, doubt it though, and I plan to stay here anyway.

So guys, what do you think about this? This is the most fascinating thing I'm found in Minecraft lately.--DemonSlayerThe3rd 20:49, 4 October 2011 (UTC)

There is nothing fascinating about this, sorry to burst your bubble. You've started a world in an old version and then upgraded to a new version (therefore a new world generation) which messes up the borders of your current world. Alternatively, the seed has changed (causing new generation). And before you say that it's a new world, there's a semi-bug where if you create a new world with the same name of an old one some chunks won't get deleted completely and this kind of stuff happens. --Wizjany 20:59, 4 October 2011 (UTC)
Not true, this is a brand new 1.8.1 world, I literally just made it 20 minutes ago, with a completely different name from any other world I've created. None-the-less, this type of error should also be noted in the page, since I see nothing in the article regarding this specific type of chunk error.--DemonSlayerThe3rd 21:40, 4 October 2011 (UTC)

Questions[edit source]

Is there a program that will load chunks for you. So i wanted to load all chunks within 20 chunks of my position and it loads them without you have to walk to each on??? –Preceding unsigned comment was added by (Talk) 00:23, 8 October 2011. Please sign your posts with ~~~~

Question about chunk loading[edit source]

I have a question about how things are loaded in multi-player. It says here that 32,768 blocks are loaded per chunk, and that 441 chunks are loaded when a player logs in.

If every block was sent as a byte (up to 255 unique blocks), that would come to a total of 14,450,688 bytes, or 13.78 megabytes on login ; which is a HUGE amount for even modern internet connections to send to every player. Am I missing something here? –Preceding unsigned comment was added by (Talk) 07:09, 8 January 2012. Please sign your posts with ~~~~

They are GZIP compressed. --DeathByNukes 20:01, 8 January 2012 (UTC)
Actually 13MB isn't all that much these days. Even with a low end DSL connection. Plus, not everything loads at once. You will get data in smaller bits (called packets) which will load on demand as they come in. For example, the first thing to load is the first set of blocks where you will spawn at (usually 4x4x4 blocks) then it will begin loading the graphics (this is just before you see the world, during the loading screens) by the time your computer has loaded the first set of blocks and has had time to load the UI and 3d rendering you have received the next 8x8x8 blocks. Then it continues to build the world 4x4x4 at a time as packets continue coming in. You see this effect when you first see the rendering, the world continues to build around you. This is packets continuing to come in. You have to add an extra 1MB for overhead, Error correction and positional information. I'm not certain that all 32,768 are sent to the client. Also, 441 blocks, if each was a single byte of data, that would be 0.44KB, not 13MB. also, only 16x16x16 are contained in a chunk. which is 4KB (4,096 bytes) per chunk and if 9x9x9 chunks are sent to the client that equals 2.9MB. So your download time is only 15-22 seconds on the slowest DSL possible, including error corrections and positional data. Quilnux 19:58, 23 August 2013 (UTC)

Ore Probability[edit source]

Is it safe to say that there isa near-100% chance of finding Diamonds in a chunk? I'm currently quarrying a 64x64 area and am hoping to find some diamond. I also need to point out that there are the 4 full chunks (in a snow biome, can see the chunk outlines), so the oddsof me finding 4 formations are what? LightRod 01:03, 30 March 2012 (UTC)

It's possible for a chunk to contain no diamond ore, if it tried to generate in the same space as a cavern or lava pool. However, on average (over several thousand chunks), there's about 3 diamond ore per chunk. So a 64x64 quarry (4x4 chunks) should produce around 45-50 diamonds, more if you explore caves as well. -- Orthotope 02:31, 30 March 2012 (UTC)

Chunk regenerating[edit source]

I just started a new world (singleplayer, apparently latest version, no mods), and I noticed that at least one chunk appears to regenerate when I re-enter the world, discarding the changes I made. So, for example, I was standing in a town, I added some steps, logged out and logged back in, and the steps were gone. I've tested this several times, including going elsewhere, verifying things saved normally, and then returning to the place where it failed and verifying it still does not save changes. I haven't verified that the borders of the problem are exactly a chunk, but I have verified that it is geographically localized to a contiguous area. In other words, if it happens at [x,y], and at [x+50,y], then it also happens at [x+25,y]. I've tried googling to get information about this behavior, but have not managed to find any similar bug reports. Any one have any insight into how this might be happening and if there's anything I can do besides avoid that area? 15:03, 7 March 2013 (UTC)

I don't know what it could be, but the coordinates you give suggest it's a lot bigger than a single chunk. Chunks are 16 blocks each way, a 50-block range is at least 4 different chunks. Have you looked at the logfiles? If not, try that. --Mental Mouse 15:19, 7 March 2013 (UTC)
I just randomly picked numbers to show it was contiguous. (Not sure I really needed to clarify in that way, since I had already said, "It's contiguous," but...) It's not as big as I suggested. Anyway, thanks for the suggestion; I'm going to guess my problem is this error: Bad file descriptor
at Method)
at aaj.a(SourceFile:327)
at aaj.a(SourceFile:279)
at aak.close(SourceFile:230)
at aam.a(SourceFile:137)
at aam.c(SourceFile:125)
at aiw.b(SourceFile:29)

Not sure what to do about it yet, but at least I've made a start... :D I guess I will now begin to google once again... 21:38, 10 March 2013 (UTC)

No page or info about spawn chunks[edit source]

The minecraft wiki does not currently have a page about the spawn chunks (the chunks around the spawn that remain loaded all the time which allow iron golem farms to constantly produce iron golems). I believe this is a major lack. There are a lot of useful to the player info about the spawn chunks. 19:08, 23 April 2013 (UTC) purple

My Chunks are mixed up![edit source]

So, I have a baby sister, and while I was looking at some chunk files, just to see how the code was, I got up to use the restroom, when I came back, my baby sister was sitting there, with a big grin on her face, and all the files screwed up. (I loaded them in a text file) So, I logged into Minecraft a little while later, and I brought up one of my worlds, some of the chunks were gone, it seemed like there was a weird jungle/desert hybrid where a forest used to be, there was a mountain growing out of my castle, decorated with giant mushrooms, there was a floating jungle temple, and on ocean in the middle of a city I built. Can anyone tell me what the heck happened to my chunks? 23:14, 28 June 2013 (UTC), I believe your sister may be at fault. Should you have something that may edit your world running, she may have pressed buttons, therefore messing up your world. -Creepergoboom64 17:09, 9 July 2013 (UTC)

Chunk loading with redstone[edit source]

There are a lot of people talking about chunk loading with redstone, I think some information about that should be added to this page. (there are ways to load chunks using redstone or hoppers, and make a buttons to load/unload far chunks)
Also information about processing loaded chunks should be included.
--Xbxp 17:10, 30 July 2013 (UTC)

I'm not completely sure, but I've heard that a hopper facing into a chunk boundary will keep the chunk the hopper is facing loaded as long as the one with the hopper in is, but only partially and it won't process entities but it does process redstone and hoppers. If you make a trail of hoppers from a spawn chunk you cana keep a chunk partly loaded this way. Also I've heard a large enough square of hopper loaded chunks allows the central ones to process entities. Also, I think (but I'm not sure) that if a dispenser fires something into a nether portal, and there are hoppers o the other side to catch it and another dispenser fires it back, so the item shuttles back and forth between the two dimensions, the chunks on both sides stay loaded as long as they start off loaded. If this works I think it would be theoretically possible to have a chain of these portal loops starting in spawn chunks and leading to more distant chunks, each of which could be activated by redstone. 16:31, 17 March 2014 (UTC )

WTH?!?!?!?!!?!?!?[edit source]

I honestly have no idea. What happened here? I tried reloading the world but it's still there! Ravenstorm13713 (talk) 21:49, 18 March 2014 (UTC)

Did you create that world with the same name as a previous world? If that previous world wasn't sufficiently deleted this can occur, or if the world settings change after chunk generation. --GufNZ (c: (talk) 22:30, 18 March 2014 (UTC)

Nope. It's one of only five worlds I have. And WTH does " or if the world settings change after chunk generation " mean? Ravenstorm13713 (talk) 23:06, 18 March 2014 (UTC)

What the...[edit source]

HELP. One day, I opened up my survival world, and there was this super-stubborn chunck error. i've tried everthing suggested on this wiki, and nothing works. reloding chunks, blowing TNT in it, NOTHING. i've seen a creeper walk into it, and come out again. i wasn't able to hit it, but it could hit me just fine. WHAT IS GOING ON??? How do I fix this? CAN it be fixed? –Preceding unsigned comment was added by (talk) at 17:01, 16 April 2014‎ (UTC). Please sign your posts with ~~~~

A little late now, but may help someone later. If all the other ways fail, use MCEdit and delete the bad chunk, then save. When you then open the world in Minecraft it should regenerate the missing pieces. I've been having this problem recently on 1.8.8 for some reason, on a world created in that version. I don't know how similar the names have to be for it to cause a problem with previous versions, this current one is named 'Meow 1.8.8', and I previously had one named just 'Meow'. --Azaram (talk) 17:25, 5 November 2015 (UTC)

Reloading chunks from an old map in a new version.[edit source]

If I created a map in beta 1.7, then converted it to 1.8.1, and any unloaded chunks were reloaded using the new generation, resulting in nasty biome shifts and disappearances, as well as huge cliffs.

Is there a mod or tactic or program I can use to prevent this so that I can play on my old maps on newer versions? –Preceding unsigned comment was added by (talk) at 07:48, 29 November 2014‎ (UTC). Please sign your posts with ~~~~

...I don't know. Search in Minecraft Forums. And, please sign your comments with ~~~~. --Naista2002File:Grid Book and Quill.png File:Grid Iron Pickaxe.png 08:12, 29 November 2014 (UTC)

A change to chunk edge identification technique in Bedrock Edition?[edit source]

I browse the wiki whenever I play, and I've finally decided to try contributing a bit myself. Apologies if I make formatting mistakes.

The final sentence in the "Finding Chunk Edges" section appears to be outdated as of 4/4/2018. Running bedrock edition on Windows 10, toggling "Fancy Graphics" appears to load all chunks in at once; there no longer appears to be the 'split-second' referenced in the article of just the player's chunk being rendered. I don't know enough about wiki maintenance to confidently make the change myself. –Preceding unsigned comment was added by Dystricht (talkcontribs) at 19:52, 4 April 2018‎ (UTC). Please sign your posts with ~~~~

Chunk Visualization[edit source]

"Visualization of the ground portion of a single chunk. The entire chunk extends up to a height of 256." How is a reader supposed to know how many layers or blocks the ground portion covers? The Altitude page clears up this confusion, but there is no reference to it from the Chunk page. I do not think everyone will realise chunks are not stacked ontop of each other. A better description might be in order to reduce reader confusion. E.G: "Visualization of the ground portion of a single chunk. The entire chunk extends up to a height of 256, beyond what is shown here." This would make it clear a large(r) area of the sky is included. Or some mention of the ground portion's height. E.G: "Visualization of the surface and ground portion of a single chunk, consisting of the bottom 127 layers. The entire chunk extends up to a height of 256 (blocks/layer)." I'm not sure how to word the description, especially because I think the surface level is not included in the 'ground portion' of the visual representation. But I am confident some changes to this page would clear up some confusion for readers.--Mushini (talk) 08:06, 8 March 2019 (UTC)