What the frick is this biome? It looks horribly, gamebreakingly broken. If you walk on it, you instantly die, all items dropped on it also insta-disappear [so gravestones are useless], block-inspection also gives the raw block ID name, and half of the textures don't even load.
WTF is this?
- Thread starter Anhrak
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Well, despite the glitchiness, it's definitely more than a glitch. Which pack are you playing? It has likely been added by one of the mods you have installed.
EDIT: It seems to be a Thaumic Horizons biome, but it shouldn't be appearing in the Overworld AFAIK, so you probably have a biome ID conflict or something.
EDIT: It seems to be a Thaumic Horizons biome, but it shouldn't be appearing in the Overworld AFAIK, so you probably have a biome ID conflict or something.
Stock FTB Infinity 1.8.2 has a biome ID conflict between Thaumic Horizons and BoP. There are two solutions:
Thus, to fix your world while keeping Thaumic Horizons, you would have to change BoP biome ID 69 to a free ID, use a tool to search your entire world file for biome ID 69 and replace it with the free ID you selected, and then use a tool to erase any chunks that generated with the Pocket Plane blocks so that they will regenerate.
If you want to fix your world and disable Thaumic Horizons, you can skip the step involving biome IDs and just erase the chunks with Pocket Plane blocks. Or just load a world backup.
- Open the BoP config, find the biome using ID 69 and reassign it to an unused ID.
- Disable Thaumic Horizons.
Thus, to fix your world while keeping Thaumic Horizons, you would have to change BoP biome ID 69 to a free ID, use a tool to search your entire world file for biome ID 69 and replace it with the free ID you selected, and then use a tool to erase any chunks that generated with the Pocket Plane blocks so that they will regenerate.
If you want to fix your world and disable Thaumic Horizons, you can skip the step involving biome IDs and just erase the chunks with Pocket Plane blocks. Or just load a world backup.
Was this fixed in version 1.9.0 of Infinity? I didn't see anything about it in the changelog... I'm not literate enough about changing configs to feel brave enough to make the change myself, so I'll probably just not play until it gets fixed. Don't want to find my base destroyed because of this.
just checked lush swamp is still set to use biome id 69 so looks like thats a no
You can do a biome ID dump with NEI in order to find a free ID to use. However, if you have any Lush Swamp generated in your world, you'll need a tool to go into the files and overwrite all occurrences of biome ID 69 to whichever ID you reassigned it to. I'm pretty sure that MCEdit can let you change biomes, but I don't know if it has a command for remapping IDs across an entire save.
Alternatively you can stay on Infinity 1.7, or update to Infinity 1.8 but disable Thaumic Horizons (which is newly added to the pack, so you won't lose anything in an existing world by disabling it).
The main issue with reassigning IDs is that if another update corrects the IDs, or assigns a new biome to the free ID that you reassigned the biome to, you'll have to repeat the process of editing your save.
TBH I think it was a mistake to add Thaumic Horizons to Infinity. I'd have only done it with Unstable (where worlds aren't meant to survive between versions anyways), new packs (where the IDs could be properly assigned without conflicts), and packs where biome ID 69 is free (and thus adding Thaumic Horizons doesn't introduce a conflict), due to the fact that you can't reassign biome IDs in an existing pack without breaking existing worlds. I would recommend less technical users to disable Thaumic Horizons until its developer adds a config file and the FTB team corrects the conflict.
Well, that would depend on whether it was near your base or not. Each region file corresponds to a 512x512 area (32x32 chunks) so if the affected area were in a different region from your base you could delete the region file corresponding to the area that was messed up and it would regenerate the next time you loaded the world and went there. If your base is in the same region, then deleting the region would delete your base. Alternatively, you could theoretically open up a region file and only delete the afflicted chunks, but that takes a bit more work and requires programs like MCEdit, whereas for deleting an entire region you can just open the save directory and delete the region file.
Assuming the coordinates on your JourneyMap display are accurate, unfortunately the biome seems to be generated on a corner where four regions intersect, so you will need to delete four regions.
Assuming that this is the Overworld, find your saves directory, open the save, find the folder named 'region', open it, and delete the following regions:
This will wipe out a 1024x1024 block area around the affected area. This essentially means anything that you build, gravestones, mobs and animals, terrain, etc. are erased. When you return to these areas, the terrain and animals will be regenerated. Most generation should be the same as it was originally since it is generated from your world seed. Only worldgen that does not use the world seed will change - this will probably just be certain random features from a few mods. And, of course, the area that generated improperly due to the biome ID conflict will generate as it was supposed to with the proper biome (assuming that you corrected the conflict - if you didn't change BoP's config or disable Thaumic Horizons, the broken biome will just generate again).
If you don't want to delete such a large area, open up MCEdit and just delete the affected chunks.
Once you've modified your save and deleted the affected areas, open it up again in Minecraft. Check to make sure that the area has indeed been regenerated properly, along with checking that all of your creations are intact.
Assuming that this is the Overworld, find your saves directory, open the save, find the folder named 'region', open it, and delete the following regions:
- r.-4.-1.mca
- r.-4.0.mca
- r.-3.-1.mca
- r.-3.0.mca
This will wipe out a 1024x1024 block area around the affected area. This essentially means anything that you build, gravestones, mobs and animals, terrain, etc. are erased. When you return to these areas, the terrain and animals will be regenerated. Most generation should be the same as it was originally since it is generated from your world seed. Only worldgen that does not use the world seed will change - this will probably just be certain random features from a few mods. And, of course, the area that generated improperly due to the biome ID conflict will generate as it was supposed to with the proper biome (assuming that you corrected the conflict - if you didn't change BoP's config or disable Thaumic Horizons, the broken biome will just generate again).
If you don't want to delete such a large area, open up MCEdit and just delete the affected chunks.
Once you've modified your save and deleted the affected areas, open it up again in Minecraft. Check to make sure that the area has indeed been regenerated properly, along with checking that all of your creations are intact.
BoP has had Biome ID conflicts since Infinity was launched. Particularly, Twilight Forest biomes generate in the Overworld. This "Dimensional Bleed" has been reported since the first week of launch, but it has never been addressed, to my knowledge (note that our server is several versions behind at this point, but I've not seen anything in the change logs about it).
It's a shame things like this don't get fixed in testing before the pack is live. The majority of people either don't have the skill or don't have the will to fix it themselves.
Best of luck on your fix. Remember to back up everything. Make backups of your backups. Never can be too sure when you're playing God.
It's a shame things like this don't get fixed in testing before the pack is live. The majority of people either don't have the skill or don't have the will to fix it themselves.
Best of luck on your fix. Remember to back up everything. Make backups of your backups. Never can be too sure when you're playing God.
It isn't that simple to fix. Because of the new vanilla biomes in 1.7 it gives less biome ids for mods and since Biomes O' Plenty takes up most of them it leaves little room for dimensions.
It isn't intentional. Look in the ids config and you'll see that it conflicts with the Lush Swamp biome.
It doesn't mean that the Lush Swamps are replaced. When two biomes share an id they both have a chance to spawn
I've seen a couple of the Twilight Forest biomes in my Overworld as well. However, it is less blatant than a biome full of end portal texture blocks that inflict void damage when you touch them.
It's not too bad as long as you can account for all mod-added biomes when doling out the IDs, you don't have more than the maximum number of biomes, and preferably that all biome-adding mods have a config file. The main issue here with 1.8 is that the newly-added Thaumic Horizons cannot be configured and its biome conflicts with an existing biome in the pack, meaning that to rectify the conflict, the other mod's config would need to be changed, which would render existing worlds semi-broken.
Lush Swamp was okay in 1.6 and 1.7. When updating to 1.8, any areas already generated will see their biome name change (since a different biome is overriding the ID) but the terrain will remain that of the original (correct) biome that was previously generated. Any newly generated areas will be broken, though.
I think Forge should add a warning that appears on the title screen when there's an ID conflict that doesn't outright crash the game (e.g. biome ID conflict). That way you know right away that something is not right rather than having to catch a possible warning message buried in the console.
I guess that means I won't have to patch my world's biome IDs with the Python program I wrote.