Hi,

When using the ReplaceToBiomeName option in custom biomes on a forge server, the client sees the biomes as being "plains". The problem only occurs when using forge. When using the same configuration files in Bukkit, the client sees the correct biome names.

The version of TC used is v2.6.1. The version of forge is 10.12.1.1060 (Minecraft 1.7.2).

I've tried running a client with TC installed as well, but this made no difference.

I've tried this with inheriting and non-inheriting custom biomes and custom biomes with ids below and above 256. When using an id above 256, TC does not give an error about there not being a "ReplaceToBiomeName" option, suggesting that is does recognise the option.

If I've missed some important detail or if you need more information, let me know.

EDIT: Here is a configuration with one custom biome that has the mentioned problems:
WorldConfig.ini
http://pastebin.com/RidauEWf
ForestMod.ini
http://pastebin.com/10Ykwuez

KPW

Thanks, I will look into it. If I understand it correctly, the steps to reproduce are as follows:

• Create a new world with the default settings.
• Create a custom biome, let it spawn in the world.
• Give the custom biome a value for ReplaceToBiomeName.
• On a Forge server, the Forge client now sees the biome as Plains, regardless of the actual value of ReplaceToBiomeName.
• On a Bukkit server, it still works correctly.

That is correct, those steps will cause the problem to appear here.

Thanks for fixing this so fast!

Actually, I'm testing it now using the latest build server build, and the problem is still present here. I completely removed the world and created new TC config files just to be sure, ReplaceToBiomeName still doesn't work.

Should now be fixed, thanks for reporting!

Download at the build server

That's strange, for me it is now showing Taiga correctly on my biome ReplacedBlocks in my test world.

I did a clean install of forge (still the same version) and tried it again. Using your test world, ReplacedBlocks is seen as a patchwork of small random biomes (I saw ocean, deep ocean, river, mesa, forest, and more... each of them a few blocks large). Using my test world, the ForestMod biome is seen as plains.

I'm pretty sure I downloaded the correct jar (#16 http://mctcp.com:8900/job/TerrainControl%20-%20Master%20-%20Gradle/default/lastStableBuild/), although forge identifies TC as version 2.6.0 (is this related to the "Mod TerrainControl is missing the required element 'version' and a version.properties file could not be found. Falling back to metadata version 2.6.0" notice?).

Second try. I used existing world save files (first I tested on Bukkit, then on Forge), so the bug was hidden for me. The biome ids were incorrect in the save file if it was generated by Forge, so the Forge client couldn't display it correctly.

I again did a clean forge install (same version), and installed TC build #17.

Using your test world I get the following crash report: http://pastebin.com/LmJtkdjJ.

Using my test world TC doesn't crash, and the ForestMod biome seems to be mostly correctly labeled, however, all the other (default) biomes are incorrect, consisting of small patches of other biomes (I saw plains, savanna, savanna hills, ocean, beach, and more...).
When not using ReplaceToBiomeName, the ForestMod biome is also incorrectly tagged.

21b348b

I should remember: always upload the latest changes. Sorry for all this trouble...

TerrainControl build 19 now works with your and mine testworld. However, the server now crashes if I change IsleInBiome in ForestHills.bc:

IsleInBiome: Forest, ForestMod

This crash only happens when I use ReplaceToBiomeName in ForestMod.bc. As far as I can remember it did not happen before this issue was closed.

The following crash report is produced:
http://pastebin.com/rTjnzWMX