Bukkit

@ryudragon3

Yeah they are hidden from the list until the files get approved. It can take several days to get a file approved.

How to create a Tatooine world:

http://dev.bukkit.org/bukkit-plugins/hothgenerator/pages/tatooine/

1.16 uploaded. Now with tatooine (dry desert) worlds.

@ryudragon3

You can have both world types at the same time. I've added additional configuring where you can specify which type each hoth world is.

The tatooine worlds (desert) has something called thirst. Thirst will go up when exposed to the sun and down if you step into water or get into shelter. Once thirst is too high you will take damage.

@ryudragon3

How about this?

http://dev.bukkit.org/bukkit-plugins/hothgenerator/images/21-desert-mode/

hothgenerator 1.15 has been uploaded. Should appear in the download list shortly.

Please use at least craftbukkit 1.7.5 with this release.

@Shado47

I'll release a 1.7 version during the next few days.

I think I have solved the /reload problems. First by placing all schematic rendering in separate tasks that can be stored on disk and second by circumventing the bukkit problem of using the wrong instance of the chunk generator.

If you are making a terrain generation plugin and need to handle /reload properly then add something like this to your plugin onDisable() function:

// Unload worlds to make sure the ChunkGenerator is reloaded properly
List<World> worlds = this.getServer().getWorlds();
for(int i=0;i<worlds.size();i++)
{
	World world = worlds.get(i);
	if(this.isHothWorld(world))
	{
		List<Player> players = world.getPlayers();
		for(int j=0;j<players.size();j++)
		{
			Player player = players.get(j);
			player.kickPlayer("Server reloading");
		}
		this.getServer().unloadWorld(world, true);
	}
}

@ryudragon3

Shouldn't be too hard. I guess I could make it possible to configure if the plugin should generate a sandy world or an icy world.

But first I have to deal with the 1.7 issues and perhaps find out a way to prevent people from disabling the plugin while it is still generating chunks...

I'm actually working on a 1.7.x version at the moment. Unfortunately bukkit has decided to deprecate a lot of functions so it's quite painful to go through. For instance, with the removal of the setData() function for blocks there's no way to set the height of snow. There's simply no replacement API for this.

Also being reliant on pasting external schematics based on block type ID' s into the world forces me to re-implement my own type ID to Material conversion which I will have to keep updated for every new release.

The setData problem is the big issue though since that means that I have to reimplement specific handling for each block type that takes a data parameter. Such as the rotation of chests or color of wool.

Unfortunately this all means that plugins won't be able to handle future blocks or unknown blocks properly without updating the code in the plugin.

I'd much rather had prefered if bukkit had hold on to an abstraction of the block type ID's and data values regardless of what mojang does with the id's internally so that every plugin wouldn't have to make their own abstraction.