Lupine00 Posted April 14, 2018 Posted April 14, 2018 I have a recurring issue; it's happened under many different game setups, with a wide variety of other mods installed. (This is running unmodified DCL 6.3). At some point, DCL events stop happening. It's obviously hard to tell exactly when they stopped in each game, but after a while you notice something is missing. Loot events, misogyny, and the main rape feature all stop triggering, and the messages that you get about rape triggers also stop (no more messages about how people might noticce you naked, it's dark, etc). Combat defeats do not stop working. Despite there being no restraints being worn, I've found that hitting FREE ME, seems to restart rapes. It does not restart cursed loot events, and I have yet to find a way to do that. Ah, it does, but you have to use it more than once. However, keys still drop. For example, I set all chances to 100%, arousal weight to 0, cooldown 0, minimum arousal to 0, per container scales to at least 1.0 (some can go higher). It says in debug that the cursed loot chance is 100%. Then I loot every barrel in Whiterun. Nothing. I got some keys. I loot every plant in Whiterun. Nothing. I got some keys. Go out of whiterun, kill everything that moves, loot corpses. Nothing. Any suggestions on how I might kickstart or unstick the main loot functionality? For example, some way to properly stop and restart the main timed events quest? I tried things like disabling DCL events completely in debug, then re-enabling. Re-enabling was hard. I'd untick the box, and close the MCM, and on re-opening the MCM, it would be open again. Eventually, by unticking it, then clicking on other DCL menus, the unticking it again, and repeating, I got DCL to un-disable and allow access to MCM again. It didn't change anything. It wasn't until I tried FREE ME, that rapes started up again. Never mind, disabling and re-enabling events, then hitting FREE ME again seemed to fix it. While I have quite a few mods installed, I got this same sort of behaviour from DCL without them, just much later in the save's lifetime. In this case, it's occurred before level 10, around save 140. The problem feels more like it's a stuck mutex, than a missing alias. The way that FREE ME fixes it might confirm or refute this. Not sure. (Incidentally) I have some log spam at start up like this: Spoiler [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script dcur_shacklesquestscript attached to dcur_shacklesQuest (34025F88) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] ERROR: Property BoundIdle2 on script DvCidhna_ErikurScr attached to DvCidhna_Erikur (3C01D8D1) cannot be bound because <NULL form> (11032CC3) is not the right type [04/14/2018 - 04:33:16PM] ERROR: Property BoundIdle on script DvCidhna_ErikurScr attached to DvCidhna_Erikur (3C01D8D1) cannot be bound because <NULL form> (110284F5) is not the right type [04/14/2018 - 04:33:16PM] warning: Property HentaiPregnancyVictimFaction on script hentaipregnancy attached to HentaiPregnancyQuest (130012C7) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script dcur_lockedglovesquestscript attached to dcur_RubberGlovesQuest (3404E128) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] warning: Property MME_Status_Global on script MME_Status attached to mme_StatusCheck (3706BAAD) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] ERROR: Element of property struggleIdles on script dcur_lbquestscript attached to dcur_lbquest (3404039A) cannot be bound because <NULL form> (110444E7) is not the right type [04/14/2018 - 04:33:16PM] ERROR: Element of property struggleIdles on script dcur_lbquestscript attached to dcur_lbquest (3404039A) cannot be bound because <NULL form> (110444E8) is not the right type [04/14/2018 - 04:33:16PM] ERROR: Element of property struggleIdles on script dcur_lbquestscript attached to dcur_lbquest (3404039A) cannot be bound because <NULL form> (110444E9) is not the right type [04/14/2018 - 04:33:16PM] warning: Property lockedglovesscript on script dcur_mastercontrollerscript attached to dcur_mastercontroller (34025A23) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script dcur_lb_lockedglovesquestscript attached to dcur_lockedRubberGlovesQuest (34044463) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script iddeirshquestscript attached to iDDeRestraintsQuest (2300B4DB) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] ERROR: Property ArmBindIdle on script iddeirshquestscript attached to iDDeRestraintsQuest (2300B4DB) cannot be bound because <NULL form> (110284F5) is not the right type [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyB on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyD on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property BleedOutIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDChastityBeltStruggle01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyC on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyE on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property ZapYokeBleedoutIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS06 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD06 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeHorny01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyA on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS05 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeHorny02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD10 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDH01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD05 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD09 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDChastityBeltStruggle02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDH03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeHorny03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS04 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD04 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property ZapArmbBleedoutIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle04 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property ArmbinderIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD08 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD07 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDH02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDBeltedSolo on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyE on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyA on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyC on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyD on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyB on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property I got the same spam when the game was absolutely new, and no LO changes did anything to fix it. I can see it's mostly animations not binding. DCL works fine despite these message (though probably some animations do not play properly, and I notice that the hog-tie wiggle game is not animating). Does anyone else get spam like this? Or is it just me? If it's just me, I guess I might need to blow away my entire Skyrim setup and start from scratch, because new installs, or new games with different setups in MO just produce the same spam, as long as DD/DCL chain is in the LO (excepting the small number of messages relating to other mods, like DevCid, MME, HP, etc).
Nightmyste Posted April 14, 2018 Posted April 14, 2018 42 minutes ago, DeviousPolarbear said: Hey, is there any way to disable the self bondage feature? I tried lookign through the settings but I couldn't find anything that would disable it. My character's refusal to depart with equipment is flooding my inventory lol That would be under consequences Look for bondage lover and uncheck the box, after that you can drop DD items In the same section you can also deactivate selfbondage
Inanis Corvus Posted April 14, 2018 Posted April 14, 2018 So since I never got a answer. I going to assume its impossible to get the 3 touch of XXXX spells without having the rest of the mod.
LazyBoot Posted April 14, 2018 Posted April 14, 2018 6 hours ago, Nightmyste said: 6 hours ago, DeviousPolarbear said: Hey, is there any way to disable the self bondage feature? I tried lookign through the settings but I couldn't find anything that would disable it. My character's refusal to depart with equipment is flooding my inventory lol That would be under consequences Look for bondage lover and uncheck the box, after that you can drop DD items In the same section you can also deactivate selfbondage To add to this, you can also sell or drop items in houses you own when the setting is on.
LazyBoot Posted April 14, 2018 Posted April 14, 2018 6 hours ago, Lupine00 said: I have a recurring issue; it's happened under many different game setups, with a wide variety of other mods installed. (This is running unmodified DCL 6.3). At some point, DCL events stop happening. It's obviously hard to tell exactly when they stopped in each game, but after a while you notice something is missing. Loot events, misogyny, and the main rape feature all stop triggering, and the messages that you get about rape triggers also stop (no more messages about how people might noticce you naked, it's dark, etc). Combat defeats do not stop working. Spoiler Despite there being no restraints being worn, I've found that hitting FREE ME, seems to restart rapes. It does not restart cursed loot events, and I have yet to find a way to do that. Ah, it does, but you have to use it more than once. However, keys still drop. For example, I set all chances to 100%, arousal weight to 0, cooldown 0, minimum arousal to 0, per container scales to at least 1.0 (some can go higher). It says in debug that the cursed loot chance is 100%. Then I loot every barrel in Whiterun. Nothing. I got some keys. I loot every plant in Whiterun. Nothing. I got some keys. Go out of whiterun, kill everything that moves, loot corpses. Nothing. Any suggestions on how I might kickstart or unstick the main loot functionality? For example, some way to properly stop and restart the main timed events quest? I tried things like disabling DCL events completely in debug, then re-enabling. Re-enabling was hard. I'd untick the box, and close the MCM, and on re-opening the MCM, it would be open again. Eventually, by unticking it, then clicking on other DCL menus, the unticking it again, and repeating, I got DCL to un-disable and allow access to MCM again. It didn't change anything. It wasn't until I tried FREE ME, that rapes started up again. Never mind, disabling and re-enabling events, then hitting FREE ME again seemed to fix it. While I have quite a few mods installed, I got this same sort of behaviour from DCL without them, just much later in the save's lifetime. In this case, it's occurred before level 10, around save 140. The problem feels more like it's a stuck mutex, than a missing alias. The way that FREE ME fixes it might confirm or refute this. Not sure. (Incidentally) I have some log spam at start up like this: Reveal hidden contents [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script dcur_shacklesquestscript attached to dcur_shacklesQuest (34025F88) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] ERROR: Property BoundIdle2 on script DvCidhna_ErikurScr attached to DvCidhna_Erikur (3C01D8D1) cannot be bound because <NULL form> (11032CC3) is not the right type [04/14/2018 - 04:33:16PM] ERROR: Property BoundIdle on script DvCidhna_ErikurScr attached to DvCidhna_Erikur (3C01D8D1) cannot be bound because <NULL form> (110284F5) is not the right type [04/14/2018 - 04:33:16PM] warning: Property HentaiPregnancyVictimFaction on script hentaipregnancy attached to HentaiPregnancyQuest (130012C7) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script dcur_lockedglovesquestscript attached to dcur_RubberGlovesQuest (3404E128) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] warning: Property MME_Status_Global on script MME_Status attached to mme_StatusCheck (3706BAAD) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] ERROR: Element of property struggleIdles on script dcur_lbquestscript attached to dcur_lbquest (3404039A) cannot be bound because <NULL form> (110444E7) is not the right type [04/14/2018 - 04:33:16PM] ERROR: Element of property struggleIdles on script dcur_lbquestscript attached to dcur_lbquest (3404039A) cannot be bound because <NULL form> (110444E8) is not the right type [04/14/2018 - 04:33:16PM] ERROR: Element of property struggleIdles on script dcur_lbquestscript attached to dcur_lbquest (3404039A) cannot be bound because <NULL form> (110444E9) is not the right type [04/14/2018 - 04:33:16PM] warning: Property lockedglovesscript on script dcur_mastercontrollerscript attached to dcur_mastercontroller (34025A23) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script dcur_lb_lockedglovesquestscript attached to dcur_lockedRubberGlovesQuest (34044463) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] ERROR: Property struggleIdles on script iddeirshquestscript attached to iDDeRestraintsQuest (2300B4DB) cannot be initialized because the value is the incorrect type [04/14/2018 - 04:33:16PM] ERROR: Property ArmBindIdle on script iddeirshquestscript attached to iDDeRestraintsQuest (2300B4DB) cannot be bound because <NULL form> (110284F5) is not the right type [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyB on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyD on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property BleedOutIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDChastityBeltStruggle01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyC on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyE on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property ZapYokeBleedoutIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS06 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD06 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeHorny01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyA on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS05 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeHorny02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD10 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDH01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD05 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD09 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDChastityBeltStruggle02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDH03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeHorny03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD03 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS04 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD04 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDS01 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property ZapArmbBleedoutIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property YokeIdle04 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property ArmbinderIdle on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD08 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPArmBZaD07 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZaZAPCArmBZaDH02 on script zadlibs attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDBeltedSolo on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyE on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyA on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyC on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyD on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property [04/14/2018 - 04:33:16PM] warning: Property DDZazHornyB on script zadbq00 attached to zadQuest (1100F624) cannot be initialized because the script no longer contains that property I got the same spam when the game was absolutely new, and no LO changes did anything to fix it. I can see it's mostly animations not binding. DCL works fine despite these message (though probably some animations do not play properly, and I notice that the hog-tie wiggle game is not animating). Does anyone else get spam like this? Or is it just me? If it's just me, I guess I might need to blow away my entire Skyrim setup and start from scratch, because new installs, or new games with different setups in MO just produce the same spam, as long as DD/DCL chain is in the LO (excepting the small number of messages relating to other mods, like DevCid, MME, HP, etc). Have you tired enabling the on-screen debug messages to see if they give any insight into the issue? Or just looking at the log-messages (assuming you have those enabled)
Lupine00 Posted April 14, 2018 Posted April 14, 2018 Just got a belt of Misogyny for the first time in the DD4 era. I've probably had it turned off in the last few playthroughs because chastity belts break so many mods, or aren't properly handled by them, but anyway... Was it always three body restraint keys to remove? Now, I know I can change my settings to work around this ... but with a relatively default setup, it basically means you'll never get it off (at least until LBA triggers - if it triggers). The chance you can get three rare keys in the interval between rapes, after which your (relevant) keys are stolen again, is impossibly small. And you're perma-pegged at 100 arousal in that thing, so looting anything at all mainly results in you getting bound up worse, and more keys lost, and so it goes... Now, my character has some "arousal issues", left over from time in the rubber doll suit, which probably contribute to the "practically full all the time" problem - and that pre-existing condition doesn't help things... But still, this does seem a trifle punitive for an event that is a reasonably common occurrence, not some rare, "highly punishing" quest. This is just another day of cursed loot... Spoiler What happened next was, horny as hell, "looted" a nice striptease collar and pony boots, asked for help, got put in a breast-yoke and gloves. Then robbed, then given a useless key, raped, robbed again, raped, keys taken, looted skooma, looted a regular restraint key, raped, keys taken ... can I get to a town with enough people to trigger LBA, and complete it, without dying? I still don't know. Will it remove the high-security items? I'm not sure. Also, from a DCL-self-consistent-lore sense, it's bizarre, as the men all claim to need only one key to open it, a common key they "had crafted", and yet you need three rare ones? It makes nonsense of the dialogue. Surely, if it has to be a rare key, one would be quite sufficiently challenging for a fairly commonplace item? And here it the other thing "body restraint" ?? Why do we have to suffer something so opaque? Why is the easiest chastity belt to get locked in, not operated with chastity keys? Body restraint sounds like it belongs to a corset, or perhaps a straight-jacket. This has confused new players for years, and seeing it again here, I think, as I've thought many times, why can't key naming be more intuitive? If ordinary chastity keys are common enough, requiring three of them still wouldn't be a trivial matter, and would be quite high-security enough for most quests. If you really want a belt to be near-impossible to remove, then have it need five chastity keys. Acquiring those, with the default rapist-steals-keys mechanic would be near impossible, and with only regular old key-loss mechanics, still hard.
Lupine00 Posted April 14, 2018 Posted April 14, 2018 34 minutes ago, LazyBoot said: Have you tired enabling the on-screen debug messages to see if they give any insight into the issue? Or just looking at the log-messages (assuming you have those enabled) Yes, actually I did. And while DCL was not working, they simply didn't appear. This makes perfect sense, but doesn't help diagnose much. After FREE ME, I looted a couple of plants, and after about twenty seconds lag, suddenly the messages for the post-FREE-ME loots appeared. After that, the message was lag reduced for further looting, and all chances reported looked normal, and information about arousal was all correct. It was as if DCL was completely jammed up until the FREE ME ran, though, as I say, keys were lootable, but no events or debug messages happening.
Lostdreamer Posted April 14, 2018 Posted April 14, 2018 42 minutes ago, Lupine00 said: Just got a belt of Misogyny. The men all claim to need only one key to open it, a common key they "had crafted", and yet you need three rare ones? *Shrug*. 'Cause it's Cursed. Actually, that's not a fair reply. I also find many of the more, ahh, 'interesting' DCL items to be overly punishing to escape and freely admit I have a tendency to safeword out of them once I have got myself to a blacksmith. My understanding is that they are ment to be frustrating, inconvenient and hard to escape from by intention and that many people enjoy such elements. I however don't particularly enjoy the 'spend hours and hours scratting around defenseless hunting for keys' element of the gameplay, so have a tendency to shortcut it using the tools within the mod. I figure the safeword function is there for when you hit the 'fed up of this shite now' point to allow you to continue enjoying your game. Unfortunately, after a few times through the loop that point ends up coming up sooner and sooner. It may be worth tweaking key drop weights - Rare keys are not biased by need iirc so you may well find that a seemingly very high drop rate isn't actually unbalancing for your gameplay. Equally, you may find that removing / reducing the risk of key loss so that they become useful treasure items you can keep and use as you need them may also help. Most rare keyed items will let you unlock them one key at a time as well i believe. I think the default settings in most SL/Devious mods are set to a 'testing' level rather than a 'balanced gameplay' point so don't be afraid of experimenting / changing. I have yet to find a balance that works for both standard and 'interesting' items. Standard items seem to work best with high key loss rates so that when they are spawned you can't just escape - you have to go hunting for those keys. But those same high key loss rates make the rare keyed items even more punishing as you won't have any keys / can easily lose some of the keys you have collected.
Lupine00 Posted April 14, 2018 Posted April 14, 2018 Shroud Hearth Barrow - there's a puzzle gate that you can lock from the inside. Normally, you can't leave SHB without opening the gate, from the inside, first. Except with DCL combat defeat. You can. And then you're locked out of SHB forever, bar cheating. In an ideal world, you would only get ported out as far as the near side of the gate, but of course that's not where the entry marker is...
Lupine00 Posted April 14, 2018 Posted April 14, 2018 19 hours ago, Lostdreamer said: I however don't particularly enjoy the 'spend hours and hours scratting around defenseless hunting for keys' element of the gameplay, so have a tendency to shortcut it using the tools within the mod. I figure the safeword function is there for when you hit the 'fed up of this shite now' point to allow you to continue enjoying your game. Unfortunately, after a few times through the loop that point ends up coming up sooner and sooner. It may be worth tweaking key drop weights - Rare keys are not biased by need iirc so you may well find that a seemingly very high drop rate isn't actually unbalancing for your gameplay. Equally, you may find that removing / reducing the risk of key loss so that they become useful treasure items you can keep and use as you need them may also help. Most rare keyed items will let you unlock them one key at a time as well i believe. I think the default settings in most SL/Devious mods are set to a 'testing' level rather than a 'balanced gameplay' point so don't be afraid of experimenting / changing. You have to remember, every time you are raped, you lose your accumulated keys. If you can't stash them somewhere nearby, you're never going to get them. You cannot accumulate three rare keys when you are raped without fail every time the cooldown expires, and in practice far more often because you keep triggering loot events when trying to find keys, and some loot events include a free bonus rape. In this case, the only key drop rate that is getting you out of that belt is ... phenomenal. I think I'd need to get one about every third container, and even then it would take a while, because presumably, unless the chances were set up "just for this", I'd get other rare keys some of the times. They would not be rare keys any more, they'd be litter. And that's ignoring the "unwanted" loot, you know? Because that is going to fire like crazy with all that arousal, unless you change it so it doesn't. There isn't a way for the player to "balance" this without some pretty gross "cheating", there just isn't. This seemingly innocent belt means you will probably die in it unless you cheat out of it, or make some very particular configuration changes that amount to cheating. I think that might be fun for a severely punishing device that you might see once in a playthrough, but I always thought the misogyny belt is a common comedy item that's supposed to be a regular, but escape-able, nuisance. Or maybe I'm not seeing something obvious here. How does Kimy deal with it? Wait a minute... Is this one of those devices where I can unlock the locks ONE AT A TIME and I don't need to hold all three keys together? ... As it turns out, no. No, it isn't. I think it might be. Doh! I'm so dumb. As I haven't had a single body restraint key in around four hours of play, I've had no chance to find out. I probably have to loot 100-200 containers to get one, and with the various obstacles its ... quite hard ... to loot any at all. But I'm sticking with it. At least it seems possible. Seems I was wrong again. I got a body restraints key. You can't use one key at a time. You have to get three together at once. It is hard. One way to balance this belt is to reduce the requirement to one rare key, or at most, two common chastity keys. Beyond that, you have to set a key drop rate of insane, or you need you have an inventory full of nothing but restraints and be in Dawnstar, or you need to trigger LBA (and I'm not sure that would get you out of it). Or maybe... Maybe you have enough of the required keys at home alraedy, and hope they don't slip through your clumsy fingers. Because they might. As for the helpful blacksmith, he thought what I needed wasn't removal of the belt, but raping, then addition of an armbinder and some pony boots. I got those off, but not the belt, and then the incident with the striptease collar... Of course, there's nothing stopping me saying "if I find even one rare key, I'll free myself with cheats". But for the people who think cheats should be blocked or punished, I have two words, "unintended consequences". Or I could just say "this is boring, I'm done with it now," and hit free me. Again, I'm making my play choice. How neat would it be if Kimy had decided to punish that by putting me in a full bondage set and teleporting me to a lair of giant spiders in Blackreach? I think that would probably be an untick DCL and never tick again moment. But I'm not suggesting Kimy would ever do that. I think I've made my point about cheats now. Job done.
Lostdreamer Posted April 14, 2018 Posted April 14, 2018 59 minutes ago, Lupine00 said: You have to remember, every time you are raped, you lose your accumulated keys. It's possible this isn't DCL - there are a couple of other mods that take keys on a rape event (?Devious Captures for example.). But it's also quite possible it is. I've had a quick look and can't see a slider/toggle for it - I must admit I had assumed that as everything else in DCL was configurable that would be as well. And I wasn't trying to say you were doing it wrong. I was actually saying "Yes, i find this sort of thing a problem as well and I havn't yet an ingame workaround." ...but I'm ok with using the safeword function occasionally. I'm happy with the idea of abstracting it as "I've made it out of the wilderness into the safety of a city, and can now safely escape from the weird dedric curses with the help of guards/priests/blacksmiths/mages/whatever." I consider it a part of the functionality of the mod I added to my game. But other people don't. And that's the beauty of massively modded skyrim - you can make it what you want it to be, and don't have to do things my way or anyone else's.
Reesewow Posted April 14, 2018 Posted April 14, 2018 1 hour ago, Lupine00 said: There isn't a way for the player to "balance" this without some pretty gross "cheating", there just isn't. This seemingly innocent belt means you will probably die in it unless you cheat out of it, or make some very particular configuration changes that amount to cheating. I think that might be fun for a severely punishing device that you might see once in a playthrough, but I always thought the misogyny belt is a common comedy item that's supposed to be a regular, but escape-able, nuisance. Or maybe I'm not seeing something obvious here. How does Kimy deal with it? The way I deal with *extreme* items like this is to simply allow myself to store keys safely as soon as I find them using the settings available in Cursed Loot. Namely, the ability to move keys to other containers without dropping/losing them (shakey hands). Usually this means onto a follower or into a mod-added storage that isn't affected by Cursed Loot (Deep Storage spell from Apocalypse is usually what I use). Basically, IMO you should probably turn off shakey hands at least while locked in an item like that, and no I wouldn't consider that "cheating" anymore than I'd consider lowering the difficulty of a game if I was literally being brick-walled by a sudden insane difficulty spike. Personally I don't have a problem with there being a few extremely rare *brutal* items in Cursed Loot that may require a few tweaks to settings in order to have them play nice. The other solution is always to simply remove it via adding keys with console or using the built-in free me command if you don't want to play out the scenario because it doesn't work well with your preferred settings. For sure, possibly that particular item would be better if the scenes it triggers didn't remove your keys, but it is possible that was the whole idea of the item. If so, I imagine the way you are supposed to remove the belt is to avoid males at all costs and do solo dungeon spelunking until you find the keys to remove it.
larrylaile Posted April 14, 2018 Posted April 14, 2018 Hi! I've managed to get the mod working fine for me using MO, but I've stumped upon an issue I do not know how to fix. I'm playing with a male character, but the NPCs treats myself as a woman. 3 out of 5 times I try to speak to an NPC, they would go ahead and say something like "Come here, woman!", or ask my character if they could tie him up (devious devices). I've tried tweaking with some of the options for some of the installed mods via the Mod Configuration Menu but to no avail. Anyone has any solution to this? Thanks.
LazyBoot Posted April 14, 2018 Posted April 14, 2018 13 minutes ago, larrylaile said: Hi! I've managed to get the mod working fine for me using MO, but I've stumped upon an issue I do not know how to fix. I'm playing with a male character, but the NPCs treats myself as a woman. 3 out of 5 times I try to speak to an NPC, they would go ahead and say something like "Come here, woman!", or ask my character if they could tie him up (devious devices). I've tried tweaking with some of the options for some of the installed mods via the Mod Configuration Menu but to no avail. Anyone has any solution to this? Thanks. Well, the author has stated that this mod expects a female character, and there are few/no gender checks included. So most of this isn't really considered a bug, I would think. However you can turn off the "Come here, woman" bit by turning off the "misogyny" option (it's under "rape" or "consequences" I think). The asking to tie up bit is from the device comment system. It's how it triggers when you're not wearing any devices.
DeviousPolarbear Posted April 14, 2018 Posted April 14, 2018 10 hours ago, Nightmyste said: That would be under consequences Look for bondage lover and uncheck the box, after that you can drop DD items In the same section you can also deactivate selfbondage Thanks, I figured there would be a setting for it but I was overlooking it. Lol. Appreciated
valcon767 Posted April 14, 2018 Posted April 14, 2018 2 hours ago, Lupine00 said: Or maybe I'm not seeing something obvious here. How does Kimy deal with it? some settings to check that may (or may not) help with the belt situation there are several settings on several different pages of the Cursed Loot MCM that have to be adjusted to work together to get the results that work best for the individual player. Cursed Loot MCM General Page - Parameters section - Chance to Lose Keys (this setting can happen on ANY cursed loot event) ; i have mine set down to 15% (and with the number of events i hit that works for me) Event Parameters page - Yoke Parameters - key steal weight (additional chances for keys to be stolen in addition to the general setting when wearing a yoke) ; i have mine set down to 10 here (happens but not super frequent), also the High Security section adjust cost for blacksmith to remove high security restraints etc. Miscellaneous Options - Shaky Hands (adjust the chance of a key "disappearing" when moving it form you personal inventory to anywhere else, even dropping on ground) ;i have this set to 25% (seems to work out to about a 1 in 3 times i lose whatever key i am moving) Escape Options page - Restraints Escape - adjust settings for keys and rare keys to desired levels, Escape Options section - make sure favor useful keys is checked ; i use a 15% setting for regular keys here and a 9% for rare keys (type of rare keys at default), and with the favor useful keys i normally get a key that will work ; on whatever restraint is currently locked on me when i get a key Consequences page - NPC Action Weights - adjust to taste (this is what a NPC will do to you when you talk to one wearing devices) Bondage Adventure page - Steal your stuff and Rape weights may need adjusting here ; as far as i can tell this affects any merchant you talk to while wearing a device in addition to other settings (basically bonus chances) you will also have to check all other mods MCMs (check all pages if you want to be sure) for key steal mechanics. you will have to adjust those as well, if they have them (i have 4-6 other mods that steal keys under the right conditions, and i am being a little lazy by not digging through over 60 additional MCMs to look up which ones they are offhand). hope the information helps someone. 1
Alpia Posted April 14, 2018 Posted April 14, 2018 Got across this armor https://nsfwmods.com/files/file/3-unpb-tekken-tag-tournament-2-unknown-armor/ now a few times and if you are in for new ideas I could imagine this beeing used similar to the rubber collar and the parasite. The armor already has two versions one covering only the lower body and one covering the breast area aswell and it could like the rubber collar grow if you dont get rid of it, while it pleasures your character by exploring deeply what it covers. I could see it like the parasite since its rather a living armor requiring you to find someone helping you to get rid of it, by a sexual ritual or like with the parasite you'd have to collect things to create a potion. If you get rid by it with a ritual it could involve estrus, but dunno about that since estrus is optional for your mod, still could imagine its fitting well since it has animations including simliar slimy stuff and a healer may tell you how to find them, once you with the help of the healer found such a "creature" you interact with it (could be a furo tub model to interact with) and one of the slime animations from estrus would trigger and once its done with you it uses the slime on your body and the energy/liquid it extracted from your body in the act to grow itself bigger so it makes sense it takes the slime of you from a "lore" point of view. Simpler scenario would be as said like with the parasite creating a potion to get rid of it while it as said deeply explores your body and grows. What this armor is missing to be perfect in my eyes is only a version where you are nearly completly or completly covered though I neverd edited a armor in that way I assume you may have more expierience or know someone who does. Hope you may like the idea and find some time to bother with it.
Lupine00 Posted April 14, 2018 Posted April 14, 2018 7 hours ago, larrylaile said: I've managed to get the mod working fine for me using MO, but I've stumped upon an issue I do not know how to fix. I'm playing with a male character, but the NPCs treats myself as a woman. 3 out of 5 times I try to speak to an NPC, they would go ahead and say something like "Come here, woman!", or ask my character if they could tie him up (devious devices). Use TESV Translator to rewrite all the dialog so it fits a submissive (or just unlucky) male character.
Lupine00 Posted April 14, 2018 Posted April 14, 2018 7 hours ago, Reesewow said: The way I deal with *extreme* items like this is to simply allow myself to store keys safely as soon as I find them using the settings available in Cursed Loot. Namely, the ability to move keys to other containers without dropping/losing them (shakey hands). Usually this means onto a follower or into a mod-added storage that isn't affected by Cursed Loot (Deep Storage spell from Apocalypse is usually what I use). Basically, IMO you should probably turn off shakey hands at least while locked in an item like that, and no I wouldn't consider that "cheating" anymore than I'd consider lowering the difficulty of a game if I was literally being brick-walled by a sudden insane difficulty spike. Personally I don't have a problem with there being a few extremely rare *brutal* items in Cursed Loot that may require a few tweaks to settings in order to have them play nice. The other solution is always to simply remove it via adding keys with console or using the built-in free me command if you don't want to play out the scenario because it doesn't work well with your preferred settings. For sure, possibly that particular item would be better if the scenes it triggers didn't remove your keys, but it is possible that was the whole idea of the item. If so, I imagine the way you are supposed to remove the belt is to avoid males at all costs and do solo dungeon spelunking until you find the keys to remove it. I agree completely. If you look back at my second post on this, the long one, I've added a new possibility. So I think misogyny belt is probably implemented fine as is... Though it is a bit of a hard item for its default frequency, particularly if you have high-security items off generally. But my real point here was never about DCL being over-hard - it was always about the line between cheating and simply picking easy options, and how sometimes when the options don't do what you want, you might need to resort to blunt tools to get the outcome you find most fun.
LucentShard Posted April 15, 2018 Posted April 15, 2018 I apologize if this has be asked before but, After installing the latest update, the rape function or the sex function no longer works and I don't know how to fix it. -NPCs decide to rape PC, pushes down PC, walks away. -Sleep at night, NPCs show up to rape, do nothing and walks away. -Guards catch PC doing public indecency, demands sex, does nothing. I've tried installing with a clean save, it doesn't work. I no longer have an older version of this mod to go back to. Does anyone have a solution?
WaxenFigure Posted April 15, 2018 Posted April 15, 2018 8 minutes ago, LucentShard said: I apologize if this has be asked before but, After installing the latest update, the rape function or the sex function no longer works and I don't know how to fix it. -NPCs decide to rape PC, pushes down PC, walks away. -Sleep at night, NPCs show up to rape, do nothing and walks away. -Guards catch PC doing public indecency, demands sex, does nothing. I've tried installing with a clean save, it doesn't work. I no longer have an older version of this mod to go back to. Does anyone have a solution? Have you opened the console after a rape attempt and looked at the messages there to see what the Sexlab Framework said when the rape was attempted?
LucentShard Posted April 15, 2018 Posted April 15, 2018 13 minutes ago, WaxenFigure said: Have you opened the console after a rape attempt and looked at the messages there to see what the Sexlab Framework said when the rape was attempted? I just tried with sleeping rape. Debug messages on upper left corner of screen: - "You are getting pulled out of bed by strong hands" - "You are getting pushed down" NPC shows up, shows me on the ground with hands tied, I am untied and NPC walks away. Opened up Console command to check for messages: No new messages at all. No sexlab messages at all.
LesboIsBesto Posted April 15, 2018 Posted April 15, 2018 A friend shared version 6.1 of DCL so I could play without waiting for my other mods to update for DDi 4.0 & shiiiiiieeeettt dood dis mod has more customization options than any other mods I've gotten from here lmao. Need some explanation on a few things tho: 1. Does its combat surrender lead to the events listed in that section after the rape ends? Like if I set SD+ to high chances, I'll get enslaved whether they human or creature? Same with similar events like the flash bang trap. 2. Even if I set the rapist gender to women, can men still participate in all other events & mod functions, even if it isn't technically a rape event? 3. On top of that ^ do the rape events & others like NPCs placing devices on me conflict with Deviously Enslaved? I have that mods events set to happen every 30 seconds for now but when I play normally, I wanna know if I'll be getting double items & rape depending on my vulnerability settings & if it's redundant to have either active together? 4. Can this mod's events occur during enslavement from other mods? Even ones that would conflict with enslavement from other mods like SD+ or Devious Cidhna? 5. If I disable Death Alternative but leave Defeat alone & change its settings so the health threshold is disabled, would that work ok? Only stuff I could think of so far, will probably think of more later. Either way, this mod looks lit af so can't wait to play it thoroughly!
valcon767 Posted April 15, 2018 Posted April 15, 2018 1 hour ago, Destroyah340 said: A friend shared version 6.1 of DCL so I could play without waiting for my other mods to update for DDi 4.0 & shiiiiiieeeettt dood dis mod has more customization options than any other mods I've gotten from here lmao. Need some explanation on a few things tho: 1. Does its combat surrender lead to the events listed in that section after the rape ends? Like if I set SD+ to high chances, I'll get enslaved whether they human or creature? Same with similar events like the flash bang trap. 2. Even if I set the rapist gender to women, can men still participate in all other events & mod functions, even if it isn't technically a rape event? 3. On top of that ^ do the rape events & others like NPCs placing devices on me conflict with Deviously Enslaved? I have that mods events set to happen every 30 seconds for now but when I play normally, I wanna know if I'll be getting double items & rape depending on my vulnerability settings & if it's redundant to have either active together? 4. Can this mod's events occur during enslavement from other mods? Even ones that would conflict with enslavement from other mods like SD+ or Devious Cidhna? 5. If I disable Death Alternative but leave Defeat alone & change its settings so the health threshold is disabled, would that work ok? Only stuff I could think of so far, will probably think of more later. Either way, this mod looks lit af so can't wait to play it thoroughly! player perspective on these points 1 - yes it does the rape event first, then the outcome event (enslavement or whatever) 2 - if you set the rapist gender to females only, men should still be able to participate in the non rape events 3 - yes and no, they can conflict, but should not as both have check in the mods to prevent this from happening. you will have to adjust the settings to get them to play nicely and get the results you want. i personally set the time outs on both mods to the same (usually 6 hours) so that they will not try to run events at the same time mostly. you can get double items and rapes if both trigger at the same time (time out settings will help prevent this), but normally you will get one, then a short time later the other will trigger. just play with the settings to get the results you want. 4 - they (conflicting events) should not happen during enslavement from other mods (it is usually really good at not firing during that time). 5 - not sure as i have not used DAYMOYL in long time now, but i do know you can adjust defeat to handle player anti-death. just make sure to not use Cursed Loot's Combat Defeat if you use DAYMOYL and/or Defeat. ; Cursed Loot MCM - Rape page - Rape Triggers - turn off combat surrender (this will let Defeat/DAYMOYL handle that part). ; Cursed Loot MCM - Rape page - Bondage Attacks - boots make helpless - if turned on ANY bondage boots will make PC helpless to prevent rapes etc. all by themselves.
Lupine00 Posted April 15, 2018 Posted April 15, 2018 57 minutes ago, valcon767 said: 3 - yes and no, they can conflict, but should not as both have check in the mods to prevent this from happening. you will have to adjust the settings to get them to play nicely and get the results you want. i personally set the time outs on both mods to the same (usually 6 hours) so that they will not try to run events at the same time mostly. you can get double items and rapes if both trigger at the same time (time out settings will help prevent this), but normally you will get one, then a short time later the other will trigger. just play with the settings to get the results you want. Despite some checks, and some initial progress on inter-operation, there are really so many ways DCL (or DD generally) can result in oddities or problems with SD+ enslavement. You don't want to begin an SD+ enslavement with pre-fitted DD items - really, you don't - you might find yourself in a lot difficulties, and SD+ has enough ways to go awry as it is. If you have to hit FREE ME during an SD+ enslavement, it will be broken, so that option goes off the table. As things stand, there is no clean path from DCL combat defeat to SD+. Simple Slavery can get you there in theory, but it has a whole raft of problems of its own, particularly if followers are involved. SS ought to have the smarts to strip all the DD items before putting you up for sale but it doesn't, and if there are quest items, it simply can't remove those. SS ought not to sell such "tainted" slaves. Who would buy one? It's like buying a car that still has the previous owner in it! Until (if it ever happens) DCL gets a feature to make the transfer to SD+ slavery on defeat directly, I don't think there will be a solid solution that can properly take into account the items that you have on you, and remove them, (and even then CD would probably throw DCL for a loop). One approach is to manually perform an SD+ submission when it looks like defeat is imminent. If you want to do this, you might want to use DAYMOYL instead of DCL's built-in defeat, because you can set DAYMOYL so it gives you a quiet period, where the enemies are calmed, to make your SD+ surrender. You can't really do it with DCL, because once you're defeated, its scripts start, and you'll probably be teleported somewhere, even if you manage to get a surrender in. Then you have the worst of all worlds, where you're being pushed and pulled in different directions by different mods, so avoid doing it. Ironically, Zaz had mechanics to try and resolve all this, by tracking if you were a slave or not - to allow mods to signal to each other that you were already a slave and not to try and "steal" you. But those functions were muddled, and didn't really do the right thing or in the right way, so I'm doubtful they are used. Until SS, DCL, SD+ and CD get to together and agree on an API for performing reliable slave transfers between mods (and temporary "loans" if POP were to get in on the act), this problem won't be fully resolved. I don't have high hopes such an API will be developed. It simply isn't on the radar of the authors, and I'm not sure they would agree how to proceed even if they thought there was demand for such functionality - which generally there doesn't seem to be.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now