Is it so hard to just download a mod to increase the height limit?
The height limit will never change in vanilla Minecraft. Not only is it unnecessary for 95% of the games playerbase, but it would require a complete overhaul of the game that would more than likely take months to achieve.
Is it so hard to just download a mod to increase the height limit?
Do you realize the annoyances and complications that appear when relying on mods for that? You'll have to wait for updates with every new MC release, and your worlds won't work for others. Additionally, you'll have to be wary of mod incompatibilities.
The height limit will never change in vanilla Minecraft. Not only is it unnecessary for 95% of the games playerbase, but it would require a complete overhaul of the game that would more than likely take months to achieve.
You don't know that, and it certainly would not take months to include.
Is it so hard to just download a mod to increase the height limit?
The height limit will never change in vanilla Minecraft. Not only is it unnecessary for 95% of the games playerbase, but it would require a complete overhaul of the game that would more than likely take months to achieve.
That kind of attitude just makes me sick.
Cubic Chunks Mod is a prime example of the fact it can be done. Jeb, who knows how the game is programmed and such since he works with it. Could one day optimize it to run just fine with a 256 world.
Unnecessary? Well lets stop adding the jungle biome, and other cool things. It's all unnecessary
OK, take your minecraft saves and multiply the size by 2. Now take the time it takes to generate the world and double it. Then take the lag you get in the game normally then double it. Not to mention that 126 is the most stable height for MOST COMPUTERS. Jens and Jon wouldn't risk doubling the height limit if it would lag a large portion of the community.
TL;DR Just because its doable doesn't mean it should be done. The mod exists for those who's computers can handle it. If you are saying 1080 doesn't lag you then that doesn't mean that it won't affect the speed for other computers, it just means that you can run that big of a world.
Not that this would affect me, 8 Gb of ram and a top of the line GPU.
Cubic chunks pushes it to like 65,000.
I am SURE Jeb can get 256 with no problem. Just takes some optimization, which Minecraft needs anyway.
Rollback Post to RevisionRollBack
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
Why:They make height limit a single integer for modders to easy edit.
And im about to rant about this Java takes more memory thing:
i code in java myself,and i have to say,the Minecraft code is messy.
Java is not the problem when it comes to memory,it depends in 2 factors:
1.the computer
2.How the coder codes his game
Notch started off coding a little sloppy,meaning that the game would run on low
FPS.Now,they are cleaning up the code,meaning that you can run higher FPS.Notch started
learning Java from his dad and at home,always working with tech.From what im coding(making my own game
to tell you),Java can actually not take as much memory IF your code is all in order.people who say Minecraft takes
memory probably have a bad computer(i have a Intel family chipset,not really a computer for gaming),or just dont
know how to configure.And to add to that,Java takes less methods than other coding languages to do one thing.
If people actually knew there coding languages they would know.To add to that,Java is easy to start of while
C/C++ will need some time to learn.Want to know why the game is limited to 64 blocks?No,not because of java,as
Notch could add chunks that load when you go lower.64 is a coding number,this is how much "int" can hold,64(from what i know).It can hold -64 to 64,and adding this to a array makes the whole world "128".Now,since he has edited the code,
now anyone can change height limit.I know that if the game was written in C/C++,it would run a little smoother.but,of course,it would take way more methods to code the same thing.C/C++ uses many different things than Java,so people say its "better",when they can do the same thing.So,in the end,Notch will never convert the game,so shut up about it and do it yourself and see that there isn't much difference.
Ok...None of that tells me a good reason that we cannot have 256 height.
A mod has done much more without blowing up the game, and if you say the game is messy. Then cleaning it up more and more will ease the process.
Rollback Post to RevisionRollBack
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
Why:They make height limit a single integer for modders to easy edit.
And im about to rant about this Java takes more memory thing:
i code in java myself,and i have to say,the Minecraft code is messy.
Java is not the problem when it comes to memory,it depends in 2 factors:
1.the computer
2.How the coder codes his game
Notch started off coding a little sloppy,meaning that the game would run on low
FPS.Now,they are cleaning up the code,meaning that you can run higher FPS.Notch started
learning Java from his dad and at home,always working with tech.From what im coding(making my own game
to tell you),Java can actually not take as much memory IF your code is all in order.people who say Minecraft takes
memory probably have a bad computer(i have a Intel family chipset,not really a computer for gaming),or just dont
know how to configure.And to add to that,Java takes less methods than other coding languages to do one thing.
If people actually knew there coding languages they would know.To add to that,Java is easy to start of while
C/C++ will need some time to learn.Want to know why the game is limited to 64 blocks?No,not because of java,as
Notch could add chunks that load when you go lower.64 is a coding number,this is how much "int" can hold,64(from what i know).It can hold -64 to 64,and adding this to a array makes the whole world "128".Now,since he has edited the code,
now anyone can change height limit.I know that if the game was written in C/C++,it would run a little smoother.but,of course,it would take way more methods to code the same thing.C/C++ uses many different things than Java,so people say its "better",when they can do the same thing.So,in the end,Notch will never convert the game,so shut up about it and do it yourself and see that there isn't much difference.
Sorry, but I can't help but chuckle reading this.
I have no doubts that you code in java, but I do doubt you don't get tons of errors.
There is a a SPACE after a comma, and a period. Why do people post THOUSANDS OF TIMES
AND STILL NOT UNDERSTAND THIS BASIC CONCEPTS OF GRAMMAR?
In school,you learn that there are no spaces after a period,not even a space after a comma.
Who taught you that, exactly?
I was taught that you need one space after most punctuation, and that up to two spaces are acceptable at the end of sentences (except in MLA format.) Spaces are meant to make sentences easier to read.
Rollback Post to RevisionRollBack
Mostly moved on. May check back a few times a year.
Meh,i may be wrong with the comma thing but the period thing is what it is.
And yes we do need 256,maybe a few options for changes?
Like:
Height Limit:126,256,370
Or something.
In world Options.
Short - 128
Normal - 256
Tall - 384
Rollback Post to RevisionRollBack
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
The first thing that needs to be done is for the chunks to be made cubic. It's the only reasonable way to get 1,024+ high worlds.
Then we could have options for finite worlds (capped at bedrock and a certain height) or infinite worlds. Options should be given for how much of the world height the terrain generator actually uses.
Infinite worlds would have limitless sky for the player to build in. There are different ways to deal with what used to be bedrock and below. Caves and resources could continue to generate downwards like normal, encouraging endless exploration downwards until the player gets sick of it. Alternatively, the space could be filled endlessly with one type of block, such as lava or stone, discouraging downwards exploration in favor of outwards exploration but still allowing the player to clear the way for building.
Rollback Post to RevisionRollBack
Mostly moved on. May check back a few times a year.
I have a question, they say it requires more of youre PC to have a heigher world, but what is the space is just empty?.
In creative mode you can go up into infinite height, my fps doesnt drop if im at 128 or at 500 height.
Atleast add height in survival, you dont have to put anything there, atleast being able to build heigher than 128 would be awesome, and it doesnt take any performance hit.
I actully think my FPS increased lol
That's because there aren't any chucks loading, since you're so far above the height limit.
I have a question, they say it requires more of youre PC to have a heigher world, but what is the space is just empty?
If it is possible to build in a location there is an "air" placeholder block that still takes up some memory.
Unloaded chunks don't take up processing power, but they do take up hard drive space. Chunks that have never been generated take up neither, so your world file is only as big as you actually explore (even in an infinite world.)
The reason your performance is increasing is probably because blocks and monsters are no longer visibly being rendered (based on fog distance.) Their locations are probably still in memory with the current system, because it doesn't unload chunks based on height.
I have a question, they say it requires more of youre PC to have a heigher world, but what is the space is just empty?.
In creative mode you can go up into infinite height, my fps doesnt drop if im at 128 or at 500 height.
Atleast add height in survival, you dont have to put anything there, atleast being able to build heigher than 128 would be awesome, and it doesnt take any performance hit.
I actully think my FPS increased lol
A difference in ceiling height, but not matter (block count), would only make the slightest modicum of difference to your framerate. The data is loaded onto the RAM, but the rendering is essentially the same. Increasing world height isn't as detrimental to the framerate as some people make it out to be- though it does depend on how the world was generated. You will notice an impact if the land is generated a the 50% mark like it is now. If you generate a 256 high map then you'll have (roughly) 128 blocks below you.
As for your FPS increasing, it's because the blocks below weren't being rendered.
I did tried the height mod back in pre 1.9. I see almost no fps difference in 128 and 256 height. However it's little laggy on 512x and very laggy on 1024x. Flat lands on 1024x produces no lag for me. 256 height isn't really that hard to run except for old laptops.
Because classic map is not infinite.
I don't know how it would work "fps" wise on raising the height on Normal Infinite maps.
The height limit will never change in vanilla Minecraft. Not only is it unnecessary for 95% of the games playerbase, but it would require a complete overhaul of the game that would more than likely take months to achieve.
Do you realize the annoyances and complications that appear when relying on mods for that? You'll have to wait for updates with every new MC release, and your worlds won't work for others. Additionally, you'll have to be wary of mod incompatibilities.
You don't know that, and it certainly would not take months to include.
That kind of attitude just makes me sick.
Cubic Chunks Mod is a prime example of the fact it can be done. Jeb, who knows how the game is programmed and such since he works with it. Could one day optimize it to run just fine with a 256 world.
Unnecessary? Well lets stop adding the jungle biome, and other cool things. It's all unnecessary
Cubic chunks pushes it to like 65,000.
I am SURE Jeb can get 256 with no problem. Just takes some optimization, which Minecraft needs anyway.
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
That's if he just typed in 256. Cubic chunks mod shows that is is possible without breaking the RAM/Power bank for most users.
Vanilla Minecraft should be
256 Normal World
With the choice of a Short World, 128.
I cannot express to you how much better the game would feel without this constant "Small feeling".
Sure we can run around for thousands of blocks...But I can only go 60 deep, or 60 tall? Please.
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
Ok...None of that tells me a good reason that we cannot have 256 height.
A mod has done much more without blowing up the game, and if you say the game is messy. Then cleaning it up more and more will ease the process.
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
Sorry, but I can't help but chuckle reading this.
I have no doubts that you code in java, but I do doubt you don't get tons of errors.
There is a a SPACE after a comma, and a period. Why do people post THOUSANDS OF TIMES
AND STILL NOT UNDERSTAND THIS BASIC CONCEPTS OF GRAMMAR?
Anyway.
We need to push for Vanilla 256.
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
I was taught that you need one space after most punctuation, and that up to two spaces are acceptable at the end of sentences (except in MLA format.) Spaces are meant to make sentences easier to read.
Mostly moved on. May check back a few times a year.
In world Options.
"The oceans of minecraft are vast and nearly endless... and we just have a floating little box to traverse across them..." - doctorseaweed2
64
128
256
512
That would be pretty bitchin' in my opinion.
Then people with older and/or weaker computers shouldn't play on that setting. Simple.
Yes, that's why I offered the number as a suggestion: so one could have a small world.
Then we could have options for finite worlds (capped at bedrock and a certain height) or infinite worlds. Options should be given for how much of the world height the terrain generator actually uses.
Infinite worlds would have limitless sky for the player to build in. There are different ways to deal with what used to be bedrock and below. Caves and resources could continue to generate downwards like normal, encouraging endless exploration downwards until the player gets sick of it. Alternatively, the space could be filled endlessly with one type of block, such as lava or stone, discouraging downwards exploration in favor of outwards exploration but still allowing the player to clear the way for building.
Mostly moved on. May check back a few times a year.
That's because there aren't any chucks loading, since you're so far above the height limit.
Unloaded chunks don't take up processing power, but they do take up hard drive space. Chunks that have never been generated take up neither, so your world file is only as big as you actually explore (even in an infinite world.)
The reason your performance is increasing is probably because blocks and monsters are no longer visibly being rendered (based on fog distance.) Their locations are probably still in memory with the current system, because it doesn't unload chunks based on height.
It might be more correct to say they should be changed from horizontally tiled 16x16xMapHeight chunks to 16x16x16 chunks in all directions.
Mostly moved on. May check back a few times a year.
A difference in ceiling height, but not matter (block count), would only make the slightest modicum of difference to your framerate. The data is loaded onto the RAM, but the rendering is essentially the same. Increasing world height isn't as detrimental to the framerate as some people make it out to be- though it does depend on how the world was generated. You will notice an impact if the land is generated a the 50% mark like it is now. If you generate a 256 high map then you'll have (roughly) 128 blocks below you.
As for your FPS increasing, it's because the blocks below weren't being rendered.