Licenses - Player Oppression

[Ursur1major]

I'm having trouble with the bikini armour license, I have the license and I've set the keyword according to "EroticArmor,Keyword1" example I saw on here but everything gets confiscated regardless with the keyword on them.

I double checked that I have the license and that the items have the keyword.

 

Did some more testing and the "EroticArmor" keyword doesn't seem to work either, everything gets confiscated regarldess.

Edited February 6, 2025 by Ursur1major

[Nuascura]

1 hour ago, Ursur1major said:

I'm having trouble with the bikini armour license, I have the license and I've set the keyword according to "EroticArmor,Keyword1" example I saw on here but everything gets confiscated regardless with the keyword on them.

I double checked that I have the license and that the items have the keyword.

 

Did some more testing and the "EroticArmor" keyword doesn't seem to work either, everything gets confiscated regarldess.

Did you enable Life Insurance? If Life Insurance is enabled, it'll confiscate your items regardless until you purchase both a Bikini License and Life Insurance.

[Nuascura]

On 2/2/2025 at 5:46 PM, asdterewt said:

Thank you for providing the mod. I would like to make a request: could you consider incorporating a hardcore mode in a future update？

By hardcore mode, do you mean an option to lock-in and disable changing MCM settings?

[Ursur1major]

3 minutes ago, Nuascura said:

Did you enable Life Insurance? If Life Insurance is enabled, it'll confiscate your items regardless until you purchase both a Bikini License and Life Insurance.

Life insurance is disabled

[Nuascura]

@Ursur1major If you tagged everything relevant with BM_LicensesBikiniItem, would that make a difference?

Something else to try: disable both Armor and Clothing licenses if you have them enabled.

 

Otherwise, if both of the above test steps fail, pass a papyrus log from the point of character creation. Run through enabling Licenses during that same game session. Once everything is set up the way you want it to be, save the game and pass the log. We can check if there are any errors there.

[Ursur1major]

38 minutes ago, Nuascura said:

@Ursur1major If you tagged everything relevant with BM_LicensesBikiniItem, would that make a difference?

Something else to try: disable both Armor and Clothing licenses if you have them enabled.

"Keyword not found"

And turning off the licenses does work, but at that point I'm playing without licenses, tested ditching my bikini license and the MCM said it was invalid, none of the guards cared that I was running around in bikini armour.

 

I will post the papyrus log tomorrow, haven't got the time now I'm afraid.

[Ursur1major]

20 hours ago, Nuascura said:

Otherwise, if both of the above test steps fail, pass a papyrus log from the point of character creation. Run through enabling Licenses during that same game session. Once everything is set up the way you want it to be, save the game and pass the log. We can check if there are any errors there.

Papyrus.0.log

[Nuascura]

@Ursur1major Well at least no log errors. But you need to enable "Log Traces" under Licenses > Auxliary to allow Licenses to spit out its manually-placed traces.

 

21 hours ago, Ursur1major said:

"Keyword not found"

Wdym keyword not found? What LPO version are you using? Did you remember to add Licenses as a master to your plugin?

[Nuascura]

@Ursur1major Quick update, posting as a separate reply: No need to do any more testing for now. Thanks for the report of your issue. I've isolated it to a mistake in how I create the arrays after you enter the text prompt within the MCM. I'm surprised no one else said more of this issue.

 

Edit: lol seems we posted at the same time.

To clarify your experience for any future problems you have:
Papyrus increments the log numbers. So, Papyrus.0.log is always the latest log. If there is a new log needed to be generated for your current session, the old Papyrus.0.log is incremented to Papyrus.1.log, and so on.

Edited February 7, 2025 by Nuascura

[Ursur1major]

32 minutes ago, Nuascura said:

@Ursur1major Well at least no log errors. But you need to enable "Log Traces" under Licenses > Auxliary to allow Licenses to spit out its manually-placed traces.

 

Wdym keyword not found? What LPO version are you using? Did you remember to add Licenses as a master to your plugin?

It spat out two Papyrus.2 logs so hopefully they are the same (They look like it from a quick glance) and this one isn't missing anything, this time with Log Traces enabled, sorry for missing that.

 

I do not know how to add keywords directly through plugins, was using OSL Aroused which lets you add keywords to attire as well (not as permament and you have to be wearing them) and if I try to add a Keyword that OSL Aroused cannot find it says "Keyword not found". I can add keywords from other mods I've tested that.

 

I see my version is slightly behind 1.21.1

 

Edit: Saw your response right after posting mine, hopefully this additional info can still be of help

 

Papyrus.0.log

Edited February 7, 2025 by Ursur1major
Proper latest Papyrus version this time

