Minecraft Forums

If you like the game then why not just buy it?

I don't see any waterfall.

He is not real. He never was real. I doubt it will ever be real. It is a joke that is put on the end of many change-logs.

Quote from Danster5oo

I hate how Mojang has never made me mad.

I like how Mojang has never made me mad.

everything. especially the new sounds.

Why does everyone hate the new sounds? I think they are great, including the cow sounds!

This should be stickied.

Quote from Raggarcowboy

I'm pretty sure mods still will have to update though... Minecraft changes parts of its code with every new update, and the modders will have to adapt :/ but anyway, it will be awesome for modders, because it is a lot more simplified to make mods

They do change parts of their code but the mod API is separate code that will never change.

No matter how fast you are going and how sharp the turn is the minecart will never fall off the tracks.

If you die you come back to life out of your bed.

You can stand on top of the very tips of grass. You don't sink in to grass blocks at all. same with sand.

Quote from Classicvibe

well there's a bunch of people on the MC subreddit wailing about it and as far as i can tell Dinnerbone pays attention to it.....

Are there any programming obstacles stopping the developers from making this dimension right now? Or was it just a choice they made.

It was a choice they made. They already had the code.

Quote from subzerostig

The thing is that this is another one of those threads such as:
'OMG Mojang you screwed up again it would of been far better OMG Change it now'

While this thread isn't quite like that it does have certain traits

Also think about what would happen if they replaced the end:
'OMG Mojang you removed the ender dragon. How am I supposed to finish the game now?' and also...
'OMG Mojang you broke my enderman XP Farm fix it now I want to get to level 30 in 5 minutes!!!'

While I do agree that the end would benefit from a bit more love and care and attention, I do think that you don't appreciate as much as you could do and that it isn't completely useless, it just needs to be given more attention(Just to point out that then other people would start complaining again such as: 'Y U MKE END gud when We Wnt New Terrain Naow!', I guess that no one will ever be happy... sigh)

You didn't read it. The skylands would be a new dimension or tf it was in the end it would be after you kill the dragon and it would not ruin xp farms because enderman would still spawn but only on the endstone island.

Hello everybody,

This mod adds support for HD textures and a lot of options for better looks and performance.

Doubling the FPS is common.

You can follow the OptiFine development here: reddit.com/r/OptiFine, sp614x@twitter or http://optifog.blogspot.com.

Resources: translations, documentation, issue tracker.

Get the Magic Launcher for easy mod installation, compatibility checking and more.

Donate to OptiFine and receive the OptiFine cape as a sign of your awesomeness.

The cape is visible to everyone using OptiFine. Thank you for being awsome.

Download OptiFine

Get all OptiFine versions here: optifine.net

Features

Editions

Even Older Versions

If you have previously used MCPatcher for HD Textures, HD Fonts or Better Grass (important)

Compatibility with other mods

Installation

For Minecraft 1.6.2 and newer

For Minecraft up to 1.5.2

Please test and report back, include CPU, GPU and FPS before/after. Feedback is always welcome.

Copyright

---

Table of Contents:

Overview
Changes in how things work
Frequently Asked Questions
[WIP] The Cubic Chunks Mod!
Gallery
Supporting this suggestion
Special thanks

[spoiler=Tl:dr]Q: Won't this increase lag?
A: Absolutely not. The title of this suggestion and big red letters at the top of this post aren't lying. If you want to know how, then I suggest you actually read this post.

Q: Will this change terrain? Will this break existing worlds?
A: No. Terrain change is not necessary. Existing worlds can be converted fairly easily with a process described later in this post.

Q: How can sunlight or rain work with infinite vertical space?
A: I suggest you read Coping with sunlight, because it's too complex for a tl;dr.

Q: I have a different question but still don't feel like reading this post. What do I do?
A: Too bad, read the FAQ. I put way too much work into this for the entirety of it to be ignored.[/spoiler]

---

Overview:

In Minecraft, the sky is the limit - literally. It doesn't matter how many thousands of blocks a player has traveled, or what dimension they're in, or even if they're playing in creative or survival, the highest they can ever build is up to a height of 256. Why is that? If Minecraft can have a world that's infinite in the north, in the south, in the east, and in the west, why can't that world be infinite up and down too?

