Search the Community

View File [XCL] X-Change Life Mod Loader Utility This is the official utility that can be used for applying mods to the game X-Change Life. Find mod loader usage details here: https://gitgud.io/xchange-life/mod-loader/-/wikis/home And a step-by-step guide for applying mods with this utility: https://x-change.life/wiki/docs/mods/ Developed by @togashikokujin who is a primary contributor to the X-Change Life project. If you feel like buying me a coffee, https://ko-fi.com/togashikokujin. The mod loader will always stay free, though. Starting with version 2.4.0, we had to up the Java version from 8 to 17. If you get the oh-so-helpful "A Java exception has occurred" when running the jar version, you will need to install a newer JRE. https://www.oracle.com/java/technologies/downloads/ is a good place for that if you don't already know what you're doing and have other preferences. NOTE: If you're using the installable version of the mod loader, be sure to install it to a folder other than your XCL folder. It will delete everything in its folder when you install updates. We do not have control over this aspect of the installer. Submitter togashikokujin Submitted 01/30/23 Category Gameplay Utilities  

SL Triggers Redux View File SLTR lets you run simple scripts without the need to compile and without worrying about Papyrus script dependencies or whether your script will build. SLTR comes with some scripts for you, thinks like giving yourself a little gold, healing yourself, giving yourself a drink. You can also write your own custom SLTScripts. And finally, you can set up triggers, ways to make SLTScripts run in response to game events, like on game load, on changing location, or even tied to custom keymappings of your choice. All of this is configurable via MCM or text files if you prefer. It is ESL flagged to minimize impact on your load order and most dependencies are loaded dynamically, so aside from the requirements of SKSE and PapyrusUtils, everything else is optional depending on what functionality you want. Requirements: SKSE Address Library for SKSE Plugins PapyrusUtil powerofthree's Tweaks Optional: SexLab Framework (if you want SexLab events and commands) SexLab P+ Framework (this version works as well) OStim Standalone Console Util Extended (if you want to execute Skyrim console commands in your scripts) (or another ConsoleUtil variant) MfgFix (if you want facial expression related commands in your scripts) Devious Followers Continued OSLAroused Devious Devices NG/Devious Devices SE Pet Collar Nether's Follower Framework Autonomous Sex Framework More Details Please!: The source code is available at https://github.com/sltriggersredux/sltriggersredux which also has a Wiki. There is also a LoversLab SLTriggers Redux Club available for better organized sharing of SLTR related content (i.e. SLTScripts, mini-games, add-ons). SL Triggers Redux (SLTR, though you may still see references to SLT) is two things: first, it is a scripting engine for the SLTScript scripting language and second, it is an extensible set of triggers that let you set up SLTScripts to be run in response to in-game events. The original focus of SLTR was purely on the four basic SexLab events (Sex Start, Orgasm, Sex End, Separate Orgasm via SLSO), but the framework has been expanded to not be tied solely to SexLab events. In addition, out of the box, you can also set up hotkeys to run scripts on demand, set scripts up to run on the (in-game) hour, and even run scripts directly via console command. These scripts are simple text files with the .sltscript extension, with an easy to understand syntax and a number of examples available to work from. Scripts are comprised of commands. Commands can be functions like "av_set" (to set an Actor Value) or syntactic commands like "goto" (to script execution to a different line). SLTR comes with a base library of functions available for scripting that is growing. That said, it features an extension architecture through which mod authors can implement additional functions that would be available to other users of SLT that also install the extension. This allows the ability to expand the function library without needing it to be added to the core library. You don't have to program the scripts to use them. A selection is available for you to work with from the get-go, plus any you want to copy and modify, and of course you can also share scripts with other SLTR users. (I hold no copyright over any SLTScripts anyone creates, just so you know.) Visit the SLTR wiki for complete details, including script examples and SLT API documentation for your SLTScripts, as well as integration features. Supported Events Events that occur in game (SexLab orgasm, Key press, Fast Travel) can be configured to fire triggers, which in turn can result in running scripts if the filters match. Currently, you can run SLTScripts in response to the following events: Core Keymapping (triggers in response to your choice of hotkey mapping, with optional modifier and DAK support) Top of the Hour (triggers on the in-game hour (or on the next such hour after sleep or travel)) New Session (triggers on each new game load) Player Cell Change (triggers on each Cell change; this happens more frequently than you might think, so be careful about heavy scripts with this, and protect against spamming i.e. player running back and forth across cell boundaries could generate spammed script executions) Player Opened Container (triggers after a Player opens a container; depending on timing of the backing ActiveMagicEffect landing, might not run until after the container is closed) Player Location Change (triggers on each Location change; typically much less frequent than Cell change) Player Equipment Change (triggers when the player swaps equipment) Player Combat State Changed (triggers when the Player's combat status changes) Player Hit Or Is Hit (triggers when the Player is hit; this can result in a lot of executions so be careful with filter selection and heavy scripts) Timer (triggers on a per-minute timer, delayed anywhere from 1 to 60 minutes) Harvesting (triggers when harvesting typical harvestables; e.g. plants, mushrooms, butterflies) Fast Travel Arrival (triggers when you arrive after fast travel) Vampirism Transitions (triggers when: you become a Vampire, you are cured, you transform to a Vampire Lord, and you end the Vampire Lord transformation) Werewolf Transitions (triggers when: you are cursed, you are cured, you transform into a Werewolf, and you end the Werewolf transofmration) Vampire Feeding (triggers when you begin vampiric feeding) Player Swim Start/Stop Player Water Enter/Exit Soul Trapped SexLab (optional) Start Stop Orgasm Orgasm, Separate Stage Start Stage End OStim (optional) Start Stop Orgasm SceneChange Scripts Provided These are some of the SLTScripts provided out of the box with just the Core install. That means you can run any of them from the console, or in response to any trigger, with no additional configuration. Making more SLTScripts available is simple; add them to your 'Data/SKSE/Plugins/sl_triggers/commands/' folder and on your next game launch you will see them. The 'target' of a script might be someone other than the player i.e. if you target them when using the console commands or if an event fires that targets them, like SexLab Separate Orgasm. Core SLTScripts Add perk point.sltscript Alcohol.sltscript Cast Calm.sltscript Cast Fear.sltscript Cast Light.sltscript Change stats (bad).sltscript Change stats (good).sltscript Change stats (mix).sltscript Cry.sltscript CureDisease.sltscript Doomstone Lover.sltscript Eat (sweets).sltscript Give Gold(10).sltscript Harm (-100).sltscript Heal (+100).sltscript Learn skill (Mage).sltscript Learn skill (random).sltscript Learn skill (Thief).sltscript Learn skill (Warrior).sltscript Lovers comfort.sltscript MFG Reset.sltscript Necks bitten(+1).sltscript Show Limited RaceMenu.sltscript Sound - Levelup.sltscript Toggle Collision.sltscript Toggle God Mode.sltscript SexLab SLTScripts (included when selecting either of SexLab/SexLab P+) CumControl.sltscript DD Unlock All.sltscript DF Reset All.sltscript DF Set Debt to 0.sltscript Disease.sltscript Heart beat(A).sltscript Sex is crime.sltscript SL Aggressive Sex With Player - Anal.sltscript SL Aggressive Sex With Player - Oral.sltscript SL Aggressive Sex With Player - Vaginal.sltscript SL Masturbate Self.sltscript SL Sex With Player - Anal.sltscript SL Sex With Player - Oral.sltscript SL Sex With Player - Vaginal.sltscript SLS Destroy Random License.sltscript SLS Evict from Markarth.sltscript SLS Evict from Riften.sltscript SLS Evict from Solitude.sltscript SLS Evict from Whiterun.sltscript SLS Evict from Windhelm.sltscript SLS Magic Curse Add.sltscript SLS Magic Curse Remove.sltscript SLS Revoke All Licenses.sltscript SLS Revoke Random License.sltscript SLS Send to Kennel - Markarth.sltscript SLS Send to Kennel - Riften.sltscript SLS Send to Kennel - Solitude.sltscript SLS Send to Kennel - Whiterun.sltscript SLS Send to Kennel - Windhelm.sltscript SLS UnEvict from Markarth.sltscript SLS UnEvict from Riften.sltscript SLS UnEvict from Solitude.sltscript SLS UnEvict from Whiterun.sltscript SLS UnEvict from Windhelm.sltscript Time Control.sltscript Time Slow.sltscript Vision blurred.sltscript OStim SLTScripts (included when selecting OStim) OStim Disease.sltscript OStim Heart beat(A).sltscript OStim Masturbate Self.sltscript OStim Sex is crime.sltscript OStim Sex With Player.sltscript OStim Time Control.sltscript OStim Time Slow.sltscript OStim Vision blurred.sltscript General Adult-oriented SLTScripts (included when selecting any of OStim/SexLab/SexLab P+) Contamination - MME_Lactacid.sltscript Contamination - Transformative Elixir.sltscript PetCollar - Add Keyless.sltscript PetCollar - Add.sltscript PetCollar - Remove Keyless.sltscript PetCollar - Remove.sltscript Add-Ons/Mini-Games Available These are add-on packs or mini-games implemented through SLTR. These may alter gameplay or introduce new mechanics. Typically these involve combinations of SLTScripts, pre-built triggers, and sometimes configuration files. PetCollar Game - (Requires: SexLab, PetCollar; Contents: SLTScript, trigger, JSON) At the start of SexLab scenes, your followers will (somewhat) randomly choose to equip and unequip the "Keyless Pet Collar" from the PetCollar mod. This is the one which cannot be picked or removed by the wearer. Consumption Lifestyle - (Requires: Transformative Elixirs; contents: SLTScript, trigger) When the non-stealth varieties of Transformative Elixirs appear in containers the player interacts with, they will automatically pull them into their inventory and consume them. Additionally, a periodic timer will run which will look for these items and consume them. Speaking of Copyright and Licensing / Attribution: All work associated with "SL Triggers Redux" aka "SLTR" aka "SLT" (in relation to it's origin) is derived from the original, SL Triggers, by Fotogen. I received approval to continue development. More info available on the SLTR Wiki. All other work that exists as part of this project as well as the associated SKSE C++ plugin project (when it's not hosted here) is and always will be MIT Licensed. All SLTScripts created by anyone else are subject to their copyright and I hold none over them. Code and data related to container activation was graciously provided by @Bane Master from Deviously Enchanted Chests; they deserve any credit for the efficacy of the container activation logic and I'll take the heat for the issues with my implementation. As agreed, this code and data, as part of this project, will remain MIT Licensed. Installation: If You Are Updating From An Older Version If you are moving from Fotogen's original SL Triggers, you will need a new save. If you are updating from one version of SLTR (this mod) to a newer version, check the CHANGELOG, but I'll likely still recommend a new save. Regardless, especially for small version jumps, it doesn't hurt to try first without a new save. That said, I have often found that both Fotogen's and mine seem to be able to survive the following: Save your game and quit Skyrim Remove the old version Run Skyrim, load your save, click through the warning, save, and quit again Perform any necessary cleanup (e.g. some versions no longer understand old script formats like JSON) Install the new version Run Skyrim and enjoy your new version However, in case of support, if a problem persists beyond that, the next logical step would be to test on a new save if possible. If You Are Installing For The First Time Using MO2 Is Recommended I personally use ModOrganizer2/MO2 and even then, often just through whichever modlist I'm using via wabbajack. If using MO2, dragging an SLTR install .zip into the downloads tab should be sufficient to make it available to install into your list. Similarly dragging it into your active load order should be sufficient to have it installed and running when you next play. It doesn't (at this time) have any particular load order requirements so feel free to move it about as you need. If, However, You Are Doing A Manual Install SLTR itself is a typical mod install with a SKSE plugin. It installs into Data\ as you would expect Mod And Plugin Logging Output Mod logging output will appear in whichever folder SKSE is configured to output to. On a typical Windows 10 Steam install, for example, I think this ends up in your 'Documents\My Games\Skyrim Special Edition\SKSE\sl-triggers.log' folder. Generally I also send log output from Papyrus script through the plugin, so all log output should be located in that one file. Once It Is Installed Once installed, you should now find in your 'mods' folder a new sub-folder, 'sl_triggers' (or whatever you named it during install). The mod folder structure at install should look something like: interfaces\ - containing e.g. translation files scripts\ - containing compiled .pex files SKSE\ CustomConsole\ - config file for ConsoleUtil-Extended to provide improved console commands Plugins\ sl_triggers\ commands\ - pre-made SLTScripts you can link to triggers without having to do any coding commandstore\ - folder available for SLTScript usage as well as shared persisted files (other locations are not excluded) extensions\ sl_triggersExtensionCore\ - trigger definitions (JSON) for events handled by the 'Core' extension new triggers for the 'Core' extension will be created here (but may end up in your overwrite or other folder specified for output files) you can place your own JSON files (as long as the filename can be a valid string in the Skyrim Papyrus VM) here without needing to use the MCM this also allows you to share triggers created by others sl_triggersExtensionSexLab\ - trigger definitions (JSON) for events handled by the 'SexLab' extension new triggers for the 'SexLab' extension will be created here (but may end up in your overwrite or other folder specified for output files) similarly, this works for any extension; for now there are only 'Core' and 'SexLab' offered by the mod sl_triggersExtensionCore-attributes.json - DO NOT EDIT; JSON-based definitions for the SLTR MCM to handle Core triggers sl_triggersExtensionCore-libraries.json - DO NOT EDIT; JSON configuration for Core function libraries sl_triggersExtensionSexLab-attributes.json - DO NOT EDIT; JSON-based definitions for the SLTR MCM to handle SexLab triggers sl_triggersExtensionSexLab-libraries.json - DO NOT EDIT; JSON configuration for SexLab function libraries containers.json - JSON configuration for Containers (provides support for the Core trigger: On Player Activate Container) you can modify this file to add containers from other mods that will be detected; it includes some examples you can also define which containers will be considered "Common" for filtering purposes; some defaults are included settings.json - created at first launch to avoid being overwritten during updates sl-triggers.dll - SKSE plugin; CommonLibNG-SSE based; uses Address Library; should support most used versions source\ scripts\ - containing source .psc files for the .pex files sl_triggers.esp sl_triggers_CHANGELOG.txt sl_triggers_function_library.md - Markdown documentation for available SLTScript functions provided by SLTR (other functions may be provided by third party extensions and function libraries) sl_triggers_function_library.txt - Text documentation for available SLTScript functions provided by SLTR (other functions may be provided by third party extensions and function libraries) sl_triggers_sltscripts.txt - Basic information about SLTScript; for the best documentation visit the [wiki](https://github.com/lynnpye/sl_triggers/wiki). In-Game Configuration If you have SkyUI installed, you should have an MCM available as 'SL Triggers Redux'. Any extensions registering themselves with SLTR will be listed on the left. The main SLTR MCM screen has an 'Enabled' option (on by default), a 'Debug' option, and a number of Granular Debug options, all of which are off by default. This will cause very little logging output. Even with all 'Debug' options off, during SLTScript parsing, if errors or important warnings or info need to be reported, they will be sent to that log. If your SLTScript isn't behaving as expected, check the log first. All of the 'Debug' options will output to the log file and will absolutely impact performance, both of your SLTScript and likely the game itself. This can be useful when troubleshooting your scripts, but don't leave it on for general play. Selecting an extension displays it's triggers if it has any defined, and gives you the option to create more. Each trigger has filter options on it's card for you to customize when the scripts should be applied. In game, if you are using the MCM to create new triggers, or as any new files are generated by SLTR (like new .json files if you create SLTScript that does so), they will be generated in the 'overwrite\' folder as for any mod; if you want to manage those files, you will need to manually copy them into whatever new location you want them in. You can also "soft delete" a trigger, marking it inactive until either you restore it or go in and physically remove the trigger file. Until restored it will remain inactive. About Performance: Effort has been made to avoid scripts from stressing the system more than necessary, but there are still limitations. Each script will be run on an Actor in game (the Player or an NPC) as an ActiveMagicEffect i.e. as from a Spell. Any one Actor can have no more than 30 scripts running on them at one time. Scripts can be long-running if you make them so, so be careful not to let things run away. Okay, But How Do I Run A Script! Running Scripts Manually: You can use the console to list available scripts and run them. From the console, use: slt list To list the available scripts. To run a given script, use: slt run "scriptname" The quotes are only necessary if the script name has spaces. So, to give yourself a free 10 septims, try: slt run "Give Gold(10)" Setting Up a Keymapping: If you have a script you want to be able to run at the press of a button, set up a Keymapping trigger. This is most easily done through the MCM. Go to the "SL Triggers Redux" MCM and choose the "SLTR Core" extension. Then click "Add New Item" on the right. Choose "Keymapping" as the event type, then select the key you wish to map it to. Finally, click the "Do 1" drop down and select a script to run. Exit the MCM and you should be able to run that script on demand just by pressing your mapped key! What Is Different From the Original? Fotogen's original sl_triggers effort is great and still works well. Plus I had already added some of these features (like the Keymapping and Top of the Hour event handling) to it. - Extensible - It is very easy to expand functionality to add more operations to be available in your scripts with the new command libraries; Papyrus script developers can create their own .psc file with global functions to add new operations that will be available to any script run on the system - New script format - The original format used JSON which is conveniently supported in the Skyrim environment but not convenient for development; the new .ini format is easier to read and works conveniently with syntax highlighting for some of the features - More than SexLab - I know, SexLab is the SL in SLT; but the framework supports any event to fire a script - ModEvent support for Script Execution - Mod authors can send mod events with a script name and SLT will run the script on the targeted Actor (or the Player if no target is available) - API support - You can also access the same features through an API if you prefer - Console command support - Some features available from the console - Additional SLTScript language features: subroutines, script-to-script execution with call arguments, named variables This is a renewal of development on the original SL Triggers by Fotogen. I received approval to continue development. Submitter hextun Submitted 04/30/25 Category Framework & Resources Requirements Required: SKSE https://skse.silverlock.org/ Address Library for SKSE Plugins https://www.nexusmods.com/skyrimspecialedition/mods/32444 PapyrusUtil https://www.nexusmods.com/skyrimspecialedition/mods/13048 Optional: SexLab Framework https://www.loverslab.com/files/file/20058-sexlab-se-sex-animation-framework-v166b-01182024/ if you want SexLab events and commands SexLab P+ Framework https://www.loverslab.com/files/file/25318-sexlab-p/ this version works as well Console Util Extended https://www.nexusmods.com/skyrimspecialedition/mods/133569 if you want to execute Skyrim console commands in your scripts (or another ConsoleUtil variant) MfgFix https://www.nexusmods.com/skyrimspecialedition/mods/11669 if you want facial expression related commands in your scripts Devious Followers Continued https://www.loverslab.com/files/file/11732-devious-followers-continued-se/ for Devious Followers related functions OSLAroused https://www.loverslab.com/files/file/20867-osl-aroused-arousal-reborn-sse-ae/ for OSLAroused specific functions (not SexLabAroused) Devious Devices NG https://www.loverslab.com/files/file/29779-devious-devices-ng/ for Devious Devices NG functions Devious Devices SE https://www.loverslab.com/files/file/5878-devious-devices-se/ for Devious Devices functions Regular Edition Compatible No Install Instructions If You Are Updating From An Older Version If you are moving from Fotogen's original SL Triggers, you will need a new save. If you are updating from one version of SLTR (this mod) to a newer version, check the CHANGELOG, but I'll likely still recommend a new save. Regardless, especially for small version jumps, it doesn't hurt to try first without a new save. That said, I have often found that both Fotogen's and mine seem to be able to survive the following: - Save your game and quit Skyrim - Remove the old version - Run Skyrim, load your save, click through the warning, save, and quit again - Perform any necessary cleanup (e.g. some versions no longer understand old script formats like JSON) - Install the new version - Run Skyrim and enjoy your new version However, in case of support, if a problem persists beyond that, the next logical step would be to test on a new save if possible. If You Are Installing For The First Time Using MO2 Is Recommended I personally use (ModOrganizer2/MO2)[https://www.modorganizer.org/] and even then, often just through whichever modlist I'm using via (wabbajack)[https://www.wabbajack.org/]. If using MO2, dragging an SLTR install .zip into the downloads tab should be sufficient to make it available to install into your list. Similarly dragging it into your active load order should be sufficient to have it installed and running when you next play. It doesn't (at this time) have any particular load order requirements so feel free to move it about as you need. If, However, You Are Doing A Manual Install SLTR itself is a typical mod install with a SKSE plugin. It installs into Data\ as you would expect Once It Is Installed Once installed, you should now find in your 'mods' folder a new sub-folder, 'sl_triggers' (or whatever you named it during install). Mod logging output will appear in whichever folder SKSE is configured to output to. On a typical Windows 10 Steam install, for example, I think this ends up in your 'Documents\My Games\Skyrim Special Edition\SKSE\sl-triggers.log' folder. Generally I also send log output from Papyrus script through the plugin, so all log output should be located in that one file. The mod will be Enabled by default and all Debug features off. This will cause very little logging output. Even with all 'Debug' options off, during SLTScript parsing, if errors or important warnings or info need to be reported, they will be sent to that log. If your SLTScript isn't behaving as expected, check the log first. In game, if you are using the MCM to create new triggers, or as any new files are generated by SLTR (like new .json files if you create SLTScript that does so), they will be generated in the 'overwrite\' folder as for any mod; if you want to manage those files, you will need to manually copy them into whatever new location you want them in. The mod folder structure at install should look something like: interfaces\ - containing e.g. translation files scripts\ - containing compiled .pex files SKSE\ CustomConsole\ - config file for ConsoleUtil-Extended to provide improved console commands Plugins\ sl_triggers\ commands\ - pre-made SLTScripts you can link to triggers without having to do any coding commandstore\ - folder available for SLTScript usage as well as shared persisted files (other locations are not excluded) extensions\ sl_triggersExtensionCore\ - trigger definitions (JSON) for events handled by the 'Core' extension new triggers for the 'Core' extension will be created here (but may end up in your overwrite or other folder specified for output files) you can place your own JSON files (as long as the filename can be a valid string in the Skyrim Papyrus VM) here without needing to use the MCM this also allows you to share triggers created by others sl_triggersExtensionSexLab\ - trigger definitions (JSON) for events handled by the 'SexLab' extension new triggers for the 'SexLab' extension will be created here (but may end up in your overwrite or other folder specified for output files) similarly, this works for any extension; for now there are only 'Core' and 'SexLab' offered by the mod sl_triggersExtensionCore-attributes.json - DO NOT EDIT; JSON-based definitions for the SLTR MCM to handle Core triggers sl_triggersExtensionCore-libraries.json - DO NOT EDIT; JSON configuration for Core function libraries sl_triggersExtensionSexLab-attributes.json - DO NOT EDIT; JSON-based definitions for the SLTR MCM to handle SexLab triggers sl_triggersExtensionSexLab-libraries.json - DO NOT EDIT; JSON configuration for SexLab function libraries containers.json - JSON configuration for Containers (provides support for the Core trigger: On Player Activate Container) you can modify this file to add containers from other mods that will be detected; it includes some examples you can also define which containers will be considered "Common" for filtering purposes; some defaults are included sl-triggers.dll - SKSE plugin; CommonLibNG-SSE based; uses Address Library; should support most used versions source\ scripts\ - containing source .psc files for the .pex files sl_triggers.esp sl_triggers_CHANGELOG.txt sl_triggers_function_library.md - Markdown documentation for available SLTScript functions provided by SLTR (other functions may be provided by third party extensions and function libraries) sl_triggers_function_library.txt - Text documentation for available SLTScript functions provided by SLTR (other functions may be provided by third party extensions and function libraries) sl_triggers_sltscripts.txt - Basic information about SLTScript; for the best documentation visit the wiki. In-Game Configuration If you have SkyUI installed, you should have an MCM available as 'SL Triggers Redux'. Any extensions registering themselves with SLTR will be listed on the left. The main SLTR MCM screen has an 'Enabled' option (on by default), a 'Debug' option, and a number of Granular Debug options, all of which are off by default. All of the 'Debug' options will output to the log file and will absolutely impact performance, both of your SLTScript and likely the game itself. This can be useful when troubleshooting your scripts, but don't leave it on for general play.

