Sexlab Sexual Fame RELOADED

[skyrim_sailor]

From what I gather reading your documentation, v4 no longer works with PW 1.2.4 (ie. PW is no longer able to use SLSFR fame as of v4 like it was able to do in v3 with the PW patch). Would it be technically too much trouble to make a patch for v4 as well? A v4 PW patch would be really useful, considering how many people have PW and how SLSFR became a de facto standard framework in people's modlists as well.
Even though your documentation says there is a replacement planned for PW, I imagine it is way further down the development road. Many people might choose to stay with v3 SLSFR / A.N.D. for this reason which would really be sad seeing the awesome development work that goes into v4.

[NymphoElf]

10 hours ago, skyrim_sailor said:

From what I gather reading your documentation, v4 no longer works with PW 1.2.4 (ie. PW is no longer able to use SLSFR fame as of v4 like it was able to do in v3 with the PW patch). Would it be technically too much trouble to make a patch for v4 as well? A v4 PW patch would be really useful, considering how many people have PW and how SLSFR became a de facto standard framework in people's modlists as well.
Even though your documentation says there is a replacement planned for PW, I imagine it is way further down the development road. Many people might choose to stay with v3 SLSFR / A.N.D. for this reason which would really be sad seeing the awesome development work that goes into v4.

 

I don't know.

 

I would have to look at how PW gathers its fame data again. If I have to build a dedicated data bridge just for SLSFR v4 and PW to interface then I probably won't bother. I'd rather spend that time pushing forward for the PW replacement. If I don't have to do that much, then maybe I'll squeeze it back in.

The other side of the coin is that I'm going to completely drop PW support in SLSFR once the PW replacement is out, so I'd rather not have more work to do at that stage.

I'm also not exactly aware of anyone else opting to stay on v3 for PW, but maybe you're just the only one that has said anything?

Edited Thursday at 04:13 AM by NymphoElf

[skyrim_sailor]

Well on page 44 there is at least one person asking specifically about PW compatibility (Sept. 27.) and on page 42 (Sept. 5-6.) there are a bunch of people requesting version 3.4.1 of SLSFR, though PW as a specific reason is not mentioned there.
Other than these posts, PW's download count is over 925000+ which may serve as a good indicator of how widespread that mod really is. 

[thehangman625]

15 hours ago, NymphoElf said:

 

Well now it depends on what you mean by "bloat".

 

Bloat, by its proper and objective definition in the context of software is "unnecessary and useless data". Just because a file is bigger than you THINK it should be doesn't mean it's bloated.

 

-----------------------

Here is a breakdown of every object saved by SLSFR:

 

Each registered plugin (ie: mods such as LMAO) is 293 Bytes each, but there are Zero by default for a total of 0.

 

Each registered tattoo consumes ~440 Bytes each for the Tattoo Memory function to work, but there are Zero by default for a total of 0..

 

Each Default Fame Location is ~1.5KB, and there are 21 of them. That adds up to ~31KB.

 

There are 10 Fame Regions, which are 328 Bytes each, which is ~3KB total.

 

Finally, each Custom Location is 1.75KB each, but there are Zero by default for a total of 0.

-----------------------

 

This means that, by default, SLSFR should be around 35KB of your CoSave upon first load in a brand new game, which is still a touch smaller than SKSE itself.

 

Also, 25MB for a CoSave is more than reasonable depending on the mods you have and how long you've been playing. 25GB on the other hand might be a different story.

 

For example: my fresh, brand new, haven't left the Alternate Start cell yet CoSave is only 109KB, but I also only have 10 mods saving to my CoSave file.

 

I am very skeptical that 4.1.1 is still the ultimate culprit, because I did my best to properly solve the underlying issue, not just slap a band-aid on it.

 

You need to either show me where the bloat is happening in your CoSave or send me your "bloated" CoSave file to inspect myself.

I was playing for around 2 hours (not counting the long ass time I spent in the starting room of Alternate Perspective), in Winterhold (the inn and the shop), the Midden, the College and the coast around it. How do I show where the bloat is happening... or where do I upload that damn save? On a filehost, or in a pm or something? Also, to identify the culprit of the bloat, I used Log Watcher, and it showed entries going up for SLSF, around 400 at a time, while idling in Winterhold. I have attached the SLSF .log for now, awaiting further instructions

Sexlab Sexual Fame Reloaded.log

[NymphoElf]

8 hours ago, skyrim_sailor said:

