i own minecraft for a few month, had my house and everything when Notch added
*new tree , *dyes
everything was going fine until i wanted to get blue.. i searched and couldnt find lapis ore.
my suggestion is this:
with every new update find a way to add those new features to old areas.
for example:
-every 1/200(or other rate) cobblestone in the right altitude could turn into lapis , ONLY in old areas.
-every 1\4(i dont know the rate of the new white tree) normal tree could be destroyed and replaced with the other tree type.
this is my idea, i think its very important to support old world owners.
the idea that one needs to wander off to new areas every new update AFTER he built a rail and a big mine is EXTREMELY ridiculous in my opinion.
Edit:
i wanted to add that the point of this forum is to bring up ideas, and yours is to say why you like it or not, not
to say that it would be impossible because of _____ blah blah blah.. leave possible or not possible to Notch's team.
the idea that one needs to wander off to new areas every new update AFTER he built a rail and a big mine is EXTREMELY ridiculous in my opinion.
This wouldn't work anyway. Oh look, that 100,000 cobble castle you just built is now a lapis mine.
i said, in the altitude. you wouldnt build a castle below ground level.
Even if Notch regen'd the world somehow and kept all human placed blocks, you'd still end up with errors everywhere.
why would i get errors? are you at the level that you understand minecraft code to judge that? besides, its already been done by someone who turned cobblestone into lapis.
technically, what you are asking is impossible. Not that it isn't a good idea, but it is not actually possible.
again, you are probably not such a professional to say that.
about the save files:
hell yeah. i have the right to keep my save files. if Notch tells me that this idea is not practical ONLY then i will give up.
hmmm.. yeah it's pretty impossible to add new things like that. what do you want ? you want some smooth stones to transform into lapis lazuli ? how would minecraft know that this stone is not part of your buildings ? how would minecraft know where to put lapis and that it doesn't interfere with other ores ?
If you want lapis lazuli, explore. it's that simple. this "new-thing-added-go-explore-to-find-it" is actually part of the game, it adds charm.
also, commieduck is right, "don't get attached to your saves", it's beta and it's possible that one day, notch will add something that destroy all your maps :]
hmmm.. yeah it's pretty impossible to add new things like that.
oh. so your'e the minecraft coding expert we've invited? good to know.
what do you want ? you want some smooth stones to transform into lapis lazuli ? how would minecraft know that this stone is not part of your buildings ? how would minecraft know where to put lapis and that it doesn't interfere with other ores ?
read my last messege.
If you want lapis lazuli, explore. it's that simple. this "new-thing-added-go-explore-to-find-it" is actually part of the game, it adds charm.
i keep the right to explore from within my mine and not go 20 minutes away distance to mine ores.
also, commieduck is right, "don't get attached to your saves", it's beta and it's possible that one day, notch will add something that destroy all your maps :]
im not even gonna reply to that. its one's choice whether to get attached to the save or not.
hmmm.. yeah it's pretty impossible to add new things like that.
oh. so your'e the minecraft coding expert we've invited? good to know.
what do you want ? you want some smooth stones to transform into lapis lazuli ? how would minecraft know that this stone is not part of your buildings ? how would minecraft know where to put lapis and that it doesn't interfere with other ores ?
read my last messege.
If you want lapis lazuli, explore. it's that simple. this "new-thing-added-go-explore-to-find-it" is actually part of the game, it adds charm.
i keep the right to explore from within my mine and not go 20 minutes away distance to mine ores.
also, commieduck is right, "don't get attached to your saves", it's beta and it's possible that one day, notch will add something that destroy all your maps :]
im not even gonna reply to that. its one's choice whether to get attached to the save or not.
its kinda late here and i have school tomorrow. ill reply anyone new in 15 hours.
the idea that one needs to wander off to new areas every new update AFTER he built a rail and a big mine is EXTREMELY ridiculous in my opinion.
This wouldn't work anyway. Oh look, that 100,000 cobble castle you just built is now a lapis mine.
i said, in the altitude. you wouldnt build a castle below ground level.
Even if Notch regen'd the world somehow and kept all human placed blocks, you'd still end up with errors everywhere.
why would i get errors? are you at the level that you understand minecraft code to judge that? besides, its already been done by someone who turned cobblestone into lapis.
technically, what you are asking is impossible. Not that it isn't a good idea, but it is not actually possible.
again, you are probably not such a professional to say that.
about the save files:
hell yeah. i have the right to keep my save files. if Notch tells me that this idea is not practical ONLY then i will give up.
OK, let me take a crack at this:
1) Plenty of people build castles underground. It's not as isolated as you think.
2) Let's assume that Notch did update pre-existing areas, you would still have to have to add more information to EACH block checking whether it has been player-placed or not. This would bloat the file size and cause generally undesirable effects in SMP and SSP.
Here's what I mean.
------------------------------------------
If you add a boolean tag for bIsPlayerPlaced; It would add 1 bit of data per block.
The minimum actual data size for this game is a 32-bit structure but players whom use 64 bit processors would be screwed as each bit actually takes up 64 bits. This would add 32/64 extra bits per block (instead of 1 bit) which increases file size (unless he did bit pushing/pulling which would be processor heavy but save file size).
There is a maximum of 64x64x128 of data per chunk which means between 16 and 32MB heavier per chunk. If you went processor heavy by bit pushing/popping, Notch would have to increase the user requirements for the game, which would in turn cut into his sales but you would have 512 KB~1MB heavier files per chunk (which is really not good).
--------------------------------------------
Finally, you can keep your save files, no one said you had to delete them. There would just be a chance they'd be useless in future patches. Notch graced us with the ability to update our worlds from alpha to beta because the changes to the engine weren't completely dramatic. When he starts rolling out dramatic changes to the game engine/structure/design; don't expect to see such quick bandaid fixes. You may have to deal with losing your save game information for good. Don't feel bad though, I still have Sega CD games even though I no longer have a Sega CD.
Unless Java heavily optimized the code before interpretation, it would be unfeasible to do so, I will say no here.
OK, let me take a crack at this:
1) Plenty of people build castles underground. It's not as isolated as you think.
Notch could add an option not to update your older section of the world.
2) Let's assume that Notch did update pre-existing areas, you would still have to have to add more information to EACH block checking whether it has been player-placed or not. This would bloat the file size and cause generally undesirable effects in SMP and SSP.
it wouldnt happen if Notch will give us an option to choose:
1.update your older sections of the world with blocks
2.dont update the older sections, play the way you play right now.
also about the underground castles situation:
if each 1/400 cobblestone block could have the chance change to Lapis, the change to your castle will be minor if at all. you might have to work 10 minutes to restore your castle to its normal state, and again, you would have the option not to update your older parts of the map.
not even one of you related to the problem i brought up:
will you give up one your save / travel to new areas
EACH time there is a new block? this idea is ridiculous.
This is a good idea in theory, so if it's possible it'd definitely be nice.
As for it's possibility, it seems like it shouldn't be impossible.
On starting up an old map after an update, it could run a conversion like it did for when they changed the save file format. Then it could run the terrain generation for the new blocks, only placing them at appropriate levels in places that are untouched (untouched would mean same blocks as it would expect in untouched map with same seed at those places).
As far as lapis goes, even if it simply replaced any smoothstone at random with lapis I wouldn't complain, lapis is much more valuable than a single block of smoothstone. If a piece of your smoothstone castle got replaced with lapis ore it wouldn't be hard to fix, and you'd get some lapis out of it.
For new trees like birch, I'd suggest some random planting in appropriate places, rather than replacing old trees.
This would be especially nice for the nether if they add new blocks, as having to travel to new locations in the nether would be a pain.
Rollback Post to RevisionRollBack
Evidence suggests that many people quote posts without reading them in their entirety.
Still no infinite strongholds D:
To post a comment, please login or register a new account.
*new tree , *dyes
everything was going fine until i wanted to get blue.. i searched and couldnt find lapis ore.
my suggestion is this:
with every new update find a way to add those new features to old areas.
for example:
-every 1/200(or other rate) cobblestone in the right altitude could turn into lapis , ONLY in old areas.
-every 1\4(i dont know the rate of the new white tree) normal tree could be destroyed and replaced with the other tree type.
this is my idea, i think its very important to support old world owners.
the idea that one needs to wander off to new areas every new update AFTER he built a rail and a big mine is EXTREMELY ridiculous in my opinion.
Edit:
i wanted to add that the point of this forum is to bring up ideas, and yours is to say why you like it or not, not
to say that it would be impossible because of _____ blah blah blah.. leave possible or not possible to Notch's team.
again, you are probably not such a professional to say that.
about the save files:
hell yeah. i have the right to keep my save files. if Notch tells me that this idea is not practical ONLY then i will give up.
If you want lapis lazuli, explore. it's that simple. this "new-thing-added-go-explore-to-find-it" is actually part of the game, it adds charm.
also, commieduck is right, "don't get attached to your saves", it's beta and it's possible that one day, notch will add something that destroy all your maps :]
its kinda late here and i have school tomorrow. ill reply anyone new in 15 hours.
OK, let me take a crack at this:
1) Plenty of people build castles underground. It's not as isolated as you think.
2) Let's assume that Notch did update pre-existing areas, you would still have to have to add more information to EACH block checking whether it has been player-placed or not. This would bloat the file size and cause generally undesirable effects in SMP and SSP.
Here's what I mean.
------------------------------------------
If you add a boolean tag for bIsPlayerPlaced; It would add 1 bit of data per block.
The minimum actual data size for this game is a 32-bit structure but players whom use 64 bit processors would be screwed as each bit actually takes up 64 bits. This would add 32/64 extra bits per block (instead of 1 bit) which increases file size (unless he did bit pushing/pulling which would be processor heavy but save file size).
There is a maximum of 64x64x128 of data per chunk which means between 16 and 32MB heavier per chunk. If you went processor heavy by bit pushing/popping, Notch would have to increase the user requirements for the game, which would in turn cut into his sales but you would have 512 KB~1MB heavier files per chunk (which is really not good).
--------------------------------------------
Finally, you can keep your save files, no one said you had to delete them. There would just be a chance they'd be useless in future patches. Notch graced us with the ability to update our worlds from alpha to beta because the changes to the engine weren't completely dramatic. When he starts rolling out dramatic changes to the game engine/structure/design; don't expect to see such quick bandaid fixes. You may have to deal with losing your save game information for good. Don't feel bad though, I still have Sega CD games even though I no longer have a Sega CD.
Unless Java heavily optimized the code before interpretation, it would be unfeasible to do so, I will say no here.
OFFICIAL POSTING/REPLYING GUIDELINES
UNOFFICIAL POSTING GUIDE (PRT)
UNOFFICIAL REPLYING GUIDE (FTC)
not even one of you related to the problem i brought up:
will you give up one your save / travel to new areas
EACH time there is a new block? this idea is ridiculous.
As for it's possibility, it seems like it shouldn't be impossible.
On starting up an old map after an update, it could run a conversion like it did for when they changed the save file format. Then it could run the terrain generation for the new blocks, only placing them at appropriate levels in places that are untouched (untouched would mean same blocks as it would expect in untouched map with same seed at those places).
As far as lapis goes, even if it simply replaced any smoothstone at random with lapis I wouldn't complain, lapis is much more valuable than a single block of smoothstone. If a piece of your smoothstone castle got replaced with lapis ore it wouldn't be hard to fix, and you'd get some lapis out of it.
For new trees like birch, I'd suggest some random planting in appropriate places, rather than replacing old trees.
This would be especially nice for the nether if they add new blocks, as having to travel to new locations in the nether would be a pain.
Still no infinite strongholds D: