Minecraft Forums

Meh, I'm not big on the idea of them being "pet" mobs. I'd like to have a regular rabbit farm.

Maybe if you tamed them with a special item (like golden carrot) they would become your "pet". Otherwise they'd just be general "tamed" and not run away from you and be able to breed and etc.

Quote from DerpyDerpp

This seems rather pointless. Can't you just use a texture/resource pack?

No. Then all bars would be gold.

What the author wants is an ADDITIONAL variation to iron bars which are gold. You know, for decorating.

Anyway, I support. Its a small improvement but it would be a good addition. Definitely worth the small amount of time needed to add it to the game.

This is happening for me as well. The src was always decompiled for you in previous versions.... but I'm not sure how that works with the new gradle stuff.

Edit: found it

You need to run
gradlew.bat setupDecompWorkspace --refresh-dependencies

as specified here:
http://www.minecraftforge.net/wiki/Installation/Source

No support due to needed a bucket of water to craft. I will never eat pickles because they can't be mass produced (since water buckets don't stack).

Quote from pinballboy7

TL;DR:

You are doing yourself a diservice. The above argument is golden.

I often disagree with the TES lack of advanced technology. The time skip between the games is huge-- yet the world seems so static. So yeah, even if you must compare the games, the premise of guns not fitting in the worlds shouldn't be accepted without supporting evidence.

I've heard that right now, non-tamed horses despawn. I think that is crap. It means you can't properly breed horses (you'd better tame those babies or they despawn). Its also hard to tell the difference between a tame horse (won't despawn) and a wild horse (will).

