Be sure to visit the User Manual before posting your question.

• BM_Licenses is the central script
• BM_Player is for Player Quest Alias and any Events that run with said alias
• BM_Licenses_Utility holds shared/common functions AND functions that external mods may wish to use
• Scripts prefixed with BM_ME indicate that they are Magic Effects linked to a spell or enchantment
• Scripts prefixed with BM_D indicate they are dialogue scripts holding start and end fragments
• Scripts prefixed with BM_Licenses indicate they are quest scripts

If there's a license you'd like to hook into, check the corresponding license variable. For example, checking Armor License validity is just a simple check of [hasArmorLicense] == true. Some notes on these license variables:

• If a license feature is disabled, the corresponding license variable is always true.
• If a license feature is enabled, the corresponding license validity is updated based on two conditions. Pseudocode for Armor License, which doesn't consider state of the license feature itself:
  • IF player has more than one of the corresponding license book item AND expiration time isn't -1
    • player has armor license
  • ELSE
    • player doesn't have armor license

To check whether a license feature is enabled/disabled, check the MCM variable. Ex. isArmorLicenseFeatureEnabled

To check whether a license is in an active cycle, verify that the corresponding BM_Licenses variable != -1. Ex. armorLicenseExpirationTime != -1

To check whether a license is in cooldown, verify that the corresponding BM_Licenses variable != -1. Ex. armorLicenseCooldownTime != -1

An alternative method that doesn't check internal values, thereby avoiding Licenses as a hard dependency, is to check StorageUtil Global variables.

StorageUtil.GetIntValue(None, "LPO_ArmorLicense", Missing = -2)

• -2 : Missing variable / mod
• -1 : License feature is disabled
• 0 : Player doesn't have the requested license
• 1 : Player has the requested license

Current API function coverage only includes public utility functions under BM_Licenses_Utility. License documents can be purchased via manual script function calls under this script. Similarly, violations can be flagged and pushed to bounty quest under the same utility script.

---

"Licenses" is the name of this mod and its MCM menu; this is the name by which this mod should be referred to.

"LPO" is the internally-used identifier for Licenses with 1.16 onward. Log traces are prefixed with the "BM-LPO" identifier. The "BM_" keyword can be used to identify scripts. The "BM-L" keyword can be used to identify Licenses' debug outputs. Previous versions identified log traces with "BMLE", which is an acronym of "BananasManiac's Licenses - Enhanced."

Below are several additional names that Licenses may be, or may have been, referred to:

- "Licenses (LPO)": Suitable for use in formality. Good as unique public identifier.

- "Licenses - Player Oppression": Suitable for use in formality. Good as unique public identifier.

- "BM Licenses": Suitable when comparing with alternative mods, or when referring to LPO's development or in informality. This name should be avoided in formality to help non-developers differentiate LPO from its BML predecessor.

- "BM Licenses Enhanced": Suitable when comparing with alternative mods, or when referring to LPO's development or in informality. This name should be avoided in formality to help non-developers differentiate Licenses from pre-1.12 versions, which some people are definitely still using.

User Extensibility

Keyword Form

• BM_LicensesArmorItem - marks item as Armor; ex. Hide Chestplate
• BM_LicensesBikiniItem - marks item as Bikini; ex. Leather Bikini
• BM_LicensesClothingItem - marks item as Clothing; ex. Prisoner Rags
• BM_LicensesWeaponItem - marks item as Weapon; ex. Iron Sword
• BM_LicensesAmmoItem - marks item as Ammo/Arrow; ex. Iron Arrow
• BM_LicensesMagicItem - marks item as Magic item; ex. Tome of Fireball, Scroll of Fireball, Staff of Fireball
• BM_LicensesJewelryItem - marks item as Jewelry, possibly enchanted; ex. Circlet of Major Restoration
• BM_LicensesBarterItem - marks item as tradable even without a Trading License
• BM_LicensesIgnoreItem - marks item to be ignored
• BM_LicensesIgnoreLocation - marks location to be ignored

