That's where some extra error handling could be useful, i suppose. It's waiting for the server to say it's done preparing the spawn area. I guess the server must have had a problem that didn't cause it to crash, but for some reason it must not have said [INFO] Done! in its console like it normally does. You can use control+C to exit the application, although you might have to kill the server manually. Then i'd launch the server and see what it says in the console.
It gets the path for the server's working folder based on the path for the jar provided, so i dunno, maybe it couldn't figure that out without the .\. Anyway, it should output to the console 3 messages per iteration: one with the coordinates it's setting, one "starting server", and one "stopping server". Then there are a couple more messages at the beginning and at the end of processing. How long it takes depends greatly on the system, and i really have no idea. I got bored after 30-60 minutes of watching a 10,000x10,000 level get about 10% of the way done so i went to bed. 1,000x1,000 takes a few minutes.
The progress is not outright stated (hey, an idea for the next version), but you can figure it out by looking at the coordinates it's currently working on. If you enter 1000 1000, it will build from (-500, -500) to (500, 500).
On a related note, Alpha Vespucci took about an hour and 40 minutes to produce an oblique left map of that 10,000x10,000 level.
Okay, here we go, Minecraft Land Generator 1.0.0. This was just for fun for me, so don't expect too much, and don't blame me if your house burns down and/or your dog explodes. And/or your level gets corrupted. Make a backup first.
The source is included, and you may consider it public domain. The included JNLP library uses a BSD-style license that is provided inside its .jar file.
Tested on Windows 7 only. Should be platform independent as far as i can tell, but i didn't test that. I'm willing to take feedback on fixes if they're required.
This application uses the specified Minecraft server .jar to generate land within the currently configured world, within the specified range, centered on (0, 0)*. It reads the world from server.properties, and requires that the world already exist, so run the server at least once first.
It makes a backup of level.dat before changing anything, and at the end, restores the original version, so all changes that persist after running are those made by the server itself. If it detects a backed up level.dat file, it will refuse to run, to give you a chance to figure out whether you want that or the current one.
The error handling may be a little shoddy.
* note that the default spawn point is sometimes quite far from (0, 0), so you may not spawn right in the middle.
Minecraft Land Generator version 1.0.0
Usage: java -jar MinecraftLandGenerator.jar server x y [java]
server : path to the server jar
x : X range to generate
y : Y range to generate
java : java executable to use
Examples: java -jar MinecraftLandGenerator.jar C:\MinecraftServer\minecraft_server.jar 1000 1000
java -jar MinecraftLandGenerator.jar C:\MinecraftServer\minecraft_server.jar 1000 1000 "C:\Program Files\Java\jre6\bin\java.exe"
ImageMagick? I'll have to give that a try. I can't edit a 20,000x20,000 image in gimp or acdsee on this thing. Well, maybe gimp. It's still trying to open it.
I've observed it happen on multiple, fresh worlds, and i don't see anything wrong with the level.dat files. That said, no, it's not necessarily rotated. It just looks sort of like it. And i think it might just be the materials the blocks are made of, not the placement of the blocks, that is in an odd pattern. But you can see on the map that something is strange about it.
For what it's worth, i also get frequent lighting bugs: extremely dark areas under trees or overhangs and oddly light lines across the sea floor. These fix themselves if you change the blocks or lighting nearby, of course. MCEdit or mce can fix that by recalculating lighting on all chunks, but i'm sure that could take a while for larger maps. But that's probably quite unrelated.
At this point, i have the program working great IF the x and y coords are always at the same offsets. Which, as you have described, i cannot rely on. I'll have to alter it a little to walk through the structure.
In the process of making this, though, i've been looking at my maps a little more closely, and i've noticed some of the chunks look rotated or flipped. It has nothing to do with this app; it happens even if a player walks out into new places. Take a look: viewtopic.php?f=1013&t=79772
I've been looking at the maps a little closer. It looks to me like some of the chunks being generated flipped or rotated on some maps? It's not just around the spawn point, and it's not just with certain worlds, although this one is pretty bad. I have generated several worlds and it happens in each of them to a greater or lesser extent.
It happens even when chunks are generated by a player walking to them, and seems to consist mostly of the material chosen being in the wrong spot. What i mean is very strange configurations of sand/dirt/stone. And, in some places, little holes everywhere. Looks very unnatural. I've made a couple of example images.
I looked at my old maps from before the Boo update and it occured on them, too.
On the map above, you can see weird artifacts all over the coastlines, and i've circled the one i'm looking at in the screenshot below.
Good idea. I was thinking about changing the spawn point manually but hadn't messed with it yet. Okay. But i don't think i understand this TAG_ notation, or it's out of date. The last the elements are a byte, a long (which i assume to be 8 bytes), and another long. Yet the 17th byte from the end is not a 1/0 for "winter mode"; it's a 0x6B. And i KNOW my spawnZ is not 1590167718. Guess i'll pick thorugh mce.py and see what it does, although i'm not familiar with Python yet.
If anybody thinks it would be useful for them, i can whip up a little java app to do this without the Multiplexer. But you'll still have to install Python and the required libraries.
It is not my experience that the server generates land nearly that far out. Alpha Vespucci yet shows plenty of ungenerated area within a 150-block distance. Still, yes, that's a potential method...
I understand that that's the purpose, and it's a fine purpose. I am just saying it could be nice to be able to skip the "walk to the corners" step in the latter case... but it is not necessary. That is not a difficult step.
0
0
The progress is not outright stated (hey, an idea for the next version), but you can figure it out by looking at the coordinates it's currently working on. If you enter 1000 1000, it will build from (-500, -500) to (500, 500).
On a related note, Alpha Vespucci took about an hour and 40 minutes to produce an oblique left map of that 10,000x10,000 level.
0
The source is included, and you may consider it public domain. The included JNLP library uses a BSD-style license that is provided inside its .jar file.
Tested on Windows 7 only. Should be platform independent as far as i can tell, but i didn't test that. I'm willing to take feedback on fixes if they're required.
This application uses the specified Minecraft server .jar to generate land within the currently configured world, within the specified range, centered on (0, 0)*. It reads the world from server.properties, and requires that the world already exist, so run the server at least once first.
It makes a backup of level.dat before changing anything, and at the end, restores the original version, so all changes that persist after running are those made by the server itself. If it detects a backed up level.dat file, it will refuse to run, to give you a chance to figure out whether you want that or the current one.
The error handling may be a little shoddy.
* note that the default spawn point is sometimes quite far from (0, 0), so you may not spawn right in the middle.
Minecraft Land Generator version 1.0.0 Usage: java -jar MinecraftLandGenerator.jar server x y [java] server : path to the server jar x : X range to generate y : Y range to generate java : java executable to use Examples: java -jar MinecraftLandGenerator.jar C:\MinecraftServer\minecraft_server.jar 1000 1000 java -jar MinecraftLandGenerator.jar C:\MinecraftServer\minecraft_server.jar 1000 1000 "C:\Program Files\Java\jre6\bin\java.exe"I don't know where else to put it, so have a megaupload.
http://www.megaupload.com/?d=ZO9QH4B4
0
0
For what it's worth, i also get frequent lighting bugs: extremely dark areas under trees or overhangs and oddly light lines across the sea floor. These fix themselves if you change the blocks or lighting nearby, of course. MCEdit or mce can fix that by recalculating lighting on all chunks, but i'm sure that could take a while for larger maps. But that's probably quite unrelated.
0
In the process of making this, though, i've been looking at my maps a little more closely, and i've noticed some of the chunks look rotated or flipped. It has nothing to do with this app; it happens even if a player walks out into new places. Take a look: viewtopic.php?f=1013&t=79772
0
It happens even when chunks are generated by a player walking to them, and seems to consist mostly of the material chosen being in the wrong spot. What i mean is very strange configurations of sand/dirt/stone. And, in some places, little holes everywhere. Looks very unnatural. I've made a couple of example images.
I looked at my old maps from before the Boo update and it occured on them, too.
On the map above, you can see weird artifacts all over the coastlines, and i've circled the one i'm looking at in the screenshot below.
0
0
0
0
0
0
0
0
viewtopic.php?f=1013&t=34648