I'm okay with non-craftable horse saddles if: horses don't despawn (otherwise I want to tame and saddle every horse I see, to be safe) and you can remove saddles from horses (I don't want to kill my retired steed for their saddle).

This is a mod for
Minecraft 1.5
MCP v7.42
FML 5.0.24.582
Forge 7.7.0.582

Yes, I know 1.5.1 is out, but I haven't updated.

This mod is written terribly, doesn't use any of the forge interface. I just modifies base classes. Part of the reason I'm posting it is perhaps someone will want to add to it/ clean it up. If so, shoot me an email.

What this mod does:
It generates hair/eye/skin colors for villagers.
There are 10 hair colors (4 alleles, red, blond, brown, black), although 4 of those colors are shades of black.
There are 10 eye colors (4 alleles, gray, blue, green, brown), although 4 of those colors are shades of brown.
There are 5 skin colors.
It preserveds the outfits of the 5 professions
There are 10x10x5x5 (2500) villager textures included in the pack, although some (like very dark skin with bright blond hair) aren't used due to the way phenotypes are calculated.

When two villagers mate a child with the appropriate genotype is created.

When multiple villagers are created at once in a village (like in creative, or when a new village is generated) all the villagers have similar (but not the same) genetics.

Here's a screen shot:


You can download the mod at:
http://misc.prinnysq...d_Villagers.zip

Complete support. Building extra tall towers and spawning giant mountains = awesome

This is a good idea. Personally, I'd like to see a difficulty between Peaceful and Easy where there are no monsters, but you need to eat and don't super regen life. That way survivalists can play realistic "survival" that doesn't include fantasy monsters.

Motivation: Minecraft (for me at least) is about conquering your world. You add structure and light and build zones of safety. But an unnoticed dark corner, even in an otherwise sealed immaculate area allows monsters to spawn. What if you want a dimly lit garden for midnight strolls? Its time consuming to even ascertain if a particular block is going to spawn monsters (count distance from all the nearby light sources).

I have two related suggestions. First, Lapis Glasses, that allow you to see if a block is sufficiently lit (minus the sun) to stop monster spawning. Second, the Lapis Orb, a holy totem that stops monster spawning in a certain area regardless of light level.

Lapis Glasses:


Lapis Glasses can also be found rarely in dungeon chests.

When you are holding the glasses you can right click to put them on. All nearby blocks (maybe 100x100x100) will have there tops tinted red if monsters can spawn there and tinted blue if monsters cannot spawn. This does not take into account light from the sun, since that's transient.

Lapis Orb:


Lapis Orbs can rarely be found in dungeon chests.

Lapis Orbs are totems that prevent monsters from spawning in an area (11x11x7) centered on the orb. Its not a light source, it can be buried or displayed, its effect works regardless.

Questions:
Is the Orb over powered?
I don't think so, but feel free to comment. Torches stop monster spawning and are easy to make. The orb is far harder to make resource wise. Torches and glowstone will probably continue being the lead ways to stop monster spawning. However, for some custom builds, the orb would be a great option. Especially since it can be hidden in walls.

Is having an "orb" anti-minecraft?
I think an orb would be some sort of holy symbol. I like the idea, but I'm not set on it. If anyone has suggestions on how to improve, I will listen. Its the functionality I care about.

Why do we need the glasses if we can just count distances to light blocks?
The glasses would be necessary to see the effect of the orb. But more importantly, it would free players to make more creative structures in less time. Players could put on the glasses, tour their buildings, and be confident they are monster proof. It would also show new players who find them in chests the explicit limit of torches and other light sources.

How do the glasses work?
Well they could be programmed a number of ways. I was thinking the top texture of the blocks would be tinted when rendered, similiar to how biomes tint grass. The tint would be very noticable, and it would be red or blue depending on if monsters could spawn.

Edit 2/2/13:
Changed "gold" and "lapis" to "gold ingot" and "lapis dye" because that's what I meant. This might be overpowered (as mentioned below), but feel free to discuss. Remember, you can light a huge area with torches easily- it just looks really bad.

Added the "How do the glasses work" question.

Edit 2/3/13:
Added crafting pictures. Changed the spawn protection of the Orb to 11x11x7.

---

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.

PETITION DETAILS
In 1.3 we got new types of wood that correspond to the log they come from, but only 3 blocks are actually those colors: the normal blocks, slabs, and stairs. Lets add more.
All of these are for aesthetics.

Each idea is rated by a 5 star rating of their importance of being added.
= Probably shouldn't be added
= Probably won't be added
= Good Chance
= Could be added
= Should be added at all costs

Crafting
There could be two ways that crafting works.

IDEA 1: The output of the crafted item will be based on which wood type is most used. If there is a tie between the items, the output item will be oak type.

IDEA 2: By Ouatcheur, Crafting the items will of course, be the exact same, but trying to crafting something will multiple colors will give you the color that is used the most in the ingredients. In case of a tie, the 'winning' color will always be the one from the ingredient that has the smallest Block-ID (or damage value, for tied-in-number ingredients that all have the same smallest Block-ID).

Multicolored Buttons

To me, the way buttons mixed into the block they're made of was a great hidden redstone advantage. Adding multicolored buttons won't be too much, just a way so you can hide buttons on multiple wood types.

Multicolored Plates
The same reason behind the buttons, plates can be hidden to the block they're made of, plus can be used for tables.

Multicolored Sticks
Multicolred sticks would open up new available colored blocks. The sticks, however, will not create multicolored tools.

One problem though is that the texture of the current sticks is the same color scheme as the spruce planks, so either the Oak sticks will have a new color, or the Spruce sticks will be darker than their block color scheme.

Multicolored Doors, Fence Gates and TrapDoors
If anything, doors appear on every house, and it would be nice for the doors to match colors of their houses. Trapdoors, and fence gates too could match multicolored fences and the color of houses.
Fences gates will also have their type depended normal, so different sticks or planks will be no different.

Multicolored Fences
A commonly suggested idea, obviously since fences are used a lot. They match many aesthetic perspectives for biomes.

Multicolored Chests and Trapped Chests
What belongs in every house and is needed by every Minecrafter? Yes it's chests you dummy.
Why not? Their wood colored, great decor, and they don't have any current aesthetic advantages.
This would also include Trapped Chests. No better way to make a trap insuspicious than disguising it as a regular looking chest.

Multicolored Bookshelves
As a full block itself, bookshelves should've been color compatible in the first place.

Multicolored Signs
Suggested by Fortanono.
Color signs add an aesthetically appeasing decoration so you can make letters mix into the background, and make those fancy couches.
Also, due to how dark Spruce and Dark Oak is, the text for them will be automatically colored white to make them easy to read.

Multicolored Ladders
Suggested by numerous souls.
Color ladders makes your wood colored house more appeasing, blinding into a block's background, and adding more decoration options.

Multicolored CraftingTables
Crafting tables are largely composed of the wood texture, making them stick out like a sore thumb. Although not having large decorative uses, it can make houses more symmetrical.

Multicolored Beds
If they ever implement wool color based beds, this could go along with it, quintupling the possible mixes. Of course that would also make a complete mess of inventory... so this probably shouldn't and won't be added.


Multicolored Pistons
Believe it or not, this revolutionary redstone objects are decorational as well. They can be used as fancy tables so multicolors could help you with your interior, plus, can help you hide the pistons with the wood background.
(Pictures Coming Soon)

Multicolored JukeBoxes and NoteBlocks
Although they're largley different from wood textures, they can pimp up your houses. Note blocks can have their song sections color-coded to keep your songs organized.
I maybe abandon this idea. There's a question in the poll if you want to support it staying or leaving.
(Pictures Coming Soon)

Multicolored Item Frames
It's a bit unfair that your stuck with the birch wood for your item frames. Like signs, the multicolored item frames could mix into their backgrounds, making it more appeasing.

Multicolored Boats
Whats a better way of sprucing up (pun intended) your docks than having boats of different colors? Better yet, you could have boat races with different colors!
When these boats crash they will drop planks and sticks according to their type.

Pictures
I mocked up some photos for what the blocks might actually look like. I wasn't able to take pictures of placed bookshelf blocks because the side textures messed up.

There is also a mod containing the fences and pressureplates that someone has brought to me.
http://www.minecraft...ces-mod-update/



If you have a Reddit account please consider upvoting to support the idea here.


Here's a banner for support.

Making these stone types appear at different layers and have different mining speed and/or pickaxe requirement would really spice up caving. What in my opinion is really lacking in the game is stuff that is exclusive to layers high up in the world. You just need to dig down to lava level and you'll get everything the game has to offer in terms of ores and raw materials. I think it would be really cool if there were ores, stone materials or other stuff that only appears in shallow cave systems or even mountain rigs.

I guess I don't have a problem with it. It just changes the mechanic slightly.

But like most other tweaks/nerfs to the food and hunger system (like the bonemeal nerf), it really doesn't affect anything other than the difficulty of very early game.

I just don't understand why they keep trying to make the first 15 minutes in a new world more difficult (it's already the hardest part of the game), just to make the rest of the game more tedious and annoying (and not more difficult at all).

