Issues on Sponge server with ProjectWorld and Mekanism
NicolasNewman opened this issue ยท 4 comments
I've tried testing this mod on my SpongeForge server and it works for nether, end, and Mekanism teleporters in the same world. However, once I try using a Mekanism teleporter in two different survival worlds managed by ProjectWorlds, the portal appears black and nothing happens when I go thorugh it.
Forge is version 1.12.2-14.23.5.2821
Sponge is 7.1.7 RC3925
ProjectWorlds is 7.2.0-0.13.1
BetterPortals is 0.3.6
Around the time I create and test a portal I see the following in the client log and nothing of interest in the server log:
17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@515091
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@52de2f89
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@5ad69abf
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@61e6820d
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@6b398378
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@48384bf1
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@2655332b
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@73f63b06
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@54734443
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@5e1eeaff
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraft.network.play.client.CPacketConfirmTeleport@51dd467c
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraft.network.play.client.CPacketPlayer$PositionRotation@13b1694a
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@17d19588
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@69384401
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@509b02b4
[17:03:48] [Client thread/WARN] [betterportals/view]: Dropping packet net.minecraftforge.fml.common.network.internal.FMLProxyPacket@5007d1ca
This is repeated many more times over the next two seconds.
Is this specific to Sponge-managed worlds? I.e. does the Mekanism teleporter work fine between vanilla overworld and nether (I don't recall ever testing that tbh)?
I placed a Mekanism portal near a nether portal in a ProjectWorlds world and the nether portal worked but the Mekanism one didn't. I'll have to test it in singleplayer.
I just tested it on the server by putting two teleporters in the same world about 200 blocks apart and it worked. I also tested a Mekanism teleporter in the nether and overworld in singleplayer and that worked as well.
Turns out there are actually two issues here (linked above), both with very similar symptoms.
I've fixed the Sponge custom world one in BP 0.3.7. I've reported details for the other one to Mekanism because I believe it should be fixed over there.
I'll be keeping this issue open until it has been fixed.