173generator
Beta 1.7.3 terrain generator
This plugin generates beta 1.7.3 terrain.
Installation
MCStats
As of version 2.3 this plugin uses MCStats to collect data about the plugin, like how many servers/players use the plugin ect. (More about MCStats)
Disabling MCStats:
Edit file plugins/PluginMetrics/config.yml and change opt-out: false to true
Updating to v2.2 and newer
Configuration
1.5 and earlier: no configuration
Commands
/reload command
/reload command is not supported. Don't use it. It WILL break 173generator (and a lot of other plugins).
FAQ
TODO list
Statistics (MCStats)
Development builds
Development builds of this project can be acquired at the provided continuous integration server.
These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Source | Development builds
When will this be updated to 1.6.2?
Meanwhile I get the plugin work on 1.6.2 with Libigot.
@Tonkovich
I'm working on Minecraft version independent build.
@Barteks2x
Your new dev build fixed everything in my issue and I thank you for that tremendously. Now the only issue is 1.6.2 :P
@Tonkovich
I will add configuration option to enable using Terrain Control biome system. If not enabled it will use only Minecraft biomes. I recommend to wait for stable build for Minecraft 1.6.
EDIT: Build #33 - should be fixed (no custom biomes). There may be some issues with spawning mobs in worlds with this generator.
@Barteks2x
Wait so you want me to use other plugins to fix a issue where a world that is not suppose to be effected by this?
Let me restate my question is case there is any misunderstanding.
My main "normal" worlds for my server go World, World2, and World3. World and World3 are the only ones set to use this generator and it works perfectly fine. However, World2 is being effected by this plugin and is causing jungles not to spawn and when your plugin is removed the jungles generate again.
I am using Multiverse for configuring the worlds to use this generator and World2 is set to generator: 'null' but continues to be effected by this plugin. I will include a copy of my worlds.yml from Multiverse if it assists in finding a solution for my issue. I understand that it is a development build and running on a development build of Bukkit but I do not know if there is a problem with Bukkit or with the setup of your plugins code.
In simple terms what I am looking for is for worlds effected by this plugin to be effected and worlds set not to be effected not to be effected. Sorry for the long comment I probably should have put this in the issues page but hopefully this is the last comment needed.
World.yml: http://pastebin.com/EKy3YHHE
@snipern
Version for Minecraft 1.6 is development build. It's caused by my biome system. I'm working on using custom biomes (Will require TerrainControl plugin and TerrainControl mod clientside to work properly, without it all custom biomes will be "plains" biome)
@Tonkovich
Custom biomes should fix it.
@Barteks2x
Hi. Love your plugin! Betaworlds is amazing! But i have a problem with horses not spawning in plain biomes when this mapgenerator is used. Does anyone know if this plugin is the problem?
Keep up the good work!
@Barteks2x
It worked perfectly fine is all other versions of minecraft but for some reason in 1.6.1 it just doesn't generate jungles for me.
@jacklollz2
Fixed.
@Tonkovich
And it works properly on 1.5.1? Maybe somethins with biomes changed in 1.6.1 (biome IDs).
The development build for 1.6.1 seems to effect other worlds even if they are not set for the generator. For instance if I have two worlds with the generator my other world will NOT generate jungles. The biome is a jungle biome but converts to plains. When the plugin is removed and that area is regen'd it goes back to jungle.
To people using the development build, just change the plugin.yml 'main' to main: com.github.barteks2x.b173gen.plugin.Generator
I got this error when updating to 1.6.1. I downloaded the latest development build for bukkit. I also downloaded the latest development build that you gave out.
[SEVERE] Could not load 'plugins\b173gen-2.1.jar' in folder 'plugins' org.bukkit.plugin.InvalidPluginException: java.lang.ClassNotFoundException: org.Barteks2x.b173gen.plugin.Generator at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:184) at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:305) at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:230) at org.bukkit.craftbukkit.v1_6_R1.CraftServer.loadPlugins(CraftServer.java:239) at org.bukkit.craftbukkit.v1_6_R1.CraftServer.<init>(CraftServer.java:217) at net.minecraft.server.v1_6_R1.PlayerList.<init>(PlayerList.java:55) at net.minecraft.server.v1_6_R1.DedicatedPlayerList.<init>(SourceFile:11) at net.minecraft.server.v1_6_R1.DedicatedServer.init(DedicatedServer.java:106) at net.minecraft.server.v1_6_R1.MinecraftServer.run(MinecraftServer.java:391) at net.minecraft.server.v1_6_R1.ThreadServerApplication.run(SourceFile:582) Caused by: java.lang.ClassNotFoundException: org.Barteks2x.b173gen.plugin.Generator at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at org.bukkit.plugin.java.PluginClassLoader.findClass0(PluginClassLoader.java:80) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:53) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:173) ... 9 more
@DipDub
If you turn generating villages off already generated villages won't disappear - create new world if you use new config. If villages are generating in new world with disabled villages - create a ticket.
It seems like it is still generating villages. Even though I turned it off.
It seems like it only works if I delete the config. Anyway it works! Thanks!
@Traybair
Yes, if you won't change configuration it will be EXACLY the same (possible few block differences like dirt->sand) If you change configuration ores, trees and dungeons position willl be different.
edit: Added your question to FAQ.
If I create a world with the seed Glacier will it be the same as the old Glacier seed?
@resitancedude
Now this pugin uses biomes that are avaible in current minecraft version. By adding new biomes I can make biome transitions more smooth like in beta 1.7 (I can add few "sub-biomes" for each biome).
add new biom like terrain control ???