Server: Can't revert to frozen GameData state without freezing first.

Issue #55 resolved
Former user created an issue

When i start my Forge minecraft server at first it initializes all mods normally, but when it then tries to initialize binnies-mod the server freezes.

the FML log:

[03:00:35] [Server thread/TRACE] [BinnieCore/BinnieCore]: Sending event FMLPostInitializationEvent to mod BinnieCore
[03:00:35] [Server thread/TRACE] [BinnieCore/BinnieCore]: Sent event FMLPostInitializationEvent to mod BinnieCore

[03:00:35] [Server thread/TRACE] [Botany/Botany]: Sending event FMLPostInitializationEvent to mod Botany
[03:00:35] [Server thread/TRACE] [Botany/Botany]: Sent event FMLPostInitializationEvent to mod Botany

[03:00:35] [Server thread/TRACE] [ExtraBees/ExtraBees]: Sending event FMLPostInitializationEvent to mod ExtraBees
[03:00:35] [Server thread/INFO] [FML/]: Trying to implement forestry hive fx...
[03:00:35] [Server thread/INFO] [FML/]: Failed: forestry.apiculture.ProxyApiculture
[03:00:35] [Server thread/WARN] [FML/]: Couldn't find vanilla template - forestry.speciesFestive
[03:00:35] [Server thread/INFO] [FML/]: Added 93 species, out of a total of 122
[03:00:35] [Server thread/TRACE] [ExtraBees/]: Sent event FMLPostInitializationEvent to mod ExtraBees

[03:00:35] [Server thread/TRACE] [ExtraTrees/ExtraTrees]: Sending event FMLPostInitializationEvent to mod ExtraTrees
[03:00:56] [Server thread/TRACE] [ExtraTrees/ExtraTrees]: Sent event FMLPostInitializationEvent to mod ExtraTrees

[03:01:20] [Server thread/WARN] [FML/Genetics]: Can't revert to frozen GameData state without freezing first.
[03:01:24] [Server thread/INFO] [FML/Genetics]: Applying holder lookups
[03:01:36] [Server thread/INFO] [FML/Genetics]: Holder lookups applied

when i remove the binnie-mod jar from the mod folder the server runs without issues, so i believe the fault lies here.

Comments (2)

  1. Gerbert Meinz

    allocating more memory to the server seems to have fixed it, sorry for wasting your time... (just made a account to tell you)

  2. Log in to comment