DigitalVixen Core

- Introduction -

This mod only contains functions for some of my other mods, such as a centralized place to set hotkeys. Only download and install if required by another mod of mine.

This mod now also contains Cyberware and Injectors for my Shattered Chrome and Chrome Plating mods. They will show up at Ripperdocs inventory even without those mods installed but if you have no use of them they are benign and don't do anything just sitting there.

Now also contains various APIs useful for my other mods - and whichever other mod may want to use them!

Since 4. 3. 0 it also holds the item database for my mods - one place that knows what a piece of gear is (carry capacity, holster slots, armor, etc), with an in-game editor - and it draws the tooltip lines my mods add to items.

TL;DR - Stuff my other mods needs to survive!  (✿◠‿◠)

- Translation Layer -

I'm consolidating all my translations into this one mod, this means that as a translator you can do all your work to translate my mods in one single place. Unfortunately, this is manual work which takes a lot of time to do - especially with as many options as I have in some of my mods, but it will be done.

- Translation Instructions -

a) First create the following folder structure someplace that isn't in the installed mod (it will simplify packaging) for the mod you wish to translate:

r6\scripts\DigitalVixenCore\translations\<ModYouWishToTranslate>

b) Next you open the <language>.reds file found in that directory in the live mod, place it in your new folder structure.

c) Next open the file and start translating!

d) Now that the translation process itself is done, it's time to pack up the mod so you can install it. It's easy, just a few more steps!

To create the translation mod itself: (this is for W10, W11/Linux/etc might be different):

1. Right click the r6 folder in your own folder structure.

2. Select "Send To".

3. Select "Compressed Zip Folder".

4. Name the Zip file something appropriate, such as "SarahsTranslation-CE-SE-v4. 8. 3.zip" - it's a good idea to use the same versioning as the version of the mod you're translating.

5. You can now install the Zip as a new mod in MO2 or Vortex, load it after my mod and that should be it!

6. Additionally you're more than welcome to upload the translation to the Nexus as long as it only includes the translated file.

Lastly - thank you so much for your contribution!

- Options -

The mod hosts the hotkey settings for my mods, all in one place. As of 4. 1. 0 they live in my Redscript Config Framework hub: press F8 in-game (or use the Configure Mods button in the main menu), open DigitalVixen Core, and every installed mod of mine has its own hotkey section. Keyboard and gamepad bindings are both supported, and Mod Settings is no longer needed for any of it.

Modifier keys: Every hotkey can take a modifier you hold while pressing it. There is one modifier slot per hotkey, so it belongs to whatever device you bind it on: bind a keyboard key and it gates the keyboard hotkey, bind a controller button and it gates the controller hotkey. The other device's hotkey keeps firing on its own.

Tracker Status window: Optional, needs RedWindows.

A live diagnostics overlay for troubleshooting: open DVCore Tracker Status from the RedWindows dock to watch what the trackers believe right now - player state, cyberware regions, every worn piece with its item-database row, active scenes and workspots, item gate. Game stays unpaused.

Item Editor window: Optional, needs RedWindows (and RedFunctions to save).

Open DVCore Item Editor from the RedWindows window manager. It lists what you're wearing in two sections - the Equipment-EX outfit and the vanilla slots - with each piece's facts listed (carry, holsters, armor, style, faction, head/face cover, footwear). Click a piece, pick values from the dropdowns, SAVE ROW: only the columns you changed go into r6\storages\DigitalVixenCore\itemfacts.user.json, the database reloads, and FAC Carry Capacity / Chrome Plating / Street Sense pick it up on their next scan. The Pattern field is the record path by default - shorten it to a prefix (e.g. Items. Jacket_01_) to cover every colour variant. REMOVE USER ROW reverts to the shipped data and heuristics. Shipped file is different from the edited file so updating i