Rimworld is allergic to its own DLC

[johnyoga]

I have no mods running.

Tried starting DLC and the game is giving me error messages.

Rimworld is allergic to its own DLC.

[Tynan]

Sorry, there are so many mod config errors that the log cuts off before any other errors are displayed.

Tons of your mods don't seem to support 1.1, so if you unsubscribe from those ones it may clear out the log so we can take a look.

Also you can just post the log file directly; it's a lot easier to handle than copypasting into a Word document!

Moving this to support.

[johnyoga]

Hello Tynan,

I have attached the log file.

All mods were/are unchecked. Why is the game seeing anything as active?

Maybe just fix this issue? 

Marc

[Tynan]

Hi john,

That log file is from RimWorld alpha 18; circa 2017. Do you have an updated log file?

The game isn't seeing the mods as active; it's just reading the metadata on startup so it can show you their names, descriptions, authors, etc. It seems you have a huge number of incompatible mods installed and you could probably fix your issues by clearing the mod list entirely and starting over.

[johnyoga]

Hello Tynan,

The issue now manifests in a different way...

I deleted all the mods, as you had asked from my Workshop. Then, I built them up, all 1.1.

The game worked fine. Closed it, used it the next day, it worked fine. Today, I open it up, with no changes I made/didn't touch any dials/added no additional mods, and I get the attached error issues.

Also, I go to the prescribed folder location, and I only see that output log dated 3/13/2018. If there is another log file location, please direct me to it.

For some odd reason, the DLC is not consistent in how it grabs mods, and checks some of those that were never checked.

[Canute]

If there is another log file location, please direct me to it.

The logfile location is currently a mess.
At the option you got a button "Open log file folder" try this.
You should maybe see Player.log and Player-prev.log.

[johnyoga]

Thank you, Canute!

The Player and Player Prev are attached.

Regards,

Marc

[Canute]

johnyoga,
the log is full of old mods, didn't you said "I deleted all the mods, as you had asked from my Workshop" ?
If you take a look at the log itself all these
"Mod Draggable Corners is missing packageId "
are from 1.0 mods because the packageId got include with 1.1

Later CameraPlus is giving out an error.

So again
unsubscribe from all 1.0 only mods from the workshop.
Delete all 1.0 only mods from your mods folder
Even when you don't activate them, Rimworld still browser through them which increase the loading time.
Deactivate all mods ingame.
Slowly build up your modlist, with 5-10 mods.
Check the ingame log window if any error (red text) show up.
Don't use a mod that throw out errors, look at the mod discussion,ask the mod author about it.

And when after this still a problem appear with the DLC, you can report it.

[johnyoga]

That is correct, all old mods were unsubscribed from the workshop.

I also deleted all old save mod lists like "Marc's Mod List 1, 2..."

I do have mods on my C drive, but, they were unchecked as I have always stated.

I know I am repeating myself: The game worked fine with the new mods loaded - fresh from scratch (1.1)...the new game worked once, twice, but then when I went to play a third time, magically it must have turned on the mods from my C drive (out of nowhere) and now shows those error messages.

On that slightly different topic: Others are using that particular mod in question for 1.1 with no issues.

The DLC game is, for some odd reason, sporadic in how it looks at mods, and turns on unchecked mods (and they are only in the C drive) at will.

That is a defect that should be fixed.

For now, I will find that C drive mod file location that has collected dust over the years with no issues, and delete what is in there, too.

Marc

[Canute]

There is only one spot Rimworld look for local mods, it is inside the Rimworld installation the Mods folder.
If you have somewhere else mod files, Rimworld don't care.
I can't realy say how the Workshop mods get handled since i don't use steam.
But when you got some time and wan't a 100% clean install, Manualy delete the Rimworld installation, then let steam reinstall/verify it.
You even should delete the saveddata folder (where you found the logfile) and delete the whole Rimworld from Ludeon folder (unless you want keep some safegames).

Workshop mods are easy for people to use, since they auto. get downloaded and installed.
But they can be a curse too when they get updated and the modauthor made some mistake.

Rimworld and the DLC get updated too (it is still hotfix phase) but that shouldn't break anymore mods like it does at the first days.

So when you geting error's from one day to another it is proll some mod issue.

[johnyoga]

Hello,

What I think is happening is that the DLC gets confused as to what is checked on 1.1 and what is on a person's C drive as a mod; it simply turns it all on.

In any case, I have deleted the C drive mods and I am no longer getting that error message.

Thanks for trying to help, Canute.

Marc