note 1: LicensesJewelryItem is a single-purpose keyword and does not correspond to VendorItemJewelry per se; an item with LicensesJewelryItem is for detecting possible enchanted jewelry under the Magic License feature, and said item will not pass as Jewelry for Trade Validation with that keyword alone. To flag an item as a tradable jewelry, tag it with either VendorItemJewelry or LicensesBarterItem. For dual purpose Magic License and Trading License, VendorItemJewelry will again be satisfactory, but you can also opt to tag with both BarterItem and JewelryItem for an equivalent Trading License effect. BarterItem naturally considers items in addition to Jewelry, such as cooked and raw food items and any other miscellaneous items you would consider low value as well.

note 2: The above keywords are "override keywords" as your items, even if added via mods, are typically already tagged with a corresponding vanilla VendorItem keyword. These keywords are not equivalents of, and do not replace or ignore, corresponding VendorItem keywords. But they do follow the same filtering sequence/priority. The only keywords unique to Licenses, strictly in terms of functionality within this mod, are LicensesBikiniItem and LicensesIgnoreItem.

FormID List

• BM_LicensesIgnoreWorldspace - marks worldspace to be ignored
• BM_Cities - marks location as a City (cross-references with keyword count LocTypeCity)
• BM_Towns - marks location as a Town (cross-references with keyword count LocTypeTown)
• BM_Worldspaces - marks space as Worldspace
• BM_LicensesIgnoreSpell - marks spell to be ignored

note: FormID Lists must be merged downward to retain changes that are otherwise lost by overwriting plugins.

---

Armor License
Restricts items tagged with VendorItemArmor.
If enabled, the player cannot equip any armor unless they hold an Armor License. You can optionally configure the Armor License to also provide Clothing License privileges, allowing a single license to cover both item categories.

Bikini License
Restricts or permits the use of Bikini-tagged items depending on the mode selected.
This license supports two mutually exclusive configurations, Restriction and Exemption, each governing how Bikini items interact with the other licenses.

• Mode: Bikini License (Restriction setting)
  In this mode, the Bikini License functions as a minimal outfit allowance until more comprehensive licenses are acquired. If the player holds only a Bikini License and lacks both Armor and Clothing Licenses, they are permitted to wear items classified as Bikini. If the player later acquires an Armor or Clothing License, the restriction is lifted and they may wear any licensed item. Upgrade path logic: Bikini → Clothing → Armor
• Mode: Bikini Exemption (Exemption setting)
  In this mode, Bikini rules act as an overriding restriction. Even if the player holds Armor or Clothing Licenses, they are still limited to Bikini items unless they also hold a Bikini Exemption. If the Bikini Exemption is acquired, the player gains the ability to wear any clothing or armor item, as permitted by their other licenses. Upgrade path logic: Clothing → Armor → Bikini

Keyword Filtering Behavior
Items are identified as Bikini-compatible using keyword filters. The default keyword BM_LicensesBikiniItem is always active. Additional keywords—such as EroticArmor from SexLab Aroused—can be added in the MCM. These are matched using OR logic. Custom keyword lists can be created by separating entries with commas. Due to MCM text field limits, longer keyword lists should be added and imported via settings.json. LPO allows up to 32 keyword entries total (of which one slot is always occupied by BM_LicensesBikiniItem). Exceeding the MCM limit will not corrupt data unless the imported array is re-saved in-game through the text box. This keyword system defines what counts as a “Bikini item” under both Restriction and Exemption modes.

Clothing License
Restricts items tagged with VendorItemClothing.
If enabled, the player cannot equip any clothing unless they hold a Clothing License. This functions like a player-only nudity law. Most appropriately used with mods like kaxat’s SES or Corsec’s non-DD patches, where NPC behavior also reflects clothing logic. Less immersive if only the player is affected.

Magic License

Restricts the following: wielding spells; casting spells; using dragon shouts; using or equipping enchanted items.

Note that Enchanted Clothing qualifies as both a magic and clothing item. Vice versa for all the other applicable item types. A Nullify Magicka curse is available for you to enable. If no valid source is selected for the curse, guards will not fine individuals without the curse. If there is a valid source, however, the player will incur a fine unless they are cursed. The curse can be applied from either a collar or a spell. The former option requires Devious Devices. Since the enchantment is applied to a tangible object, the player is allowed the option to escape this curse while out-of-sight. LPO also integrates with SlaveTats to display tattoos while the player is cursed. The tattoos are not the curse itself; they simply act as indications of an active curse.

