Closed fira closed 5 years ago
I got intrigued and Galacticraft Wiki said it worked with earlier versions, so I got digging by testing with different versions... And indeed, it works with Forge 2705 and Sponge 7.1.0-BETA-3361 Looks like a regression in either Forge or SpongeForge, i'm going to try to find the affecting change...
Works with 2705 / 7.1.0-BETA-3475 I'm guessing there was an incompatibility when moving from Forge 2705 to Forge 2768 ? Could be related to the change in Forge 2717 rewriting Dimension Manager, the associated Pull Request (4902) in Forge : https://github.com/MinecraftForge/MinecraftForge/pull/4902/files
We did go about resetting a lot of configs when this occurred for #2499, so I could see how DIM IDs are related if theyre saved locally or something to make them out of sync.
Re-tested with latest SF 3540 and GC 4.0.2.190 (latest) and it seems to connect fine going between planets. If there's still an issue, please provide a description how it's being reproduced and with which builds.
I am currently running
SMP install running MC 1.12.2
Server:
Client:
Plugins/Mods:
Issue Description We're running a Custom Modpack and I recently migrated server and added in SpongeForge and plugins among other things. It took days and days to troubleshoot before finding out by isolating the mods and setup on another server and digging in various mods source, but by all accounts it seems that Enabling SpongeForge on Server side breaks the way the Client is made aware of Dim Providers
I'm not sure why exactly, but I've noticed this causes the following behaviour:
Relevant ClientLog :
Nothing seems to go wrong on Server Side. But Clients just don't apparently get the required information to run net.minecraftforge.common.DimensionManager.getProviderType I have no clue why this is the case, but it's quite a show-stopper for some mods :-/