Thats why you should always do a backup of your configs
.Also sbreens configs are from an earlier version and I noticed that the FTB team added, removed and changed some config values in those files
FTB Monster crash when arriving at moon/mars
- Thread starter danielcb114
- Start date
.Also sbreens configs are from an earlier version and I noticed that the FTB team added, removed and changed some config values in those files
Fat lotta good that does, tried that before, screwed up mods that had changes done. have always had to do manual re-configs of the config files since Monster 1.0.2 (first one we learned and started out with was 1.0.1 cuz we are slow to get updated news.)
TL;DR: What is the safe way to keep config changes across updates on the server side since launcher does auto config updates. (Used to steal config and mod files from server after we manually configured server.)
TL;DR: What is the safe way to keep config changes across updates on the server side since launcher does auto config updates. (Used to steal config and mod files from server after we manually configured server.)
Gah! I'm an idgit! How simple is that? I use Linux, but there is a file compare program that I could use to do the exact same thing! Thanks very much, I know it might seem like a silly little thing to you, but sometimes I don't think of little things like that and you helped me out a lot. Thanks again for the help!
I am currently testing the ore generation on overworld by adding the galacticraft ores to the CoFH ore gen. If it works nicely ill place the config I used.
Any luck? I'm still getting Gascraft relates server crashes. If so please post config files, would be helpful for us. Thanks in advance.
Description: Exception in server tick loop
java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:897)
at java.util.HashMap$KeyIterator.next(HashMap.java:928)
at mekanism.api.transmitters.DynamicNetwork.tick(DynamicNetwork.java:115)
at mekanism.api.gas.GasNetwork.tick(GasNetwork.java:117)
at mekanism.api.transmitters.TransmitterNetworkRegistry.tickEnd(TransmitterNetworkRegistry.java:87)
at cpw.mods.fml.common.SingleIntervalHandler.tickEnd(SingleIntervalHandler.java:34)
at cpw.mods.fml.common.FMLCommonHandler.tickEnd(FMLCommonHandler.java:141)
at cpw.mods.fml.common.FMLCommonHandler.onPostServerTick(FMLCommonHandler.java:274)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:622)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:484)
at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:583)
These are the current configs that I use haven't had success with the ore gen though. Got a QuarryPlus running on max size to see how it worked out
PS. If it still crashes look in the FTB Client console when you are arriving at the moon.
If you see the console getting spammed with "[GasCraft] Error generating resorces for chunk @. "
Then its the bedrock issue.
PS. If it still crashes look in the FTB Client console when you are arriving at the moon.
If you see the console getting spammed with "[GasCraft] Error generating resorces for chunk @. "
Then its the bedrock issue.
Last edited:
Thanks much, I'll look at the server and the client. I have players now on the moon, but it seem only when new chunks of the moon are generated.
Yeah 'fraid so with the same "Gascraft error" as before. As I said before,it seems to happen when someone generates new chunks on the moon when exploring.
Ah frick, I thought it wouldn't generate after changing the configs file. We have players that have made bases on the moon already, is there anything that can be done w/o moon reset? I'm pretty sure that we may have to reset the moon Dim, but was wondering if there might be ANYWAY around this oversight of mine.
Look in the configs for the cofh/cofhworld.cfg. in there look for B:RetroactiveFlatBedrock=false
And set it to true.
Restart the server and test it out. Cant besure that this works. If not try deleting the dimension. Make sure you back it up first though. If it doesnt work you can atleast restore it.
Kewl. Did backup the current moon and re-generated it anyways. New moon seems to be holding strong, and had a talk with other players and so long as the overworld isn't lost then they were willing to start fresh. So thank you very much and we are testing this new config with the old moon and will letcha know if it goes well and stops crashing.