[Nuascura]

@Ursur1major Try out this patch. This patch needs to be installed over 1.22.0.1 / 1.22.0.

 

I recently updated the front page's stable release, so I'm holding off for a bit on any public changes to that extent.

 

Edited February 15, 2025 by Nuascura
Removed Attachment

[Ursur1major]

1 hour ago, Nuascura said:

@Ursur1major Try out this patch. This patch needs to be installed over 1.22.0.1 / 1.22.0.

 

I recently updated the front page's stable release, so I'm holding off for a bit on any public changes to that extent.

Licenses - 1.22.1-beta.1 (Patch).7z 13.17 kB · 1 download

From initial testing this seems to work perfectly, walked through Whiterun wearing armour tagged with both EroticArmor and and then different armour with _SLS_BikiniArmor that I added manually without being accosted by any guards while having the Bikini License.

Edited February 7, 2025 by Ursur1major

[Ursur1major]

1 hour ago, Nuascura said:

@Ursur1major Try out this patch. This patch needs to be installed over 1.22.0.1 / 1.22.0.

 

I recently updated the front page's stable release, so I'm holding off for a bit on any public changes to that extent.

Licenses - 1.22.1-beta.1 (Patch).7z 13.17 kB · 1 download

Spoke too soon, did some more testing, reset the mod and tried again.
With Bikini license but without Armour License all items with both _SLS_BikiniArmor and EroticArmor keywords were confiscated

Papyrus.0.log

[Nuascura]

@Ursur1major Your log is showing a lot of errors due to "none" objects. Which is to say that it can't properly access my script property objects. 1.22 makes a small change that caches the player actor reference rather than retrieve it every time we need to reference the object.

 

Restart Licenses in-game and try again. If that doesn't work, try this while Licenses is disabled in-game via the MCM:

stopquest BM_Licenses_Utility

startquest BM_Licenses_Utility

 

And then enable Licenses again. And if that still doesn't work, re-do the cycle but run this console command instead:

resetquest BM_Licenses_Utility

Edited February 7, 2025 by Nuascura

[Ursur1major]

19 minutes ago, Nuascura said:

@Ursur1major Your log is showing a lot of errors due to "none" objects. Which is to say that it can't properly access my script property objects. 1.22 makes a small change that caches the player actor reference rather than retrieve it every time we need to reference the object.

 

Restart Licenses in-game and try again. If that doesn't work, try this while Licenses is disabled in-game via the MCM:

stopquest BM_Licenses_Utility

startquest BM_Licenses_Utility

 

And then enable Licenses again. And if that still doesn't work, re-do the cycle but run this console command instead:

resetquest BM_Licenses_Utility

None of those seemed to work I'm afraid, I'll try on a new character.

Papyrus.0.log

[Nuascura]

Something else simple to try, which is how I verified the bug in the first place and subsequently verified whether it was fixed:

1. Enable only Armor License, Clothing License, and Bikini License, leaving their settings at default
2. Under the Bikini License section, add VendorItemArmor as a Bikini keyword
3. Give yourself an Iron Armor (yes, the vanilla one)
4. Wear that armor and see if the guards approach you

Again, these were the steps I followed to try and replicate your issue. At this point, I'm unable to replicate the issue any further since none of the guards try to approach me at all while I wear this "bikini" Iron Armor.

[Ursur1major]

22 minutes ago, Nuascura said:

Something else simple to try, which is how I verified the bug in the first place and subsequently verified whether it was fixed:

1. Enable only Armor License, Clothing License, and Bikini License, leaving their settings at default
2. Under the Bikini License section, add VendorItemArmor as a Bikini keyword
3. Give yourself an Iron Armor (yes, the vanilla one)
4. Wear that armor and see if the guards approach you

Again, these were the steps I followed to try and replicate your issue. At this point, I'm unable to replicate the issue any further since none of the guards try to approach me at all while I wear this "bikini" Iron Armor.

Completely new save, followed that list step by step, still got my armor stolen.

Just to double check, I I've been writing the keywords so "EroticArmor,Keyword1" because that's what someone on a earlier comment said, just double checking that this is correct, there are no spaces and I'm using the correct symbols? Should the Citation marks be included? I have not been including them since they aren't there by default.

Papyrus.0.log

[Nuascura]

4 minutes ago, Ursur1major said:

Just to double check, I I've been writing the keywords so "EroticArmor,Keyword1" because that's what someone on a earlier comment said, just double checking that this is correct, there are no spaces and I'm using the correct symbols? Should the Citation marks be included? I have not been including them since they aren't there by default.

