NFF Followers.zip

Among other things, when ASF determines the player, in particular, should be accosted, a popup will open, with 'Accept', 'Refuse', 'Cancel' as options by default with 'Acquiesce' and 'Decline' as optional choices you can enable in the MCM. Aside from having the choice of 'Accept' or 'Acquiesce' lead to a scene involving the requestor, by itself ASF doesn't do anything else. But what it does do is send a mod event out containing which choice the player made, whether they consented to have sex or not, and the requesting Actor.

So I added a new trigger, along with a new SLTriggers Redux MCM tab, Adult General, and in it have added the new 'ASF (Autonomous Sex Framework)' event option. You then have the filters you would expect and the option to run a trigger. Here's the MCM:

And here is the ASFHandleRefusal.sltscript, which will move player gold to the requestor, with the amount determined by the requestor level:

msg_console "ASFHandleRefusal start"

set $rname resultfrom actor_name $request.adult.asf.requestor
set $rlvl resultfrom actor_state $request.adult.asf.requestor "GetLevel"
set $steal resultfrom item_getcount $system.player $system.forms.gold
set $rlvl resultfrom rnd_int 1 $rlvl
set $steal $steal * $rlvl
set $steal $steal / 100
msg_notify $"{rname} takes {steal} gold since you refused them."
item_remove $system.player $system.forms.gold $steal false $request.adult.asf.requestor

msg_console "ASFHandleRefusal done"

Get it while it's hot.

Drunk Boyfriend: If a male actor with relationship rank of 3 or greater is nearby he will rape the player.

Disgusted Girlfriend: Taunts the boyfriend with random messages (e.g., "You're not done yet?"). Feel free to add your own.

I tested with various follower mods. Boyfriend script should be configured as an event on a timer. Girlfriend can be on a SL Begin, End, Orgasm, or Separate Orgasm doesn't matter. There was a funny mod in FO4 called something like "Bad Boyfriend" or Harassment (?) that gave me the idea.

Toxic Relationship.zip

SLTScript Function Library: https://github.com/sltriggersredux/sltriggersredux/wiki/Function-Libraries

SLTScript Scripting: https://github.com/sltriggersredux/sltriggersredux/wiki/Scripts

A copy is also included in the download.

is a mod hosted here on LoversLab that allows you to configure buffs/debuffs for many game values (e.g. Health, Health Regen, skills like Conjuration, OneHanded, etc) as well as a variety of more adult themed values, based on a large number of monitored values related to items worn, the state of things such as MME, Apropros2 and so on, and then keep them updated by polling every so often, all configurable via MCM. It includes a "Limits" page where you can control the maximum amount of change SLD can apply (so even if multiple different buffs give +50, if you have a Limit of +50, it will never exceed +50 for that stat).

If you have used SimplyBalanced before, this is similar in that it applies a wide range of buffs, albeit scaled based on various inputs.

I just posted an update to SexLab Disparity, 14.5, that adds 10 new values to monitor: 5 GLOB (GlobalValue) records added via the SLD .ESP, and 5 StorageUtil keys that it will monitor.

It's not an "officially supported" version, so I bear responsibility for it.

Using SLTScript functions like global_getvalue and global_setvalue, you can get and set the GLOB records using the editorIDs "_fwb_GLOBTracker0"-"_fwb_GLOBTracker4".

Using the "storageutil" function you can do the same with the StorageUtil keys "_fwb_SUTracker0"-"_fwb_SUTracker4":

  storageutil set none "_fwb_SUTracker0" float 33.3

  storageutil get none "_fwb_SUTracker0" float

What this gets you? If you have wanted a way to, with SLTR, keep a set of buffs or debuffs going, but manipulate them from time to time, consider adding SLD to your modlist and using one of the trackers (GLOB or SU, whichever you're more comfortable with). Then you could remove all of the SLTR script you might have added for updating actor values (assuming they're values SLD handles currently) and just monitor and manipulate a single (or more if you're doing something complex) value, letting SLD handle updating the amount of buff/debuff to add.

This is, in my opinion, the single most important feature of SLTR; the ability for users (possibly mod authors if they were so inclined to provide SLTR support) to wrap up new functions as bindings for SLTScripts.

Since it involves Papyrus development, including needing things like "header only" .psc files for builds, I'm going to assume you have some idea of what you're doing in that regard. I can help perhaps with some guidance but by and large you'd need to setup and be at least a little comfortable with Papyrus development.

You'll want, at minimum, a header version of `sl_triggersCmd.psc`, so you have access to the required functions, but again, at minimum, it would need a definition for `CompleteOperationOnActor()`.

The general idea is this:

- sl-triggers.dll, on game start, looks in 'SKSE/Plugins/sl_triggers/extensions/' for all '*-libraries.json' files, and parses them, looking for the Papyrus script names it needs to scan. It also notes their priorities. All function libraries are enabled by default.

- For each Papyrus script name it finds, it checks the Skyrim Papyrus VM for that script type and then loops through all of the functions defined

- It looks for functions matching the declaration (e.g. 'some_function' in this case): Function some_function(Actor CmdTargetActor, ActiveMagicEffect _CmdPrimary, string[] param) global

- During SLTScript execution, when the parser determines that a token represents a function name to be called, the plugin is asked to call the appropriate function

- The plugin finds the script where the function is defined via hash lookup and dispatches a static call to the VM with the parameters

- At this point sl_triggersCmd is sitting in a loop waiting for completion

- Calling sl_triggersCmd.CompleteOperationOnActor() at the end of your function notifies sl_triggersCmd to continue execution

So, by simply building your script with appropriately configured functions, and providing the -libraries.json file to point to it, you can add your own functions and even distribute your compiled .pex/-libraries.json combo to others.

By way of another example, if you install SLTR with OStim or SexLab selected, it also includes the adult-general library, with function libraries for OSLA and SLIF. The following files, which again would be installed with SLTR if you select OStim or SexLab, would constitute a function library and could have been shipped separately. Note that the *Adapter*.psc files are just helpers for the *CmdLib*.psc files.

- SKSE/Plugins/sl_triggers/extensions/sl_triggersCmdLibAdultGeneral-libraries.json

- scripts/sl_triggersAdapterOSLA.pex

- scripts/sl_triggersAdapterSLIF.pex

- scripts/sl_triggersCmdLibOSLAroused.pex

- scripts/sl_triggersCmdLibSLIF.pex

Put another way, I could fall of the face of the planet, and people could still add new function libraries to expand supported bindings for any mod or any other function you'd want to expose.