In Minecraft's earliest days, in Classic and Indev, the world was not infinite in any direction. This was because the entire world needed to be generated at the same time, and the entire world needed to be simulated at the same time as well. This led to a conundrum - the bigger the world, the more it lagged.
Notch didn't like this. He knew his players liked to explore and build large creations, so he found a way to make the world truly infinite. When the Minecraft '' class='bbc'>Infdev came out, it brought with it truly infinite worlds. Suddenly, players could travel hundreds of thousands of blocks in any direction, and never encounter a barrier, or become too laggy.
The Infdev update brought about a very large change to Minecraft worlds to accomplish this feat. For the first time, instead every world being just a single huge piece, they were broken up into a two-dimensional grid of pieces, called chunks. Through breaking the world up into pieces, this 'chunk system' enabled infinite worlds by letting Minecraft create new pieces and simulate them only when it needs to.

Why does that not apply to the vertical axis? Because the type of 'chunk system' Minecraft uses right now is a linear one, which, by using only a two-dimensional grid to map out chunks, means that it is impossible for chunks to stack on top of one another, and by extension, meaning that a single chunk must cover the entire vertical space. This brings back the problem that the Infdev update was supposed to eradicate, now only with chunks, instead of an entire world; the bigger a chunk is, the more laggy it is. You can't just increase the height limit and make chunks taller, because it will become laggier, and laggier, and laggier to do it.
That's why, to fix this, Minecraft must change over to a cubic chunk system. Under this system, 16³ block chunks are aligned on a three-dimensional grid, completely eliminating maximum height as an aspect of lag.

The immediate benefits:
•Minecraft worlds become as virtually infinite vertically as they are horizontally: The absolute limit being Y = ±30,000,000.
•A large FPS increase: Alpha testers report an FPS increase of 100~200%.
•Increase in running capability: Computers running Minecraft on Tiny render distance will handle only 30% the blocks they do now.

The possible features:
•Spherical render/load distance: Reduce handled blocks by up to 30% by cutting corners made of unneeded chunks.
•Server chunk occlusion/exclusion: Reduce bandwidth usage and defeat hackers by only sending data for visible chunks.
•Three-dimensional biomes: Save biome data per chunk rather than per block column, create volcanoes with magma chambers, underground rivers, tropical skylands floating over icy taigas, and more.

The disadvantages:
•Unloaded gravity-pause: Falling non-player entities and fluids will be forced to pause their fall if they reach unloaded chunks, but will resume falling when those chunks are loaded.
•Slow falling-pause: Players with slower computers and smaller render distances will have falling occasionally paused as they fall into unloaded chunks, until new chunks can be loaded.

The problems:
•Current sunlight and rain calculation methods cannot work with infinite vertical space: The solution to this is described here.
•Current BiomeDecorator cannot work with multiple vertical chunks simultaneously: The BiomeDecorator code must be altered to function correctly with this, or removed.
•Current cave generation method is executed an extra time for each vertical chunk created simultaneously, leading to lag spikes on world generation: Cave generation's method must be altered to suit this system more.
•Current grass/dirt generation algorithm forces additional chunk requests when chunks are loaded, causing chunks to load slower than they should: This algorithm must be replaced with something else.

---

Changes in how things work:

Obviously, the implementation of this new chunk system will change quite a few things. These changes are mostly either necessary or in the interest of increased efficiency. Such changes are categorized and explained below.

How worlds will be stored:
[spoiler]How the current storage works, and what changes:
Interestingly enough, the current method of storage, the Anvil format, is derived from the storage method that the original Cubic Chunks mod used. The Anvil format stores individual chunk as a series of 16³ quasi-cubic chunks. These 'fake' cubic chunks allow for easier reference of specific data, but they still can't be separated from each other, meaning that it fails to reap the full benefits of this system. Even so, the change allowed Mojang to double the maximum height with no performance hit. Chunks are stored in groups of 32², inside 'MCRegion' files, for a total of 1024 chunks.
By nature, cubic chunks does away with the 'quasi-cubic' nonsense. In terms of chunk grouping, instead of using groups of 32³ chunks, new "3DRegion" files would contain groups of 16³. This means each 3DRegion file contains 4096 chunks, four times as many as MCRegion files. However, each 3DRegion contains only one fourth the amount of blocks. For per-chunk positional metadata, 3DRegion files would use the same number of bits as MCRegion files, after compression. Calculations show that the same area encompassed by a single MCRegion file would consume 64 kilobytes of extra space with 4 3DRegion files, which is nothing.

