Quote from Evil_Lee03»

i'm unshure i just thought it would be kinda cool,and plus they can already use armor and weapons so they probrobly have still got some brain

Oh, no, i was just asking. I think the idea has merit.

Quote from NinjaKid51»

uh

i am a rapper

i like smoking and girls

i am a thug that does drugs

swag

snapbacks

i wear my pants way down below my butt because i think it's cool, but everyone else hates it

except for my homies

which is why we are homies

swag

i wear gold chains around my neck and every inch of my skin is covered in ink

swag

swag

swag

snapbacks....

-every rap song ever

no, I'm not racist. I just hate today's definition of rap music.

What do you mean "today's rap"? If you think all rap is like that you're either not taking the initiative to find music you like, instead opting to mindlessly hate on not only an entire genre but an entire era of music, or you're delusional. I also like how you change from "every rap song ever" being the same, but then do a 180 and say 'uh no i only meant "today's rap"'.

Quote from LegendaryEnder»

The graphics. They think Minecraft is an '80s game. They want realistic graphics, but they only end up with lag and even more ugly graphics. Yep, super high resolutions can sometimes become ugly.

First of all, I've heard this reasoning tons of time and it's unbelievable how wrong it is. People don't think Minecraft is an "80's game", they think it has bad graphics, sure, but it isn't synonymous. And it does have bad graphics, in a way: Minecraft is incredibly resource intensive for something that isn't particularly good looking. Obviously it's because of the size and scope of the game world, but people who are just trying it out won't know that (unless they did background research). Plus, the amount of garbage videos that clog up Youtube would have definitely turned me off it it was my only exposure to the game.

As for the OP: I personally think the stereotyping is warranted, as the fanbase skews young. This is inevitable, because the more popular a game is the younger the fanbase will be. Why do you think CoD gets such a bad rap?

Quote from ajniN_rednE

Every server is down! I tried to restart my router and it isn't fixed! Weird isn't it:blink:

I hope it is back up soon:unsure:

No way man Minecraft is now down permanently have a good life gg

Quote from gvt123

Vague/Wishlist.

Nothing to say, please post your next suggestion with more information.

//vote4close

It's called the report button.

The shears are lacking in uses. Aside from getting wool and decorative plant blocks, they do nothing, and have no combat uses, unlike every other tool besides the compass and name tag. Therefore, I suggest we make the shears part joke weapon.

To attack a mob with the shears, you have to charge it up, like a bow. However, there is still only a 50/50 chance that it will work, but if it does, they will die instantly. Any mob killed will drop one, and only one, of every drop, including the head. For balance reasons, this instantly destroys the shears, and they must be at full health to use. If it is not at full health, it won't work. It hurts the drop rate for most drops, so they aren't perfect for every situation. They CANNOT be used on the Enderdragon, for obvious reasons, nor on Wither Skeletons. Using it on the Wither has a unique effect, which I'll describe below.

When used on the Wither, it will shatter, and will cut off one of the side heads. This will slightly gimp it's shooting, making fighting it easier. If you have another pair of shears, you can clip the other head, but the middle one is un-shearable.

As a side note, this is useful in creative for clearing out a group of mobs in a build/map, if switching to peaceful is not an option (Your map/build requires a zombie to work, for example.).

Also, I found a thread that was full of hostile people who obviously didn't understand it. Then again, the OP was too.

We should probably try to spread this thread, seeing as it has a most complete image of how this would work. A good reason enough to keep it around for a little while longer.

Quote from Khanh173

Didn't I mention slime blocks and flying machines? Who need improved boat when we can fly instead? If you want boats that badly, you can just make a flying machine on the same layer of the sea surface, and cover its mechanics with boats's parts and decoration, and you have a boat. And the improved boat is not convincing: the game have no wind mechanic, and in case of a bigger boat, need rowing, which can consume much more energy and affect hunger because its human-powered, unless Steve has telekinesis LOL.

You did mention slime blocks and flying machines. Archimedes ships CAN FLY if you give them balloons. Did you check the mod page or did you just make an assumption?

As for the lack of realistic mechanics: Who cares? We don't have any sort of rowing for tiny boats, and yes, you need to propel it in SOME way, this isn't just for bigger boats. Wind mechanics have never applied for those boats either, I don't know why you expect these too.

This is a simple concept: You can save presets you've made. You have the option to name it, and put a screenshot as the preview. If you don't, it'll just be the default picture used when a resource pack has no picture set.

I'm also bad at GUI design, so if anyone feels up to it, I would appreciate concept art.

---

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.

Quote from PicklePackle

"Whoa, free game that I want!"

TAKEN

"Dammit."

^ LIKE DIS IF U CRY EVERTIM

