Skimpy Armour Keyword Editor 1.0.0b

The Skimpy Armour Keyword Editor is a visual tool used to create or edit RobCo Patcher .ini files for use with the Skimpy Armour Keyword Resource (SAKR). The goal is to allow for quick edits of existing files without recreating the entire .ini or editing it manually by hand.

Key Features
 

• Visual editor for quick keyword injection and editing.
• Generates new .ini files on the fly.
• Toggles to show/hide Top or Bottom keyword sections
• Accepts a .csv from Rubber Duck's SAKR RCP Tool and/or an existing RobCo Patcher file (.ini or .txt).
• Using both the .csv and .ini will adjust the RobCo Patcher file to match what is currently in the mod. E.g., Version 2 of Eli's Armour Compendium added several clothing items requiring keywords.
• Validates all SAKR keywords and merges data from multiple sources. First entry wins, while others are discarded (duplicate handling).
• Hover tooltips on every keyword explaining its meaning and use. E.g., Difference between a tank top and halter top.
• Native support for high DPI displays.
• Options to either copy-and-paste the generated .ini or download it at the press of a button.
• Features a console to display script logic and troubleshooting info.
• No internet connection or server-side processing required—runs entirely offline in your browser.
• Heavily commented styles and code to enable customization.
• Designed to fit seamlessly into Rubber Duck's SAKR/RCP Gen toolset and processes.

Requirements

Modern browser (e.g., Chrome, Firefox, Edge).

Compatibility
 

• Works with .csv exports from Rubber Duck's SAKR/RCP Gen tool.
• Compatible with RobCo Patcher .ini files formatted for SAKR.
• Handles multiple input files, with first-wins merging.

How to Use

The Skimpy Armour Keyword Editor works in conjunction with Rubber Duck's SAKR/RCP Gen tool and the associated SAKR/RCP Gen User Guide.
 

This tool specifically replaces steps 4 to 6 of the guide's process, which we focus on below:

• Double-Click on the HTML file to open it in your browser.
• Drag-and-drop source files (.csv, .ini, or .txt) into the Drop Zone or click to select desired files. A list of all files will appear.
• Click on Process to activate the Manage and Export tabs.
• Click on the Manage tab and adjust as necessary. You can confirm that changes were registered by going into the Console tab (useful for troubleshooting).
• Once satisfied with your changes, Click on the Export tab.
• Optional: Adjust the load order prefix. This is only required for specific edge cases (e.g., ESL patching) and should generally remain blank.
• Look over the generated preview.
• Click on Download to get a copy.

Follow the rest of the steps from the SAKR/RCP Gen User Guide to integrate with your existing RobCo SAKR infrastructure.

Frequently Asked Questions

Why does this exist?
I was looking for a way to change RobCo Patcher .ini files without creating an entirely new .ini or editing the file manually.

For example, Vtaw Wardrobe No. 8 features a fantastic body harness and corset. Both fully expose the breasts, but SAKR registers them as being covered. With this script, I can quickly make a change and test the change in-game within minutes.

Why is this in HTML?

There are several reasons to create an HTML/CSS/JavaScript solution:

• Modern web-browsers easily handle large tables that adjust dynamically to displays.
• Documents can be quickly compared with one another using Browser Tabs.
• CSS makes it straightforward to adjust the style.
• This script has ZERO requirements beyond a browser.
• No need to install anything.

How do I de-select a radio button?

Click on the already-selected radio button again. It acts as a toggle and will clears the selection for that keyword group.

Why can't I select multiple options in the same group (e.g., Bra Normal + Bra Micro)?

The radio buttons are designed that way on purpose. The goal is to prevent mutually exclusive keywords from being applied. I.e., A bra cannot be normal, bikini, and micro at the same time, but it can be normal and sheer.

Can I host this somewhere?

Yes. The permissive license allows for such use, and a webserver will treat the contents as static HTML.

Why would I need to provide a load order prefix?

It helps with RobCo Patcher when patching an ESL. Unless you need this particular capability, I recommend steering clear of it and using the default 6-digit FormID. Invalid prefixes are skipped silently.

Script is showing fewer changes than I've actually made?

Changes are measured by item (line), not individual keywords applied.

Why is there a console?

The console is primarily a debugging tool. It will also list reasons why certain decisions were made, such as:

• Clothing item dropped because it does not exist within the .csv.
• Keyword was dropped because it was not valid.
• That multiple entries were found with keywords for the same item.
• That the Load Order prefix was dropped due to not being valid.

Can I change the look and feel?

Yes. Simply adjust the CSS styles to suit your needs. These are located near the top of the HTML document.

What if I want a French or Russian version?

This script can be translated and contains all language-specific elements within two constants:

• LANG. Contains language related to the look, feel, and code:
  • HTML.* Language elements found within the HTML itself.
  • SCRIPT.* Language found within the JavaScript Code.
  • LOG.* Language used for logging of operations and tasks.
• TOOLTIPS. Descriptors applied directly to the table when editing keywords. These were kept separate due to their integration with other SAKR elements.

Can I fork the code?

Yes. The license and code were specifically designed to allow for it.

A Special Thanks To

I would like to thank Rubber Duck for his tool and guide that made SAKR repositories a reality.

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.