Minecraft Forums

Quote from Ghobe»

So I've been looking into the ore processing thing and I'll have the Tier 3 setup soon, but uh...the tier 4 requires gravel/flint/gunpowder...which I've been throwing gravel/flint into the ocean...but I can fix that...the real problem is gunpowder. Is there a way to farm this with these mods or is it still mass murdering creepers and praying?

Edit: Post corrected, with thanks to grimallq for needed info.

Crusher + Cobble = Gravel
Purification Chamber + oxygen gas + Gravel = Flint
Crusher + Flint = Gunpowder

Quote from Ghobe»

So it doesn't really do anything if TE isn't installed then...hmm. Alright. And thanks for the actual values. But just to verify.

Combustion Engine with Fuel = 60 RF = ?? when going into machine directly = ?? when going into Mekanism Energy Cube.

Advanced Solar Panel in Desert = 300 Joules = ?? when going into machine directly = ?? when going into Mekanism Energy Cube.

If you could fill those in so I can understand, that'd be great.

That depends on what mod the combustion engine is from, whose pipes is transporting it and what mod the machine using it, is from.

A BC Combustion engine produce RF's and can only output directly to a machine that uses RF's
A Mekanism Bio-Generator produces Joules's and can only output to Joule compatible machines.
A TE Generator (not familiar with the mod) generates RF's and can only output to RF compatible machines.
All 3 will output to a pipe/tube/cable/conduit/etc capable of accepting that power type.

An energy transporting pipe has to be used to power machines that use a different energy type.
Mekanism Energy Cube's maybe the exception, since they will convert between energy types , also.
.
Since version 6.1.6, BC now produces and handle's RF only.It's pipe's will only handle RF's,
Mekanism cables use Joule's, but will convert during input and output,
and a TE conduit uses RF's. and converts during input/output, also.