/null
Yes. You might want to go read the Opening Post a little more thoroughly, or I guess you can do what most of the rest of us did and pick it up as you go along. The limit is currently 40.

I present a new command, the /pos command! Here is the basic command:

/pos <Position Number> [Coordinates]

Where you can set a position at special coordinates which can be moved and used instead of coordinates, such as like in worldedit where you set two positions and fill that area with a certain block, which you could do with this command:

/fill pos1 pos2 diamond_block

Just a thought.

Humans (later renamed Monsters) are mobs which take the form of clones of the default skin. They used to be created by pressing G while playing in Classic mode, but this function was later removed. If the player has a custom skin, any humans created will still use default skin and will not assume the look of the player. Humans could not create or delete blocks, they would just move around the map aimlessly, walking in slightly imperfect circles and jumping occasionally. While walking, they would flail their arms around and move their head randomly. Humans were affected by solid blocks, but strangely not liquids, walking through them as if they were air.

Humans used to be spawned by using a map editor or mod. When spawned, however, they pursue and kill the player. Strangely, they do not use the punching animation that a normal player would use, they only run into the player like a Zombie would.

Since Beta 1.8, Humans can no longer be spawned in game even with a map editor or mob spawner, the mob spawner will appear blank, no model will be inside, and no mob appears.


Monsters ( but I will just call them NPCs from now on ) are used only in map making , and are summoned using /summon NpcHuman . They don't have a spawn egg , so they can't be summoned by none-OPs just like Giants .

NPCs are very specially , with the ability of having costume behavior to different NPCs and even costume skin files .
List of NBTdata tags :
Team : insert an integer here , NPCs with different teams will fight each other and will never turn hostile to NPCs of the same team . 0 means that they will be passive to all NPCs , and all NPCs will be passive towards them . When summoned without setting the team it will default to 0 .
/summon NpcHuman ~ ~ ~ {Team:1}
This will create - for example in a costume RPG map - a " Steve " NPC that attacks anyone from Team 2 and so on .

Behavior : Passive / Hostile / Natural / Follow . the NPCs behavior towards players only . this wont affect their behavior towards other NPCs or mobs , Follow makes them share the same AI as tamed wolves ( without sitting ) but they wont leap at the target like wolves do . When not set , it defaults at Natural .
/summon ~ ~ ~ NpcHuman {Team:0,Behavior:Follow}

Skin : Can only be used if a player is using a resource pack . for a resource pack to be NPC compatible , there will be a folder in the entities folder ( where there are skins for horses & zombie and all other entities ) that contains .png skin files , skins must use the Piped model . When not set , it will default to Steve's skin .

/summon ~ ~ ~ NpcHuman {Skin:["name_of_resource_pack","Skin_name"]}
Or even : ( Thanks UndeadGaming606 )
/summon ~ ~ ~ NpcHuman {Skin:[SkinOwner:"Player_name"]}

/summon ~ ~ ~ NpcHuman {Skin:["Adventure_RPG_pack","Dwarf_skin1"]}

This will summon a Dwarf using the skin file named Dwarf_skin1.png in the Adventure R.. whatever resource pack . he is also passive to all NPCs since he doesn't have a team and he is Natural to the player since we didn't set any behavior .

NOTE : Health , speed , knockback resistance , follow range , and all other attributes work on NPCs as well as other mobs . If given bows , however they will shoot it unlike zombies that will just smack you in the face with the bow .

The NPC control item is obtainable ONLY in commands , it allows editing of NPCs after spawning them . you just right click them with the item .
To get it use /give @p npc_controller
NOTE : I'm working on the screenshots .
- Imagine Vanilla mercenaries made with the Follow behavior and a costume skin made with NPCs ?
- Just spam a bunch of NPCs in different teams and watch them die one by one .
- Make an NPC human a boss fight in an adventure map about Herobrine ( not that I believe in his existence )
- Make a defense minigame where your base is been invaded with NPCs and you and what's alive of your army must survive epic battles ( instead of just a 1 vs many Zombies battle )
- For fun
- Did I mention using them for fun ?
- Wow so many uses . And still , minecraft is a sandbox and creative game . The implementing of one mob will open roads to infinite amazing possibilities for command blockers and map makers and even minigame makers ! ( but I think minigame maker and map maker is the same thing ... well ... )

Quote from Roflyx

Okay, this requires extreme mesaures.

*casts a little fireball and throws it to grass*

I'll better make sure it doesn't go too far.

-thousands and thousands of grasslings who were camouflaged as soil run away in shock and terror as their only home is killed and devoured by roflyx's cruel power-

-We set out alone to find new plains, exposed to the danger of the forests-

lik if u cri everytim

Are you using CTRL + A to select the code beforehand? If CTRL + C/V isn't working, that's the only thing I can think of to help.

