Inactive [WGEN] PhoenixTerrainMod V0.8.2 - Now BOBs spawn from saplings[1060]

Discussion in 'Inactive/Unsupported Plugins' started by Matt, Jul 28, 2011.

  1. Offline



    Phoenix Terrain Mod - world generator.

    Version: v0.8.2
    Download at

    Phoenix Terrain Mod is a mod based off of Bucyruss's BiomeTerrainMod. It basically allows you to customize Minecrafts terrain generation to control ore spawns, terrain types, biome size, basically everything. It was continued by R-T-B however he has since discontinued.

    Khorn has decided to continue the mod as Phoenix Terrain Bukkit plugin. Most recently Khorn has partnered with Rebelj12a and to integrate the Phoenix Terrain Community better and provide better support for users of Phoenix Terrain.

    Sponsored by


    Example Images
    Show Spoiler


    What you can control with settings file:
    • Biome sizes.
    • Temperature and moisture limits.
    • Caves generation.
    • World water level.
    • Terrain generation.
    • Tree density.
    • Ores generation.
    • Block replacement.
    • Custom object spawn.
    • Multi world support, config per world.
    How to install:

    Video here

    Step 1: Drop PTMBukkit.jar into the plugin folder.

    Step 2: Modify bukkit.yml in the root folder and add the line

            generator: PhoenixTerrainMod
    Step 3: change the "YOUR_WORLD_NAME" into the name of the world you want to work with.

    Step 4: Save the YML and boot your server.

    Step 5: Go into the newly generated Ini file and adjust accordingly (that is, in your plugins folder look for the new PhoenixTerrainMod folder with corresponding folder to your world and inside the BOB folder & ini file).

    Step 6: Your done!

    Optional Steps:
    These are to follow after Step 6. If you wish to add custom items like the BOB's which are custom style tree's, little island statues, etc, then drop the applicable ones into the Plugins/Phoenix.../"world"/BOB/ folder. World being the name of the world its generating. Once you reboot the server again, it will load those files accordingly and they will generate in your map.

    Additional/Multiverse Steps:
    After you've generated a world via Multiverse. Go into the multiverse folder and look for the worlds.yml. In there, you want to add the below code.
    generator: PhoenixTerrainMod
    To the bottom of the worlds.yml mouthful. This is AFTER you've generated the world, just add it to the bottom line of the entire setup (with proper YML spacing like the rest of the config).

    Settings file:
    This is edited SteelCrow's guide to the PTM settings
    His main post here
    Show Spoiler

    This is my attempt to explain the settings ini file for the PTM (Pheonix Terrain Mod) which is the successor to Bucyruss' terrain mod.

    This guide is accurate as far as I can tell and within my understanding of the settings. I am quite likely in error regarding some things. Feel free to correct me and let me know to update. However, be prepared to be required to provide examples and/or verifications.

    That said, lets begin.

    A quick note about seeds. The seed you use still plays an important part in what your world is like. The settings affect how the seed gets implemented, they do not override or replace the seed. You should generate several worlds with different seeds before deciding whether a set of settings is whast you were trying for or not.

    <All Biome Variables>

    These set the global environmental conditions. Currently they only affect the generation of the world and biomes therein, not the designation overlay that MC uses for weather etc.

    Modifies the size of biomes. Larger values generate larger biomes.
    "This settings affects the average dimension of biomes on a linear scale, so every doubling of this value will quadruple the area of biomes."
    Think of it as sort of a radius multiplier. Setting it to 5 is a huge biome, it'll be a long ways before it changes. 2 to 3 is decent. 100 should be thousands of meters across, maybe tens of thousands.
    The initial 1.5 setting is the normal vanilla biome size setting. Remember that this is a multiplier of the variable sized vanilla biomes.

    Sets the minimum and maximum moisture of the world
    Moisture is a percentage. 1.0 = 100%
    Setting both to the same number or small range will limit the range of biomes generated. (see biome chart) Used to generate only certain biomes types or to exclude biome types by setting the ranges appropriatly when used in conjunction with the tempurature settings

    Sets the minimum and maximum temperature of the world.
    Again a percentage expressed as 1.0 = max temp.
    Used the same way as the moisture settings.

    The tempurture vs moisture biome diagram:

    Those are the default settings. Settings range is -1 to +1. smaller (and neg) numbers mean less chance of snow and ice, higher means greater chance.
    I don't know how accurate this is given that Notch played with the snow and ice regeneration part of the algorithm. Before 1.6.6 the ice wouldn't regenerate, now it will. This may now only set the INITIAL conditions and nothing more. I haven't had the chance to test it yet.
    There is also a sort of biome overlay in MC that PTM attempts to adapt. Untested at this time.

    <Swamp Biome Variables>

    Places a strip of mud or clay (size is dependent on the swampSize setting number) around the edge and below surface water. This will only occur in swampland biomes. The muddySwamp setting takes priority over the claySwamps setting.

    <Desert Biome Variables>

    Will remove all water from desert and ice desert biomes.
    If you set your temperature and moisture settings to generate a desert world, making waterlessDeserts:true will result in the only surface water being in notch ponds. Setting notch ponds to false will result in the only water being in underground lakes and streams.

    Will remove all dirt from the surface of deserts. This setting was introduced because changing some terrain generation settings will cause dirt to erroneously appear on the surface of desert biomes.

    Will turn on the ability to let dirt appear on the surface. This setting occurs after removeSurfaceDirtFromDesert so turning both on will cause dirt to appear in your desert biomes.

    Sets the frequency at which dirt will appear in the desert. The setting corresponds to the average number of chunks before a dirt block will appear. Example: setting desertDirtFrequency:100 means that, on average, you will encounter one dirt block every 100 chunks in the game.

    <Cave Variables>

    This controls the odds that a given chunk will host a single cave and/or the start of a cave system.

    The number of times the cave generation algorithm will attempt to create single caves and cave systems in the given chunk. This value is larger because the likelihood for the cave generation algorithm to bailout is fairly high and it is used in a randomizer that trends towards lower random numbers. With an input of 40 (default) the randomizer will result in an average random result of 5 to 6. This can be turned off by setting the "even cave distribution" setting (below) to true.

    Setting this to true will turn off the randomizer for cave frequency (above). Do note that if you turn this on you will probably want to adjust the cave frequency down to avoid long load times at world creation.

    Sets the minimum and maximum altitudes at which caves will be generated. These values are used in a randomizer that trends towards lower numbers so that caves become more frequent the closer you get to the bottom of the map. Setting even cave distribution (above) to true will turn off this randomizer and use a flat random number generator that will create an even density of caves at all altitudes.

    The odds that the cave generation algorithm will generate a single cavern without an accompanying cave system. Note that whenever the algorithm generates an individual cave it will also attempt to generate a pocket of cave systems in the vicinity (no guarantee of connection or that the cave system will actually be created).

    The number of times the algorithm will attempt to start a cave system in a given chunk per cycle of the cave generation algorithm (see cave frequency setting above). Note that setting this value too high with an accompanying high cave frequency value can cause extremely long world generation time.

    This can be set to create an additional chance that a cave system pocket (a higher than normal density of cave systems) being started in a given chunk. Normally, a cave pocket will only be attempted if an individual cave is generated, but this will allow more cave pockets to be generated in addition to the individual cave trigger.

    The minimum and maximum size that a cave system pocket can be. This modifies/overrides the cave system frequency setting (above) when triggered.


    <Terrain Variables>
    Sets the water level of the world. Also depends on there being water to lower. See the moisture settings.

    If this value is greater than 0, then it will affect how much, on average, the terrain will rise before leveling off when it begins to increase in elevation. If the value is less than 0, then it will cause the terrain to either increase to a lower height before leveling out or decrease in height if the value is a large enough negative.

    This is supposed to control height of the land. Has been 'broken' in the past. A high number will give you very sharp cliffs and high plateaus. It's easy to have the land end up at the max height level by accident. Experiment in small increments. Also it's dependant on the world seed used.

    If this value is greater than 0, then it will affect how much, on average, the terrain (usually at the ottom of the ocean) will fall before leveling off when it begins to decrease in elevation. If the value is less than 0, then it will cause the terrain to either fall to a lesser depth before leveling out or increase in height if the value is a large enough negative.

    May be 'broken'. Seems to control the underwater slope/roundness to the bottom of the oceans. A high number will result in sudden sharp plunges to max depth. (good for underwater worlds) High numbers will effectively remove all beaches and shoals.

    Be aware this can affect 'valleys' as well. It may in some circumstances raise land if negative.

    Can increase (values greater than 0) or decrease (values less than 0) how much the landscape is fractured horizontally.

    Think of this as how often a horizontal line is fractured. That's not accurate as far as what is happening but it does let you grasp the nature of what this does. The higher the number the more fractures. Think of it as continents being smashed into smaller bits. Increase for archipelagos decrease for continents. (not accurate, but allows you to grasp the general function)

    Negative fractureHorizontal should stretch out terrain features and make for smoother, flatter terrain.

    Can increase (values greater than 0) or decrease (values less than 0) how much the landscape is fractured vertically. Positive values will lead to large cliffs/overhangs, floating islands, and/or a cavern world depending on other settings.

    This controls how often the vertical 'line' fractures. As the vertical height limits the number of visible fractures this setting doesn't always seem to effect much change. This is the setting that will give you plateaus and floating islands and the overhangs, undercuts and arches. A setting about 5 should get you floating islands.

    Negative fractureVertical values should smooth out terrain features such as the sides of things like hills and cliffs.

    Can sometimes create lag when it generates a massive underground vault near bedrock. Especially with large cave complexes.

    Fracture is applied near the begining of the terrain generation and affects the basic shape and nature of the land.

    Hard to explain, but think of these as terrain chaos settings. The larger the values the more chaotic/volatile landscape generation becomes. Setting the values to negative will have the opposite effect and make landscape generation calmer/gentler.
    Another way to think of them is the amount of noise added to the general terrain shape.

    Adjust the weight of the corresponding volatility settings. This allows you to change how prevalent you want either of the volatility settings to be in the terrain. Values should be between 0 and 1 and sum to some number equal to or less than 1. An example would be to set volatility1 to something high and volatility2 to some negative number. Then adjust volatilityWeight1 to a small number (say 0.1) and volatilityWeight2 to a larger number (0.85). This should result is mostly calm/flat landscape with the occasional chunk of terrain floating or jutting into the air.

    Volatility is applied near the end of the terrain generation and essentially affects the roughness of the base terrain.

    If you want flat land with rare but violent cliffs, you would have low horizontal fracture, and one volatility at 0 and the other one high, like 5+ (or more!) with a low weight, like .05 or something. Remember the weights may add up to no more than 1. I assume the unused % of the weigh allows the seed to generate nuetrally with no application of either volatility..

    Removes the bedrock form the bottom of the map.
    Turns the bedrock layer into a single, flat layer one block thick.
    Turns all bedrock into Obsidian


    <Replace Variables>
    Attempts to replace all surface stone with its nearest non-stone neighbor block type (dirt, grass, sand, gravel, or clay). If it cannot find a suitable neighbor block to duplicate, then it will default to Sand in Desert biome types and Grass in all others.

    Will replace blocks after any generation. Use block Ids to select blocks.

    Replace any gravel to sand.
    ReplacedBlocks :13=12,17=20
    Gravel to sand and wood to glass.

    <Cactus&Tree Variables>
    Use Bob objects during world generation
    Untested. Not sure myself.
    determines whether vanilla trees spawn or not.
    Sets the global, starting tree density for all biomes. Increasing the value increases the density of trees in all biomes.
    Sets the tree density in each biome individually. Large negative values are used to prevent trees from spawning at all.
    (untested that the variable range is between 1-8, with -20 guaranteeing no trees spawn.)
    (untested; tree density rates are bypassed by the bob object placement of bob trees)
    These settings adjust the creation variables for cacti.

    <Lava Pool Variables>
    The levels at which any caves are filled with lava (initialy the bottom 10 layers near bedrock)

    <Underground Lake Variables>
    Enables underground lakes.
    Allows underground lakes to spawn in the air.
    These settings adjust the creation variables for underground lakes.

    < Above Ground Variables>
    Pretty self-explanitory.
    Frequency is the number of times, per chunk, that the game will try to make a placement.
    Rarity is the odds (out of 100) that the game will actually make each placement.
    The above settings mean that yellow flowers will occur twice per chunk. (2x100%)
    Roses will show up on average once per two chunks (1x50%)
    Brown mushrooms once per four chunks (1x25%)
    Red mushrooms about once every seven chunks (1x13%)
    Reeds, ten per chunk (10x100%)
    Pumpkins, once per thirty-three chunks. (1x3%)
    Remember that the spawn requirements must also be met. So if there's no dirt next to water the reeds will not spawn all 10, only what can.
    Pumpkin settings are for a pumpkin patch (So I believe, haven't tested).
    <Above/Below Ground Variables>
    Changes the water source spawning algorithm to a flat distribution. Normally, water sources are distributed with a higher frequency toward the bottom of the map.
    Water and lava sources are the single source blocks that create waterfalls and lavafalls, both above and below ground.
    The numbers seem high to me, but I think there are spawn conditions that result in the majority of the placement attempts being aborted. I've never seen a single water source placed in a cave ceiling or be buried in a wall. I assume then that they need to have the placement location open on one side with a minimum volume of air to spawn. So while the above settings seem like waterfalls will happen fifty times per chunk (50x100%) they actually occur far less frequently.

    Setting it to true will remove those surface ponds of lava and water.
    <Below Ground Variables>
    These 'ore' deposit settings are all alike and will be explained together. The initial settings are the vanilla MC settings.
    "Frequency is the number of times, per chunk, that the game will try to make a deposit.
    Rarity is the odds (out of 100) that the game will actually make a deposit."
    Using the Lapis as an example; What it means is that the world generator is always going to try to place one deposit of lapis per chunk (DepositFrequency). Each try has 100% chance of happening (DepositRarity). And that placement will be from 1 to 7 blocks of Lapis (DepositSize).
    So in a single chunk these settings can spawn anywhere from 1 to 7 blocks of Lapis.
    If the Deposit Frequency was changed to 5, it could spawn anywhere from 5 to 35 blocks of Lapis. This is PER CHUNK. 35 Lapis in a single chunk is one lapis in every 5x5x5 block in the 16 layers available with these settings. And it will occur like that in each and every chunk in the world. There would be far more lapis around than you would ever be likely to use.
    I personally don't like simply increasing these settings as it makes the survival game far too easy. However coupled with the additional three sets of settings for each ore can make for interesting distribution patterns.
    There are four deposit setting per ore. What this allows [with a little creativity] is multiple variations in the sizes and locations of ores.
    For example;
    These two settings will produce iron as normal, plus because of the use of the rarity2 (etc) settings, it will once per 100 chunks (on average) produce an additional iron deposit of between 1 to 30 blocks. A 'vein' of iron ore per se., deep down.
    Another example;
    These will produce some unusual effects.
    Set one will produce the usual vanilla distribution of gold. There will always be two deposits of 1-8 gold per chunk.
    Set two will deposit a single grouping of 1-16 gold just below sea level, but only once in every 20 chunks. It's likely that some of it will be replaced with ocean so you'll often find these lying in the deeper areas of water, when you don't find them in caves or solid rock. Keep in mind that if you drop your sea level they can be exposed on the surface.
    Set three will usually, but not always manage to deposit a regular sized deposit of gold high up on mountains. There has to be a mountain high enough there for this to happen. But if there is this set will probably place one there.
    Set four will produce an 'gold ore rich' layer across the entire world (as each setting affects every chunk in the world) it'll place 1-2 gold in the two layers allowed about 5 times per chunk. a single 16x16 layer is 256 blocks in total. So it'll be 1-20 gold in that layer. But it'll be wherever there is stone crossing those layers.
    Because all four different settings were used all four will occur together. Keep that in mind as these four together will produce anywhere from 10-60 gold per chunk. In vanilla there is usually only 2-16. So using all four together can lead to excessive amounts of ores.
    A word of caution. When determining deposit sizes remember to leave room for everything else. Stone, dirt, sand, water, the other deposits, etc. It's easy to go overboard with random settings and overload the chunks. You can essentially overwork and freeze the program with too many deposits and a lot of large deposits as it'll try to fit it all into the single chunk.
    Making ten deposits of 200 blocks of ore per chunk can fill about 15 layers of each and every chunk with that ore.
    Also a lot of deposits attempts will most certainly slow down chunk generation. Expect a great deal of lag and crashes may occur if you set these excessively.

    • /ptm - available commands
    • /ptm reload - reload configuration for your world.
    • /ptm biome - show what biome in your location.
    • /ptm list [page] - List bob plugins for this world
    • /ptm spawn BOBName - Spawn bob to specified place
    More screenshots from setting share thread:

    Show Spoiler







    Known bugs:
    • Above ground objects regen wrong some times. (Mainly trees)
    -fix: bo2 all biome
    -fix: bo2 half spawn
    - Added grow from sapling
    - Added spawn command.
    - Added DefaultSettings.ini on start
    - Added Default BOBPlugins folder on start
    - Added BOB list command for world
    - Fix custom objects biomes.
    - Fix dungeon settings.
    - Add check command.
    - Add waterBlock settings - block id of sea water.
    - Add ceilingBedrock settings - bedrock on top layer.
    - Add disableNotchHeightControl - when enabled terrain generate on full map,
    without height factor.
    - Add CustomHeightControl - list of custom height factor, 17 double entries, each entire control of 7 blocks height from down. Positive entry - better chance of spawn blocks, negative - smaller.
    - Forgot to add copying from old folders to new, sorry.
    - Add reload and biome commands.
    - Better replacement, some fix with plugin init.
    - Fix underground lakes.
    - Remove oldgen.
    - Fix flowing bug.
    - Fix replacement.
    - Some code clean up.
    - Fix regen and may be wrong generation after restart.
    - Convert older bukkit version to be a plugin.
    External links:
    Original authors: R-T-B, Bucyrus

    Bukkit version author: Khorn
  2. Offline


    This is a known bug in 1.8 minecraft and has nothing to do with the PTM plugin. :)

    Hit the grass with bonemeal and you should get some red flowers to generate.
  3. Offline


    Nope it is my bug :p

    Logs logs logs ..

    Search in this thread ... it was here

    I create new name for this plugin - "Terrain control"
    Waiting for approval ...
    Also i want to migrate dev.bukkit project forums from this thread ...
  4. Offline


    No, seriously, look at the known bugs page for Minecraft, it's right there!
  5. Offline


    Nope ...
            genYFlower = new WorldGenFlowers(;
            genRFlower = new WorldGenFlowers(;
    It is my code ...
  6. anyone has a schematic to bo2 converter ?
    i've tried the link on minecaft forums, but the author seems to have disappear and his site is down ..

    thx :)
  7. Offline


    Here is a PTM config that will generate a Skyland. I modified the diamond occurrance so it would happen higher up as there is literally no land below 24, where diamond commonly drops.

    Attached Files:

  8. Offline


    A dev version of Bukkit is avaliable for 1.9 pre 5. Any chance of seeing a compatible version ?
    So we can prepare our map for release ?
  9. Offline


    Well I'm having a problem while using PTM within "MyWorlds" multiworld plugin.

    here is a error report I get when I try to create a world using PTM :

    [INFO] Trakaan [/] logged in with entity id 1338 at ([gen2] -141.75, 66.0, 253.21875)
    2011-10-31 15:10:31 [INFO] [MyWorlds] Trakaan Issued a world creation command for world: Gen3
    2011-10-31 15:10:31 [INFO] [MyWorlds] Loading or creating world: 'Gen3' using seed -7477158563732212164 and chunk generator: 'PhoenixTerrainMod:'
    2011-10-31 15:10:31 [INFO] PhoenixTerrainMod: settings for 'Gen3' loaded
    2011-10-31 15:10:31 [INFO] PhoenixTerrainMod: enabled for 'Gen3'
    2011-10-31 15:10:31 [INFO] New max size: 1764
    2011-10-31 15:10:31 [INFO] New max size: 5476
    2011-10-31 15:10:31 [INFO] New max size: 18496
    2011-10-31 15:10:32 [INFO] New max size: 19044
    2011-10-31 15:10:32 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'world' in plugin My Worlds v1.13
        at org.bukkit.command.PluginCommand.execute(
        at org.bukkit.command.SimpleCommandMap.dispatch(
        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
        at net.minecraft.server.NetServerHandler.handleCommand(
        at net.minecraft.server.NetServerHandler.a(
        at net.minecraft.server.Packet3Chat.a(
        at net.minecraft.server.NetworkManager.b(
        at net.minecraft.server.NetServerHandler.a(
        at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
        at net.minecraft.server.MinecraftServer.h(
    Caused by: java.lang.NoClassDefFoundError: net/minecraft/server/NoiseGeneratorOctaves2
        at com.Khorn.PTMBukkit.Generator.BiomeManagerPTM.<init>(
        at com.Khorn.PTMBukkit.PTMPlugin.WorldInit(
        at com.Khorn.PTMBukkit.Generator.ChunkProviderPTM.getFixedSpawnLocation(
        at net.minecraft.server.World.c(
        at net.minecraft.server.World.<init>(
        at net.minecraft.server.WorldServer.<init>(
        at org.bukkit.craftbukkit.CraftServer.createWorld(
        at org.bukkit.command.PluginCommand.execute(
        ... 12 more
    Caused by: java.lang.ClassNotFoundException: net.minecraft.server.NoiseGeneratorOctaves2
        at$ Source)
        at Method)
        at Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        ... 22 more
    What I'm wanting to do when it will work :
    - a skyland (with big islands if possible)
    - a underground map only (like normal underground but 128 height with bigger caves)
    - a ice/snow world.

    go here to check the full post about this problem on minecraftforum :
  10. Offline


    Download last version from here
  11. Offline


    thank you a lot it was in fact the problem.
    Ps: can anyone give me clues about how to config a world similar to the old skylands ?
  12. Offline


    I posted a worlds file which will do nearly exactly that - look back to my previous posts in this thread.
  13. Offline


    Anyone knows how I can add ore's from IdustrialCraft and Buildcraft?
  14. Offline


    it works !!!

    I'm just curious. What did you change in the config ? I can't find what makes this config work where mine was only doing "simple" floating islands.

    By the way, as I said I will need other generation settings : a nether like world (no idea how to do that), and I find a way to have a full underground world but is there a simple way to have big caves ?
  15. Offline


  16. Offline


    I have no idea, I'd have to look at what you created. My settings are cribbed from an example Khorn created a few pages back - I kept tweaking it until it worked. Two significant things I did was greatly increase the occurrance of ExtremeHills and set oceans to zero. In addition, I tweaked the fill so that the islands would be taller.
    Good luck! :)

    I haven't messed with nether worlds yet.

    I've played a bit with cave generation - I would massively increase the occurance of random clusters of caves as well as make the existing cave networks larger. Also, stretch your ravines so they're longer and taller.
  17. Offline


    Use replace or wait next version ..
  18. Offline


    Having trouble with install. When I change the bukkit.yml file to include a world and boot up the server I don't get a new world ini file generated. the worlds directory is still empty. ideas what I could be doing wrong?
  19. Offline


    Working fine here; enjoying it immensely.

    Among the biomes in BiomeConfigs/*.ini are 'Hell', 'River' and 'Ocean'. The 'biomeChance:0' suggests that these biomes won't come up normally during generation, which is true for the 'Hell' biome, but 'Ocean' and 'River' biomes still get inserted. I tested by changing the 'SurfaceBlock' of the ocean biome to wool and lower the water level to 8m. I get huge valleys and plains of wool, but I was expecting not to see any ocean biome terrain at all. In 'PhoenixTerrainModSettings.ini' I see a setting for "riversEnabled:true" -- is there a setting where I can set something like "oceansEnabled:false" ?

    While I'm here: we need more documentation. There are plenty of settings in the BiomeConfigs/*.ini files that still have no description. The format for the BOBPlugins/*.bob and BOBPlugins/*.bo2 files are obvious, but could still use some documentation, along with description of the "<BOB Objects Variables>" settings.
  20. Offline


    Since this plugin doesn't come with documentation, and reading 30+ pages of forum messages is such a chore, I'm writing an article for PhoenixTerrainMod on the bukkit wiki. It's easier to use 'living document' format like a wiki article than to wait for a forum header post to be updated.

    I will include SteelCrow's explanations of what he (she?) found out about configuration files, but I will reformat her (his?) documentation to match the format of the 0.9.6 config files.
    Tanite likes this.
  21. Offline


    Oh man ... i will not use old name " PhoenixTerrainMod" in next version
    Matt is out and he did not give me any control of this thread and dev.bukkit plugin page ..

    So new will be - TerrainControl
    Also i make big changes in resource section and trying explain this setting in configs files ..
    I hope i will make beta release this night.

    New version is out and now it is TerrainControl
    I will read this thread too but priority is this

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 18, 2016
  22. Offline


    Whelp. (╯°□°)╯︵ ʞɹoʍ
    I'll collect what I can and put it over there instead. If nothing else, expect a big heap of *.bo2 files from me. The *.shemata -to- *.bob thing is nice, but good luck finding schematic collections that aren't huge grandiose constructions. I have a collection of 140+ smaller objects more appropriate for random spawning in the landscape.
  23. Offline


    Oh 140 objects :confused: ..
    You have that as schematic ?
  24. Offline


    Am i right in thinking that this will generate the same world with the default settings as notches code?
  25. Offline


    Are we to use the same PTM folder or do we now need to make a separate one for TC?

    Also, is it used in the same manner as PTM?
  26. Offline



    Nope ... new folder name - TerrainControl
    Yes same manner except default settings.. they are removed
  27. Offline


    I want to be in the center of my world had no ores. And to the amount of ore increased when increasing the distance from the center. Or vice versa.
    Any ideas with TC?
  28. Offline


    Hmm only by hands .. like spawn with one settings .. use some pre generate plugin for create area with that settings.
    Change settings and create new area ...

    I may add this feature but not now :(
    Hwo likes this.
  29. Offline


    So i should to generate world 160x160 with settings1
    than 320x320 with settings2
    1600x1600 with settings10

    or better generate from 1600 to 160

    How to do it without overwriting / deleting world from prev step?

    Is there a global ore rarity and frequency settings? Or i need change settings for each biome?
  30. Offline


    Lets say I want to create a world that is ENTIRELY out of water. Something like atlantis. With mini glass domes on the bottom of the world, with glowstone in em. So mainly like water domes with glowstone. You can probably imagine this. Mini sand mountains, and some seaweed if possible? So its like water covered earth, and mini small towns of people live in domes underwater to survive from being drowned. The water goes up indefinetely. and i want a portal from that world to the main world. So far, I have multiverse core, portals, and netherportals. Please explain the steps, HOW, or even send me a map file and i'll use that instead.
  31. Offline


    Hello everyone. Original author of PTM RTB here. I'm glad someone has been maintaining this. The original source code is available somewhere I assume? I'd love to compare it to my old SSP/SMP code to see if I can bring a version up to par and make them both compatible as much as humanly possible.

    If you don't want to share that's ok. The original source was GPL'd technically but you've done so much work I won't dare hold you to that. Just some spec sharing in that case would be nice.

    Forgive me if you posted it somewhere, currently on my cell phone and didn't see it.

Share This Page