Minecraft Forums

Quote from baddaspig»

Is there a world download for this? I want to just explore this vast destroyed world and find people's bases and stuff.

The world file size is over 170 gigs so im gona say no

Quote from arthaiser»

that is not even close to the topic of this thread, please next time read the whole thing before making a random comment

There was no need to be rude there, I was just pointing out an error in your thread. If you want people to agree with your ideas don't be rude.

I do agree with your idea though.

This is a rather small suggestion that would just make managing potions a little bit easier.

As you know in 1.8 rabbits were added to the game. One of their drops, rabbit fur has almost absolutely no use whatsoever (except crafting small amounts of leather which can be gotten abundantly from cows). Now though they can be crafted into a potion pouch.

Here is the recipe



Note Leather=Rabbit fur


How it would work: When held in your hand you can right click the pouch and put potions into it. It has 9 slots (from the dispenser) each slot can hold one potion (splash or regular it does not matter). you can circle through the the potions with the right and left arrow keys. All potions would be grouped together, so as an example lets say my pouch has 3 splash potions of harming, 2 splash potion of poison, and a swiftness potion. when I have the bag selected It will group the potions by most amount to least, so the slot would say Splash potion of harming II #3. If I right clicked the potion would be thrown and it would change to Splash potion of harming II #2. If I hit right arrow twice it would then say Potion of swiftness minuet:second #1. If I then hit left arrow once it would say Splash potion of poison #2 minuet:second etc... The pouch can only hold 9 potions of any type.


Important: You can only have one potion pouch With potions in it in your inventory at a time. If a potion pouch that is holding potions is already in a players inventory and potions are attempted to be placed in another pouch the 2nd pouch will be dropped along with its potions. If a potion pouch is dropped on the ground it will lose all of its contents. Neither of these mechanics apply to containers (like chests or dispensers).

Note these are the dispenser options from the poll

Option 1: when the dispenser is activated all Splash potions in the pouch will be used, all Regular potions would be dropped, and the bag would be dropped as well

Option 2: all potions and the bag would be dropped on the ground.

Its your computer seriously on my desktop I get around 170 fps and on my laptop i get around 60-50 fps on 1.8.3 So yea as Baum said its you

Quote from SpaciousName»

No guns, lasers or beams of any kind in vanilla minecraft sorry. I haven't even read the original post.

You absolutely cannot do that ever! you can never just look at the tile of a suggestion and say "oh i don't like that name so I don't like what's being suggested" read the thread than post again I despise when people do this I am literally disgusted

This is just a running joke you make it sound like it will turn into something terrible. There would literally be no point to remove it.

If you have silk touch you can mine out some grass from the mainland and replace the mycelium with it but the biome will be the same unless you change it with an external program (like mc edit).

besides the retexturing of the stone slab I support this suggestion. We also need stairs and slabs for the prismaine that would make everything a little nicer.

Please no. When I want fire and wood to be anywhere near each other in a build i surround the wood with string so it can not catch fire (blocks can only catch fire when exposed to air). Making any block that is not flammable, flammable is a horrible idea because it could make old creations burn which, is why this would be a mistake.

First: Let a Beacon's regeneration work on villagers. Villagers are unable to heal themselves, villagers are unable to hide or defend themselves particularly well, and zombies as a predator are too much for the standard village to handle. They die swiftly and often even despite players' best efforts. A regeneration effect may actually keep them alive long enough for a player to deal with the threat. I don't think it's too much to ask that an end-game powerful item like a Beacon do something like this.

Second: Let the population to door ratio be 1:1. It makes no sense to have 3 doors to one villager. The villages we have now feel empty, and attempting to increase the population takes lots of space, especially when keeping zombie defenses in mind. The villages are already spread out over a wide area. The villagers do not need any more room than one door per person, and I cannot think of any rational game balance reason that it is that way. The food/trading breeding requirements from 1.8 are enough of a population cap as is.