Converting existing worlds:
Most people are probably wondering something like "But won't this totally destroy all existing worlds?". Absolutely not; conversion could not be simpler. When a non-cubic world is loaded after the implementation of this system, a conversion process will begin and convert the entire world at once(To avoid making chunk loading take longer during play). First, all existing MCRegion files will be divided into quarters to create 3DRegion files. Then, all existing chunks are divided into sixteenths using the quasi-cubic properties to identify boundaries. After that, conversion is done.

The "isEmpty" flag optimization:
A 1-bit flag is added to each chunk, named "isEmpty". If the chunk consists of 100% air blocks, this bit is 1, any other case makes it 0. When the bit is 1, all data for the chunk besides the isEmpty flag is deleted and ignored, which reduces filesize. Empty chunks are never loaded, and locations where they occur are merely simulated as entities reside in them. The chunk will only load when something requires saving inside it.[/spoiler]

Changes to terrain, ores, etcetera:
[spoiler]Terrain:
By default, nothing will change. Small bits of terrain generation code need to be reconfigured to work properly with Cubic Chunks.

Biomes:
By default, nothing will change.

Ore generation:
By default, nothing will change.

Structures:
By default, nothing will change.

The Void:
After conversion to Cubic Chunks, the void and bedrock layer will still exist and generate as they always have. However, the void(Not the bedrock layer!) will not exist as a hard limit and is able to be moved, but not removed, by editing an associated NBT data tag inside a world's level.dat. This feature, that allows for increasing the maximum depth, is intentionally disabled without external programs, to prevent terrain change of any sort. It is intended to be used by experienced mapmakers and world generation mods only.

Superflat settings:
Existing superflat worlds will not change. However, new superflat worlds will gain a new decoration parameter, 'void'. Inclusion of this parameter will cause the void to form below the lowest defined layer. Exclusion of it will cause all layers below the lowest defined layer to copy the settings of that layer.[/spoiler]

Coping with sunlight:
[spoiler]There used to be a solution here, but it wasn't deemed good enough by Jeb. Suggest solutions in this thread.[/spoiler]

Changes to servers:
[spoiler]Settings:
There's a setting inside the Server.properties file called 'max-build-height'. The setting makes it impossible for any player to place or remove blocks above that height.
With the implementation of Cubic Chunks, a new setting named "maximum-generation-depth" would be added. The void, bedrock layers, and magma layers will generate normally at and above the Y level designated by the value of this setting.

Chunk occlusion/exclusion:
Using the raytracing methods already available in the code and used for explosion calculations, servers can identify which chunks are visible to a player, within safe assumptions, and only send the data for those chunks. This both reduces bandwidth usage, and cripples the usefulness of X-Ray cheats.[/spoiler]

Render/Load distance alterations:
[spoiler]After the implementation of Cubic Chunks, view distances' radii will apply to the vertical axis too. This reduces handled blocks in the cases of tiny and short render distances, and increases them in the cases of normal and far render distances. This can be optimized by utilizing a spherical render distance instead of a cubic one, which would reduce handled blocks in all distances except Far.[/spoiler]

---

Frequently Asked Questions:

[spoiler=FAQ]Q: This is impossible.
A: No it's not. See below.

Q: Is this available as a mod?
A: Not yet! But it will be!

Q: I like X-ray! What if I don't want it to be broken?
A: First of all, breaking X-ray hacks will only be possible to do in multiplayer. That said, the system that would break X-ray would be possible to disable by the server owner. If the owner doesn't disable the system, then they don't want you using X-ray, and you should not be doing what the server owner doesn't want in the first place.

Q: I play on a PvP/Anarchy/Raid/Faction server. Won't this system let people pillar up into the sky and create a base thousands of blocks in the air and never be found?
A: No.