Welp, that'd be the issue. Don't include the quotation marks. They aren't there by default because the way I gave you a default is intentional. If you included quotation marks, LPO would read it like this:

Keyword 1 = "EroticArmor

Keyword 2 = Keyword1"

 

Examples of proper inputs:

EroticArmor,VendorItemArmor

EroticArmor, VendorItemArmor

VendorItemArmor

 

[Ursur1major]

6 minutes ago, Nuascura said:

Welp, that'd be the issue. Don't include the quotation marks. They aren't there by default because the way I gave you a default is intentional. If you included quotation marks, LPO would read it like this:

Keyword 1 = "EroticArmor

Keyword 2 = Keyword1"

 

Examples of proper inputs:

EroticArmor,VendorItemArmor

EroticArmor, VendorItemArmor

VendorItemArmor

 

In that case I input them correctly

Edit: Hopefully that image will load

Edited February 7, 2025 by Ursur1major

[Nuascura]

5 minutes ago, Ursur1major said:

In that case I input them correctly

Edit: Hopefully that image will load

Oh sorry I misread your reply.

 

Since you're on 1.22 now, you might as well try using the BM_LicensesBikiniItem again. These new keywords were introduced with 1.22.

Also, you do need to enable Log Traces again for Licenses to properly output the reason for your bounty event.

[Ursur1major]

16 minutes ago, Nuascura said:

Oh sorry I misread your reply.

 

Since you're on 1.22 now, you might as well try using the BM_LicensesBikiniItem again. These new keywords were introduced with 1.22.

Also, you do need to enable Log Traces again for Licenses to properly output the reason for your bounty event.

Apologies, I am tired, right. Repeating the first experiment again VendorItemArmor, that will be number 0, for full documentation.

BM_LicensesBikiniItem, included the Papyrus log for that one for the sake of completionism. These should both have Log Traces enabled unless my brain has fried.

Edit: Bloody hell I am tired, I forgot to tell the results, VendorItemArmor did indeed not work again, no change there, didn't expect it to.

BM_LicensesBikiniItem worked, put it on some Iron Armour, no response from guards, put on banded iron armour without the keyword, guards respond immediately and confiscate it, had confiscate items from inventory enabled and my Iron Armour did not get grabbed.

Papyrus.0.log Papyrus.0-1.log

Edited February 7, 2025 by Ursur1major

[Nuascura]

13 hours ago, Ursur1major said:

VendorItemArmor did indeed not work again, no change there, didn't expect it to.

BM_LicensesBikiniItem worked, put it on some Iron Armour, no response from guards, put on banded iron armour without the keyword, guards respond immediately and confiscate it, had confiscate items from inventory enabled and my Iron Armour did not get grabbed.

VendorItemArmor should work, because I was just now able to flag my vanilla Iron chest armor thing as a bikini item again.

Internally, Licenses goes like this:
1. Grab all VendorItemArmor items

2. Grab all VendorItemClothing items

3. Remove any items with bikini keywords

 

So bikini filtering is a logically confined override at the end of the function stack. And the fact that BM_LicensesBikiniItem worked for you means the violation check process itself works (for context, BM_LicensesBikiniItem is always part of the array, as an irremovable part that's placed in front of your other bikini keywords). That likely means our keyword array creation, the array that we fill with the keywords you type out, is broken for you.

 

Can you try putting a space after the comma? Do this:

EroticArmor, VendorItemArmor

 

If this doesn't work, run this command:

showquestvars BM_Licenses

 

Console will show you all script properties attached to BM_Licenses script. Press [page up] to scroll if necessary. We're looking for the "KeywordBikiniItem" entry and what is filling its array.

 

----------

 

Edit: I think I found the issue. It's because a accidentally left a whitespace in the delimiter. "EroticArmor,VendorItemArmor" won't work at the moment, but "EroticArmor, VendorItemArmor" will work fine.

Edited February 8, 2025 by Nuascura

[Ursur1major]

@NuascuraThat does indeed seem to work, tested out with the SLS_BikiniArmor Keyword again as well, seems to work so far.

Thank you!

[bubba999]

A quick question about Licenses and Devious Followers. DF works with SL Survival but does it work with Licenses? I like how you can let the follower take care of them and then charge you the gold.

[Ursur1major]

7 hours ago, bubba999 said:

A quick question about Licenses and Devious Followers. DF works with SL Survival but does it work with Licenses? I like how you can let the follower take care of them and then charge you the gold.

I would imagine not as it is Devious Followers hooking onto SL Survival for that feature, and sadly it doesn't seem like anyone is currently actively developing any of the Devious Follower's mods currently so odds are integration is not on the table, at least not from its side.