I don't know if anyone said this, but the math in the first post is all kinds of off. I mean, chunks aren't that big. Only 16 by 16 blocks. While I think some of the ideas for weather and disasters are good, I think they need to be tweaked to better fit into gameplay and code.
GmMkr, your math is a bit off. The game can store a total of INTEGER.MAX_VALUE() + ABS(INTEGER.MIN_VALUE()) chunks. That's around 5 billion total chunks. That's not squared, or anything. You can tackle that in straight lines, or in a giant square. But as soon as you hit the end of your 5 billion-ish chunks, the game will overwrite old ones.
Thus, the maximum straight distance you can achieve is
2147483648 + Absolute value[-2147483647] x 16 meters/blocks.
68719476720 blocks. 68 billion blocks in a straight line.
That said, in a square world, you can only have 262143 blocks on the sides before hitting the chunk limit.
That's not getting into the cubic root.
Still, a large square world, 262 kilometers ahead and 262 to the right, from the leftmost corner is bigger than any video game ever.
And the scary part? If Chunks were saved in a Long offset instead of an Int offset, that number would be even more infinite.
That said, the logistics to make Minecraft a planet are... Game-destroying at best. The entire system would have to be rewritten to come to any system like that. That said, to make it emulate a planet would be easier; Instead of overwriting old chunks when you reach map limit, make the next chunk you walk into the original chunk. That would be difficult, as well, though, because you're not limited to moving in a square, which would be the only way this would surefire work.
I don't think making Minecraft a planet is a necessary application of logistics.
While I agree with your ideas, I find it's kind of pretentious to just shrug them off with "trust me, it'll upset the balance."
The fact of the matter is, all you can really narrow Minecraft down to is its namesake: Mining materials and crafting with those materials. Technology has nothing to do with it. Time has nothing to do with it. Minecraft is a game in which the player is tasked with mining materials in order to build objects and structures as he so desires. I mean, there's no such thing as a pickaxe made of diamonds. Ever.
Guns - Just get a mod, there's not enough community support. No real reason, except few people want them.
Weaker Creepers - Options -> Peaceful
Obsidian Tools - While I'm not sure about Obsidian tools, I do think there needs to be another unique use for Obsidian, aside from portals. (Because I've been to the Nether, once, and it bored me to death)
Diamond drop - Oh, just get Invedit if you want diamonds. I can't even think of a way for Mobs to justify being filled with diamonds.
Nukes - SuperTNT mod (Or Invedit some more TNT into your inventory)
Cars - I know no vehicle capable of jumping up one-meter spaces.
Levels, stats - Well, maybe in the coming Adventure Mode. Sounds fun for that, but not Survival.
Focus your suggestion energies on things the game actually needs, like a new water system, and streamlining its memory consumption. I still think Java was a poor language to write it in.
Oh, and doubling Map Height would only require using the negative side of the data variables that hold Chunks, which would not increase memory consumption, as it requires the entire range of the variable to be loaded, in the first place. (Source(s): Knows Java) The problem is backwards compatibility, as all chunks would have to be updated. That said, the actual code to implement a map height change would require little, and would be almost entirely revision to the map generator. (Which is getting to need it, anyway)
And technology's a moot point, anyway, since we're using crates that shoot arrows when activated by a radioactive red dust, and using that same dust to make 16-bit ALUs.
I'm not entirely sure I like the idea of single-object air vehicles much at all. I mean, maybe the hot air balloon and some glider, but not much else. I'm more into the creative process ending with my fast aircraft.
With a few modifications to your ideas for implementation, I like it. Use a collision system to keep players aboard moving vehicles. While I'm pretty much all for your train idea, (Not entirely sure how you'd plan on making a drill work), I must say I'd rather have some manual build interface for watercraft and aircraft, with more options as to design components.
Using block-collision entities, one could theoretically make a floating fortress (air or sea) that could be moved by a single control system. (This brings interesting ideas for redstone, as the simple binary system it already is)
Given the correct implementation, it wouldn't be out-of-thought to create a massive airship that can land in water, with a bay for smaller watercraft, float through the skies, carry a crane and defensive cannon batteries, a hangar for smaller aircraft, and some pallet system to lower and lift cargo while in the air, thus implementing all 3 bounds within one large vehicle. It would be the most resource-intensive thing ever, but so cool, and so encouraging of creativity and play.
Cazador, where is your absolute proof that this won't happen? I mean, we have a Kinect running on a PC and a Kinect is for a Xbox 360. And some of the best coders and hackers will probably take PC Kinect Minecraft to the Xbox 360. Then make a like pixel version for still working NES's, and hack it to work with the PS Move, and the Wii Remote. I am not saying you are wrong, but there is a probably a high chance of all this.
Compatibility does not work that way!
ANYTHING can be recoded to work on a computer, but the adverse of such is not true.
This is true. Personal Computers can be formatted to run all kinds of software systems. Porting a game from console to PC is as simple as telling the PC to use a different set of logic to process the game. Consoles can only access the logic engine they were manufactured with. That's why you don't get PC games to console, but console games to PC.
What you don't realize, Evillemon, is Minecraft runs on thousands of files, simultaneously. I deleted 5 2MB worlds, manually the other day. It took 15 minutes, not because the files were large, but because Windows had to delete 5213 separate files. Minecraft saves each chunk, individually, and it's my guess that a very substantial amount of the reason it's so sluggish is because it has to index each file and search for each, individual chunk, and place and render it, actively. That isn't simple at all. (And apparently, is Notch's Mojang's top priority right now) Again, on fairly wimpy settings, Minecraft uses nearly all of the memory available to a current console, and leaves none for its System tasks. So, to make room for the necessary tasks, it would need to be further streamlined and its functionality reduced.
I have twice the memory of the Xbox 360 and PS3 on my machine right now. I'm also running Vista on that mere, one gigabyte. My system processes take up a little under half that. Adding Minecraft to the task tray slows me to hell, unless I end each non-necessary process, myself. In doing so, I've accidentally killed SVCHost many times, and bluescreened myself. (Why does it let you kill THAT process, but not certain others, even as Superuser?) The Xbox and PS3 have slimmed-down firmware, comparatively, but its system processes still take up a lot of memory.
In summation, even if the consoles could process the code for Minecraft, they couldn't play it, because they don't have the physical capacity.
0
0
Thus, the maximum straight distance you can achieve is
2147483648 + Absolute value[-2147483647] x 16 meters/blocks.
68719476720 blocks. 68 billion blocks in a straight line.
That said, in a square world, you can only have 262143 blocks on the sides before hitting the chunk limit.
That's not getting into the cubic root.
Still, a large square world, 262 kilometers ahead and 262 to the right, from the leftmost corner is bigger than any video game ever.
And the scary part? If Chunks were saved in a Long offset instead of an Int offset, that number would be even more infinite.
That said, the logistics to make Minecraft a planet are... Game-destroying at best. The entire system would have to be rewritten to come to any system like that. That said, to make it emulate a planet would be easier; Instead of overwriting old chunks when you reach map limit, make the next chunk you walk into the original chunk. That would be difficult, as well, though, because you're not limited to moving in a square, which would be the only way this would surefire work.
I don't think making Minecraft a planet is a necessary application of logistics.
0
The fact of the matter is, all you can really narrow Minecraft down to is its namesake: Mining materials and crafting with those materials. Technology has nothing to do with it. Time has nothing to do with it. Minecraft is a game in which the player is tasked with mining materials in order to build objects and structures as he so desires. I mean, there's no such thing as a pickaxe made of diamonds. Ever.
Guns - Just get a mod, there's not enough community support. No real reason, except few people want them.
Weaker Creepers - Options -> Peaceful
Obsidian Tools - While I'm not sure about Obsidian tools, I do think there needs to be another unique use for Obsidian, aside from portals. (Because I've been to the Nether, once, and it bored me to death)
Diamond drop - Oh, just get Invedit if you want diamonds. I can't even think of a way for Mobs to justify being filled with diamonds.
Nukes - SuperTNT mod (Or Invedit some more TNT into your inventory)
Cars - I know no vehicle capable of jumping up one-meter spaces.
Levels, stats - Well, maybe in the coming Adventure Mode. Sounds fun for that, but not Survival.
Focus your suggestion energies on things the game actually needs, like a new water system, and streamlining its memory consumption. I still think Java was a poor language to write it in.
Oh, and doubling Map Height would only require using the negative side of the data variables that hold Chunks, which would not increase memory consumption, as it requires the entire range of the variable to be loaded, in the first place. (Source(s): Knows Java) The problem is backwards compatibility, as all chunks would have to be updated. That said, the actual code to implement a map height change would require little, and would be almost entirely revision to the map generator. (Which is getting to need it, anyway)
0
I think the better question is will it SSSSSSSSSSSSSSSSSS before he hits it?
0
For that matter, please, punctuate your statement, which I can only assume is derogatory of the concept, so I can understand its full meaning.
0
0
Guys, Aigaion.
0
0
0
0
0
0
Anyway, check my post on that thread, as it well-relates to this one.
0
Using block-collision entities, one could theoretically make a floating fortress (air or sea) that could be moved by a single control system. (This brings interesting ideas for redstone, as the simple binary system it already is)
Given the correct implementation, it wouldn't be out-of-thought to create a massive airship that can land in water, with a bay for smaller watercraft, float through the skies, carry a crane and defensive cannon batteries, a hangar for smaller aircraft, and some pallet system to lower and lift cargo while in the air, thus implementing all 3 bounds within one large vehicle. It would be the most resource-intensive thing ever, but so cool, and so encouraging of creativity and play.
0
This is true. Personal Computers can be formatted to run all kinds of software systems. Porting a game from console to PC is as simple as telling the PC to use a different set of logic to process the game. Consoles can only access the logic engine they were manufactured with. That's why you don't get PC games to console, but console games to PC.
What you don't realize, Evillemon, is Minecraft runs on thousands of files, simultaneously. I deleted 5 2MB worlds, manually the other day. It took 15 minutes, not because the files were large, but because Windows had to delete 5213 separate files. Minecraft saves each chunk, individually, and it's my guess that a very substantial amount of the reason it's so sluggish is because it has to index each file and search for each, individual chunk, and place and render it, actively. That isn't simple at all. (And apparently, is
Notch'sMojang's top priority right now) Again, on fairly wimpy settings, Minecraft uses nearly all of the memory available to a current console, and leaves none for its System tasks. So, to make room for the necessary tasks, it would need to be further streamlined and its functionality reduced.I have twice the memory of the Xbox 360 and PS3 on my machine right now. I'm also running Vista on that mere, one gigabyte. My system processes take up a little under half that. Adding Minecraft to the task tray slows me to hell, unless I end each non-necessary process, myself. In doing so, I've accidentally killed SVCHost many times, and bluescreened myself. (Why does it let you kill THAT process, but not certain others, even as Superuser?) The Xbox and PS3 have slimmed-down firmware, comparatively, but its system processes still take up a lot of memory.
In summation, even if the consoles could process the code for Minecraft, they couldn't play it, because they don't have the physical capacity.