Perk Conditions Framework (PCF)

Fallout 4, its DLCs, and mods all use perk conditions everywhere, from crafting recipes to dialogue checks and more. While working on Classic FNV Skill System, I ran into an annoying limitation: mods that replace or remove vanilla perks are usually forced to rely on hidden perk management or create manual compatibility patches for every mod that still checks those vanilla perks.

Perk Conditions Framework was made to get around that. Instead of constantly adding and removing hidden perks or patching individual records, PCF can handle those perk checks at runtime and allow custom Perks, Actor Values, or Global Values to satisfy them instead.

For example, a mod that normally requires Intimidation for a dialogue option can now accept a custom perk or skill requirement instead. You can also create new requirements for crafting recipes and dialogue options with NO ESP PATCH REQUIRED. These custom requirements can include quest-stage checks as well. Simply specify the conditions in your mod's TOML file and you're good to go.

Classic NV Skill System's 2. 1 update was built around this framework. With PCF, we are able to replace crafting requirements across the game with CNVSS Perks and Actor Values while also updating requirement text and SWF artwork in supported interfaces. PCF also handles custom description replacements.

PCF works through simple TOML configs included with your mod. You tell it which perk requirement you want to target, then what you want to use instead. The source perk can come from the base game, a DLC, or another mod.

For example, you can replace a vanilla perk requirement with one of your own perks:

Fallout4.esm|0004D869|Classic Skill System.esp|00000133|1|REPLACE

Or replace a perk check with an Actor Value requirement:

Fallout4.esm|0004A0DA|Classic Skill System.esp|00000FA0|>=|25|REPLACE

That example replaces Gun Nut Rank 1 with a requirement of Repair 25+.

The original recipe, dialogue option, or other record does not need an ESP edit. PCF handles supported perk checks at runtime, so the same rule can automatically affect vanilla, DLC, and mod-added records that check that perk, including existing perk checks on message-box buttons.

The examples on this page use forms from Classic NV Skill System (CNVSS). When writing configs for your own mod, use the plugin names and FormIDs for the forms you want to target.

REPLACE and OR

PCF supports two main replacement modes.

REPLACE completely replaces the original perk requirement with your configured condition.

Fallout4.esm|0004A0DA|Classic Skill System.esp|00000FA0|>=|25|REPLACE

In this example, the original Gun Nut requirement is replaced by Repair 25+.

OR keeps the original requirement valid while also allowing your custom condition to satisfy the check.

Fallout4.esm|0001DAFF|Classic Skill System.esp|00000FA5|>=|40|OR|CUSTOM

With this setup, either the original vanilla perk requirement OR Unarmed 40+ can satisfy the condition.

OR rules also require you to choose what the player sees in supported interfaces. End the rule with one of these options:

OR|ORIGINAL

OR|ORIGINAL keeps the original requirement text and artwork while allowing the custom condition in gameplay.

OR|CUSTOM keeps both conditions valid but displays your custom requirement text and artwork instead.

Custom Requirement Names

Custom Perks, Actor Values, and Global Values can also be given their own UI names.

Classic Skill System.esp|00000FA0|"Repair"

Classic Skill System.esp|00000FA1|"Science"

Classic Skill System.esp|00000F