Right now, Wither Skeletons only spawn in Nether Fortresses. People have been asking for more features to be added to the Nether, and as of now all the features in the Nether are in Nether Fortresses except for glowstone, Zombie Pigmen, and Ghasts. Nether Fortresses have Nether Bricks, Blazes (necessary for potions), Nether Warts, and right now Wither Skeletons as well. Why should half of all the features of the Nether be all in Nether Fortresses? I don't know about you, but whenever I go to the Nether it is almost always to find a Nether Fortress. In addition to that, Wither Skeletons right now only drop a Wither Skeleton Skull 2.5% of the time. That's a 1 in 40 chance of you getting a Wither Skeleton Skull. For those of you who haven't done the math, that means you need to kill an average of 120 Wither Skeletons to summon the Wither. I spent a half-hour in a Nether Stronghold and found 3 Wither Skeletons. Do the math - I don't know about you, but I don't have enough time to hunt down 120 or more Wither Skeletons just to summon a boss.



All this points to a very simple solution: Move Wither Skeletons out of Nether Fortresses. This would increase how common they are, and give players a reason to explore more of the Nether beyond just Nether Fortresses. It's a very simple idea, but a very effective solution. In addition, this is a way to get a hostile mob into the nether. Right now the most common mob is neutral, and Ghasts are fairly rare. Wither Skeletons would give a reason to make the player cautious. All a player really has to watch out for wandering around the nether now is lava and the occasional Ghast. They would spawn about as commonly as Endermen do now in the Overworld. NOTE: This would not stop Wither Skeletons from spawning inside Nether Fortresses, as the name probably implies (sorry). It would just allow them to spawn everywhere, including both inside and outside Nether Fortresses.


Rinnsal has added this as an optional feature to his Nether mod! If you want to check out how this idea would work in the Nether while having some really cool new Nether items as well, check out his mod here: NetherStuffs 0.19 by Rinnsal The download link is at that page, along with a mod review video and a description of all the awesome stuff in the mod. I highly recommend it! Additionally, Builderb0y has created a mod that allows Wither Skeletons to spawn everywhere in the Nether without all that extra stuff. Here's the download link: http://www.mediafire...a7ttstxokee2puv Just put it into the minecraft.jar and you're done.




[size=small]NOTE: Because of the recent influx of posters who have given two sentence posts and haven't even bothered to look at the FAQ, any post that clearly could have been addressed with a trip here will be replied to with a simple "See FAQ #X". I highly encourage you to at least peruse the questions before posting ignorant criticism.[/size]


You'll be added if you , or I happen to see a positive comment. For why, see the FAQ. [size=medium]


PLEASE LEAVE CONSTRUCTIVE CRITICISM, SUPPORT, AND IDEAS!



Robe's Art has made an awesome banner for this idea. If you like this idea and want to help support it, just copy the code below into your signature, then highlight it and click "Remove Formatting" (the eraser in the upper left)!

[url="http://www.minecraftforum.net/topic/1493398-move-wither-skeletons-out-of-fortresses"][img]http://i.imgur.com/JWt7JOo.gif[/img][/url]

Here are some old banners you can also use:
Having trouble with a banner? See the last question in the FAQ for help and troubleshooting. [represent]

Carpeted Stairs
Basically, we already have carpets and they work quite well. They both decorate blocks and even slabs if in the right conditions. The thing is, if you want to make stairs leading up to some fancy place or something other than that, carpets can provide some more aesthetics. Only thing is, carpets don't work with stairs. That's the idea I want to propose to you.





They would basically look like this, and have the same effects of normal carpets(like lifting you off the ground a bit). If you're wondering how I made this, I actually used entities in minecarts to make the effect of it being there.

Only thing is, it doesn't raise you up the ground a bit and is quite complicated for a normal Minecraft player to even do, not to mention it can't be done in survival. Also, if used too much, the entities(minecarts) would cause a lot of lag.



Their hit-box would be the red glass, so it takes up that space.

The Problem
From the knowledge of Mojang and others, the way the game is currently coded can't be made to add this, or will take some recodes in certain areas. So I have some suggestions made by others, which gives other ways on how to add a carpeted stairs, only it doesn't actually have a higher hit box on top of the stairs. So if it really does take a long time to recode to add something like this, these will do as well.

Morph In
The suggestion here made by Deonyi, said that if you right click a stairs with a carpet, the texture of the carpet would switch to one with a thin line of carpet on top of it. If broken, it would give back the stairs and the carpet.

Classic Crafting
Suggested by Deykhal, it basically means that they will add blocks with carpets on them as a crafting recipe. However, it isn't a new model, and is just the textures change like the Deonyi's one.

That's all really, it's quite simple. Do tell me how you feel about this suggestion, and ways I can improve it if needed.