11 Replies
>debug
We need more information to help you. Before launching the game again, open the Mod Manager and use the "Generate debug info" option, then send the zip file produced in this channel.
If you need to access older log files, see https://docs.ficsit.app/satisfactory-modding/latest/faq.html#Files_Logs
https://cdn.discordapp.com/attachments/719242895114108938/1197930890572075079/debuginfo.png?ex=65bd0f14&is=65aa9a14&hm=4d5221515f6d9b66df173be45f34ad354bfc0fbb3626b2fe7f1bdaaa35e150f5&
also what do you mean "locked"
eg. a manufacturer that you built
and then you lose access to manufacturers
so it's locked
ah, well still provide the debug info as it'll let the mod author know what they might need to do. there's probably some cached data that's not getting updated causing the problem
SMM: 2.9.3
CL: 273254
SML: 3.7.0
Path: C:/Program Files (x86)/Steam/steamapps/common/Satisfactory/Engine/Binaries/Win64/
Launcher ID: steam
Command Line: -NO_EOS_OVERLAY
Solution
I think the recipes changes to null products. I will try to fix it
They shouldn't the ficsmas code already handles blocking people from sampling things with disabled recipes. And it wokrs on more than fiscsmas items as they used it as a way to sunset things like the old bouncy pads
Hmmm. I think i made something wrong with the "toggle" in contentlib ( locking and unlocking it in runtime )