BioMed
Control the biomes of your world!
BioMed enables you to:
- Convert sections of any map to a different biome!
- Convert whole maps to the same biome!
- Good for creative & flat world maps!
- Regenerate map sections with a different look! (Kind of working - see notes.)
- Generate your own mushroom islands! (See notes.)
- Thaw your spawn!
- Freeze your spawn!
- Spawn nether mobs in a normal world!
Instructions
Please read the entire overview before posting bugs/questions. Most reported bugs/questions are already answered here. If your Question is not answered here, try the Troubleshooting page.
Download BioMed.jar and copy it to your plugins directory. The plugin will generate a config file on first run, which you can then edit if desired (in game commands are recommended, however.)
The only parameters that cannot be controlled in-game are in the "options" section. They are:
- allowglobal
- allowop These options control the ability to set global biomes and use commands as op, respectively. They are enabled by default, so you will need to set them to "false" if you do not wish for your players to use them.
In-Dev / Requested
Reworking the command system! Leave a comment with suggestions. Looking into improving quality of some global biomes Looking into time-dependant biome regions (day/night cycles) Remove dependency on WorldEdit for selections (will still integrate if present) Whole-biome replace Free-form selections Brush tool
BioMed "In-Dev" is currently at version 0.7.1, and it is built against Craftbukkit-1.4.7-R1.0.
Latest Build notes:
- No longer requires WorldEdit (small bug introduced in v0.6)
- Global biomes are
currently unavailableJust added!in need of revision. They still work, but you may be disappointed over previous builds.- The commands for changing global biomes are still the same, so see the commands page for details.
- Use the biome "none" in your command to disable the global biome.
- All newly-generated chunks will be 100% the biome you specify. This will cause your global biome to be generated in areas where it wouldn't normally, and can have some weird results. File a ticket for any "buggy" behavior you find.
- BioMed will attempt to update existing chunks to the global biome whenever it is changed. It can only do this for currently loaded chunks, however. I am looking into a way to get around this, but for now be aware that you will have to fix a lot of these "holes" yourself.
- removing the global biome will not affect existing chunks. If you want to restore the default biome in an area, use one of the "clear" commands.
- BioMed will no longer store regions in its config file. On start/reload, any regions found there will be imported and removed from the file.
- User requests are always welcome. As long as the feature is reasonable to implement, I'll try to make it happen.
- I decided to not use the built-in biome API- as is- due to inefficiencies in handling large changes. My version is- in theory- much faster, but may contain bugs, or break with updates. As usual, report any bugs or error messages here for a response. Post a stack trace too for a quicker response. The more info, the better.
- NOTE on using WorldEdit's regen command: If you have a global biome set, all blocks affected by regen will be generated 100% as the global biome. This will allow you to quickly convert sections of an existing map with ease, but it still does not allow "controlled" regeneration on a small scale. I plan on implementing that as soon as I determine a good way to do it.
Commands
Permissions
Bugs
If you find a bug, or are having problems:
- Read what other users are saying, to see if there is a fix or workaround.
- If you cannot find your problem already mentioned, feel free to file a ticket, leave a comment, or PM me. If you don't feel like signing up for curse just to file a bug, you can also PM my bukkit.org account, Karl Marx.
If you are submitting a bug report, I strongly suggest that you include a stack trace as well. What's a stack trace?
@pdinklag
Not gone, just busy with other things...
Sorry the github is so out of date, though- I forgot to commit after the last release. Most of the work for 1.2.5 is actually already done, but there's way too much unfinished, new code for it to compile as is. It's a pretty big mess, and just looking at it is enough for me to close the project and work on something else. It would probably be less work for me to start over from what's on github than to undo all the changes at this point.
Anyways, it looks like all of the other biome plugins are just as abandoned now, so I'm glad someone's keeping it going.Thanks for your time!
Since dannytix seems to be gone (atm at least), I forked BioMed on github and updated it for CraftBukkit 1.2.5-R4.0.
Grab it here: https://github.com/pdinklag/BioMed/downloads
Note that this is an UNOFFICIAL release and I will not offer any support. It seems to work just like 0.4 did and I added support for Jungle and Jungle Hills biomes.
I wanted to make a nether in the normal world with this but now i can't even use it cause i have the latest version of bukkit
could you uplease pdate it soon?
Please update this to latest bukkit build, kind regards.
Greetings,
I selected an area with WordlEdit.
I set the biome to forest with "/biome set-selection forest"
And I set the global biome to forest with "/biome set-global forest"
But when I regen, it does not generate forest. There is no change.
Help
awesome plugin, just a suggestion can be there a config file to disable certian biomes or replace them automaticly with a other biome?
I really like to disable jungle biomes from the server and give people manually access to jungle saplings
@ryguy147
yes it is
a few requests:
bugs:
Is this working as of the newest Minecraft and CraftBukkit versions?
@Bug with unloaded chuncks
Maybe you shoould take a look on dynmap because dynmap is able to render not loaded chuncks so it shoudl be possible to also edit unloaded chunks. Just an idea.
_Martinius_
@dannytix
Yes, it used to be pretty much like that when I set a global biome: all chunks except for the spawn chunk were generated as the biome I set as global.
However, that doesn't work anymore since 1.2. I can't get any global biome to work now with either just WorldEdit, just Multiverse or the combination of both.
I just tried BioMed without ANY other plugins. Set the global biome of the default world ("world") to "MUSHROOM_ISLAND", stopped the server, deleted the world, started the server. Newly generated chunks report as "MushroomIsland", but they clearly aren't, see screenshot: http://stuff.pdinklag.de/2012-04-14_16.41.21.png
It's like this on all of the world now.
My config is as follows:
BioMed 0.4 in CB 1.2.5-R1.0, as said, no other plugins.
I feel like I'm missing something...
So Regenerating Map To A New Look Will Fix My Map Corruption?, coz i accidently turnt off my PC and my World is getting some errors and stuff like that, now, it generates ugly biomes, huge oceans etc
@_Martinius_
Yes, you can find it on the "Repository" page. The code on there at the moment is pretty outdated, though, so it might not be much help right now.
The problem with loaded chunks is already known. There's no built-in way to access unloaded chunks, and the server makes no distinction between unloaded and non-existent chunks; so there's no easy solution, but I'm looking into it when I get the chance.
Do you have a github?
And i would like to report a bug:
The set-global command is only working for loaded chuncks of the player if the chuncks of a map aren't loaded the biomes doesn't get changed
thanks for the awesome plugin _Martinius_
@pdinklag
That is an interesting bug. I will look into it, but my guess is that it has nothing to do with 1.2.5, but is a result of the way multiverse's regen command works. I suspect that restarting the server may sort things out with multiverse, but it probably won't touch the first few chunks generated. As for WorldEdit, it's regen command overrides any biome data in the existing chunk, so that won't work. As I recall, using regen with a global biome set does work, however, but the multiverse bug might be a problem here too. Let me know if any of that helps.
@NEREVAR117
If you are manually specifying the selection, then it disregards you current location completely. Use the f3 debug menu to get the x and z value of the "lowest numbered" block you want to change, and then just specify the width and height of a rectangle. Lowest numbered means the block within the region that has both the smallest x and smallest z- height does not matter. So, if the rectangle I wanted to change started at the coordinate x = -50, z = 20, and I wanted to make it 30 by 30; I would use the command /biome set -50 20 30 30 plains. I realize it's cumbersome, which is why I'm re-working it for the next release.
@superxz
I cannot tell from that alone, but since most problems give more information than that, I would assume that the plugin has crashed, and bukkit is just providing it's default message. Check your server logs for more details, and post them here.
I'm having some trouble with the mod
I have selected an area with WorldEdit, I typed:
/biome set-selection plains
but I get the message
/biome <set <type>¦get¦list¦clear¦set-selection <type>¦clear-selection>
any help?
/biome set [world_name x z width height] <biome name>
So how do you type that? Can I just use /biome set 30 30 plains? There should be examples for these commands. I'm trying to remove the snow biome from around a village, and I'd prefer not doing it chunk-by-chunk. I've tried several variations to get the command to work and I receive a syntax error every time.
Hey,
BioMed v0.4 does not seem to do anything for me in CB 1.2.5-R1.0.
I use it along with Multiverse.
I set the global biome of a world, regenerate it, go into it and while "/biome get-global" yields the biome I set, the world is in fact generated like a normal world, and in F3 the biomes are normal biomes. "/biome get" tells me the same as F3.
allowglobal is set to true in the config, and the config file itself lists my world with the biome I specified.
I executed these command in the main world "world" to create a mushroom island world called "alpha":
Selecting a WorldEdit area (vertically expanded), setting the biome using "/biome set-selection" and calling WorldEdit's regen does not do anything either.
Is there anything I am doing wrong here? It used to work like this before.
The log yields no errors or anything.
Setting the global biome will change the biome for all chunks that are loaded when you run the command, and cause all newly generated chunks to be generated with whatever biome you set.
Only new chunks will be have their blocks affected. existing chunks only have their biome info changed, leaving the blocks themselves as they were. Craftbukkit doesn't send biome updates currently, so you'll have to log out or move far away before you'll see the grass & leaves change colors. If you move far enough to start generating new chunks, they should all be 100% desert hills, though.
@ Danny
Me again, annoying I know, I did that command and got:
Changed the global biome to Desert hills
When/how does the world change to be that biome?