Mekanism and TE's pipe will "Convert To" or "Input From" RF, J, AE or MJ'(but MJ"s is being retired)

Using you example, the 60RF output would be unchanged when direct fed to an RF using machine,
A Mekanism cable would convert it to Joules, while moving the energy, then to whatever (supported) format the,
block at the other end used, a Mekanism Energy Cube.uses Joules, so it would not be converted a second time.
A TE conduit would keep it as RF, and convert it into Joules when outputing to the Mekanism Energy Cube.
A BC pipe keep it as RF, and pass it as RF to the Cube. The Cube would convert it to Joules.

The answer for Solar panels is the same.
The exact ending values are determined by the settings in the cfg file,
(RF output) * RFtoJoules = Final Amount in Cube.
(Joule's output) = Final Amount in Cube.

Quote from Ghobe»

Think my biggest problem with the cables is that they can't handle a combustion engine if it decides to store power. I have to destroy the engine and replace it, otherwise it just sits there with 100k RF stored up. And then my problem with Kinesis is that it's not smart enough to run the power down a separate but still connecting line if it gets choked somewhere. Though at least that limit is extremely high

Is this a BuildCraft Combustion Engine?
If, so , it's a compatibility issue, you can use the Mekanism Bio-Generator instead or Windmills to replace the power it generates.
Buildcraft has an add-on that adds teleporting pipes that you could use.
They can teleport power and items long distances to receiving teleport pipe, but need chunkloaders to keep them all loaded.

Quote from Ghobe»

You're thinking of the Configurator Tool, the Block Configurator is that "color configurable functionality" for the machines. I mean I understand how to color code it, but I can't seem to be able to get the crap to go through a pipe. Tried using Logistical Transporter with and without a Logical Sorter but I can't seem to get anything to move from one machine to another


P.S. WTB more mass storage for energy than just the Ultimate Energy Cube and laying down billions of useless cable. Same with gas. WTB Gas/Energy version of Dynamic Tank pst. ;p

P.P.S. I really hate how the edit button breaks my quote blocks on these forums.

Sorry 'bout that.

The configure sides page has 2 sets of colored buttons.
The left set controls inputs via colored logistics pipes.
A side marked as red will only accept items that pass through a red colored pipe.

The right side configures each side's behavior, where the colors correspond to the color outlines of the boxes on the main page for the machine.
if you set the left side to red, the the left will accept inputs into the input slot,
blue outputs items from the blue output slot, etc.

Yeah, I know, i'm teasing you.
Machines only output automatically when the Automatuc Output button is on.
It's in the top right corner of the configuration page, I believe it has a "A" on it.

More energy Storage? Less cables?
I believe (but don't use) EnderIO has energy storage that forms multiblock storage blocks.
So only 1 cable to it and 1 from it is needed.

Dynamic tanks will hold properly registered gases and liquids.

There's a difference between "allocating" and "needing"
You are giving the JVM permission to use up to 3GB( That's Allocating),
but MC doesn't need that much at start up.

In the F3 screen it tells howmuch memory is allocated and how is in use,
as MC's needs increase, more is allocated , up to the max amount you
allocated in the JVM Arguments options.

You will have problems if the arguments are not used correctly, the game will crash.
The rule of thumb is that you should not set the maximum to more then 1/2 of what is installed
and if you set the max, the you should set a low minimum, to make sure the game has the flexibility it needs.

Here are the JVM Arguments I use on an XP system with only 2GB ram installed:

[quote]Xmx1g -Xms256m -Xmn128M -XX:PermSize=64m -XX:MaxPermSize=128m -XX:+UseParNewGC -XX:+CMSConcurrentMTEnabled -XX:+UseCMSCompactAtFullCollection -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy

-Xmx1g -This tells the JVM that it can not use more then
1GB of ram. The value you use should be 1/2 of the total ram installed or less.
If you set it to 3g, then you must have at least 6GB ram installed.

-Xms256m - This tells the JVM to reserve a minimum of 256MB ram for MC, if it needs more, MC will request it.
I suggest you keep the value at 256m, using more does nothing useful.

-Xmn128M -This tells the JVM to set aside 128m of the allocated memory for temporary
objects that have a short lifespan.
This is used primarily by mods and has garbage collection performed on it frequently.
Objects that survive long enough are moved to long term memory instead, allowing this heap to be recycled
and help keep memory use under better control.


-XX:PermSize=64m and -XX:MaxPermSize=128m
is a fix for a bug introduced in 1.6 (i believe) that caused frequentl crashes from memory errors.
not everyone needs to use this option

XX:+UseParNewGC
-XX:+CMSConcurrentMTEnabled
-XX:+UseCMSCompactAtFullCollection
-XX:+UseConcMarkSweepGC
-XX:+CMSIncrementalMode
-XX:-UseAdaptiveSizePolicy

These are mostly garbage collection options I use, since my system only has 1GB for MC to use

That log file has too much info, it include your unencrypted Log on name and password,
it looks like you're not using the official launcher to run the game, and now every hacker has your logon info;.
I suggest that you edit that paste a.s.a.p.

Edit: FYI , yes i'm speaking to einsteinsci, edit it now

Quote from Wolve64

Is there any version of ChickenChunks for 1.7.10? Or is there any other mods that provide the means to load chunks?

no .

Immibis' Dimensional Anchors

Guys, he young, let him be curious, and stop using him as a target for your OCD.

It sounds like the map being "partially" corrupted by a mod or map editor used to create it, and tthe game is having trouble with some of the saved data
Try redownloading the map and starting over, to see if the problem happens again.
If so, read the thread s for the mods used to see if anyone else has this issue

Sorry I had responded a few hours ago but didn't realize i had gotten a bad gateway error...

I havent dealt with this eror myself, But I have edited chunks using MCEdit with no problems.
I'd suggest using it on a baked up copy of the world map, and test it as a SSP map aftwards.
You may have to delete the healthy chunks around the bad ones, too.

If this doesn't solve the problem, then its probably something to do with the fact that it's a 1.7 map and 1.8
doesn't like it :smile.gif:



Edit:
Correction I have seen this on a private server I play on.
Either the server stopped sending chunk updates or the local clients cache had become corrupted,
and I was surrounded by invisible blocks (underground caves were visible), until finnally MC crashed on me and
when I reloaded it, and rejoined the server, the chunks were displayed correctly.

TehKrush no longer maintains these mods.

Timber! - Last updated for Minecraft 1.6.2 (July 2013), download here: https://archive.org/details/timber-1.6.2
PlasticCraft - Last updated for Minecraft 1.1 (Jan 2012), download here (incl multiplayer!): https://archive.org/details/plasticcraftv3.0.2
HiddenDoors - Last updated by bspkrs for Minecraft 1.5.1 (Mar 2013): bspkr's HiddenDoors thread
Squirrels - RIP, I lost my backup for this, please message me if you have it and I will link it here!

Other mods I made: Mimic Chests (part of "Evil Minecraft"), Terraria-inspired Corruption, MoreFlowers. Helper mods: PortableWorkbench, TorchesAnywhere, CompressedRedstone, GemblockFix.

There is a much more up to date Timber mod by pizzaatime found here (2020): https://www.curseforge.com/minecraft/mc-mods/pizzaatimes-timber-mod

Anybody is free to update any of my mods or use any assets or code from them. I no longer have the sources for all of them though so you will need to use a decompiler. Good luck!

---

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.

Nice way to derail a conversation by picking at the nitty gritty parts of the post.
The fact that his post is posed as a question, implies he doesn't know and would like to find out. Referring him to youtube is a poor move on your part because you are essentially encouraging him to not use this forum ,instead to go to google and find the answer.
Good job.

To the OP, I would also like it if they could expand the trading system and make villagers more useful. Currently the only practical use for them is to build an iron golem farm. I have no clue what the villagers will sound like. I don't pay very much attention to the sounds, I usually have music on in the back-round.

To the negative people on this forum, give the guy a break. Your actions actually discourage people from using these forums. As members who have been around longer, you should know better than to be so petty, especially with someone new to the forum. In short, grow up. You guys seem to make a habit of missing the point. If my post offends you, then it was very likely directed at you. Be offended.

Quote from TrashCan-Man23

No ones putting it out there, so I thought I'd throw it out there.

If this thread had any influence whatsoever, would you agree that ocean size should be cut, oh let's say in half?

Travelling a 3,000+ wide/long (whatever) ocean, it's just annoying.

So, MC forums, where do we go from here?

100% disagree with OP.
Now this makes boats more useful, adventuring more fun, I dont like seeing a desert on the other side of an "ocean" when the ocean is maybe 10 or 20 blocks in width.

The big oceans are awesome. If you don't like them, start a new world. But leave the big oceans in the game for those of us who actually like them.