View File Lustful Void Tech Inspector Hallo!🥰 So, as a person who uses a bit too many tech mods (ACOT, GE, and things of that nature), sometimes the rare candy techs and other T5 soc techs are buried by the weight of other T4 and especially repeatable T5 techs. To keep my sanity, I made this mod that shows whether you meet the requirements for the tech weight modifiers. Also added a cheat to add the techs you fulfill the requirements for as research options. Load Order: Just put this thing after Lustful Void, and it should work fine Lustful Void Lustful Void Tech Inspector Compatibility: This should have no problems since it is just a new event file with the English loc file for the event PS: Since I made this mod using the last LV for 4.0, I put the same version on the descriptor, but it should not be a problem since LV is running ok in the new 4.3 patch Submitter DNL Submitted 04/06/26 Category Stellaris Requirements Lustful Void  

Skyrim Sentinel Supply Chain Security for SKSE Plugins TL;DR: Know exactly what's in your load order. Sentinel verifies SKSE plugin hashes against a community-curated database of official releases. 🟢 Verified | 🟡 Unknown. Portable, offline-capable, open source. What is this? Know your DLLs. Every SKSE plugin in your load order is a compiled binary you're trusting to run on your machine. Sentinel gives you visibility into that trust. It scans your mods folder, generates SHA-256 hashes, and checks them against a community-curated database of official releases. Think of it as a provenance checker—answering: "Is this the exact file the author published?" Other modding communities (Minecraft, Factorio) have dealt with supply-chain compromises. This tool exists so Skyrim modders don't have to learn that lesson the hard way. 🟡 Most Plugins Will Show as "Unknown" — That's Expected Unknown does NOT mean unsafe. It simply means the plugin isn't in our database yet. Sentinel currently covers ~100 popular SKSE plugins (Engine Fixes, RaceMenu, po3 Tweaks, etc.). Adult-specific plugins from LL are underrepresented—we're building that coverage with your help. This is a community project. The database grows as people contribute verified hashes. Scan your MO2/Vortex mods folderVerify against 100+ curated plugins🟢 Verified | 🟡 UnknownClick to copy hashes, export unknowns for submissionWorks offline with cached database Download ⬇️ Download SkyrimSentinel.exe (v0.1.0-beta) Just download and run — no Python or installation needed. 📖 How to Use Download and run SkyrimSentinel.exe Click Browse and select your mods folder Click Scan Review results — green means verified! 🤝 Help Build the Trust Registry See unknown plugins? You can fix that. Click Export Unknown after scanning Add the mod name + Nexus/LL link to the JSON Drop it in this thread or open a GitHub PR Every submission helps the next person. We're building the definitive integrity database for SKSE plugins—together. ⚠️ Antivirus False Positives Some AV tools may flag SkyrimSentinel.exe. This is a false positive—extremely common with Python apps packaged as .exe files. PyInstaller bundles Python into a single executable, which looks "packed" to heuristic scanners. This is a well-documented issue affecting thousands of legitimate apps. See also: StackOverflow discussion. The code is 100% open source—review it yourself, or run from source. VirusTotal Analysis: View Full Report Roadmap More LL-specific plugins (SexLab, OStim, DD, etc.)🔴 Revoked status for known-bad hashesMigration to Nuitka (fewer AV false positives)Auto-update for databaseDirect hash submission from the app Requirements Windows 10/11 That's it. Source Code Fully open source: GitHub Repository About Me I started modding Skyrim in 2017—struggling to run Dual Sheath Redux on a low-end rig. Since then I've moved into Cybersecurity and Software Engineering (currently in university). I built Sentinel because I love this community and want to see it stay resilient. Other ecosystems have learned hard lessons about supply-chain security. My goal is to give Skyrim modders the tools to stay ahead—without adding friction to the chaos that makes this place great. Discord: Lullavy | GitHub: Lullacy Looking for Collaborators I'd appreciate suggestions and collaborators to help with: Threat modeling for Sentinel — identifying attack vectors and edge cases Algorithm development & optimization for traversing/walking the folder structure on the client side If you have experience in security research or performance optimization, I'd love to hear from you! A Note on Development I used GitHub Copilot as a development aid. All AI-generated code was reviewed and verified before inclusion. The architecture and security model are my own. Questions? Feedback? Hashes to submit? Post below! 👇