Q: I like Minecraft's current height limits. What if I don't want to have an infinite sky or infinite underground?
A: If this system is added, all worlds will not automatically gain an infinite underground. As stated below, the Void will remain in all worlds, even after the conversion to Cubic Chunks. The ability to remove the Void will simply be there. As for infinite space in the sky, the current build limit is over one hundred blocks above any terrain that vanilla Minecraft can possibly generate. It is ENTIRELY your decision on whether or not you take advantage of this height. If you play on a server, like stated above, the server owner can set a maximum build height. If s/he doesn't, then don't play on their server - you don't play on servers where the server owners allow things you don't like. Why would you play on an anarchy server if you hate being stolen from and killed?

Q: Will this affect Redstone at all?
A: No. This system will simply make it possible to make larger redstone circuitry than before.

Q: Won't this break existing worlds?
A: No. Existing worlds can be easily converted by dividing each MCRegion file into 4 pieces, then slicing the existing 256 block-high chunks inside them into 16 individual chunks.

Q: Won't this affect mods? Won't mod authors have a hard time updating their mods?
A: The answer to this question depends solely on the answer to the following two questions: Do parts of the modification code rely on chunk data/metadata? Does the mod author want to take advantage of the features of the new chunk system? If the answers to the first and second question are both "No", then updating a mod to this system should be very easy and quick. If the answer to the first question is "Yes", then those parts of the code will need to be rewritten somewhat, but in most cases, the changes should be fairly quick and easy. The only time that it should be hard to update a mod to this system, is if the answer to the second question is "Yes".

Q: Won't this require a total rewrite of the mod API if that's released first?
A: No. Whether or not even a small part of the mod API needs to be rewritten depends on the way that it is implemented and whether or not there are API inclusions for chunk handling and other chunk-related behavior.

Q: Could a player fall into unloaded chunks if chunks aren't loaded fast enough?
A: No, they could not, and for several reasons. Minecraft has a terminal velocity, though it might not seem like it. This velocity is slower than it should take to load new chunks below the player. In cases with exceptionally slow computers, even if the player did manage to reach an unloaded chunk, their fall would be paused until that chunk can be loaded.

Q: What would happen when water, sand, or a mob falls into an unloaded chunk?
A: Nothing. The water/sand/mob would freeze in place until the chunk is loaded and it can continue moving. You can already see this same thing happening on the horizontal axis.

Q: What will happen to the Void?
A: It will still exist, along with all its effects. The only difference is that the Void is no longer a hard limit and it can be moved. After the conversion to Cubic Chunks, the Void's location will be stored in a world's ' class='bbc'>level.dat, and this location can be changed with NBT editing tools. When and where the Void exists, chunks will cease to generate.

Q: Will this affect terrain?
A: No. However, terrain generators will gain the ability to use infinite height.

Q: Will this affect ore generation?
A: No. Ore is a part of terrain generation. As stated above, terrain will not be changed.

Q: Won't all current terrain generators be incompatible with this system and need to be rewritten?
A: No. Terrain generators work independently of chunks. When a chunk is generated for the first time, it calls the terrain generator and receives a specific section of the resultant terrain to save inside itself. Because of this, some custom terrain generators can generate steep terrain all the way to Y256, where you can experience a large, flat cut-off. Since there are no chunks above Y256 to call the terrain generator for terrain, no terrain exists there.

Q: What would happen if there's a huge solid ceiling so far above you that it is unloaded? Wouldn't you just see the sky, just with everything being completely dark?
A: Yes. This already happens on the horizontal axis, and it is an issue with sky rendering, not this chunk system. As such, this has nothing to do with this suggestion. Please do not post about this.

Q: If you go deep underground, will your plants grow/ores smelt/animals grow?
A: No, because those chunks would be unloaded, just as if you had walked far away. This is a flaw with any chunk system, regardless of shape. It is a necessary evil that allows Minecraft to have infinite worlds. The only way to fix this would be to introduce a separate new system that works with chunks as they are loaded and unloaded. This suggestion deals with the chunk system itself, and not sister processes. Because of that, that is outside of the scope of this suggestion. Please do not post about this.[/spoiler]

---

[WIP] The Cubic Chunks Mod! (Tall Worlds Mod):

Cuchaz has taken it upon himself to bring us the glorious Cubic Chunks, since Mojang refuses to do so.

