Search the Community

Skimpy Armour Keyword Injector View File A FO4Edit script that injects Skimpy Armour Keyword Resource (SAKR) keywords into patched copies of relevant Armour (ARMO) records. This process uses the existing RobCo Patcher .ini infrastructure as the source of keywords, but does not require RobCo Patcher. Key Features Accepts your entire load order (every single loaded plugin) in one go. Creates the patch, adds all required masters, and injects keywords in a single run. Uses your existing RobCo Patcher .ini files. Requires no new tools to run. Creates a tiny, ESL-flagged patch. Typically under 500 KB for a setup with 400 mods. Fuzzy FormID matching. Works regardless of load order, ESL flags, or overrides. Pre-emptively adds required masters to ensure compatibility with other keyword injectors such as Armour and Weapon Keywords Community Resource (AWKCR) and Complex Item Sorter. Creates a new patch file per run to avoid keyword drift. Recommended for consistency when .ini files change. This requirement can be bypassed if the patch is already loaded in FO4Edit. Extensive, configurable logging. Uses dialogue boxes to notify the user of abnormal runs. E.g. No keywords to inject or nothing to patch. Zero performance impact in-game as the patch is generated by FO4Edit beforehand. Why This Exists Skimpy Armour Keyword Resource was designed to work with RobCo Patcher, which adds keywords at runtime. But: The Next-Gen Update (2024) broke RobCo Patcher. Users waited months for the Next-Gen alpha version of the patcher. The Anniversary Edition has an alpha version of the patcher. This script removes RobCo Patcher from the equation entirely while leveraging the existing configuration files. No more waiting. No more runtime overhead. Just SAKR support. Requirements FO4Edit. Tested on 4.1.5f. Skimpy Armour Keyword Resource (SAKR). Required in your load order. Rubber Duck's SAKR Repository, or NGamma's SAKR RobCo Patches or Equivalent. Provides the required keywords to inject. How to Use Install the script under Scripts in your FO4Edit install. (Optional) Install the blank .esp if you use a mod manager. Do NOT load ZZZ_SAKR_Direct_Injection.esp when starting FO4Edit. If loaded, the script will remind you of this requirement and allow you to bypass if desired. In FO4Edit: Press Ctrl+A to select all plugins. Right-click on any mod and Apply Script. A new window will appear. Choose Fallout4 - SAKR Direct Injection vX.X.X and click OK. Wait ~60–90 seconds (tested with 400+ loaded mods and 2.5M records). Save. Let your mod manager (Vortex/MO2) deploy the new patch. Run the game and go try on some outfits! Tip. For testing, select a few clothing mods to speed up script processing. Cleanup After Use A normal run adds several masters to ensure the winning record is copied and injected. It is recommended that you: Save ZZZ_SAKR_Direct_Injection.esp; Right-click on the mod and select, Clean Masters to remove unnecessary masters. While optional, the above keeps the patch tidy and avoids Missing Masters warnings when changing your mod order within a mod manager. Confirmation Tests The screenshots on the download pages outline various scenarios to confirm the patch works. These tests cover ESLs, base-game items, heavily overridden packs (preview patches), and exposure score changes. Shot in Kziitd Fetish Toolset. Result 100 % skimpy because that mod has no .ini in the Rubber Duck repository. Shots in a Vtaw Wardrobe 6 bikini with or without the top. Highlights the changes in exposure levels and scores. Shot in a COCO Bikini Collection showing exposure and scores change, indicating the .ESL was successfully patched. Shot in Summer Shorts with appropriate scores. Showing that base-game clothing items were successfully patched. Shots in various Vtaw Wardrobe 6 clothing with varying scores. Additionally some are blurry as they triggered Exhibitionist Streak from Provocative Perks because the player is not skimpy enough. Frequently Asked Questions Do I need RobCo Patcher installed? No. This script does not require RobCo Patcher to be installed and the patch negates its requirement for use with the Skimpy Armour Keyword Resource once generated. Will this break if I add new outfits later? No. Just re-run the script — the new items will be included in the patch automatically assuming you have associated RobCo Patcher.ini files to inject the keywords. Why does it stop if the patch file is loaded? There is no reliable way for FO4Edit to unload and remove a mod while loaded. To prevent corrupting the patch, the script confirms the patch is unloaded prior to generating a fresh patch. However, you can opt to bypass this check entirely at the risk of introducing keyword drift over an extended period of time. There are legitimate reasons for doing so: You accidentally ran the script against a mod with no clothing items. You prefer to be surgical in your application of the patch and run it for individual mods or collection. You are trying this for the first time and the default patch (empty by default) is loaded. You manually cleaned the patch yourself and want to proceed. For the above, you will simply be given an option to proceed. I hate getting asked if I want to continue when the patch is already loaded. You can disable this check entirely by setting bFORCE_CLEAN_ESP to False in the script. However, this may lead to keyword drift, especially if you are fine-tuning the .ini files to suit your gameplay. Can I keep the old patch and append changes? Yes. See above. Is this safe with 500+ plugins? Yes. Tested with 500+ mods / 3.2 million records. Process took under 180 seconds to generate a clean patch, but the time required varies based on system specifications. Will it work on Anniversary Edition? Yes. While not explicitly tested on Anniversary Edition, FO4Edit 4.1.5f which was used to develop this script fully supports that version. I still want to keep RobCo Patcher for other features (material swaps, slot masking, etc.) This script does not stop you from continuing to use RobCo Patcher. Both can coexist perfectly, but to prevent duplicate keyword injection, simply delete or move the RobCo Patcher .ini files used for SAKR keywords. Bonus side-effects of removing those .ini files: RobCo Patcher has fewer records to process reducing runtime overhead May reduce the chances of RobCo Patcher crashing. Is this compatible with Armour and Weapon Keywords Community Resource (AWKCR) and Complex Item Sorter? Yes. The script will add these as masters and carry forward any modified or injected keywords. However, this patch needs to be lower in your load order override their records. Some of my clothing packs have no .ini file for it. How can I make these? Rubber Duck has made a SAKR RCP Tool that generate the RobCo Patcher files along with extensive documentation. I keep seeing Error Assigning To and Mapping Errors in my logs. Message such as the one below occurs because the script cannot know for certain every mod that it will need to add a master. Error assigning to [ \ [FA] ZZZ_SAKR_Direct_Injection.esp \ [1] GRUP Top "ARMO" \ [77] Armor_Synth_Underarmor "Synth Uniform" [ARMO:0012B91D] \ [19] Object Template \ [2] Combinations \ [34] Combination \ [2] OBTS - Object Mod Template Item \ [8] Keywords \ [0] Keyword #0] from [ \ [A7] Synth_Fem.esp \ [4] GRUP Top "ARMO" \ [2] Armor_Synth_Underarmor "Synth Uniform" [ARMO:0012B91D] \ [19] Object Template \ [1] Combinations \ [34] Combination \ [2] OBTS - Object Mod Template Item \ [8] Keywords \ [0] Keyword #0]: [Exception] Load order FileID [A5] can not be mapped to file FileID for file "ZZZ_SAKR_Direct_Injection.esp In such cases the keywords will not be injected. However the Script naturally takes precautions to avoid this: Preemptively loads any non-ESL flagged ESM/ESP as a Master. This will cut out most of these errors. Provides an ability to add a custom list of masters. Update the sADDMASTERS constant to include a comma delimited list of additional mods you need to load as masters. Between the above, the script should all relevant masters, and inject keywords without fault. Can I modify or fork your code? Yes. The script is released under the two-clause BSD licence which is a permissive free software licence. Configurable Items The following constants may be changed to alter the script's behaviour. You only need to touch these constants if you have a very custom setup. Most users will be able to ignore these options entirely. There are listed in alphabetical order. bADDALLMASTERS Default: True Automatically adds all non-ESL flagged ESP and ESM files with ARMO records as masters. This ensures that injection will occur most of the time. Tip. Clean up the loaded masters in the mod after running the script and saving the contents. sADDMASTERS Default: '' A comma delimited list of mods that need to be mastered beyond those added as part of the standard script processing. This constant becomes critical when disabling sADDALLMASTERS. iDEBUG_LEVEL Default: DEBUG_INFO Adjust the level and verbosity of logs generated. Available levels are: DEBUG_FATAL DEBUG_ERROR DEBUG_WARN DEBUG_INFO DEBUG_VERBOSE DEBUG_PATHING bDRYRUN Default: False Kept for historical reasons. With a patch-file workflow there are no risks to the game and other mods, but it remains useful for pathing. bESLFLAG Default: True By default the ZZZ_SAKR_Direct_Injection.esp will be created as an ESL-flagged ESP. This means that the patch will not tie up a slot on your limited load order at the cost of reduced entries. Set to False if you need to inject keywords into more than 4095 items. bBALLISTIC Default: True Injects Ballistic Weave related keywords to the item in addition to SAKR. This can be useful for certain mods that expect this slot to exist for their own use and increase available clothing items. bFORCE_CLEAN_ESP Default: True Deletes and recreates the patch every run. Prevents drift when .ini files change. Set False if you prefer incremental patching on selected mods. sLOGFILE Default: '' Set the path of an external file that the log will be written to. iMERGE Default: False By default the script will drop any conflicting keyword injection. This prevents situations where a competing .ini has conflicting keyword injections to make. Any such conflicts will be logged at the end of the process to identify and sort out conflicts. If set to `True` the script will merge the conflicts together into one line. However, there are potential risks. A perfect example of this is Eli's Armour Compendium and Classy Chassis Outfits - Eli's Armour Replacer. The former includes lore friendly and non-lewd clothing items, whereas the latter will spice things up. They both use Eli_Armour_Compendium.esp and a matching identifier leading to the following situation where an item now has keywords for: 0000081A. Top Full 0000081E. Tank Top 00000821. Top Tight 0000080E. Pants Long 0000080F. Pants Shorts The above contains clearly contains keywords that are at odds with each other and should not co-exist. The resulting score will be wildly off from expected behaviour. Hence merge mode is provided for advanced users who understand the risks. When set to False the script generates a report at the end of the run. This permits you to find and correct these conflicts to ensure the desired outcome. sPATCH_ESP Default: ZZZ_SAKR_Direct_Injection.esp Name of the generated patch. ZZZ prefix keeps it at the bottom of the load order. iRECURSION Default: 5 Maximum directory depth when scanning for .ini files to prevent infinite loops. sROBCOPATH Default: F4SE\Plugins\RobCo_Patcher\armor\ Default location of RobCo armour .ini files (overridden by sSCANPATH if used). bSAKRSTATIC Default: False Use static keyword list (True) or read directly from SAKR.esm (False). False is the default as it adjusts to future releases of the mod. sSCANPATH Default: '' Hardcoded location for the RobCo Patcher .ini files. Use '' to use game defaults. sSAKR_ESP / sGAME_ESP / sPATCH_AUTHOR Self-explanatory and should never need changing. License  * * Copyright (c) 2025, M.S.M. Foster * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions are met: * * 1. Redistributions of source code must retain the above copyright notice, this * list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * Submitter msmfoster Submitted 11/28/25 Category Modders Resources Requirements FO4Edit. Tested on 4.1.5f. Skimpy Armor Keyword Resource (SAKR). Required in your load order.  

Devious Devices - KID Keyword Patches [AND+ORF+TNG] View File KID files that distribute keywords in order to integrate devious devices into different mods, or at the very least make them work better together Patches Devious Devices for the following Mods: (if you want to know what these mods do, go read the descriptions on their respective mod pages) Outfit Recognition Framework (ORF) Advanced Nudity Detection (AND) The New Gentleman (TNG) Frostfall (FROST) - WIP Covers Devious Devices from the following Mods Devious Devices + NG (Duh) - ORF + AND + TNG + FROST Lauras Bondage Shop - ORF + AND + TNG Devious Eyecandy - ORF + AND Deviously Vanilla - ORF + AND Devious Curses- ORF + AND + TNG Unforgiving Devices - ORF + AND + TNG Unforgiving Skyrim - ORF + AND Dagoth Ur - ORF + AND Deviously Pink - ORF + AND F.A.Q. How do I install? 1. Install Keyword Item Distributor (you should already have this if you use any of these mods) 2. Install my mod with your preferred mod manager 3. Profit There is only one file, do I need to use all of these mods? Nope, I am just lazy and don't want to repackage or learn how to make FOMODs. if you don't have one of the mods listed nothing will break, KID will just skip those keywords or devices. Why is this a Beta? There are a LOT of devices, I did my best to make sure I covered everything correctly but I want some feedback before I consider it stable Hey this isn't right!? No worries! Let me know, feedback is very welcome. if there is an issue with a specific device, PLEASE share the editorid for the device in question so I can review it To find an editorid, 1. install More Information Console 2. use `~` in game to open console 3. select your PC 4. go to equipment (use `shift` to select a menu option) 5. look for the text of an item that matches the device you want to report But I want this mod covered!? there is no need to yell... Also no worries, let me know and I will add it to my list to consider Frostfall Methodology This is subjective to an extent, let me know if you have thoughts but please to provide reasoning. I tried to make it "immersive" but fair. Latex (ebonite) is naturally very warm, it retains body heat really well so these get high levels of warmth and coverage Leather is a step down from its latex variant for warmth and coverage Items of similar type but with openings, for example, hobbledress vs hobbledress cleavage... generally have about the same warmth but less coverage Body slot items like yokes, rope, and boxbinders contribute nothing to warmth Keywords covered by other Mods Baka Aroused Keywords (KID files provided in bodyslide archive) CC Survival Mode Change log 1.0.3 (Beta 4) Added Dagoth Ur follower for funzies Added Deviously Pink (Untested, feedback would be nice) Added ORF_Pink to some core items 1.0.2 (Beta 3) redid some of the catsuit lines to make sure nothing was missing in DD_AND, as I noticed the same dark red items were missing from this file. Added Hobbledress, Straitjacket - hobbledress, straitjacket - catsuit, rope full, and yoke to DD_FROST 1.0.1 (Beta 2) Added Dark Red items that were missing ORF_Red Added some Frostfall keywords to catsuits and boxbinders Submitter Ondine. Submitted 11/15/2025 Category Adult Mods Requirements Regular Edition Compatible Install Instructions  

Strip What You Must - abandoned View File What this mod does: Provides six coverage keywords to indicate what sensitive body areas are blocked by an equipped item. These keywords are injected into the 01xxxxxx address space (update.esm), and so can be incorporated into any game with no heavy requirements. 01010800: BlocksOral (masks and gags by default) 01010801: BlocksVaginal (clothing/armour/belts/plugs) (basically, blocks insertion) 01010802: BlocksAnal (clothing/armour/belts/plugs) 01010803: BlocksBreast (any coverage) 01010804: BlocksGrope (breasts, armor or other rigid covering only) 01010805: BlocksSpank (rigid armor, not cloth or short skirts) 01010806: BlocksClutch (crotch, rigid coverage, protects pussy/penis) Sorry, I couldn't come up with a better term! I tried "grab", but too close to "grope"! Provides patches for all vanilla outfits, as well as those modified by various common mods. Additional patches are easily created, and can be simply merged. Includes two simple functions which are DD-aware but do not require DD: SWYM.Report: returns whether one or more areas are blocked SWYM.Strip: removes only those items blocking one or more of the areas, as selected The Strip function respects DD's Quest and BlockGeneric keywords, removing only generic items, with keys found on either of two actors passed to the function The reasoning: There are certain coverage/accessibility checks that are needed by many mods: Is a character's mouth free (for eating or dialogue)? Are various openings or regions "accessible" for sex? If not, can we use a limited stripping routine to remove just those items necessary to make a particular location accessible? Is a character "indecently" exposed, for crime checks, for modified dialogue, etc.? Is a character sufficiently exposed to permit groping, spanking, etc.? Trying to determine these things case-by-case based on occupied slots is challenging, since different clothing and armor items can be inconsistent in their slot use, and in what coverage is really represented by such use. "Slot 32" full body outfits can vary from full plate to a bikini. Some items have keywords to indicate less-than-typical coverage (EroticArmor for instance, or the various "PermitsXXX" tags in DD), but these keywords are mod-dependent, still rely on first checking whether some "standard" slots are occupied, and also can not be simply checked on a whole-actor basis - a "Sexy" keyword on an item means nothing if that item is hidden underneath non-revealing armor. Instead of keywords to indicate exposure, what is needed are keywords that indicate an area is blocked. If an area is covered by one or more items, a simple and quick WornHasKeyword will indicate this, and no other items can make the actor less exposed. The problem, of course, is that most items do not have these keywords... and that such keywords, to be universally useful, must not be tied to heavy dependencies. Hence injecting the keywords into update.esm - and this injection can be duplicated in multiple mods without harm, resulting in no hard dependencies whatsoever. I had intended just to provide the keywords, but as a proof-of-concept produced the Report and Strip functions. These can be used by other mods, or can be replaced by better ones of course. I am hoping people will have suggestions, ideas, or better ways of doing things. This framework is supportive, but useless on its own! Installation: I recommend a mod manager, of course. SWYM can be dropped into a running game. Uninstallation: I do not recommend removing mods from a game in progress; this mod can be ignored and will have nearly no impact on a game. If you must, remove and clean your save. But by itself, there is NO reason to install this, it is a resource for other mods. There are four files provided: SWYM: the Report and Strip functions. Also includes keywords. swymMCM: an MCM I used for testing, ugly and clunky. You don't need this, but can use it to try out the Report and Strip functions if you wish (only on the player). lgKeywords: a bare-bones file that does nothing but provide the keywords. This can be used as a base for additional patches. It is not needed by itself. SWYM_keyword_patches: a collection of .esp files which add keywords to clothing/armor provided by vanilla/DLC/mods as shown below. Use only those you need, placing them below the files to be patched (though I recommend merging, or at least doing bashed patches & TES5Edit merges). More must be added! How these keywords connect to clothing & armor, how I've interpreted them: The interface of SWYM (the API!): Acknowledgements: Thanks to lupine00 for the original idea of using blocking keywords, to HexBolt8 & Corsayr for keyword advice, and Kimy for helpful pointers to DD functions that are called by Report and Strip., and Monoman1 for the method of more careful soft-dependencies (for which I apparently owe thanks to lupine00 also). Other notes: I do not have SE, and assume these files are not compatible with SE, but I suspect they should be easy to adapt. The current patches reflect what I happened to have installed. It is easy to add more keywords for more mods - I can do so, but so can anyone, and I will gladly add any such patches to this collection. At this early stage, it is still quite possible to change the keywords, or add new ones though I am cautious about adding many keywords for every possible Blocking region. The current patches do NOT reflect any mods that change meshes to make armor more revealing than standard. For the most part these particular regions are probably still correct, but we could have patches for different armor replacers, for instance. The main patch assumes all 3 DLCs, since they are included with Legendary Edition. These can be split, if there's a need. Submitter legraf Submitted 01/11/2020 Category Modders Resources Requires Legendary Edition, SKSE (for the functions only) Special Edition Compatible No

SunJeong Aroused Patches KID View File Patches for armor mods published on SunJeong website to work with Sexlab Aroused Redux SE BakaFactory Edited Version/OSL Aroused/SLAX. TAWOBA and Ninirim included. All keywords are hand picked. Requirements: You'll need at least one armor mod from SunJeong website, or Nexus page. OSL Aroused or Sexlab Aroused Redux SE BakaFactory Edited Version or SLAX SE conversion by MasterDev Keyword Item Distributor (KID) Submitter Sausage Satan Submitted 03/08/2025 Category Adult Mods  

Devious Survival Compatibility Tweaks View File This mod aims to improve user experience for Survival Mode mechanics when used with Devious Devices attire. Problem is Devious Devices are not usually recognized as clothes or armor and so they do not provide warmth (or coverage) as far as Survival Mode is concerned. Player may be covered from head to toe in DD and still be recognized as naked from Survival Mode's point of view, succumbing to cold in minutes. Although DD aren't the most warm outfits according to their looks, they still should provide at least some resistance to elements. For mod compatibility list and future plans see Roadmap section below. Feel free to bring my attention to the mods you would like to get DD-Survival compatibility in the Support Thread. Requirements Hard - None. Lacking any or all Soft Requirements will not break the game, just will not inject keywords related to outfit warmth. Soft - Keyword Item Distributor (KID) - Unforgiving Devices - Creation Club Survival Mode Installation Use Mod managers or unpack archive into Data/ directory of the game. Conflicts Probably mods which assumes that Devious Device items are not Armor nor Clothing. Roadmap Completed - Unforgiving Devices + Creation Club Survival Mode - Catsuits and Corsets - Devious/Unforgiving Devices Patch + Creation Club Survival Mode - Laura's Bondage Shop + Creation Club Survival Mode - Ebonitium + Creation Club Survival Mode - Deviously Pink - Elvira's Restrictive Fashion shop + Creation Club Survival Mode WIP - Devious Devices TODO - Frostfall - Hypothermia Camping Survival - SunHelm Survival and needs (Probably already working, since it uses CC Survival Mode's keywords) - Survival Mode Improved - SKSE (Probably already working too as it also uses CC Survival Mode's Clothing warmth mechanics) How it works Creation Club Survival Mode The game looks for the following keywords on player's equipped items: - ArmorHelmet / ClothingHead - ArmorCuirass / ClothingBody - ArmorGauntlets / ClothingHands - ArmorBoots / ClothingFeet If no additional Survival_* keywords are found on the item, it will be assigned default warmth value. If item also has Survival_ArmorCold or Survival_ArmorWarm keywords, it will get ArmorCold or ArmorWarm warmth value from the table below respectively. Slot = <ArmorCold, Default, ArmorWarm> Head = 8 , 18, 29 Body = 17, 27, 54 Hands = 7, 13, 24 Feet = 7, 13, 24 Slot does not matter as long as Armor* or Clothing* keywords are assigned. License GPL v3 Credits - Devious Devices creators and maintainers - SexLab Disparity by Lupine00 for inspiration - powerofthree, creator of KID and SPID among many other things - ihatemykite, creator of Unforgiving Devices Submitter xcvbs Submitted 09/17/2024 Category Adult Mods Requirements Keyword Item Distributor (KID), Devious Devices, Unforgiving Devices Regular Edition Compatible No  

Hi, I was looking at BakaFactory's Aroused mod. It contains some new keywords, which needed to be added to Armors. I have never done that before but the guide was good enough. However, check out this: The Panty (and every other armor) has all the basic keywords, like ClothingHand, ClothingFeet. Is this normal? Or the modder was just lazy? Thanks, M