Skyrim Sentinel Supply Chain Security for SKSE Plugins TL;DR: Know exactly what's in your load order. Sentinel verifies SKSE plugin hashes against a community-curated database of official releases. 🟢 Verified | 🟡 Unknown. Portable, offline-capable, open source. What is this? Know your DLLs. Every SKSE plugin in your load order is a compiled binary you're trusting to run on your machine. Sentinel gives you visibility into that trust. It scans your mods folder, generates SHA-256 hashes, and checks them against a community-curated database of official releases. Think of it as a provenance checker—answering: "Is this the exact file the author published?" Other modding communities (Minecraft, Factorio) have dealt with supply-chain compromises. This tool exists so Skyrim modders don't have to learn that lesson the hard way. 🟡 Most Plugins Will Show as "Unknown" — That's Expected Unknown does NOT mean unsafe. It simply means the plugin isn't in our database yet. Sentinel currently covers ~100 popular SKSE plugins (Engine Fixes, RaceMenu, po3 Tweaks, etc.). Adult-specific plugins from LL are underrepresented—we're building that coverage with your help. This is a community project. The database grows as people contribute verified hashes. Scan your MO2/Vortex mods folderVerify against 100+ curated plugins🟢 Verified | 🟡 UnknownClick to copy hashes, export unknowns for submissionWorks offline with cached database Download ⬇️ Download SkyrimSentinel.exe (v0.1.0-beta) Just download and run — no Python or installation needed. 📖 How to Use Download and run SkyrimSentinel.exe Click Browse and select your mods folder Click Scan Review results — green means verified! 🤝 Help Build the Trust Registry See unknown plugins? You can fix that. Click Export Unknown after scanning Add the mod name + Nexus/LL link to the JSON Drop it in this thread or open a GitHub PR Every submission helps the next person. We're building the definitive integrity database for SKSE plugins—together. ⚠️ Antivirus False Positives Some AV tools may flag SkyrimSentinel.exe. This is a false positive—extremely common with Python apps packaged as .exe files. PyInstaller bundles Python into a single executable, which looks "packed" to heuristic scanners. This is a well-documented issue affecting thousands of legitimate apps. See also: StackOverflow discussion. The code is 100% open source—review it yourself, or run from source. VirusTotal Analysis: View Full Report Roadmap More LL-specific plugins (SexLab, OStim, DD, etc.)🔴 Revoked status for known-bad hashesMigration to Nuitka (fewer AV false positives)Auto-update for databaseDirect hash submission from the app Requirements Windows 10/11 That's it. Source Code Fully open source: GitHub Repository About Me I started modding Skyrim in 2017—struggling to run Dual Sheath Redux on a low-end rig. Since then I've moved into Cybersecurity and Software Engineering (currently in university). I built Sentinel because I love this community and want to see it stay resilient. Other ecosystems have learned hard lessons about supply-chain security. My goal is to give Skyrim modders the tools to stay ahead—without adding friction to the chaos that makes this place great. Discord: Lullavy | GitHub: Lullacy Looking for Collaborators I'd appreciate suggestions and collaborators to help with: Threat modeling for Sentinel — identifying attack vectors and edge cases Algorithm development & optimization for traversing/walking the folder structure on the client side If you have experience in security research or performance optimization, I'd love to hear from you! A Note on Development I used GitHub Copilot as a development aid. All AI-generated code was reviewed and verified before inclusion. The architecture and security model are my own. Questions? Feedback? Hashes to submit? Post below! 👇