Third: Houses, as loosely defined as they are in Minecraft, should have an “occupied/claimed” variable. A villager entering a house for the night (and only at night) will cause it to be “claimed,” causing other villagers to simply not acknowledge it as a house. This will get the villagers to spread out a bit and not all swarm into one house. The only exception is that child villagers will follow one of their parents, or another adult if their parents are not available.

---

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.

-snip-

Jitterclicking is harder than you think.

if you like 'jitterclicking' then use hoes. 1.9 adds these options.

Quote from Bishounen_Floyd»

In answer to the OP's question: Because some of us realize that HARDER is not the same as VARIETY or BETTER.

The new combat learning curve is WAY too steep for a game who's largest target market is children. Children who will be the most likely to have difficulty with the new combat system and will walk away from Minecraft much more readily than older players. This means less new players to replace people leaving, resulting in a shrinking player base.

Maybe some Elitists are OK with that. You can see them in this thread mindlessly repeating the "people don't like change" mantra, as if it will magically make the complainers go away and keep the Elitists in their happy place. But for Mojang this is bad. Perhaps less bad now that they have Microsoft to be their sugar daddy, but still bad. MS is going to want to get that 2 Billion back, and heads will roll if the player base shrinks because of bad changes. The new combat changes are, by any logical and reasonable measure, bad.

The rest of the update is actually pretty nice. I like the upgraded End, more blocks are nice, and the other stuff is interesting at least. But the combat system is TERRIBLE and needs to go. Mojang needs to back out the combat changes and just go back to the drawing board, getting HEAVY input from the community and tapping mod makers who have well-balanced weapon mods for ideas.

The Minecraft community has made most of Mojang's management rich beyond the dreams of Avarice.(Especially Notch, but he took the money and ran) We deserve an AMAZING combat update. Not this hacked-together weak sauce garbage.

Why are you complaining about the combat system being difficult to get in to? That's the least of the game's difficulty curve issues; what about things like crafting being completely essential to surviving and having only the vaguest of hints to its existence? How are people supposed to guess that the Nether exists whatsoever, much less create a portal? Survival is obtuse and difficult to get into in 1.8, 1.9 isn't creating a new problem so much as adding a little to an existing one.

Even then, it's not that difficult to get into. The only unintuitive thing about the new combat system IMO is that attack indicators are turned off by default, so someone isn't going to realize that spamming will deal pitiful damage until a few minutes of fighting mobs have passed.

Quote from Bishounen_Floyd»

The new combat changes are, by any logical and reasonable measure, bad.

What logical and reasonable measure? Yours? I don't see any arguments in your post that cannot be easily disassembled and thrown out the window. Group-name-calling, appealing to Microsoft who only pays the bills, suggesting that a damage indicator is too hard to understand, and suggesting Mojang get input from people who they already got input from.

That's not logical. That's ad hominem, irrelevant distractions, nonsense, and ignorance, respectively. You also have some confirmation bias in your second post.

Quote from Bishounen_Floyd»

In my experience, everyone who tries the new combat dislikes it. They may have been excited at first, but the more they use it, the less they like it. I expect this number to grow unless Mojang pulls the combat changes.

Well interestingly your "everyone" doesn't' include the 20 or so people I know who play Minecraft. Half of them including me don't care one way or another about "the new combat" and the most of the rest like it. The ones who don't like some of the new things are still going to play Minecraft for all the other things they do like about it and will live with the new combat. Please try not to make it sound like you speak for everyone who plays minecraft when you don't. As was already stated you may hate it but others like it. Also I wonder what " the more they use it the less they like it " means. It doesn't take me any time at all to decide I don't like something but, I, as well as most people may get to like something by working with it, which I think is the opposite of what you are trying to say.

Quote from Bishounen_Floyd»

In my experience, everyone who tries the new combat dislikes it. They may have been excited at first, but the more they use it, the less they like it. I expect this number to grow unless Mojang pulls the combat changes.

I must not be everyone, because I have literally no complaints about the current combat system.