-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Angel's Mod Compatability #114
Comments
I'm not sure what the problem could be. It just reads the mods from the mods folder. Maybe double check and make sure everything is there. |
It works just fine with angelsrefining_0.9.7 but crashes with the same error as soon as angelspetrochem_0.7.4 is added. |
Neither am I :( Hence the ticketing here... It really makes no sense why it works with the 16.16 client, but not with your docker container... I guess I could try a standard headless server to test and see if the same issue is there... If it is then it would have to be an issue with the mod itself. |
@spitefultowel If you post a list of all the mods you are using then I can try and reproduce. I don't play with mods, so I start with a clean mods directory. I downloaded the following: That must not be sufficient because you have a lot more things loading there. Give me a specific list and I'm happy to try it out. I don't want to try and reverse engineer it from your output however. |
bplein, I actually reduced all loaded mods to just the angels stuff which were causing issues. List from my PC (not the docker container) is below.
|
So are you saying that only angels is required to reproduce? I can ignore and not download rso, bobs, "Squeak" and FARL? What is in the mods directory on the docker container? That's where you are having the problem. Showing the list from another location doesn't do any good if they aren't the same. |
@bplein it's the same list of mods, but with just angel's petro (which requires angel's refining) I can reproduce. Angel's refining by itself doesn't cause issues (which is why I believe it may just be a mod issue. |
@spitefultowel I just ran into this; and it turns out this is a simple configuration error. The issue happens because of the default map-gen-settings.json that the container tries to use:
Note the autoplace_controls property, and how it has a "copper-ore" setting. This is the setting that the game is choking on. Angel refining disables all stock ores aside from coal, and the map generator complains when you try to set up ore spawning for an ore it does not understand. The issue should always occur if you have angels refining installed and active. I reproduced this issue using only angels refining and a splattering of bobs. Are you certain you dont see the issue with refining? That might be an indication that refining is not loading normally. Check your mod-list and make sure it is enabled. To fix this and get the mod running on the server, you need to set up a map-gen-settings.json file with the correct autoplace settings for the ores that angels expects. For example, I am using this map-gen-settings file
The fix here is that I removed the entries for ores that are no longer present in the game. I also added in entries for angels ores and fissures, but this is not required. Just removing the incorrect ore entries is enough. Adjust the settings to your liking, and place this in whatever directory you volume-mount to the container's /factorio directory. |
@RoboPhred awesome info! Using your config fixed it all. :-) |
I had the same issue today. For me it was enough to remove the values that threw the error so my object looked like this:
|
I tried running the docker container with mods. It runs no issues with Mods but as soon as I activate Angels petro chem, angels refining, and angels smelting it goes into an infinite crash loop. Same mods run with no issues on 16.16 client.
The text was updated successfully, but these errors were encountered: