BlueMap causes clients to think they need it locally.
Graftax opened this issue · 3 comments
What i did / Steps to reproduce
- Read the BlueMap CurseForge page and note that it says "This is a SERVER-ONLY mod!".
- Shut down server and add BlueMap-1.5.5-forge-1.16.4.jar to the server mods folder, then start it again.
- Open Minecraft and note the red "X" in the server selection menu indicating that mods are out of sync.
- Open logs/latest.log and note the line: "Server has additional mods that may be needed on the client: [email protected]".
Expected result
Client is not warned about mod sync when BlueMap is present on the server.
Actual result
Clients are warned that they may be out of sync when selecting the server.
Context
BlueMap-1.5.5-forge-1.16.4
Linux/Forge 36.2.0
Had BlueMap-1.6.0-forge-1.16.4 installed and downgraded to 1.5.5. Clients are still able to connect, but the sync issue causes them to report it as a problem to me, repeatedly.
A minor problem, hopefully the fix is as easy as updating acceptableRemoteVersions.
A minor problem, hopefully the fix is as easy as updating
acceptableRemoteVersions.
From Forge Documentation:
//Make sure the mod being absent on the other network side does not cause the client to display the server as incompatible
ModLoadingContext.get().registerExtensionPoint(ExtensionPoint.DISPLAYTEST, () -> Pair.of(() -> FMLNetworkConstants.IGNORESERVERONLY, (a, b) -> true));```