we started a custom world and I accidentally made ore way too rare. we have built quite a bit already so restarting a new world is the last thing we want to do
Based on those you really did go too far; reducing the number and increasing the range makes it much harder to find anything (the fact that diamond normally has a range of only 16 means it isn't as hard to find as the per-chunk ore counts suggest, when compared to ores like iron, when mining within its range).
That said, you can use MCEdit to repopulate chunks, which will regenerate ores and other features; they will generate differently if you change the settings (otherwise, ores generate the same way so regenerating chunks only makes new ores if you filled in what was mined with stone). To change the preset you can use NBTExplorer to directly edit the generatorOptions tag in level.dat (or does the server save it elsewhere? I assume you got the preset used from somewhere), which stores it in the same format as the preset code shown. Note that existing chunks will have somewhat more ores (depending on the new settings) than new chunks, including new ores in the walls of existing mines and previously mined-out caves (making it easy to harvest them); trees and other features will also be regenerated so you might end up with trees and stuff in places you don't want them to be; any stone (smooth or its variants) used in building will also be replaced with ores, so you probably want to test this first.
Based on those you really did go too far; reducing the number and increasing the range makes it much harder to find anything (the fact that diamond normally has a range of only 16 means it isn't as hard to find as the per-chunk ore counts suggest, when compared to ores like iron, when mining within its range).
That said, you can use MCEdit to repopulate chunks, which will regenerate ores and other features; they will generate differently if you change the settings (otherwise, ores generate the same way so regenerating chunks only makes new ores if you filled in what was mined with stone). To change the preset you can use NBTExplorer to directly edit the generatorOptions tag in level.dat (or does the server save it elsewhere? I assume you got the preset used from somewhere), which stores it in the same format as the preset code shown. Note that existing chunks will have somewhat more ores (depending on the new settings) than new chunks, including new ores in the walls of existing mines and previously mined-out caves (making it easy to harvest them); trees and other features will also be regenerated so you might end up with trees and stuff in places you don't want them to be; any stone (smooth or its variants) used in building will also be replaced with ores, so you probably want to test this first.
Yes; it shows new blocks added since 1.5 as "future block" with a missing texture but can copy them, even find/replace if you manually put the ID in (block IDs are still numeric in the save files; metadata is also still the same even though the game no longer uses it internally); items (editing) might be more problematic but you can still copy stuff. I just tested it as well by copying a dungeon from a 1.8 world, then pasted it into another world, then loaded it in 1.8 and the items in the chests were there (MCEdit did throw an error when I tried to edit an item ID; "TypeError: Expected unicode, got int" but you should only have to copy stuff).
Also, if you are just repopulating chunks you only need to click on the "chunk control" button (rightmost button at the bottom), then Ctrl+A to select all chunks, then on the left-hand menu click "repopulate".
In any event, you always want to make a backup first before doing anything; you can also use MCEdit to analyze the world to see just much much of each ore is present (among other things, making veins bigger increases the size in a nonlinear fashion; dirt/gravel/stones are set to 33 but are very often twice the size or more, likely because the size is like a radius for a distorted spherical blob of blocks; for comparison, you can use the values I show in this thread).
Yes; it shows new blocks added since 1.5 as "future block" with a missing texture but can copy them, even find/replace if you manually put the ID in (block IDs are still numeric in the save files; metadata is also still the same even though the game no longer uses it internally); items (editing) might be more problematic but you can still copy stuff. I just tested it as well by copying a dungeon from a 1.8 world, then pasted it into another world, then loaded it in 1.8 and the items in the chests were there (MCEdit did throw an error when I tried to edit an item ID; "TypeError: Expected unicode, got int" but you should only have to copy stuff).
Also, if you are just repopulating chunks you only need to click on the "chunk control" button (rightmost button at the bottom), then Ctrl+A to select all chunks, then on the left-hand menu click "repopulate".
In any event, you always want to make a backup first before doing anything; you can also use MCEdit to analyze the world to see just much much of each ore is present (among other things, making veins bigger increases the size in a nonlinear fashion; dirt/gravel/stones are set to 33 but are very often twice the size or more, likely because the size is like a radius for a distorted spherical blob of blocks; for comparison, you can use the values I show in this thread).
got everything done right and increased the chance of iron and gold to 10 size and 10 count and I still dont see any in the world. coal is at 15 size and 17 count and its everywhere. I can tell it worked though because I saw new coal
does the server constantly check the server.properties for generation settings? what I'm thinking could have happened is its did repopulate but it's using the old settings from when the world was first created and never checked the server properties again?
got everything done right and increased the chance of iron and gold to 10 size and 10 count and I still dont see any in the world. coal is at 15 size and 17 count and its everywhere. I can tell it worked though because I saw new coal
does the server constantly check the server.properties for generation settings? what I'm thinking could have happened is its did repopulate but it's using the old settings from when the world was first created and never checked the server properties again?
Did you restart the server? I don't think you can even open a save in MCEdit while it is being used by the game, or you get an error or can't save. Also, it may be using the settings in level.dat instead, similar to how the player data in it overrides the player.dat file in singleplayer (this is why if you move a player in MCEdit you have to move the generic "player" as well); you probably should change both of them.
Also, you can analyze an area in MCEdit to see if more ore has actually been generated, comparing it to before (for example, select a 100x100 area, bedrock to sky, with one corner at 0,0 and the other at 100, 100 (just select the 0,0 block and use the "nudge" buttons above the bottom to resize it, then go to that area in-game to load the chunks; this last may also be your issue because only chunks loaded by a player will be repopulated).
Also, be sure to save after repopulating chunks; I've noticed that if you do so and quit MCEdit doesn't prompt to save changes and doesn't save.
Did you restart the server? I don't think you can even open a save in MCEdit while it is being used by the game, or you get an error or can't save. Also, it may be using the settings in level.dat instead, similar to how the player data in it overrides the player.dat file in singleplayer (this is why if you move a player in MCEdit you have to move the generic "player" as well); you probably should change both of them.
Also, you can analyze an area in MCEdit to see if more ore has actually been generated, comparing it to before (for example, select a 100x100 area, bedrock to sky, with one corner at 0,0 and the other at 100, 100 (just select the 0,0 block and use the "nudge" buttons above the bottom to resize it, then go to that area in-game to load the chunks; this last may also be your issue because only chunks loaded by a player will be repopulated).
Also, be sure to save after repopulating chunks; I've noticed that if you do so and quit MCEdit doesn't prompt to save changes and doesn't save.
It actually did repopulate but there is 0 iron ore in any chunks still. Do you know of a way to edit the level.dat so I can change the settings from within there?
I solved the entire issue! First, you have to use NBTExplorer to open the level.dat. there will be an entry within this file called "generation". double click it to edit it and manually change it here. then save it and open the world in MCEdit, ctrl A to select the entire world. then push a button called something like "chunk options" and then "repop". let it complete then save and quit MCEdit. that's all there is too it!
yes, same world, but all the ore, trees and it seems like the animals regenerated as if the world was just created. everything we made was still intact. the only issue we had was someone who used stone for their house had some coal in their walls
isnt that the case with almost every new command block command in this update?
As a server admin, it's kind of a joke to use the rationality that it is "OP" when I could easily spawn 1000 of every ore in a minute if I wanted to.
{"coordinateScale"\:684.412,"heightScale"\:6000.0,"lowerLimitScale"\:212.22534,"upperLimitScale"\:282.6338,"depthNoiseScaleX"\:200.0,"depthNoiseScaleZ"\:200.0,"depthNoiseScaleExponent"\:0.5,"mainNoiseScaleX"\:80.0,"mainNoiseScaleY"\:160.0,"mainNoiseScaleZ"\:80.0,"baseSize"\:8.5,"stretchY"\:10.219226,"biomeDepthWeight"\:1.0,"biomeDepthOffset"\:0.0,"biomeScaleWeight"\:4.077465,"biomeScaleOffset"\:0.0,"seaLevel"\:49,"useCaves"\:true,"useDungeons"\:true,"dungeonChance"\:100,"useStrongholds"\:true,"useVillages"\:true,"useMineShafts"\:true,"useTemples"\:true,"useMonuments"\:true,"useRavines"\:true,"useWaterLakes"\:true,"waterLakeChance"\:7,"useLavaLakes"\:true,"lavaLakeChance"\:16,"useLavaOceans"\:false,"fixedBiome"\:-1,"biomeSize"\:5,"riverSize"\:5,"dirtSize"\:33,"dirtCount"\:10,"dirtMinHeight"\:0,"dirtMaxHeight"\:256,"gravelSize"\:33,"gravelCount"\:8,"gravelMinHeight"\:0,"gravelMaxHeight"\:256,"graniteSize"\:33,"graniteCount"\:10,"graniteMinHeight"\:0,"graniteMaxHeight"\:80,"dioriteSize"\:33,"dioriteCount"\:10,"dioriteMinHeight"\:0,"dioriteMaxHeight"\:80,"andesiteSize"\:33,"andesiteCount"\:10,"andesiteMinHeight"\:0,"andesiteMaxHeight"\:80,"coalSize"\:17,"coalCount"\:15,"coalMinHeight"\:0,"coalMaxHeight"\:255,"ironSize"\:2,"ironCount"\:9,"ironMinHeight"\:0,"ironMaxHeight"\:255,"goldSize"\:3,"goldCount"\:7,"goldMinHeight"\:0,"goldMaxHeight"\:255,"redstoneSize"\:18,"redstoneCount"\:20,"redstoneMinHeight"\:0,"redstoneMaxHeight"\:255,"diamondSize"\:2,"diamondCount"\:3,"diamondMinHeight"\:0,"diamondMaxHeight"\:240,"lapisSize"\:5,"lapisCount"\:5,"lapisCenterHeight"\:0,"lapisSpread"\:255}
Based on those you really did go too far; reducing the number and increasing the range makes it much harder to find anything (the fact that diamond normally has a range of only 16 means it isn't as hard to find as the per-chunk ore counts suggest, when compared to ores like iron, when mining within its range).
That said, you can use MCEdit to repopulate chunks, which will regenerate ores and other features; they will generate differently if you change the settings (otherwise, ores generate the same way so regenerating chunks only makes new ores if you filled in what was mined with stone). To change the preset you can use NBTExplorer to directly edit the generatorOptions tag in level.dat (or does the server save it elsewhere? I assume you got the preset used from somewhere), which stores it in the same format as the preset code shown. Note that existing chunks will have somewhat more ores (depending on the new settings) than new chunks, including new ores in the walls of existing mines and previously mined-out caves (making it easy to harvest them); trees and other features will also be regenerated so you might end up with trees and stuff in places you don't want them to be; any stone (smooth or its variants) used in building will also be replaced with ores, so you probably want to test this first.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
does MCEdit even work for 1.8 worlds?
Yes; it shows new blocks added since 1.5 as "future block" with a missing texture but can copy them, even find/replace if you manually put the ID in (block IDs are still numeric in the save files; metadata is also still the same even though the game no longer uses it internally); items (editing) might be more problematic but you can still copy stuff. I just tested it as well by copying a dungeon from a 1.8 world, then pasted it into another world, then loaded it in 1.8 and the items in the chests were there (MCEdit did throw an error when I tried to edit an item ID; "TypeError: Expected unicode, got int" but you should only have to copy stuff).
Also, if you are just repopulating chunks you only need to click on the "chunk control" button (rightmost button at the bottom), then Ctrl+A to select all chunks, then on the left-hand menu click "repopulate".
In any event, you always want to make a backup first before doing anything; you can also use MCEdit to analyze the world to see just much much of each ore is present (among other things, making veins bigger increases the size in a nonlinear fashion; dirt/gravel/stones are set to 33 but are very often twice the size or more, likely because the size is like a radius for a distorted spherical blob of blocks; for comparison, you can use the values I show in this thread).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
got everything done right and increased the chance of iron and gold to 10 size and 10 count and I still dont see any in the world. coal is at 15 size and 17 count and its everywhere. I can tell it worked though because I saw new coal
does the server constantly check the server.properties for generation settings? what I'm thinking could have happened is its did repopulate but it's using the old settings from when the world was first created and never checked the server properties again?
Did you restart the server? I don't think you can even open a save in MCEdit while it is being used by the game, or you get an error or can't save. Also, it may be using the settings in level.dat instead, similar to how the player data in it overrides the player.dat file in singleplayer (this is why if you move a player in MCEdit you have to move the generic "player" as well); you probably should change both of them.
Also, you can analyze an area in MCEdit to see if more ore has actually been generated, comparing it to before (for example, select a 100x100 area, bedrock to sky, with one corner at 0,0 and the other at 100, 100 (just select the 0,0 block and use the "nudge" buttons above the bottom to resize it, then go to that area in-game to load the chunks; this last may also be your issue because only chunks loaded by a player will be repopulated).
Also, be sure to save after repopulating chunks; I've noticed that if you do so and quit MCEdit doesn't prompt to save changes and doesn't save.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
It actually did repopulate but there is 0 iron ore in any chunks still. Do you know of a way to edit the level.dat so I can change the settings from within there?
yes, same world, but all the ore, trees and it seems like the animals regenerated as if the world was just created. everything we made was still intact. the only issue we had was someone who used stone for their house had some coal in their walls