1.13...?
Craftaris opened this issue · 4 comments
Is anyone planning to update the plugin to 1.13?
rutgerkok just dropped me an email confirming that he has decided not to update TerrainControl to 1.13.
Hey @rutgerkok,
Sorry to hear that developing TC wasn't fun anymore, although I can imagine and I know what sacrifices it can take. I and everyone at OTG want to thank you for the enormous amount of work you've done for TC, and for making OTG possible. You'll always be welcome on the OTG Discord (/OpenTerrainGen) and Reddit (give us a holler and we'll give you a developer role), and you'll always be listed as one of the original developers. Drop by for a chat any time, you may even find a few familiar faces :).
Gigantic thanks for everything and all the best mate!
That's what I thought.. Honestly TerrainControl is one of the best plugins, many servers depend on it, mine included. I suppose this 8 year old plugin really deserves a continuation.
Oh man If I somehow got a hand of much free time I'd update this.
@rutgerkok Have you looked at the new world generator yet? Is it much different?
I'll keep an eye on OTG as well!
The Minecraft code has changed quite a bit. However, that shouldn't hurt TerrainControl - it does not use Minecraft code much. It lives in its own parallel universe. I don't think this update is any more difficult that any other Minecraft update. Even the changeover from static block ids + data values to the new system doesn't affect TerrainControl much: materials are all abstracted away in the LocalMaterialData interface.
However, adding new features becomes more and more difficult. We have like five different biome generators, config files can be arranged in many ways with many file extensions and I think there are three different generators for the base terrain. The complexity of adding a new feature is extremely high, and if you refactor something you have a high risk of breaking someone's configuration files. TerrainControl's error handling consists of printing a message and then resetting that part of the config, which can have very destructive results. It's no surprise that TerrainControl's forks mainly focus on Forge (and largely ignore Bukkit) to reduce the complexity.
At some point maintaining this plugin was just no longer fun. I have still maintained it for a few more years, as I was using some features of TerrainControl on my own server. However, for Minecraft 1.13 I simply decided to write a small plugin (https://github.com/rutgerkok/Dough) that only provides what I personally need for a custom world generator.