Well on page 44 there is at least one person asking specifically about PW compatibility (Sept. 27.) and on page 42 (Sept. 5-6.) there are a bunch of people requesting version 3.4.1 of SLSFR, though PW as a specific reason is not mentioned there.
Other than these posts, PW's download count is over 925000+ which may serve as a good indicator of how widespread that mod really is. 

 

That's anecdotal at best. Divide the number of downloads by the number of releases and you get a more accurate representation of how many use it.

 

For example, SLSFR only has ~3,000 actual users despite the mod having over 120k downloads. I've released about 40 different versions, so the math adds up. This is also assuming each user only downloads each version of the mod once, which I know for sure is not the case, but I have no idea how many downloads are duplicates, so a more accurate estimate is probably closer to ~2,000. The download counter on LL is wildly misleading because it only tracks total downloads no matter who clicks it, whereas Nexus tracks both unique and total downloads, and unique downloads are the better metric to gauge popularity.

 

Those posts made previously are more likely asking because they're complaining that I broke a wabbajack list despite repeatedly saying I don't support mod lists for the entire time I've been an author.

 

I'm not necessarily saying you're wrong about how many people would want this, I'm just saying that your proposed evidence isn't convincing due to the reasons I've laid out.

 

Regardless, I appreciate the feedback.

 

6 hours ago, thehangman625 said:

I was playing for around 2 hours (not counting the long ass time I spent in the starting room of Alternate Perspective), in Winterhold (the inn and the shop), the Midden, the College and the coast around it. How do I show where the bloat is happening... or where do I upload that damn save? On a filehost, or in a pm or something? Also, to identify the culprit of the bloat, I used Log Watcher, and it showed entries going up for SLSF, around 400 at a time, while idling in Winterhold. I have attached the SLSF .log for now, awaiting further instructions

Sexlab Sexual Fame Reloaded.log 472.29 kB · 0 downloads

 

Idk what "Log Watcher" is but it doesn't sound like the proper tool to make an assertion that a mod is causing bloat. It sounds like this tool only tells you what mods are the most busy, and SLSFR has a lot of logging and busy functions, but that has nothing to do with bloat. A busy mod can still have literally zero impact on your CoSave size.

 

If you can't upload the file here, then linking a Google Drive or Mega upload (or anything similar) will suffice.

Edited Thursday at 03:39 PM by NymphoElf

[skyrim_sailor]

5 hours ago, NymphoElf said:

 

That's anecdotal at best. Divide the number of downloads by the number of releases and you get a more accurate representation of how many use it.

 

For example, SLSFR only has ~3,000 actual users despite the mod having over 120k downloads. I've released about 40 different versions, so the math adds up. This is also assuming each user only downloads each version of the mod once, which I know for sure is not the case, but I have no idea how many downloads are duplicates, so a more accurate estimate is probably closer to ~2,000. The download counter on LL is wildly misleading because it only tracks total downloads no matter who clicks it, whereas Nexus tracks both unique and total downloads, and unique downloads are the better metric to gauge popularity.

 

Those posts made previously are more likely asking because they're complaining that I broke a wabbajack list despite repeatedly saying I don't support mod lists for the entire time I've been an author.

 

I'm not necessarily saying you're wrong about how many people would want this, I'm just saying that your proposed evidence isn't convincing due to the reasons I've laid out.

 

Regardless, I appreciate the feedback.

I guess these are fair points overall, but unless many more people who download step up in favor of the patch, I don't think anybody else could bring up more convincing evidence than this. If you find the time to make the patch happen anyway, that would be awesome. Thanks for your work on the mod!

[thehangman625]

20 hours ago, NymphoElf said:

 

That's anecdotal at best. Divide the number of downloads by the number of releases and you get a more accurate representation of how many use it.

 

For example, SLSFR only has ~3,000 actual users despite the mod having over 120k downloads. I've released about 40 different versions, so the math adds up. This is also assuming each user only downloads each version of the mod once, which I know for sure is not the case, but I have no idea how many downloads are duplicates, so a more accurate estimate is probably closer to ~2,000. The download counter on LL is wildly misleading because it only tracks total downloads no matter who clicks it, whereas Nexus tracks both unique and total downloads, and unique downloads are the better metric to gauge popularity.

 

Those posts made previously are more likely asking because they're complaining that I broke a wabbajack list despite repeatedly saying I don't support mod lists for the entire time I've been an author.

 

I'm not necessarily saying you're wrong about how many people would want this, I'm just saying that your proposed evidence isn't convincing due to the reasons I've laid out.

 