File Name: SixColorOverlay File Submitter: Bwog File Submitted: 30 Apr 2014 File Category: Models & Textures Requires: RaceMenu v2.5.1 SixColorOverlay is a utility for users who want to make their own overlay designs, and provides the option to publish them as mods. It requires RaceMenu v2.5.1 to add overlays for warpaint and tattoo's on the head, body, hands and feet. To experiment with overlay designs, and to use them in game, SixColorOverlay contains 6 dummy files for each of the 4 body areas; hands, feet, face and body. The dummy files are meant to be overwritten with your own design. Six overlays is a lot, but is meant to test several different designs at one time, and to bring your final design in Skyrim, with up to 6 independent colors. Up to 6 independent glow colors are optional. The dummy files are 1K .dds files, but can be overwritten by any size you want. Look in Data/textures/Actors/Character/Overlays for Body, Hand, Feet and Face folders. For instance, rename your body paint file to BodyColor1.dds and overwrite BodyColor1.dds. Open RaceMenu and choose BodyColor1 in the texture list, choose a color for the texture (a color for glow is optional). A mod with your final design can be made by unpacking this mod, overwrite with your .dds files, and archive with 7-zip. Warnings: be aware that this is my first mod and that is has been tested for a short time only. It works when other overlay mods are present or absent. I had an unintended (but reversible) glow effect once when two overlay mods added textures to the same area. It works when Racemenu Loose Base Scripts v2-5-0 is present or absent. TES5Edit gave no warnings on loading. Installation: use a mod manager or install manually. RaceMenu v2.5.1 is required. I put it after RaceMenuMimic.esp (not required, not present) with BOSS Userlist Manager. Loading after Racemenu or Racemenu plugin is probably OK. Edit nioveride.ini in Data/SKSE/Plugins to use 6 overlays for hand, feet and face (default is 3). Credit: I mentioned that this is my first mod but only part is from me. Compiling became a guessing game for me; I got help from B3lisario, and from Uriel who compiled it for me (which is of course a crucial step). Racemenu includes Netimmerse override and these mods make overlays possible, both were made by expired6978. Credit: Link to this page if you want to post this somewhere else. Nothing is required of users, but a (link to) an image with home made overlays would be nice. Overlays can be shared. Example: In the image 3 different textures are used, which each were given a different texture color and just tiny bit of a glow color (similar, or very different from the underlying texture color). Hands, Feet and Body each have 3 textures (I made no textures for the head this time). The original is a photo from the ESA/Hubble site, credit: ESO, edited version of heic0913c; http://sci.esa.int/h...l-box-heic0913/ For more images (earlier version) see http://www.loverslab.com/topic/15224-show-your-skyrim-counterpart/page-539?do=findComment&comment=759968 Click here to download this file

View File Nosis' Locks: Arbitrary Read/Write Locks "Protects your code against CTDs better than Trojan protects against STDs" v0.3.0 Description NosLocks gives you an generic read/write locking mechanism to use as you see fit. It abstracts out the GotoState() paradigm of Papyrus effectively allowing a single script to have multiple states at the same time (via semaphore barriers). This library provides classic read/write locking capabilities: many readers and zero writers, or one writer and zero readers. WARNING Semaphore barriers are dangerous if you aren't careful with them. Only you can prevent dead-locks by avoiding modding while intoxicated! BETA Notice (No Longer a Warning) v0.3.0 is a mid-beta release. It's barely been tested under real world conditions but has been heavily self-tested at this point. The API will likely change a bit as well. I'm putting it out there mostly so that other modders can try it out and give feedback/make requests before I move it to a more late beta/stable state and lock the API. It's core has been proven enough at this point that I encourage you to start using it for any projects that you don't plan on releasing in the next few weeks (I expect to declare it late beta/stable by then). My plan is simple. Once it's stable the API gets locked and, other than an unexpected bug fix or two, freeze development of it entirely. So now's the time to make requests, suggestions, etc. Why Would I Need This? If you're a modder then it will help you elegantly protect your code from race conditions, particularly with complex multi-state code that "yields the floor" at inopportune moments. If you're not a modder it might be because another mod is using this (doubtful right now). You can stop reading here unless your curiosity is just boiling over. Dependencies v0.3.0: Maybe SKSE? If you want great debug information then it's a must have. Otherwise I believe nothing should be broken if you don't have it. If someone could test WITHOUT SKSE (try running the debug dump and see what's in your logs) and get back to me, I'd greatly appriciate it. v0.2.x: None. Zip. Zilch. Not even Skyrim.esm. Nothing. Upgrading From 0.2.x If you had any allocated locks in your save file then a clean save is required due to a bug that's now been fixed. Upgrading From 0.1 Clean save. Start over. Your code will be broken anyhow due to API changes. What's New (from 0.2.x to 0.3.0) Bug fixes (two major), support for ActiveMagicEffect as owner, and a bunch of debugging methods/capabilities. In detail, the following was done... What's New (from 0.1 to 0.2.x) A lot. Heavy API refactoring. No bug fixes because I didn't find any . Two major API usage changes: Locks are now "owned" so that they may be garbage collected when deadbeef. You no longer have to manually get the manager. Everything you need is scoped globally. In detail the following has changed... Reference Guide NosLocks: NosLock: Console Commands: Quick-Start Example The below demonstrates NosLocks in a nutshell... NosLock MyLockEvent OnInit() MyLock = NosLocks.AllocLockForForm(Self)EndEventInt Function GetSomething(Actor whatever, Int lockID=0) MyLock.ReadLock(lockID) Int res = gottenFromSomeProtectedData MyLock.Unlock() Return resEndFunctionFunction SetSomething(Actor whatever, Int lockID=0) MyLock.ReadLock(lockID) If (!GetSomething(whatever, lockID)) lockID = MyLock.UpgradeLock() If (!GetSomething(whatever, lockID)) ; check again manipulateSomeProtectedData EndIf EndIf MyLock.Unlock()EndFunction . In-Depth Example Owned vs. Unowned Locks In 0.1 all locks were unowned. Starting with 0.2 it's now strongly preferred that you allocate owned locks. If the script using the lock is a Form use AllocLockForForm(). If it's an Alias use AllocLockForAlias(). If it's an ActiveMagicEffect use AllocLockForAME(). Explict lock freeing is still preferred of course, but now the locks can be garbage collected when someone uninstalls your mod. A Note About Lock Upgrades If you are unfamiliar with read/write locks (but understand the concept of mutexing), keep something in mind: you can not make assumptions about the state of your data after the upgrade. The upgrade is not an atomic operation. During the upgrade another writer might have come along and changed your protected data. Basically... Write Lock IDs Two things... First, 0 is the only invalid write lock ID, so don't expect 0. Second, they should be passed around in a fully reentrant manner. Don't globalize them (it's tempting... I know) or you might find yourself scratching your head about why you're dead-locking when it looks like you shouldn't be. Lock Leaking Release those locks back to the manager if they have a limited life time! Be kind. There's 128 of them but that runs out quickly if they aren't released but new ones keep getting acquired. Examples: If you're using a lock in a magic effect, NosLocks.FreeLock(MyLock) on the effect finish event! If you have a lock for a quest that only is used when the quest is running, release it when the quest stops! If you have "permanent" locks and start an "uninstall" procedure, give them back or they will walk in limbo for eternity! If you don't remember to release then owned locks will be garbage collected periodically (not optimum of course), but unowned locks will be lost forever! Leaking unowned locks may eventually result in the player's save game being 100% deadbeef. Pre-emptive FAQ Please read before asking questions/asserting positions as they might already be addressed. Please try it out (not on a stable branch of your project) and let me know what you think. Particularly if there's issues or feature/API request changes. ~ nosis Submitter nosis Submitted 08/19/2014 Category Modders Resources Requires Special Edition Compatible

