订阅以下载
Docworld Vanilla Props Expended Continued

Please update to 1.4

Thank you Wololo, Just wanted to make sure it wasn't going to affect anything.

I have the same message. it's because I copied the mod locally with fluffy mod manager. it has no influence but yes you can always change the name yourself.

Package Id has _copy in the id. So it comes up as wololo.docpropsfonctional_copy. I use RimPy so I understand it is the mod loader flaging it as a warning. I didn't know if it would break the mod if i changed the PackageID to wololo.docpropsfonctional from wololo.docpropsfonctional_copy

@Rime Pendragon Update Done.

OK, thanks.

@Rime Pendragon I don't play rimworld anymore due to a hardware problem and I don't have the courage to reinstall my stable 400 mod setup for the moment.

I will try to find a solution later but in the meantime, use the version from Mile.

This mod causes a conflict with Vanilla Base Generation Expanded. Here is the log:
https://gist.github.com/HugsLibRecordKeeper/c16894bebbf4c552c892cc1c0dd1cd0d

The mod author of Vanilla Base Generation Expanded says: "The other mod isn't patching the right way. They are removing the VE definition to add their own, causing the issue."

Because its a Mile's Resurrected Mod Its most likely Mile's Jurisdiction rn. (Respected Mod)

(Possibly) Not compatible with "Functional Vanilla Props" by Primus the Conquer which does the same thing your mod does.