Weapon License

Restricts items tagged with any valid vendor weapon keyword.

Excludes staffs but covers ammo. Be sure to un-equip your ammo; Vanilla game auto-equips the player with ammo in some cases, so it's your own responsibility that you don't trigger another license violation should you already be fined for the first instance of ammo-related violation.

Crafting License

Restricts use of all workbench furniture bar cooking pots.

Checker runs once when you enter, once when you exit, and once every 10 seconds while you remain in-furniture without a license. If you find yourself getting caught all the time, try crafting outside settlement locations.

Trading License

Restricts purchase of any items beyond food and jewelry.

Items must not hold enchantments. Also prohibits the player from selling anything. Merchants will nonetheless do business with you, though they will flag you for violation. Likewise, dealing business within sight of town guards is an obvious no-no. Note that, even with a Trading License, players can't buy any equipment they don't also have a license for; players will incur a Trading Violation even if Trading License is disabled. You could try a fence or khajit caravan to trade with you free of restrictions. Equipment trading validation operates adjacent to the Trading License feature and can be disabled separately.

Curfew Exemption

Restricts lollygagging after-hours.

This feature ignores location filters. Curfew start and end times can be changed via the MCM. Internally, LPO waits about 10 seconds after violation detection before flagging you for an active bounty event. The delay helps guard against small player mistakes. Additionally, LPO provides a once-per-day Curfew Leniency pass - guards won't take your gold for the first Curfew Violation of each day. Regardless, once caught, you'll be sent to either the closest inn or the enforcing guard's jail if an inn couldn't be located within a suitable distance from your character. Location overhauls may add inn markers outside city worldspaces; if so, you'll want to disable "Differentiate Worldspaces" if you use the Travel Permit feature.

Travel Permit

Restricts travel outside registered locations.

If you enabled this feature while in Whiterun City, your recorded location is Whiterun City. If enabled in Riverwood, vice versa. This feature is only enforced with both City and Town locations, disregarding your locational filters. Purchasing a permit will allow you free travel out of your recorded location. Ultimately, what happens with this permit feature depends on the circumstances. 1) If you are found safe inside a town or city, or forfeited your permit for an early expiration, you will not incur a fine; 2) If you were discovered outside a settlement location but are confronted inside a settlement, you'll receive a fine while your current location becomes your recorded, enforced location; 3) If you are discovered and confronted outside a settlement location, you may be arrested and sent to Jail. Enforcement ignores locational filters. If enabled, followers will allow you immunity from Travel rules.

Life Insurance

Restricts primary license privileges.

Enabling the Insurance option causes guards to ignore primary license rules unless you also have an insurance on-hand. For example, guards will flag you for an Armor Violation even if you have an Armor License. However, if you do have an Insurance, you'll be protected from item confiscations regardless of your other license validities. Holding a Life Insurance along with an equipment license will allow you to resume standard privileges with applicable equipment. Beware that Insurance prices are variable by way of two modifiers. These multipliers cannot be disabled, and only the misbehavior modifier can be reset when disabling the mod as a whole.

Whore License

Restricts prostitution.

Dummy feature. LPO mainly handles purchase and expiry. External scripts may optionally flag a Whore Violation for LPO to handle punishment. Check utility script for integration. The following are mods known to integrate with LPO for this feature: Autonomous Sex Framework by kaxat; Devious Interests by Taki17; Simple Player Prostitution by mort65; TDF Enhanced Prostitution by Horred.

Collar Exemption

Enforces collars.

Enabling this feature will require you to wear a Devious Devices collar. LPO checks for items tagged with zad_DeviousCollar. Guards will automatically equip you with a collar should they catch you without one, regardless of if you've enabled the option to equip restraints on license violation. Guards will remove your collar after you purchase an exemption. However, if you've designated a collar as your Nullify Magicka curse source, guards will instead disenchant your collar.