Mods Optimizer View File Hello everyone, this is a small application that I made for myself in a hurry. I'm not sure that this forum is the best place for such utilities, but since the main task of this application for me is inextricably linked with the content from this forum, I decided to share it here. Correct me, if I'm wrong ? Description I often come across releases of some kind of creative work (sims, lots, etc.), in which the author includes absolutely all the custom content used in the creation. And, unfortunately, I always passed such releases because of the problem of duplicate files. A lot of the custom content that comes with the releases is already in my mods folder. Structured. I'm not sure I fully understand how EA solves duplicate mods folder problems, but as a developer I can tell you for sure that the physical memory of my disk and the RAM of the EA process are not infinite ? This utility allows you to scan your mods folder and your desired custom content folder in order to find only those files that you don't actually have. As a result, you will get a new folder with custom content that you can safely place in your mods folder. Note: this is proof of concept app, which can have bugs. If you have any questions or comments please contact me, I will try to help. Version 1.0.1 Fast Scan added. You can find it in new panel for settings (on by default) With Fast Scan new.mp4 Without Fast Scan old.mp4 Submitter wyler Submitted 09/10/2021 Category Uncategorized Requires May require latest .NET Runtime.  

XEdit Scripts - Automate Utilities (SLA, SLS, + other stuff) View File Check for NPC Tint Masks.pas Checks a mod's NPCs for face tint files in the directory you specify. Edit "sTintMaskPath" to point to your mod's FaceGenData\FaceTint directory. Make sure it ends in a backslash. The texture file name gets appended to it. e.g. "mods\[My MO2 mod dir]\Textures\Actors\Character\FaceGenData\FaceTint\[My Mod's ESP/ESM file name]\" IMAD removal.pas This file will create a image space modifier removal bat file "removeimods" in your SSE game directory. If you change your load order you will have to rerun this. To use it. Load the target ESM/ESP files in SSE Edit. This can be your entire load order. CRTL+Click the target ESM/ESP files. Or CTRL+A for your entire load order. Right click on any of the target ESM/ESP files and select "Apply Script...". Select "<new script>" from the list of available scripts dropdown You'll see the New Script Template. Copy all. Delete it. Paste the IMAD removal PAS script. Save it and name it. Run it Each "rimod" command is followed by the source mod in a comment. e.g. rimod 0401EB05; DLC2DBBookLevelIod [IMAD:0401EB05] - [04] Dragonborn.esm rimod 04023F86; DLC2HMDaedraExpImod [IMAD:04023F86] - [04] Dragonborn.esm rimod 04024FBC; DLC2HMDaedraExpImod02 [IMAD:04024FBC] - [04] Dragonborn.esm rimod 040317D8; DLC2MiraakTeleportIMODStatic [IMAD:040317D8] - [04] Dragonborn.esm rimod 04031D26; DLC2StandingStoneReleaseImod [IMAD:04031D26] - [04] Dragonborn.esm While in game you can use "bat removeimods" to remove all image space modifiers. If the something that is applying the modifier is still active it will come back. You can then ALT+TAB out of the game and edit the bat file and remove "rimod" commands to find the troublesome mod. TAWOBA SLS JSON.pas Generates a BikiniArmors.json file for SexLab Survival. Before you start. Right click on any file under "SKSE\Plugins\StorageUtilData\SL Survival\" in MO2's Data Tab and select "Reveal in Explorer". Copy the full path to SL Survival's Storage Util's directory. You'll need this later Making a "BikiniArmors.json" file with SSE Edit. Load the TAWOBA mod in SSEEdit Right of the TAWOBA ESP file name and select "Apply Script..." Select "<new script>" from the list of available scripts dropdown You'll see the New Script Template. Copy all. Delete it. Paste the TAWOBA SLS JSON PAS script. Change "sJsonPath := 'E:\';" to SL Survival's Storage Util's directory. Make sure it ends with a backslash. "BikiniArmors.json" gets appended to it later. Save it and name it. Run it The script uses the ArmorMaterialXXXXXX keywords to sort and categorize the armor. TAWOBA SL Aroused and Survival.pas Automates a large portion of adding SLA and SLS keywords to armor. Instructions for using the xedit script: The Xedit script searches the armor's name for keywords to determine what SLA keywords are applied. The SLS keyword "_SLS_BikiniArmor" is applied to every piece of armor. The SLA keyword "EroticArmor" is applied to any match when the armor's name contains one of the following words boots thong pants bikini skirt thigh harness "SLA_BootsHeels" gets added to any piece if armor with the words "boots" in its name. "SLA_ThongLowleg" added with "thong" in its name. "SLA_MicroHotpants" added with "pants" in its name. "SLA_MiniSkirt" added with "skirt" in its name. "SLA_ArmorHarness" added with "harness" in its name. "SLA_Brabikini" added with "bikini" and "top" in its name. "SLA_ArmorHalfNakedBikini" added with "bikini" and "top" but not with "dwarven" in its name. Feel free to modify and share! Submitter jbezorg Submitted 05/11/2021 Category Other Requires Sexlab Aroused Redux, Sexlab Survival Regular Edition Compatible Yes