Do CDF json rules support comments with the typical escape characters like "//" somehow? Asking because normally json syntax does not allow comments and the current C.O.I.N. rules have comments inside (which makes syntax checkers mark it as invalid json)
That is a very good question. True, the JSON standard doesn't allow for comments. However, given as how that is a stupid decision, I've elected to ignore it. The parser I use (jsoncpp) has a feature to ignore comments, which I use.
found 3 typos in the documentation: - missing "," after the "conditions" object in all the examples - missing line break before "Depending on how they are combined, you can create different rule types." - the example for "Container Base Form Condition" is not in a code block
Nope, not this mod. Ores are essentially activators that trigger when they are hit. There are a few ways to identify a potential culprit: 1. Check the ore script (should also be included in Legacy of the Dragonborn) 2. Check the ore deposits themselves (the activators, not the references)
We found out what that was - a combination of a CDF unintended behavior and a COIN bug.
tl;dr -> Fixed now, check latest update.
CDF, when parsing conditions, skips forms that cannot be found (if the plugin is missing). This is intended - it allows you to specify mod added forms without needing a dependency. However, the unintended part is that if NO forms are found the change still happens, just without a condition. This is what was happening in COIN - COIN was looking for ccBGSSSE067_LocTypeAyleidRuin, which ONLY exists in ccBGSSSE067, but did not create a dependency on that AE CC.
If you had ccBGSSSE067, all was fine. If you DIDN'T - then it would be distributed everywhere. That last part was CDF's unintended side-effect that was addressed in the latest update.
103 comments
1.5 Backport by Fuzzles
1.6 Backport by LuciusPortanius24
- missing "," after the "conditions" object in all the examples
- missing line break before "Depending on how they are combined, you can create different rule types."
- the example for "Container Base Form Condition" is not in a code block
1. Check the ore script (should also be included in Legacy of the Dragonborn)
2. Check the ore deposits themselves (the activators, not the references)
tl;dr -> Fixed now, check latest update.
CDF, when parsing conditions, skips forms that cannot be found (if the plugin is missing). This is intended - it allows you to specify mod added forms without needing a dependency. However, the unintended part is that if NO forms are found the change still happens, just without a condition. This is what was happening in COIN - COIN was looking for ccBGSSSE067_LocTypeAyleidRuin, which ONLY exists in ccBGSSSE067, but did not create a dependency on that AE CC.
If you had ccBGSSSE067, all was fine. If you DIDN'T - then it would be distributed everywhere. That last part was CDF's unintended side-effect that was addressed in the latest update.
Assorted Vampire Fixes and Tweaks
it calls on this mod
Container Distribution Framework For the Viscera module
i launch this and i get a DLL warning error, that recommends me to abort the launch..
the launcher error points to this mod.
"a DLL plugin has failed to load correctly"
"CDF.dll reported as incompatible during load"
can you explain this ?
For now, v2.2.1 it is