Collective 2.60 requiring client-side installation
McManning opened this issue ยท 1 comments
Information
Minecraft version: 1.12.2
Forge version: 14.23.5.2855
Environment: Multiplayer
Mod name: Collective
Mod version: 2.60
Description
I'm looking to test Tree Harvester on a server. From reading issue #511 it seemed like I didn't need to force clients to install any additional mods to get it working, but the Collective dependency seems to be dependent on a clientside install as well. Is there something I may be misconfiguring / overlooking on my end?
Crash report
Mod rejection info:
[12:41:13] [Netty Server IO #1/INFO] [FML]: Client protocol version 2
[12:41:13] [Netty Server IO #1/INFO] [FML]: Client attempting to join with 14 mods : [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected]
[12:41:13] [Netty Server IO #1/INFO] [FML]: Attempting connection with missing mods [movillages, collective, fastleafdecay, pixelrustles, treeharvester, vanilladeathchest] at CLIENT
[12:41:13] [Netty Server IO #1/INFO] [FML]: Rejecting connection CLIENT: Collective: Requires version 2.60 but mod is not found on client.
[12:41:13] [Netty Server IO #1/ERROR] [FML]: Network Disconnect: Server Mod rejections:
Collective: Requires version 2.60 but mod is not found on client.
Thanks for submitting the issue and giving the mod a try! All my 1.12 mods have ', acceptableRemoteVersions = "*"' header in Main.java, but I forgot to add this in Collective itself. I've fixed it in version 2.62 of the mod.
https://www.curseforge.com/minecraft/mc-mods/collective/files