When using FollowTheGourd's Codex Plot GUID and Resource Finder, I notice that the codex entries for my custom standalone module are visible in the OC, even when my module is disabled on the DLC screen.
I guess this is an in-game bug, because my codex plots are only in the module override folder.
Not sure if it's appropriate to report it as a toolset bug on the wiki?
Bug : codex for standalone custom module visible in OC
Débuté par
Proleric
, juil. 08 2010 04:32
Retour en haut
#2
Posté 09 juillet 2010 - 01:28
FollowTheGourd
-
- Members
- 572 messages
I'll have to check soon, but what exact path in your mod are you using? When you say "module override" is that to say it's under addins/[UID]/module/override instead of ...core/override?
#3
Posté 09 juillet 2010 - 05:55
Proleric
-
- Members
- 2 362 messages
Yes, exactly that, for my codex plots. The toolset puts them in the toolsetexport subfolder.
I put your utility in the Program Files packages core override temporarily, but that's not causing the bug.
Another symptom is that if my module is disabled on the DLC screen, I have to force load OC saves, even though my module doesn't extend core or Single Player. This doesn't happen with a similar module that doesn't have a custom codex.
I put your utility in the Program Files packages core override temporarily, but that's not causing the bug.
Another symptom is that if my module is disabled on the DLC screen, I have to force load OC saves, even though my module doesn't extend core or Single Player. This doesn't happen with a similar module that doesn't have a custom codex.