Also, your poll needs a "Don't care" option.

Being able to skip the night isn't "powerful". It's a way to not make the player afk for 10 minutes when they want to be working on something outside.

Shelters are ridiculously easy to build. Dig a hole three down, jump in, and put a block of dirt over your head. There, you're safe for the night. Removing the ability to skip the night just adds an inconvenience to the game without adding actual challenge. Even worse, early game is where the players are most likely to just sit out the night because they aren't as well-armed and haven't lit up the area yet. You're removing convenience when players most need it and when they already face the most challenge.

Quote from LordLucas13789

I've read a few of the posts on this thread and I'm not going to knock the concept at all it would be fascinating to see the outcomes.

I do however think that the whole concept is flawed at the most basic scale that Minecraft is a game and people want to enjoy the experience. This is not a problem if you end up a general, commander, dictator, trader for example. The roles are rich and interesting and the communication between each would be very stimulating i'm sure. But for those who have a humdrum existence gathering wood or slaving with a nerfed pickaxe in a mine would not enjoy it so much and, I fear, would not stick with the study.

Several people have expressed similar ideas in this and other threads, arguing from the assumption that everyone wants to be the boss and that not being the boss is no fun. In my experience, this is simply not true, both in games and in reality, and it betrays I think a rather serious misunderstanding of the nature of leadership. Being the boss is not simply a matter of being the one who gets to tell everyone what to do; that is actually the hallmark of a very poor leader.

Throughout my life, I have more often found that the problem is not that everyone wants to be the leader, but that nobody is willing to or those who are have no idea how to lead. I remember the chaos of trying to have my garage band jam with a bunch of other musicians, and how hard it was since everyone was so friendly and nobody wanted to impose by taking charge. When I finally did decide to swallow my lack of pride and ambition and call out what we should try to play next and count it in (being the drummer helped here), everything went much more smoothly.

Years later, in a roleplaying game, I thought to try to explore the ambition trait that I generally lack, and tried to play a character who wanted to lead. It was actually kind of frightening how readily the other players embraced following a leader. History bears this out: people just love to unite behind a leader. And all that fighting and rebelling and warfare? It's not because everyone wants to be the leader. It's because they want to follow different leaders.

So I'm really not worried about people choosing not to play if they don't get to be the king. Seriously, that is the very least concern I have about this experiment.

I'm not really keen on being the leader, and neither are most people, I've found.