Regardless, I appreciate the feedback.

 

 

Idk what "Log Watcher" is but it doesn't sound like the proper tool to make an assertion that a mod is causing bloat. It sounds like this tool only tells you what mods are the most busy, and SLSFR has a lot of logging and busy functions, but that has nothing to do with bloat. A busy mod can still have literally zero impact on your CoSave size.

 

If you can't upload the file here, then linking a Google Drive or Mega upload (or anything similar) will suffice.

Here is my co-save right before I disable the mod. This was 95 MB. The password to the zip is 'slsfr'.

[NymphoElf]

9 hours ago, thehangman625 said:

Here is my co-save right before I disable the mod. This was 95 MB. The password to the zip is 'slsfr'.

Ok, I stand corrected. SLSFR is the problem here, Try using this save on 4.1.2 though. It should clean it automatically

[thehangman625]

13 hours ago, NymphoElf said:

Ok, I stand corrected. SLSFR is the problem here, Try using this save on 4.1.2 though. It should clean it automatically

I'll try it and report my findings. In the meantime, I started a new game without SLSFR. Is it safe to add it to that existing character, where I never used the mod?

[NymphoElf]

8 hours ago, thehangman625 said:

I'll try it and report my findings. In the meantime, I started a new game without SLSFR. Is it safe to add it to that existing character, where I never used the mod?

 

It should generally be safe to ADD mid-playthrough, yes. (There are a lot of potential caveats to that though. It's not a 100% guarantee to be safe, but that goes for everything in modding.)

[Senick2]

On 10/15/2026 at 12:12 AM, NymphoElf said:

 

I don't know.

 

I would have to look at how PW gathers its fame data again. If I have to build a dedicated data bridge just for SLSFR v4 and PW to interface then I probably won't bother. I'd rather spend that time pushing forward for the PW replacement. If I don't have to do that much, then maybe I'll squeeze it back in.

The other side of the coin is that I'm going to completely drop PW support in SLSFR once the PW replacement is out, so I'd rather not have more work to do at that stage.

I'm also not exactly aware of anyone else opting to stay on v3 for PW, but maybe you're just the only one that has said anything?

I've been noticing this as well in PW, messed with the settings with no change, but I figured it was just something wrong with my game or something. I love the PW mod and it would be great to see it work again with SLSFR. That being said, I was very sad to see development halted on PW, and I can totally understand not wanting to do a bunch of work that will be rendered obsolete when/if a replacement mod is made, especially if it might take development time away from other projects (such as the replacement? :D). I'm so looking forward to a remake or w/e that can improve it or add to it  (such as unique start mechanics (the Windhelm stuff is peak, love those types of things the had a "bad end" that's more flavor/roleplay than like an end to gameplay)). I'm not sure what the real point of this rambling post was, but I guess I want to say, you do you, I'll appreciate whatever you choose and thank you for all the incredible time and effort you've put into the mods.

Edited Saturday at 06:58 PM by Senick2

[thehangman625]

16 hours ago, NymphoElf said:

 

It should generally be safe to ADD mid-playthrough, yes. (There are a lot of potential caveats to that though. It's not a 100% guarantee to be safe, but that goes for everything in modding.)

I did load that older character with 4.1.2, and it seems to work! The 95MB save would take an ungodly time/would crash without loading, with the crash report pointing to SLSFR, but an earlier save (25MB, and subsequent saves would inflate to 45=>71=>95) worked, though it took a few minutes to load. A new save now is 2,0MB! Marvelous! It seems to be fixed now, thank you for your work. But now I will test on my newer character, on which I never used SLSFR.

Edit: I loaded my new ,existing character, and it seems to work. The MCM entry didn't appear at first, even though I got a notification for 2 new menus (presumably this and fame comments), but I put "setstage SKI_configmanagerinstance 1" into the console and it made the menu show up.

Edited yesterday at 09:32 AM by thehangman625
Update on testing

[Ursur1major]

Question to people:
How do you categorize Body Tattoos on the Arms or on the sides?

And I cannot see this anywhere in the Guide, but is there a way to hide Pelvis/Chest tattoos while the outfit still has the Bra and/or Thong or similar keyword that otherwise leaves them exposed? For outfits where midriffs are covered but still reveal the panties or have a lot of cleavage, show a lot of underboob, or are just extremely skintight so technically don't actually show any skin but could still be seen as "revealing"?

Edited yesterday at 01:35 PM by Ursur1major