Cuchaz is using a API of his own creation to help assist in the making of this mod, and he's quite far along, as seen in these two tech demo videos:
[spoiler=T-Demo 1: Vertical chunk loading][/spoiler]
[spoiler=T-Demo 2: Broken height cap and no lag!][/spoiler]
With the basic functionality in place - a complete overhaul of the basic chunk system, and height limit removed - this whole concept can already be considered proven. What remains is making sure everything else functions correctly under the new chunk system. In any case, stay tuned for future updates if it interests you(If it doesn't, then you are the weakest link - goodbye!).

You can follow the mod's development in much more depth in its very own topic!

---

Gallery:

[spoiler=A mountainside with an experimental engine using Cubic Chunks designed by Nocte. 960 block view radius, and 30 FPS.][/spoiler]
[spoiler=A different view of the mountainside with the same engine by Nocte. This time, with 1600 block view radius and 15 FPS.][/spoiler]
[spoiler="A video demonstrating Nocte's engine."]

---

Support & Submission to Mojang:

If you support this, hit the rep button in the bottom-left corner of this post. It is the only good way of accurately measuring support here.

If you wish, you can put the following banner, courtesy of laz2727, into your signature. It helps to attract support from all parts of the forum!

 [url=http://www.minecraftforum.net/topic/1707097-cubic-chunks-infinite-height-elimination-of-x-ray-and-more-60-supporters/page__st__0][img]http://img833.imageshack.us/img833/443/hov.png[/img][/url]

Please help us get word out of this suggestion! Share this with your friends, with Minecraft celebrities if you're familiar with them, or even with Mojangsters like Jeb or Dinnerbone! (Do not share this with Notch. Notch doesn't work with Minecraft anymore.)

The purpose of this suggestion is to have Cubic Chunks implemented in Vanilla. Being available as a modification does not fulfill that purpose. The modification featured in this suggestion is to act as a proof-of-concept only(Note: Its being featured here is to act as a proof-of-concept. The modification itself is on its way to becoming a fully fledged modification).

---

Special thanks:
Cuchaz, for taking Barteks' proof and running with it, to give us a truly functional Cubic Chunks mod.
Barteks2x, for updating the Cubic Chunks mod to 1.6.2, proving that it is possible.
Azraile, for posting the original suggestion and allowing me to take ownership of it.
Nocte, for helping resolve flaws and designing Hexahedra.
MineCrak, for a large amount of valuable insight and enthusiasm into the topic of Cubic Chunks.
aaronfranke, for helping resolve flaws.
PanJouda, for creating the original banner.
Flexico, for creating the predecessor to the current banner.
laz2727, for creating the current banner.
Robinton, for creating the original Cubic Chunks mod.
The_Watchman13, for answering all those stupid questions so I don't have to.

---

Note: Many calculations and information can be found among the many posts of this topic. There are too many for me to cite here, but if you wish, you can search for them yourself.

Download: Map Item Editor (map_0.dat)

Updated for Minecraft 1.7.2!

Includes new map colours

Windows, Mac OS X and Linux supported!

Follow me on twitter @tertrih

Support the development of this mod by giving a donation

Note: Map items made with the MapItemEdit can be viewed by anyone in the game, i.e. they don't need to download MapItemEdit to be able to see the map items you made with MapItemEdit. The program is only needed to actually create custom map items.

Ubuntu fully supported. The included binary should work on other linux OSs. The linux source is available on the sourceforge page, under the files tab, so you can compile it for your favourite linux OS if you so choose.

Includes script to easily use in Mac OS X!

Requires mono to work on Mac OS X, but includes a link to the mono download page.

Changes in 1.1.2

Allows you to create a banner (resulting in multiple map files) in a single click

Changes in 1.1.1

Added line, rectangle, and clear tools
Added command line picture export option

Changes in 1.1.0

Command line options added
-create newmapitem.dat picture.bmp
-nomaintain
-oldcolours, -oldcolors

Map item files can be dragged and dropped into the program

Changes in 1.0.9

Included old colours for people using versions older than 1.7.2

Changes in 1.0.8

Included proper support for transparency

Changes in 1.0.7

Added small mode if you are running a resolution with a height below 800

Changes in 1.0.6

Fixed a bug where shades of white would be added to the minecraft map as transparent
Added a paint option that allows you to paint any colour supported by minecraft maps directly to the canvas

Changes in 1.0.5

MapItemEdit now accepts the dimension to be either TagByte or TagInt. This doesn't change the user experience of the program, just a low level change that should remove problems some people have been having.

Changes in 1.0.4

Fixed a bug with the fonts
Added the new map colours introduced in Minecraft 1.7.2.

Changes in 1.0.3

Export your minecraft map files as a bitmap (*.bmp) file

Changes in 1.0.2

Use any font installed on your computer to add text to a map item

Hi guys! I have been working on a program that can view and edit minecraft map items.These are located in your minecraft save folder under the data folder, and are named map_0.dat, and increasing the number from there.

I made it mostly because I was interested in making a minecraft tool, and thought making a map item editor would be a relatively easy thing to pull off. In the end it took a bit longer, because I also decided to make a named binary tag library (the data format used by minecraft) to use in the program.

My initial version of the program wasn't as robust as a result. Using the library made my life a lot easier, as all the business with big and little endians and the bits and bytes is handled by the library. If you are interested, you can check it out here NBTSharp.




Map items in minecraft can only display a small number of colors. Each map item is made up of 16384 pixels, which is 128*128 pixels. When you import a picture, the program takes a sample from your imported picture for each of pixels in the map item. The color matching is limited, but it gets the job done. Besides pictures, you could use a picture editor to write text into a picture and convert that using the program.

The program gives the option of either stretching or squash your picture into the 128 pixels, or keeping the aspect ratio the same as the original picture.Another feature of the program is it allows you to edit the properties of the map items. xCenter and zCenter are the point at which the map is based. It defaults to 10000 for new files. Changing scale allows you to make close up or zoomed out maps. Dimension of 0 is for world map, and 1 for nether maps.

Enjoy, and keep minecrafting!

Quote from FriedPuppy»

I guess you have never been on the forums then.

I think the notion that people expect us to finish the mod before release is ridiculous. Open Alpha (which isn't that far away) will consist of only half of the content that we ultimately want to be in the project. The storyline wont even be fully implemented.

Closed Alpha testing is ongoing and rather successful as of right now. We are about to begin getting the DWCM into the hands of the rest of the Closed Alpha testers that are currently in the skype chat within the next few days.

Noone is sick of the waiting than we in the Mod Division are. Joe and I have spent a large part of 3 years working on this and Emir has been invaluable over the past 6+ months that he has joined the team. We all want it out as soon as we can, but we are not going to risk our project's integrity by releasing a halfway functioning piece of trash. Closed Alpha testing is the final step we need to take before the first public version can be released.

The fact that people are so demanding, as if DWCM were our jobs and only responsibility in fact only works against the public. I don't respond to people like this because of the simple concept of respect. Why would I choose to show someone respect when they didn't show me any in return. My mantra over the last few months has become "We are not slaves, we do not OWE anyone anything."
And to a certain degree that is and is not true. We owe the kind & absurdly patient people of the iKingsSGC & Mod Division community who have stuck with us without complaining. Those people who have true faith in us will always be my first priority when it comes to the projects. Which is why I am so excited to finally be able to fulfill that 3 year old promise in the coming weeks/months.

i wont lie, Christmas release, would be the best Christmas present haha.

"The Update that Changed the Names"

People need to be patient, Rome wasn't built in a day and neither was the doctor who franchise. Obviously none of the people complaining of the time are in a fandom, As if I recall the poor people over in the sherlock fandom had to wait 2 years. Which in comparison to the DWCM is a rather similar timeframe, I've been watching from the start, lurking in the background watching you all complain about "When is it coming out, ogm I've been waiting forever" when in truth, you're just impatient. Nothing good has come to those who have rushed projects, the wonderful people of the DWCM/S7C team/s have and still do spend their free time, not getting payed at all for this AND providing quality content that rivals that of larger studios that do it for the money? THAT is dedication, if you cannot understand that then you may as well leave.

But I feel like this will fall on deaf ears as it will soon be buried under a page or two worth of comments, then you'll all just start again so in the meanwhile I will just have to sit back yet again and wait. But before I do?

A big thanks to the Mod team for spending so much time on both projects over the years, You've given me a reason to be excited for minecraft yet again and in the meanwhile I suppose I've got Stalker and the Misery mod to keep me entertained. Until then, Adios and cheers!