Updated OP: 9/3/12 (Modified OP explanations, thanks to getpoopedonkid // Fixed Poll)
Updated OP: 3/8/12 (Fixed Poll)

---

NOTICE (As of Snapshot 12w01a):



This is an screenshot of the beach gen that was re-added in Snapshot 12w01a. Please note that this is not representative of the new beaches in general, but instead an example of what the new generation can create!

Jeb appears to have simply changed the blocks which form the transition between land and the ocean biome from dirt to sand. This forms ugly clumps of sand hardly resembling beaches on hilly terrain. This DOES NOT resemble actual beaches or beaches as they once were in Beta 1.7.3! Or reality for that matter.

What should be done to correct this:

• Simply limit the max height of sand that can generate to two to three blocks above sea level, which would be identical to beach generation prior to Beta 1.8. With beaches essentially being their own biome, such a change should feasibly be easy since it shouldn't conflict with other biomes. If you believe otherwise, please state so and why!

---

OP:

With the inclusion of the new terrain generation in recent releases, I've read about many major topics and comments having to do with terrible biome transitions involving the swamp biome and the such. However I have not seen any real topics concerning the exclusion of beaches and the issues concerning underwater bedding. So here is the point of this topic:

Summary:

1.) Beaches was a widely-liked feature of the previous terrain generator and it needs to be restored.

This should be simple enough. Just add back beaches into the terrain generator. Also gravel beaches should be returned as well. More on that later in the topic.

2.) Although a less important issue, underwater bedding, lacks the uniformity and overall realism that it used to have. Currently, lakes and oceans are covered in splotchy patches of dirt, sand, and clay.

The main argument against the current underwater bedding generation is that allows for easy access to large amounts of clay, and that clay was supposedly more rare in the previous generator. However, it was abundant, since the x=z clay generator bug that previously plagued the game was patched in 1.7.

However, to further address this issue, clay density and frequency can be increased to satisfy those who believe that more clay truly is necessary.[/indent]

The poor state of these aspects of the terrain generator has proven to be both an annoyance and an eyesore to me and the community as well. Beach gen prior to 1.8 paralleled realistic beaches and was more aesthetically pleasing in general. To further elaborate what I mean:

Beaches, prior 1.8

"Beaches" (along lakeside), 1.8 and later

Beaches, real life

As you can see, beaches do not actually generate in 1.8 and later, the "beaches" you see are actually not beaches at all; they are simply the outcroppings of the underwater sand bedding crossing onto the shore. This brings me to the next point: underwater bedding.

Underwater bedding (same pic as before, view the underwater portion), prior 1.8

Underwater bedding, 1.8 and later

Underwater bedding, comparison with 1.8 vs. 1.7, and real life (Borrowed from Dragonid's Terrain Generation Changes Remaining)

As you can see, in 1.8 and later, underwater bedding consists of ugly patches of circular splotches, whether it be in a lake or an ocean. Previously, it was both aesthetically appealing and realistic. Clay would still be fairly abundant if the patch from 1.7 were also incorporated into clay generation. If that is not enough, we can simply have clay generated in the same manner as depicted in the picture below in higher frequencies or larger quantities:

Lastly, gravel beaches should be added back. It was a realistic feature of the old terrain generator and also broke up the monotony with the constant sand beaches. It is not a necessary feature to be re-added, though it would be nice.

Gravel Beaches, 1.7 and before

Gravel Beaches, real life

To reiterate:

1.) Beaches was a widely-liked feature of the previous terrain generator and so, needs to be fixed.

2.) Although a less important issue, underwater bedding, lacks the uniformity and overall realism that it used to have. Currently, lakes and oceans are covered in splotchy patches of dirt, sand, and clay.

With this said and done, I ask that these issues be addressed as soon as it is possible. If you can, please twitter or e-mail Jeb. This is technically not meant to be a petition or anything like the very popular Dear Mojang: The Swamps are Still Ugly topic, just a reminder to show that these issues must be addressed. However, you can show your support by twittering Jeb (+ link to here) or just acknowledging it here.

Tweet Jeb at: https://twitter.com/#!/jeb_

---

Get Satisfaction Topic: http://www.getsatisf..._gravel_beaches

Also check out Dragonid's Terrain Generation Changes Remaining topic for an in-depth look at issues concerning current terrain generation!

Try out a mod that adds beach generation back into the game! http://www.minecraft...0-biome-mod-v1/

---

If you support this, you can show it by signing on to this cause. Type "/signed" in your post!

Signed:

---

Show your support outside this thread by putting these in your signature! Copy the text as it appears in either box and paste it into your signature! Also, if you have signatures of your own to contribute, please feel free to do so!

I want Steelfeathers to make another challenge.