Many people in the past have suggested increasing the height limit of the world. That isn't feasible because it greatly increases the amount of memory used by minecraft, and then many people will no longer be able to play it without getting a new computer.
I have a solution to this problem, and it involves giving each chunk a y value that it is offset vertically by in the minecraft world, so for example, mountains hundred of meters tall could be made, but their bedrock level would be much higher inside of them.
Viewed from the side is the void, each column of 4 is a chunk with playable area.
Actually implementing this in code is easy, it basically involves replacing y with y + current chunk's offset, the hard part is writing a terrain generator that can create a seamless world with this.
the problem is if you are down at bedrock level and you are trying to dig a strip mine (or any mine), you would easily hit a barrier that you would have to go over. if it were 1 or 2 okay fine, but the difference in height needed to actually make a difference in the above world would have to be big enough that it would destroy you're mining efforts.
Rollback Post to RevisionRollBack
Quote from Foxy1990 »
if some higher beings ever got to view this forum before coming to our planet they would turn back and not bother!
It would discourage strip mining, and more people would go spelunking! If you really wanted to strip mine, you could always find a large plains area, where there would be little to no offset between the chunks.
Lol, I just realized I misspelled "Height" in the title. Can a moderator fix this plz?
It would discourage strip mining, and more people would go spelunking! If you really wanted to strip mine, you could always find a large plains area, where there would be little to no offset between the chunks.
Lol, I just realized I misspelled "Height" in the title. Can a moderator fix this plz?
You can fix it yourself. Just hit the edit button at the bottom of the post.
Another issue with it is that what happens if you make a house all the way to the sky, but then realize that the top of your house can't be level. There's also no indication as to what the limit of a certain area would be, so you would have to build giant gravel towers just to find the height limit of each area.
I'd also call you out where you say that increasing the height limit would add too much memory. If notch was a decent programmer (which I hope he is) he wouldn't store air in memory, only the non-air blocks. So as long as nothing is build up there, it shouldn't increase the memory very much.
Even though I'm playing devil's advocate here, it still is a cool concept!
Another issue with it is that what happens if you make a house all the way to the sky, but then realize that the top of your house can't be level. There's also no indication as to what the limit of a certain area would be, so you would have to build giant gravel towers just to find the height limit of each area.
I'd also call you out where you say that increasing the height limit would add too much memory. If notch was a decent programmer (which I hope he is) he wouldn't store air in memory, only the non-air blocks. So as long as nothing is build up there, it shouldn't increase the memory very much.
Even though I'm playing devil's advocate here, it still is a cool concept!
No, blocks still need to be stored in an array, so doubling the height doubles the array size. It is the only way for the computer to quickly find out "what block is at the point x,y,z?"
Also, what you said about the floating house idea is a good point. I had another, slightly more complicated idea, though. Have a height offset at each corner of a chunk, so that the four chunks that share a corner have the same one, and then linearly interpolate the height offset for a column of blocks in the middle of a chunk so that the "ceiling" of the world is sloped. This has the side effect of making the terrain generators job a lot easier.
If you're suggesting that chunks should be stacked on top of each other, then that has already been suggested. The problem is that there needs to be a massive rewrite of the code to make the lighting system work with it. Is it worth it?
I have a solution to this problem, and it involves giving each chunk a y value that it is offset vertically by in the minecraft world, so for example, mountains hundred of meters tall could be made, but their bedrock level would be much higher inside of them.
Viewed from the side
Actually implementing this in code is easy, it basically involves replacing y with y + current chunk's offset, the hard part is writing a terrain generator that can create a seamless world with this.
Please tell me what you think!
Lol, I just realized I misspelled "Height" in the title. Can a moderator fix this plz?
You can fix it yourself. Just hit the edit button at the bottom of the post.
Thanks, I fixed it!
I'd also call you out where you say that increasing the height limit would add too much memory. If notch was a decent programmer (which I hope he is) he wouldn't store air in memory, only the non-air blocks. So as long as nothing is build up there, it shouldn't increase the memory very much.
Even though I'm playing devil's advocate here, it still is a cool concept!
No, blocks still need to be stored in an array, so doubling the height doubles the array size. It is the only way for the computer to quickly find out "what block is at the point x,y,z?"
Also, what you said about the floating house idea is a good point. I had another, slightly more complicated idea, though. Have a height offset at each corner of a chunk, so that the four chunks that share a corner have the same one, and then linearly interpolate the height offset for a column of blocks in the middle of a chunk so that the "ceiling" of the world is sloped. This has the side effect of making the terrain generators job a lot easier.
Maybe.
Mostly moved on. May check back a few times a year.