Give Feedback
Note: Configuring the JSON is completely OPTIONAL. This is only for people who want to fine tune how bodies get distributed. If you don't do anything to the JSON, OBody NG will work just fine all the same! Presets will get distributed randomly and you can manually change the presets ingame whenever you want, as per the usual.
If you want to proceed with configuring the JSON, READ THIS GUIDE CAREFULLY! If you configure this file improperly, OBody may stop working or you may get CTDs!!
PLEASE NOTE that NPCs who were already assigned a preset in your current save will keep that preset, even if you set a rule in this file for that NPC, UNLESS you use the Reset presets options in the MCM!!
If you are starting a New Game, you don't have to worry about that.
OBody NG ships with a JSON file where you can customise how OBody will distribute your presets! This can be done by going to the virtual folder where Vortex or MO2 installed OBody, and then opening the folder SKSE > Plugins, and open the OBody_presetDistributionConfig.json file.
Alternatively, if you installed the OBody NG Configuration Files under Optional Files section, the config file will be there instead!
Note that while JSON may seem scary at first, it's actually very easy to learn. JSON is not coding, contrary to popular belief. It's a text standard that is easily readable by humans and machines. By following this guide, you will learn JSON quickly and realise how easy it is configure.
The OBody JSON configuration file comes with the following default config:{
"npcFormID": {},
"npc": {},
"factionFemale": {},
"factionMale": {},
"npcPluginFemale": {},
"npcPluginMale": {},
"raceFemale": {},
"raceMale": {},
"blacklistedNpcs": [],
"blacklistedNpcsFormID": {},
"blacklistedNpcsPluginFemale": [],
"blacklistedNpcsPluginMale": [],
"blacklistedRacesFemale": [
"ElderRace"
],
"blacklistedRacesMale": [
"ElderRace"
],
"blacklistedOutfitsFromORefitFormID": {},
"blacklistedOutfitsFromORefit": [
"LS Force Naked",
"OBody Nude 32"
],
"blacklistedOutfitsFromORefitPlugin": [],
"outfitsForceRefitFormID": {},
"outfitsForceRefit": [],
"blacklistedPresetsFromRandomDistribution": [
"- Zeroed Sliders -",
"-Zeroed Sliders-",
"Zeroed Sliders",
"HIMBO Zero for OBody"
],
"blacklistedPresetsShowInOBodyMenu": true
}
As I said previously, this might seem weird and scary, but it's actually pretty simple. This guide will literally hold your hand on how all of this works.
The default text above, all it is doing is telling OBody to NOT randomly distribute the Zeroed Sliders preset, to blacklist the ElderRace from random distribution, and to show the Zeroed Sliders preset when you open the O menu. Nothing else. Let's go step by step on each key of the configuration to see what each one does!
npcFormID: Here you can set which presets should be applied to specific NPCs by their FormID. The FormID is their unique identifier. Works with modded NPCs!
npc: Same as npcFormID, but you use the NPC names instead of the FormID.
factionFemale: Here you can set which presets to distribute by faction for female NPCs.
factionMale: Same as factionFemale, but for male NPCs.
npcPluginFemale:: Here you can set which presets should be applied to female NPCs from a specific plugin/mod.
npcPluginMale:: Same as npcPluginFemale but for male NPCs.
raceFemale: Here you can define which presets should be applied to females of certain races. Works with custom races too! ONLY put female body presets here!
raceMale: Same as above, but for males. ONLY put male body presets here (if you don't have any, leave it empty)!
blacklistedNpcsFormID: Set which NPCs by their FormID should be ignored by OBody. Works with modded NPCs. Useful if you want modded NPCs to have a custom body you want to handle separately.
blacklistedNpcs: Same as blacklistedNpcsFormID, but you use NPC names instead of the FormID.
blacklistedNpcsPluginFemale: Here you can blacklist all female NPCs from an entire plugin/mod by simply writing the plugin name.
blacklistedNpcsPluginMale: Same as blacklistedNpcsPluginFemale, but for males.
blacklistedRacesFemale: Here you can blacklist females of entire races instead of individual NPCs.
blacklistedRacesMale: Same as blacklistedRacesFemale, but for male NPCs.
blacklistedOutfitsFromORefitFormID: Here you can write outfit FormIDs if you don't want ORefit to be applied to them. Further details and explanation is available further below.
blacklistedOutfitsFromORefit: Same as blacklistedOutfitsFromORefitFormID, but you use outfit names instead of their FormID.
outfitsForceRefitFormID: Here you can write outfit FormIDs if you want to force ORefit to be applied to them, in case ORefit can't detect them. Further details and explanation is available further below. You will not need to write anything in this key 99% of the time.
outfitsForceRefit: Same as outfitsForceRefitFormID, but you use outfit names instead of their FormID.
blacklistedPresetsFromRandomDistribution: Should be self explanatory. Set the presets you do NOT want OBody to distribute randomly.
blacklistedPresetsShowInOBodyMenu: Whether you want the blacklisted presets to show in the O menu or not.
Note that these rules only apply to the AUTOMATIC distribution by OBody NG. If you try to set a preset manually through the O menu, the rules are ignored!
You should NEVER delete any of these keys. IF you don't want to edit certain keys, leave them as they are, empty, or else it might cause problems or crashes!
Before we get into how to actually edit these values, let's take a look at some important notes before we begin.
What is a FormID?
A FormID is a unique hexadecimal identifier that every asset in the game has. They will often look something like 00013BA3, FE000800, etc.
The first two digits indicate the place in the load order. 00 belongs to Skyrim.esm because that is what is always loaded first. The first two digits are mostly irrelevant for our purposes of configuring the JSON.
The following digits are the ID itself of the asset. Leading zeroes can be omitted. This means that 00013BA3 = 13BA3.
These FormIDs can be obtained from UESP for vanilla game assets (example, go to this page in UESP, on the right side you will have all information about Hulda. The FormID is the number on the BaseID row, in this case it is 00013BA3. Do not use the number in RefID!!!).
For both vanilla game assets and modded assets, you can obtain the FormID from SSEEdit. Simply load the plugins you want to check FormIDs for there, and once it's all loaded, you can start looking for the FormID. Example image below shows the FormIDs for some NPCs from Skyrim.esm:
You can also get FormIDs ingame! Open the console and click on the desired asset you want to get the FormID from. Information about the asset will appear. You will want to note down the BaseID, like in UESP.
Please note that for FormIDs, you should also note the name of the plugin which owns the NPC. In the case of Hulda, she is a vanilla Skyrim NPC, so her owning mod is Skyrim.esm. For Serana, her owning mod is Dawnguard.esm. For a modded NPC, their owning mod is, well... the name of the plugin of the mod which adds the NPC.
If you are having a hard time figuring out the mod which owns the NPC, install More Informative Console. This is a staple mod that everyone should have. When you click on the NPC, you will get info of the owning mod. It is the "Base defined in:" field that will appear to the right of your screen when you click an NPC.
Important notes when writing the JSON
1) When putting the preset names, they must be as they EXACTLY appear in the Bodyslide & Outfit Studio preset list!
2) You can blacklist a preset, but assign it in the JSON to an NPC, race, plugin or faction. This gives you much more customisation power!
3) When you're done configuring, run your JSON through this online JSON validator to check for formatting errors. Paste your JSON file content there and click the button Validate JSON at the bottom.
If you prefer an offline solution instead, you can also use a text editor with built-in JSON formatting features. I personally recommend VS Code.
4) OBody NG decides if the NPC is blacklisted or should be applied a specific preset with this algorithm:
It starts by checking if the NPC is blacklisted in the blacklistedNPCs or blacklistedNpcsFormID keys.
If it is blacklisted, stop.
If not blacklisted in those keys, it first checks the npcFormID key.
If not defined there, it will check the npc key.
If not defined in any of the NPC keys above, it will check if is blacklisted in the blacklistedNpcsPluginFemale, blacklistedNpcsPluginMale, blacklistedRacesFemale or blacklistedRacesMale.
If it is blacklisted in those, stop.
If it is not blacklisted in those keys, it will then check the factionFemale or factionMale keys.
If not defined in the factions, it will check the npcPluginFemale or npcPluginMale keys.
If not defined in the NPC plugin keys, it will check the raceFemale or raceMale keys.
If not defined in the race keys, it will pick a random preset to assign to the NPC.
So, in short, the priority order in which the keys are checked are: blacklistedNPCs > blacklistedNpcsFormID > npcFormID > npc > blacklistedNpcsPlugin > blacklistedRaces > faction > npcPlugin > races.
This gives you more customisation power than it might seem at first glance. For example, you can effortlessly blacklist all NPCs from a certain mod with the blacklistedNpcsPluginFemale, and configure presets for a certain NPC from that same mod without blacklisting that NPC. It saves you time and makes configuration very seamless.
Knowing all of this, let's get started on how to edit the keys values!
The "npcFormID" key
Here you can define a preset or a set of presets to be given to specific NPCs based on their FormID and owning mod. After you fetch their FormID and owning mod, you simply have to do something like this:"npcFormID": {
"Skyrim.esm": {
"00013BA3": ["Bardmaid"],
"00013BA2": ["Wench Preset", "IA - Demonic", "Tasty Temptress - BHUNP Preset (Nude)"]
},
"Immersive Wenches.esp": {
"0403197F": ["Petite Mommy"],
"0400C3C0": ["s4rMs' - Gaia"]
}
},
This means that:
- Hulda (00013BA3) will always get the preset Barmaid.
- Saadia (00013BA2) will get either Wench Preset, or IA - Demonic or Tasty Temptress.
- Lyne (0403197F) from Immersive Wenches mod will get Petite Mommy preset.
- Tamda (0400C3C0) from Immersive Wenches mod will get s4rMs' Gaia preset.
Due to leading zeroes not mattering, 00013BA3 could be written as 13BA3, and 00013BA2 could be written as 13BA2. It's up to you. But when copy + pasting IDs, it might be easier to just keep the leading zeroes :)
The "npc" key
It works like the npcFormID key above, but you use NPC names instead of FormIDs. DON'T specify the owning mod of the NPC. Just the name of the NPC.
It is recommended to use npcFormID because there might be NPCs with the same name in your game. But if that doesn't bother you or if you find it easier to work with NPC names, then feel free to use this one.
Note that you must put the NPC names exactly as they appear ingame. So "Mjoll" is incorrect and won't work, but "Mjoll the Lioness" is correct and will work. Same applies to names with hyphenation - "Brand Shei" is incorrect, but "Brand-Shei" is correct!
Let's see a practical example..."npc": {
"Mjoll the Lioness": ["Hardass Warrior"],
"Haelga": ["Petite Mommy", "IA - Demonic", "s4rMs' - Gaia"],
"Temba Wide-Arm": ["Tasty Temptress - BHUNP Preset (Nude)"]
},
This means that:
- Mjoll will always get Hardass Warrior.
- Haelga will get either Petite Mommy, IA - Demonic OR s4rMs' - Gaia. No other preset can be assigned to her by OBody NG.
- Temba Wide-Arm will always get the preset Tasty Temptress - BHUNP Preset (Nude).
The "factionFemale" and "factionMale" keys
Here you can define presets to be distributed based on factions. Factions are objects that NPCs belong to so that the game can identify what they do, in what town they live in, which AI packages to apply, and a plethora of other functionalities.
With this said, this means that NPCs will belong to several factions at the same time. For example, Aia Arria belongs to both SolitudeBardsCollegeFaction and TownSolitudeFaction, because she is in the Bards College and lives in Solitude. So if you defined presets for both the bards faction and the Solitude town faction, which one would Aia Arria get?
The answer is simple: She would get a preset from whichever faction you put first in the factionFemale key. So pay attention to the order of the factions when writing the JSON.
For a full list of factions, I recommend you check them in SSEEdit under the Skyrim.esm plugin (or if you want factions from a mod, check that mod's plugin factions).
In UESP, you can go to any character page and get the factions they belong to. Example for Aia Arria.
Alternatively, you can also check an NPC's factions ingame by using More Informative Console.
Note that for the factions, you will want to put their EditorID! Factions EditorID will look something like this: SolitudeBardsCollegeFaction, CompanionsCircle, VampireFaction, SolitudeBluePalaceFaction, etc.
Let's see a practical example."factionFemale": {
"SolitudeBardsCollegeFaction": ["Hardass Warrior", "Fantasy Figure - Nude", "Royal Battle Maiden - BHUNP"],
"TownSolitudeFaction": ["QC-The Everywoman"],
"CollegeofWinterholdFaction": ["Tasty Temptress - BHUNP Preset (Nude)"]
},
"factionMale": {
"CompanionsCircle": ["HIMBO Muscled"],
"TownWhiterunFaction": ["HIMBO Simple"]
},
This means that:
- Females belonging to the SolitudeBardsCollegeFaction will get either Hardass Warrior, or Fantasy Figure or Royal Battlemaiden.
- Females belonging to the TownSolitudeFaction will get QC-The Everywoman.
- Females belonging to the CollegeofWinterholdFaction will get Tasty Temptress.
- Males belonging to the CompanionsCircle will get HIMBO Muscled.
- Males belonging to TownWhiterunFaction will get HIMBO Simple.
The "npcPluginFemale" and "npcPluginMale" keys
Here you can define presets to be distributed based on plugins. This is an easy way to set a single or several presets for all NPCs from a certain mod. You can even use plugin names from NPC replacers here.
So this brings another problem similar to the factions. For example: Adrianne Avenicci is on the Skyrim.esm plugin since she is a vanilla NPC. But if you use an NPC replacer like Bijin AIO, she will also be present in that mod's plugin. So how does OBody decide?
The answer is the same: It gives priority to what comes first!
Let's see a practical example."npcPluginFemale": {
"Bijin_AIO_Merged.esp": ["Hardass warrior", "SilverR1baka"],
"Skyrim.esm": ["Nordic Oppai - BHUNP - Nude"]
},
"npcPluginMale": {
"Dawnguard.esm": ["HIMBO Simple"]
},
This means that:
- All female NPCs which are in Bijin AIO will get either Hardass Warrior or SilverR1baka.
- All female NPCs from Skyrim.esm will get Nordic Oppai.
- All male NPCs from Dawnguard.esm will get HIMBO Simple.
The "raceFemale" and "raceMale" keys
Inside the "raceFemale" and/or "raceMale" keys, you will first define a new key with the race you want to set presets for. The race name should be as it appears in the Creation Kit. You can also find the name to be used in xEdit. The vanilla race values are as follows:
- ArgonianRace
- NordRace
- HighElfRace
- WoodElfRace
- DarkElfRace
- BretonRace
- ImperialRace
- KhajiitRace
- RedguardRace
- OrcRace
- ElderRace - this is the special race for old people.
Note that vampires are a separate race! You just have to append 'Vampire' at the end of each race name. So a nord vampire would be NordRaceVampire, and a dark elf vampire would be DarkElfRaceVampire. Pretty easy uh?
If you don't define a race inside the "race" key, it means you want OBody to distribute all presets randomly to it (minus the blacklisted presets).
Let's see a practical example:"raceFemale": {
"NordRace": ["QC-The Everywoman", "D*sney Mommy NG", "Fantasy Figure - Nude"],
"OrcRace": ["Hardass warrior"],
"WoodElfRace": ["-Zeroed Sliders-"]
},
"raceMale": {
"NordRace": ["HIMBO Simple"],
"BretonRace": ["HIMBO Simple"]
},
This means that:
- Nord females will only get QC-The Everywoman or D*sney Mommy NG or Fantasy Figure - Nude. No other presets will be distributed to Nord females!
- Orc females will only get Hardass warrior preset. No other presets will be distributed to Orc females!
- Wood Elf females will only get Zeroed Sliders preset. No other presets will be distributed to Wood Elf females!
- Nord males and Breton males will only get the HIMBO Simple preset. No other presets will be distributed to Nord males and Breton males!
The "blacklistedNpcsFormID" key
Here you can blacklist NPCs from being touched by OBody based on their FormID. It works similar to the npcFormID key from before. You put the owning mod of the NPC, and then the FormIDs of the NPCs you want to blacklist.
Let's see a practical example:"blacklistedNpcsFormID": {
"Skyrim.esm": ["00013BB8", "00013BBD"],
"CS_Vayne.esp": ["0400083D", "0402CC59"]
},
This means that:
- Irileth (00013BB8) and Jarl Balgruuf (00013BBD) will be blacklisted from OBody.
- Vayne (0400083D) and Solace (0402CC59) from the Vayne mod will be blacklisted from OBody.
Note that you can still assign a preset to them manually through the O menu.
The "blacklistedNpcs" key
Works the same as blacklistedNpcsFormID, but here you have to put the names of the NPCs you don't want OBody NG to assign presets randomly to them. Do not specify plugin names here.
Here's an example:"blacklistedNpcs": ["Saffir", "Vilja", "Lydia"],
This means that Saffir, Vilja and Lydia will not be assigned a preset by OBody NG when you meet them. You can still assign a preset to them manually through the O menu.
The "blacklistedNpcsPluginFemale" and "blacklistedNpcsPluginMale" keys
Here you can blacklist all NPCs from a plugin in an easy way. Simply write the names of the plugins, like below:"blacklistedNpcsPluginFemale": [
"CS_Coralyn.esp",
"3DNPC.esp",
"Hearthfires.esm"
],
"blacklistedNpcsPluginMale": [
"Immersive Wenches.esp",
"018Auri.esp"
],
This means that:
- All females defined in the mods Coralyn, Interesting NPCs and Hearthfire DLC will be ignored by OBody NG.
- All makes defined in the mods Immersive Wenches and Auri - Song of the Green will be ignored by OBody NG.
The "blacklistedRacesFemale" and "blacklistedRacesMale" keys
This is also straightforward and works similarly to the previous keys. Just put the names of races you don't want OBody NG to assign presets randomly to. Here's an example:"blacklistedRacesFemale": [
"ElderRace",
"ArgonianRace"
],
"blacklistedRacesMale": [
"ElderRace",
"DarkElfRace"
],
This means that:
- All females of the ElderRace (old people) and Argonian race will be ignored by OBody NG.
- All males of the ElderRace (old people) or Dark Elf race will be ignored by OBody NG.
The "blacklistedPresetsFromRandomDistribution" key
Again, also very straightforward and work similarly to the blacklistedNpcs key. Just preset names that you don't want to be randomly distributed. Example:"blacklistedPresetsFromRandomDistribution": [
"- Zeroed Sliders -",
"-Zeroed Sliders-",
"Zeroed Sliders",
"s4mRs'' - Juno",
"Royal Battlemaiden - BHUNP"
],
Make sure the preset names are exactly as they appear in the Bodyslide list, down to spacing, hyphenation and punctuation in general!
The "blacklistedPresetsShowInOBodyMenu" key
Set whether the blacklisted presets should show in the O menu for manual assignment or not. Write true if you want them to appear or false if you don't want to. Examples:"blacklistedPresetsShowInOBodyMenu": true
Or...."blacklistedPresetsShowInOBodyMenu": false
Do NOT put any other values there or the game will crash!!!
The keys relating to ORefit
These settings are more advanced and you shouldn't need to change them if you only use vanilla outfits or if you don't have skimpy/topless outfits.
First, a brief explanation of what ORefit is and how it works. As you may know, ORefit simulates the effect of clothing on breasts, so that when you wear clothes, the boobs get a pushup effect like you'd expect from real life clothing.
Skyrim has many different parts where outfits are applied, which are called "slots". This is why you can't wear Iron Gauntlets and Daedric Gauntlets at the same time - because they both use slot 33, which is for "hands".
ORefit activates when an outfit occupies slot 32 ("body") or slot 46 ("chest primary or outergarment") or slot 56 ("chest secondary or undergarment"). This is more than fine for all vanilla outfits and armors, and for most modded outfits.
However, the slot number and assignment is just a guideline, which some mod authors may not respect. This means that a mod author can make a bikini and make it use slot 33 ("hands"). As stupid as that may sound, it can happen. This is usually not a bug and is intended for various reasons, which I will not elaborate on this article.
In this case, it means that ORefit will not activate if the slots are incorrect, because ORefit expects the outfits to be assigned to their proper slots.
Another issue for ORefit is that a skimpy or otherwise topless outfit may occupy slot 32, slot 46 or slot 56. This is correct and it follows the guideline, but ORefit can't see the outfit mesh and can't see that the boobs are exposed. That is simply impossible to do.
In this case, it means that ORefit will incorrectly apply a pushup effect to the boobs. Since they are fully exposed in these skimpy outfits, they will look weird and out of place.
This can now be fixed thanks to the keys "blacklistedOutfitsFromORefitFormID", "blacklistedOutfitsFromORefit", "blacklistedOutfitsFromORefitPlugin", "outfitsForceRefitFormID" and "outfitsForceRefit"!
The outfit names must be exactly as they appear ingame, respecting upper and lower case!
For this example, I will be using the outfits Egil's Demon Hunter, Wrap Around Dress, Queen Marika's Dress and COCO Mysterious Mage, since they contain topless/transparent outfits, and in the case of Demon Hunter, an outfit part with a slot that needs ORefit forced on. Here's how the configuration will look like:"blacklistedOutfitsFromORefitFormID": {
"[full_inu] Queen Marika's Dress.esp": ["FE000817"]
},
"blacklistedOutfitsFromORefit": [
"Demon Hunter's Clothes Light",
"White Sexy Top Ouvert",
"Wrap Around Dress (Slutty) - 14"
],
"blacklistedOutfitsFromORefitPlugin": [
"[COCO] Mysterious Mage.esp"
],
"outfitsForceRefitFormID": {
"[full_inu] Queen Marika's Dress.esp": ["FE000803"]
},
"outfitsForceRefit": [
"Demon Hunter's Lingerie Light",
"Demon Hunter's Lingerie Heavy"
]
So, as I said previously, you have to write the names exactly as they appear ingame. Hence why I wrote "Wrap Around Dress (Slutty) - 14", because that is precisely the name of the outfit that appears ingame.
Overall this means that:
- One of the dresses from Queen Marika's Dress is blacklisted from ORefit.
- Demon Hunter's Clothes Light, White Sexy Top Ouvert and Wrap Around Dress (Slutty) - 14 are blacklisted from ORefit.
- ALL outfits from COCO Mysterious Mage are blacklisted from ORefit.
- The thigh strap from Queen Marika's Dress has ORefit forced on it.
- Demon Hunter's Lingerie Light and Demon Hunter's Lingerie Heavy have ORefit forced on them.
Demon Hunter's Clothes Light, Demon Hunter's Clothes Heavy and Wrap Around Dress (Slutty) - 14 are outfits from the aforementioned mods that are topless. They occupy slot 32 ("body), which is correct, but since they're topless the boobs will look out of place. By blacklisting them from ORefit, they will look natural! See the GIFs below for comparisons. Notice how the boobs and nipples are pushed together unnaturally with ORefit on for these outfits.
Demon Hunter's Lingerie Light and Demon Hunter's Lingerie Heavy are outfit parts which cover the boobs and the pelvis, but they occupy slot 52 ("pelvis secondary or undergarment"). Technically this is correct, because Demon Hunter has other parts using the other chest slots already, but since the Lingerie has a bra and its slot points towards the pelvis, ORefit will not activate for it unless we specify we want ORefit on that outfit part. See the image below for comparison. Notice the boobs getting a pushup effect when ORefit is turned on.
So, a full example of what we covered so far yields the following final result:{
"npcFormID": {
"Skyrim.esm": {
"00013BA3": ["Bardmaid"],
"00013BA2": ["Wench Preset", "IA - Demonic", "Tasty Temptress - BHUNP Preset (Nude)"]
},
"Immersive Wenches.esp": {
"0403197F": ["Petite Mommy"],
"0400C3C0": ["s4rMs' - Gaia"]
}
},
"npc": {
"Mjoll the Lioness": ["Hardass Warrior"],
"Haelga": ["Petite Mommy", "IA - Demonic", "s4rMs' - Gaia"],
"Temba Wide-Arm": ["Tasty Temptress - BHUNP Preset (Nude)"]
},
"factionFemale": {
"SolitudeBardsCollegeFaction": ["Hardass Warrior", "Fantasy Figure - Nude", "Royal Battle Maiden - BHUNP"],
"TownSolitudeFaction": ["QC-The Everywoman"],
"CollegeofWinterholdFaction": ["Tasty Temptress - BHUNP Preset (Nude)"]
},
"factionMale": {
"CompanionsCircle": ["HIMBO Muscled"],
"TownWhiterunFaction": ["HIMBO Simple"]
},
"npcPluginFemale": {
"Bijin_AIO_Merged.esp": ["Hardass warrior", "SilverR1baka"],
"Skyrim.esm": ["Nordic Oppai - BHUNP - Nude"]
},
"npcPluginMale": {
"Dawnguard.esm": ["HIMBO Simple"]
},
"raceFemale": {
"NordRace": ["QC-The Everywoman", "D*sney Mommy NG", "Fantasy Figure - Nude"],
"OrcRace": ["Hardass warrior"],
"WoodElfRace": ["-Zeroed Sliders-"]
},
"raceMale": {
"NordRace": ["HIMBO Simple"],
"BretonRace": ["HIMBO Simple"]
},
"blacklistedNpcsFormID": {
"Skyrim.esm": ["00013BB8", "00013BBD"],
"CS_Vayne.esp": ["0400083D", "0402CC59"]
},
"blacklistedNpcs": ["Saffir", "Vilja", "Lydia"],
"blacklistedNpcsPluginFemale": [
"CS_Coralyn.esp",
"3DNPC.esp",
"Hearthfires.esm"
],
"blacklistedNpcsPluginMale": [
"Immersive Wenches.esp",
"018Auri.esp"
],
"blacklistedRacesFemale": [
"ElderRace",
"ArgonianRace"
],
"blacklistedRacesMale": [
"ElderRace",
"DarkElfRace"
],
"blacklistedPresetsFromRandomDistribution": [
"- Zeroed Sliders -",
"-Zeroed Sliders-",
"Zeroed Sliders",
"s4mRs'' - Juno",
"Royal Battlemaiden - BHUNP"
],
"blacklistedPresetsShowInOBodyMenu": true,
"blacklistedOutfitsFromORefitFormID": {
"[full_inu] Queen Marika's Dress.esp": ["FE000817"]
},
"blacklistedOutfitsFromORefit": [
"Demon Hunter's Clothes Light",
"White Sexy Top Ouvert",
"Wrap Around Dress (Slutty) - 14"
],
"blacklistedOutfitsFromORefitPlugin": [
"[COCO] Mysterious Mage.esp"
],
"outfitsForceRefitFormID": {
"[full_inu] Queen Marika's Dress.esp": ["FE000803"]
},
"outfitsForceRefit": [
"Demon Hunter's Lingerie Light",
"Demon Hunter's Lingerie Heavy"
]
}
VERY IMPORTANT! When you're done configuring, run your JSON through this online JSON validator to check for formatting errors.
Paste your JSON file content there and click the button Validate JSON at the bottom.
If you prefer an offline solution instead, you can also use a text editor with built-in JSON formatting features. I personally recommend VS Code.
FAILURE TO CREATE A VALID JSON FILE WILL CAUSE OBODY NG TO NOT WORK OR CAUSE CTDs!!!
OBody NG JSON Configuration Guide
-
Total views56.7k
How to configure the OBody NG JSON Configuration File