Hi guys,
Been working on a new mod for 1.8. I realize that Forge's 1.8 versions are currently in beta and may have some issues, so I thought I'd report this issue just in case it's not an issue with my code in particular.
I've attempted to research this problem by searching these forums, but the only thing close to my error is highlighted in this particular thread:
http://www.minecraftforge.net/forum/index.php/topic,25702.msg131161.html#msg131161
However, that is due to some generation problems. I am simply attempting to teleport the player to another dimension.
Basically, as mentioned above, I'm attempting to teleport an EntityPlayer instance to another dimension. However, upon teleporting, the game crashes with both a Concurrent Modification error from WorldServer, as well as an "Already decorating" error from the BiomeDecorator class. I've tried all vanilla dimensions, but all attempts result in the same error. I've used this same code prior to 1.8 and have never had these issues until now.
@Override
public void onTravelTo(EntityPlayer player, boolean hasTravelBefore)
{
if (!player.worldObj.isRemote)
{
UniverseCore.teleportToDimension((EntityPlayerMP) player, 0);
}
}
UniverseCore.teleportToDimension() simply refers to this code:
public static void teleportToDimension(EntityPlayerMP player, int dimension)
{
ServerConfigurationManager scm = MinecraftServer.getServer().getConfigurationManager();
scm.transferPlayerToDimension((EntityPlayerMP) player, dimension, UniverseCore.GENERIC_TELEPORTER);
}
This is simply used to prevent vanilla's default Teleporter from generating a Nether portal.
Before this, I've tried using vanilla's method for teleportation: player.travelToDimension(dimensionID), but I receive the exact same errors. This also occurs regardless of what dimension I attempt to travel to. All dimensions are vanilla dimensions as well.
Apologies if I'm simply making a huge mistake somewhere, but I've tried to tackle this issue for the past few days without success. Thanks in advance for any help. You can find the error log for this issue below: