-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
33 additions
and
25 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Original file line | Diff line number | Diff line change |
---|---|---|---|
@@ -1,32 +1,40 @@ | |||
# A bukkit plugin that allows you to turn any image into a minecraft world! | # A bukkit plugin that allows you to turn any image into a minecraft world! | ||
|
|
||
Includes: | Includes: | ||
- CavePopulator |
|
||
- DesertPopulator | * CavePopulator | ||
- DungeonPopulator | * DesertPopulator | ||
- FlowerPopulator | * DungeonPopulator | ||
- LakePopulator | * FlowerPopulator | ||
- Mushroom Populator | * LakePopulator | ||
- QuarryPopulator | * Mushroom Populator | ||
- Ruins Populator - thanks @Nightgunner5 | * QuarryPopulator | ||
- Snow Populator | * Ruins Populator - thanks @Nightgunner5 | ||
- SpookyRoomPopulator | * Snow Populator | ||
- TorchPopulator - thanks @Nightgunner5 | * SpookyRoomPopulator | ||
- Tree Populator - thanks @heldplayer and @SpaceManiac | * TorchPopulator - thanks @Nightgunner5 | ||
- Ores! - thanks @Notch | * Tree Populator - thanks @heldplayer and @SpaceManiac | ||
* Ores! - thanks @Notch | |||
|
|
||
## Usage: | ## Usage: | ||
There are 2 ways to use this plugin, either through bukkit.yml or an external world manager, such as MultiVerse 2.0, that supports custom world generation. |
|
||
There are 2 ways to use this plugin, either through bukkit.yml or an external world manager, such as MultiVerse 2.0, that supports custom world generation. | |||
|
|
||
### Using bukkit.yml: | ### Using bukkit.yml: | ||
To set up a world using bukkit.yml, insert the following in your bukkit.yml configuration file: |
|
||
To set up a world using bukkit.yml, insert the following in your bukkit.yml configuration file: | |||
|
|||
worlds: | worlds: | ||
{*worldname*}: | {worldname}: | ||
generator: BananaImageToMap:{*imagefile*} | generator: BananaImageToMap:{imagefile} | ||
Make sure to replace {*imagefile*} with the name of the file *including the extension* that you |
|
||
put in your plugins/BananaImageToMap/ folder and {*worldname*} with the name of the world you wish to genenerate. | Make sure to replace {imagefile} with the name of the file *including the extension* that you | ||
put in your plugins/BananaImageToMap/ folder and {worldname} with the name of the world you wish to genenerate. | |||
|
|
||
### Using Multiverse 2 | ### Using Multiverse 2 | ||
Using Multiverse 2, which is to the best of my knowledge the only world management plugin that supports custom generators, the command is |
|
||
/mvcreate {*worldname*} NORMAL -g BananaImageToMap:{*imagename*} | Using Multiverse 2, which is to the best of my knowledge the only world management plugin that supports custom generators, the command is | ||
Again, replacing {*worldname*} and {*imagename*} with the world and image name respectfully. After that you can use it like any normal MV world. |
|
||
/mvcreate {worldname} NORMAL -g BananaImageToMap:{imagename} | |||
|
|||
Again, replacing {worldname} and {imagename} with the world and image name respectfully. After that you can use it like any normal MV world. |