MSMA: SexFight (like "Succubus Drain") and Bimbofication

[MSM_Alice]

1 hour ago, JemappelleRedacted said:

Something definitely going squirrely this update, every single Violate scene has been cancelled, even ones I've tried to manually surrender at high health, at least one from the last save had progressed to animation despite the cancel (dropped that save as I thought Insanity Framework was causing problems). Most of the others have been consistent cripple>gun down>gun back up>"I surrender">MSMA has cancelled Violate>hud and control removed. Woofles fighting in the background during the entire process, I eventually get shot by unpacified/?reaggro'd enemies, then bleedout>limbo.

 

Two new games (initial cooking was only 10min rather than 30 due to script lag being 0 according to SKK), log attached but damn is that ugly for a game not 4 hours old. Added a second log(-Copy.log) that was basically load>surrender>restrained and interrupted>surrender>gave up. Incidentally, something keeps toggling restraints to start rather than end, may be related to this glitch.

 

Papyrus.0.log 354.21 kB · 2 downloads Papyrus.0 - Copy.log 520.51 kB · 0 downloads

I shall investigate. 
To doule check: This is the very latest version, and brand new game, correct?
I was planning to do a larger update tomorrow, but this seemsserious, I postpone that and do this investigation first. 

What is a headscratcher  is I did a brand new playthrough on NG build, on a computer totally separated from my mod development build just to make sure I hadn't forgotten to pack any files in the zip file,  not 12 hours ago.
Fresh game from start  until fully building up Sanctuary, with wedge scenes, sparing no surrenders along the  way  and encountered zero  unexplainable violate cancels or fails due to missing animations

Zero issues, so  wonder if it is a specific mod that I lack,  that triggers it, since some people get it often, and some people seem to not get  that  at all.  

I even allowed for a visit  to bimbo limbo on a bleedout, no oddities.

 

Can you share the mod load-out as well?

I know where the bug that moves  the restrains at the start is coming from,  and that is unrelated.  That was on the To do list as well  for this next update. 
 

Edited September 12, 2025 by MSM_Alice

[MSM_Alice]

8 minutes ago, Slip0213 said:

Hi @MSM_Alice,

 

Sorry for the late reply.  Life got in the way.

 

 

So this is a problem that has occurred on a new game.  I was at about lvl 20 when I tried. 

 

I haven't changed my mcm setting depart mode as it's still on slow but since you mention violate I did get some violate scenes cancelled due to bleedout.  For the most part violate functions ok with a couple minor hiccups.  One bug I can mention is RC9 DD Enchantings did stop firing at some point.  Not sure how that can be related but I had to manually reset it to get it rolling again.

 

If you feel this problem is important enough to trace then I'm happy to help.  

 

Thank you.

Cancel due to bleedout and leaving for bimbo limbo is normal. 
The onyl issue is if hangs on and does not cancel as you are sent to bimbo limbo, and remains in an undefined state.

[MSM_Alice]

1 hour ago, Slip0213 said:

Hi @MSM_Alice,

 

Sorry for the late reply.  Life got in the way.

 

 

So this is a problem that has occurred on a new game.  I was at about lvl 20 when I tried. 

 

I haven't changed my mcm setting depart mode as it's still on slow but since you mention violate I did get some violate scenes cancelled due to bleedout.  For the most part violate functions ok with a couple minor hiccups.  One bug I can mention is RC9 DD Enchantings did stop firing at some point.  Not sure how that can be related but I had to manually reset it to get it rolling again.

 

If you feel this problem is important enough to trace then I'm happy to help.  

 

Thank you.

On the nex tbuild i'll just put a poup or at least a trace  with the bespoke fail reson, at least we'll know which of the  potential 10 reasons is the blocker in your case. 

Edited September 12, 2025 by MSM_Alice

[MSM_Alice]

2 hours ago, JemappelleRedacted said:

Something definitely going squirrely this update, every single Violate scene has been cancelled, even ones I've tried to manually surrender at high health, at least one from the last save had progressed to animation despite the cancel (dropped that save as I thought Insanity Framework was causing problems). Most of the others have been consistent cripple>gun down>gun back up>"I surrender">MSMA has cancelled Violate>hud and control removed. Woofles fighting in the background during the entire process, I eventually get shot by unpacified/?reaggro'd enemies, then bleedout>limbo.

 

Two new games (initial cooking was only 10min rather than 30 due to script lag being 0 according to SKK), log attached but damn is that ugly for a game not 4 hours old. Added a second log(-Copy.log) that was basically load>surrender>restrained and interrupted>surrender>gave up. Incidentally, something keeps toggling restraints to start rather than end, may be related to this glitch.

 

Papyrus.0.log 354.21 kB · 2 downloads Papyrus.0 - Copy.log 520.51 kB · 0 downloads

There is some insight into the logs. 

You did have a dog as a follower? 
Was the dog part of the scenes? (companion allowed to be violated or to be a violator)?

I see that in the second log something, but it has nothing to do with error 3 from mimirue17's playthrough; it is something entirely different.

The first violate scene: it seems to have worked normally from MSMA's standpoint; it was not MSMA that asked for the first one's interruption.
Probably there were some enemies around that attacked or something? There was just one challenge, so for sure something cut it short, only violate knows what that "something"  that  hit "Raider Scum" was. 
AFV Report: onHit actor Raider Scum during surrender, interrupting
There was just one aggressor and two victims (player and follower(dog?) )
I dunno precisely what, but  I do know it wasn't msma who asked for the first violate scene to force-stop; it stopped on its own, due tp external attack. As far as MSMA was concerned, the first violate scene went as it should have, with no emergency exit measure demanded on MSMA  side.


On the second one, on that one MSMA did ask for its interruption on astart as an emergency as  it detected that, when the second) violate  started:
- Noncritical: the punishment for the first violate hadn't been concluded yet (not necessarily critical, just potentially problematic to have two violates so close to one another), but that does put the system on alert. 
-  Critical: the companion (dog ? if I am seeing correctly)  was still involved in an AAF scene.... maybe  from the first violate, that hadn't ended yet ?) But  really I don't know how because apaprently there was just one attacker, and two victims ( you and the follower) , and if the attacker was probably involved with the player. So the follower/dog had to be free and not in an AAF scene.
I'll have to check more closely what happens with companions, and with the force end based on companion AAF status, particularly if that companion is a dog...I might not have thought to correctly  check for dogmeant, he is a special companion and a particular case, and uses a different alias reference than human companions.

Were you having Dogmeat as a companion?
That is important context. Would explain a lot.

Do you have a mod with multi-companions?
 

 

Normally, when a violate scene ends, and we reach  "last round" , MSMA also asks any companions to end their scenes too, so you don't have the player just waiting around and twiddling their thumbs waiting for the companions to be done. But because the first scene exit wasn't a normal eding one but because of an attack, this ask to the companion might have been dodged OR the determination that the companio is in an AAF scene might be entirelly incorrectly done for dog types.  
This led to the companions being otherwise engaged, (or incorrectly assumed as engaged) when the second viuolate started, and that's when things started going south. 


It is true so far, I tested a little with companions, and they were always human.
I have never tested what happens with Dogmeat as a companion.

 

Edited September 12, 2025 by MSM_Alice

[MSM_Alice]

2 hours ago, JemappelleRedacted said:

Something definitely going squirrely this update, every single Violate scene has been cancelled, even ones I've tried to manually surrender at high health, at least one from the last save had progressed to animation despite the cancel (dropped that save as I thought Insanity Framework was causing problems). Most of the others have been consistent cripple>gun down>gun back up>"I surrender">MSMA has cancelled Violate>hud and control removed. Woofles fighting in the background during the entire process, I eventually get shot by unpacified/?reaggro'd enemies, then bleedout>limbo.

 

Two new games (initial cooking was only 10min rather than 30 due to script lag being 0 according to SKK), log attached but damn is that ugly for a game not 4 hours old. Added a second log(-Copy.log) that was basically load>surrender>restrained and interrupted>surrender>gave up. Incidentally, something keeps toggling restraints to start rather than end, may be related to this glitch.

 

Papyrus.0.log 354.21 kB · 3 downloads Papyrus.0 - Copy.log 520.51 kB · 2 downloads

This firs t papyrus log is trully odd, it seems the player alias reference might have been lost at som epoint, or some script object related to violate failing to be bound to the actual scripts. 

I do see that there was a dealthclaw animation, and that session got canceleld by Violate itself because the deathclaw was hit during the violate session.  
 AFV Report: onHit actor Young Deathclaw during surrender, interrupting

 

 

for  instance, this one  puzzles me a lot 
(Sorry I had misread  before and was attributing this to NukaRide,it is in fact just  Violate) 

[09/12/2025 - 08:26:11PM] error: Unable to call EnablePlayerControls - no native object bound to the script object, or object is of incorrect type
stack:
    [None].InputEnableLayer.EnablePlayerControls() - "<native>" Line ?
    [alias playerRef on quest FPV_Player (1F000F99)].FPV_OnHit.::remote_AAF:AAF_API_OnAnimationStart() - "C:\Steam\steamapps\common\Fallout 4\Data\Scripts\Source\User\FPV_OnHit.psc" Line 1880
 

But was attempting to enable player controls on an input layer, that somehow had failed to initialize.. 

That's really strange, and shouldn't even happen. 
Was that because the script that this was called  from had gotten lost, or / file not present on disk ?
The script that this refers to needs to be bound to a script object, and that seems to be missing there.  The script object itself is "empty".
Why, I have no clear view, but it is not part of the MSMA mod.

Truly a bizarre state.


If you are using my manually altered FPV_OnHit script.. maybe  leave that out, and just work with the standard vanilla violate 1.61, and see if it gets better. 

Another  good experiment to try is  to just  use Paralisys or Death, no frenzy. 
Leave Frenzy off  for a while (settable in the MCM). 
 

Edited September 12, 2025 by MSM_Alice

[jesusblaster]

14 hours ago, JemappelleRedacted said:

Hold down the surrender key for ~8 seconds and it should abort any failed Violate scenarios 

Thanks, this worked.

[Slip0213]

2 hours ago, MSM_Alice said:

I shall investigate. 

Sure.  Here's my Mod List.  

 

Don't hold up the latest release.  This is most likely isolated to me as others have not mentioned this problem.  Hopefully we can find a solution but let's not dwell on it too long.  I'll rip apart my mod list on a new game if needed.

 

For the record this is on a new game and I completed all initial conversations with the Marina and what's-it's-eldritch-face in outside the vault.  If timing matters, I think I might have tried to boost Preston's affinity earlier than lvl 20 (with no response) but I might be confused.  

 

ModList.txt

[jesusblaster]

9 hours ago, MSM_Alice said:

So it is all good now ? 

The global variable I am checking for that message is defined in Violate and is called : AFV_IsMajorFunctionActive , that's an internal Violate flag, but if Violate is stuck, simply setting it to 0 might work (but since that global is defined as hidden, not sure how one would do that from the console) , but likely is not the right way to correct things. 

You can try to
- force Violate to end by doing what @JemappelleRedacted suggested,
- load an earlier save before the problem (as you assumed), and hope the problem does not occur again
or for the future I could also add in the MCM Debug section of MSMA mcm a "Force Violate to Outcome" button that people can use in future versions if violate status got stuck, as the Violate mod has an API interface and it does expose that function to other mods, they can ask Violate to force-end/outcome and that should reset things the right way.

Sorry for the delay in responding (time differences and all)
Yes, the suggestion of @JemappelleRedacted worked.

Edited September 12, 2025 by jesusblaster

[jesusblaster]

7 hours ago, MSM_Alice said:

One more question : 
The violate scene that failed, did it have any link to going into bleedout before violate and then to bimbo-limbo?
If yes, were you using the "fast depart" from bleedout to bimbo limbo option, or the high compatibility "slow depart" method from bleedout to bimbo limbo (which should be safer,  and the normal default)?
Maybe that fast departure is the cause, and maybe Violate got stuck.
The reason why the slow depart is the default s that I suspected the fast depart might be problematic in some edge cases. 

Not that I remember, I surrendered manually before a Mister Handy attacked me and I'm currently using the mod's default settings.

What I remember about that animation is that it glitched and didn't run as it should.

[Mimirue17]

I noticed the dog seller random encounter keeps showing up during my 1st trip to concord and that initial batch of raiders.  Where the dog companion came up in mine a few days ago I think.  I have altered timing of when I leave Sanctuary to go to concord but it seems baked into my save game that he will show up.  And of course the raiders in the middle of my Violate attack him (those not currently giving the pc the business)

[JemappelleRedacted]

13 hours ago, MSM_Alice said:

You did have a dog as a follower? 
Was the dog part of the scenes? (companion allowed to be violated or to be a violator)?

Sorry, I sometimes forget my shorthand/nicknames aren't always obvious: can't stand the name "Dogmeat", my brain autocorrects to "Sir Woofles". Yes, I had him as a follower but he shouldn't be a violate target for several reasons (Dog and Male are auto off as I understand it, Follower should be off but may have reset).

 

13 hours ago, MSM_Alice said:

I was planning to do a larger update tomorrow

Given your time crunch, and the suggestion it's unrelated to other user-end issues, I'd suggest focusing on the update. It's been established my setup is uniquely challenging anyway, and that's before factoring in the creeping hardware issues 😔

 

13 hours ago, MSM_Alice said:

To doule check: This is the very latest version, and brand new game, correct?

New game, latest version, OldGen.

 

13 hours ago, MSM_Alice said:

I tested a little with companions

Huh, this...might actually help. I figured I'd be able to run the Wedge quests easily now that I've reverted to what I was running when he worked last time, but I had a proper crash (rather than a blackscreen/no menu access/ restart computer style lockup that has happened the last few runs). Crash scanner believes it's MSMA's fault, but I wonder if it's a minion interaction?

Have a crash log (mod list is at the bottom I believe), but don't worry overmuch about debugging it, you've got more interesting and important things to do. 👍

 

Side note: QoH reminds me of a friend from r/gwa, lovely voice but the dialogue is a bit stilted. A mind splinter would be more informal, more "I'm" rather than "I Am". Great idea for the reason behind the music though!

 

EDIT

Not sure if it's the fresh reload, losing the MSMA Violate plugin, or ditching Woofles, but Wedge's bed stage got me back without a crash...step in the right direction!

crash-2025-09-13-00-28-07.log Papyrus.0.log crash-2025-09-13-00-28-07.log

Edited September 13, 2025 by JemappelleRedacted

[MSM_Alice]

57 minutes ago, JemappelleRedacted said:

Sorry, I sometimes forget my shorthand/nicknames aren't always obvious: can't stand the name "Dogmeat", my brain autocorrects to "Sir Woofles". Yes, I had him as a follower but he shouldn't be a violate target for several reasons (Dog and Male are auto off as I understand it, Follower should be off but may have reset).

 

Given your time crunch, and the suggestion it's unrelated to other user-end issues, I'd suggest focusing on the update. It's been established my setup is uniquely challenging anyway, and that's before factoring in the creeping hardware issues 😔

 

New game, latest version, OldGen.

 

Huh, this...might actually help. I figured I'd be able to run the Wedge quests easily now that I've reverted to what I was running when he worked last time, but I had a proper crash (rather than a blackscreen/no menu access/ restart computer style lockup that has happened the last few runs). Crash scanner believes it's MSMA's fault, but I wonder if it's a minion interaction?

Have a crash log (mod list is at the bottom I believe), but don't worry overmuch about debugging it, you've got more interesting and important things to do. 👍

 

Side note: QoH reminds me of a friend from r/gwa, lovely voice but the dialogue is a bit stilted. A mind splinter would be more informal, more "I'm" rather than "I Am". Great idea for the reason behind the music though!

crash-2025-09-13-00-28-07.log 76.61 kB · 0 downloads Papyrus.0.log 178.17 kB · 0 downloads crash-2025-09-13-00-28-07.log 76.61 kB · 0 downloads

Unrelated to Wedge, but to the initial violate after violate sequence:  the logs and context  did help me did find out a flow issue related to the scenario where two different violate scenes involving the player were coming one after the other at less than 4-6 seconds distance, an aspect that I thought so improbable that it didn't need its own handling.  It now has some specific checks that look for that and handle it. 

What was happening  before was that at the end of the post-violate attacker punish function, I was checking if there were any major Violate function still running, to ensure  a clean end. And since they were indeed running, (but not "still running", not  because they were stuck but because the second violate surrender and sequence had started anew in the interim), I was wrongly assuming that the first surrender never properly ended and needs to be force stopped.

I modified that implementation and now each Violate surrender sequence as a per session unique ID  that it passes to the punish function, so the punish function has local context  knows well which violate sequence/session it was called from.  By knowing that , it knows also that it has no business force-ending a newly started violate session that has a different ID.

To increase safety I also took the liberty to have the MSMA mod just not apply any frenzy as punishment when the player has a follower in ( the specific condition is when the victim actor buffer of violate is greater than 1, and that one is the player).
That should make it so outcome can only be paralysis and/or death while followers are involved, never frenzy. 
Frenzy happens only when it is selected in the MENU as possible AND the player must be solo. 
At least for a while things settle more bugs are sorted out, I will leave it like that.

Probably it will be some 14 more hours until I publish the new version, there' still al lot to add in it. (but I might drop test builds version on the thread on the way .) 

 

 

Edited September 13, 2025 by MSM_Alice

[MSM_Alice]

12 hours ago, Slip0213 said:

Sure.  Here's my Mod List.  

 

Don't hold up the latest release.  This is most likely isolated to me as others have not mentioned this problem.  Hopefully we can find a solution but let's not dwell on it too long.  I'll rip apart my mod list on a new game if needed.

 

For the record this is on a new game and I completed all initial conversations with the Marina and what's-it's-eldritch-face in outside the vault.  If timing matters, I think I might have tried to boost Preston's affinity earlier than lvl 20 (with no response) but I might be confused.  

 

ModList.txt 11.6 kB · 1 download

I already added a MCM option so that the Charm/prostitution key will just spawn a text popup with a reason of why it check it didn't pass, why didn't start. 
If that option is on. The only reason that does not spawn a popup is " being in an AAF scene).

It will be there in the next release. 

[Mimirue17]

Not sure if you noticed - Darthroman animations were updated - new Dildos are available and a solo animation laying down was added!   A scene which is labeled FF I believe - where one F uses the dildo on the other F.   Might be useful for an interrogation scene, or simply as a punishment scene when super mutants are not needed yet - would be funny to see a Hologram female able to use the dildo on the player as punishment like the first time the Limbo guys punish the player - then upgrade to super mutants when the player persists in behavior that gets her killed - or as an alternative if the player uses her get out of jail card > fine no SM but you are still getting reamed with a big dildo!

[MSM_Alice]

17 minutes ago, Mimirue17 said:

Not sure if you noticed - Darthroman animations were updated - new Dildos are available and a solo animation laying down was added!   A scene which is labeled FF I believe - where one F uses the dildo on the other F.   Might be useful for an interrogation scene, or simply as a punishment scene when super mutants are not needed yet - would be funny to see a Hologram female able to use the dildo on the player as punishment like the first time the Limbo guys punish the player - then upgrade to super mutants when the player persists in behavior that gets her killed - or as an alternative if the player uses her get out of jail card > fine no SM but you are still getting reamed with a big dildo!

Thank you. Will take a look. if enough different ones are available I will make sure that the four dildo friends are different in the next update. 

Right now I am working on making a parallel orgasm sound system, with more variation than the one in sex Attributes , so there are a bit different for the varied types of orgasms than a player can have in MSMA.  And with some awareness of how fast they follow one after the other, as so to dynamically use longer or shorter sound sound, as appropriate.

 (and that also is dynamically reduced in volume when QOH speaks during sex, like all other SexFight sex sounds) 

[MSM_Alice]

New test version fresh out of the oven.

Things to test: 

 

• New camera mode in all AAF scenes. It is needed for mid-aaf scene gameplay as the old fly cam had no subtitles and no dialogue selectors. Configurable ( and toggleable) in the new QoH MCM page. 
  • It is not that different except, it orbits around the actors, (can be rotated with the mouse), and can be biased/framed (up down left rigth and zoom in/out ) via keys one needs to set in the MCM.  This is done by altering the game's 3rd person camera settings. When AAF scene ends, 3rd person camera  returns to normal 3rd person camera, except if using Custom Camera mod,  then it should correctly return to your Custom Camera mod settings. 
• Violate should no longer forget that restraints are supposed to be added only on end, and only if the sexfight was lost. 
• Solved some flow issue with violate scenes following one after another too fast
• For now disabled frenzy if player has a follower.  Frenzies NPCs can happen only when the player is solo, otherwise is just death of Paralysis as successful outcomes. 
• Violate should now always remember that we always want the hud on in violate scenes. (but still if missing maybe toggle it on)
• All 4 magic dildos are now distinct,  thanks to  AAF_darthroman_creature_pack - Downloads - Advanced Animation Framework - LoversLab 1.0.3.a update.  Installing 1.0.3a is mandatory. If you are running NAF you need to regenerate your XMLs as there are some small XML changes to use the new anims.
• Added debug option to offer a visible reason via popup window on why the prostitution key does not do anything sometimes.  @Slip0213

 

• Probably upgrade from 0.7827 is  okay, but not much further..

 

There were some pretty extensive changes so I can have the infrastructure for the Queen of Hearts activities, so not putting it on the main page just yet. 

 

 

Edit: 7830 is deprecated  , See Download post below, 4 posts down, a new version of the mod, 0.7831 with a corrected bug , a bug  that in some circumstances, was blocking Charm/prostitution unless a console command was used after visiting wedge for caps.  ( Set MSMA_SanctBimboInSession to 0.0  )
https://www.loverslab.com/topic/245511-msma-sexfight-gameplay-bimbofication/page/62/#findComment-7128856

Edited September 14, 2025 by MSM_Alice

[Slip0213]

53 minutes ago, MSM_Alice said:

New test version fresh out of the oven.

You're awesome.

[Slip0213]

Nice!  The debug switch gave the reason.  Supposedly I can't prostitute myself because I'm filming with Wedge and friends.  I did another scene with them and tried again to no avail.  It seems I'm stuck.  

 

EDIT: I was planning on starting a new game with this update so I'll try to recreate the issue but hopefully it's a one-off. 

 

Edited September 14, 2025 by Slip0213
Starting a new game

[MSM_Alice]

3 hours ago, Slip0213 said:

Nice!  The debug switch gave the reason.  Supposedly I can't prostitute myself because I'm filming with Wedge and friends.  I did another scene with them and tried again to no avail.  It seems I'm stuck.  

 

EDIT: I was planning on starting a new game with this update so I'll try to recreate the issue but hopefully it's a one-off. 

 

Thank you.
That gives us something to work with before I build the corrected version on the main page. 
For instance now
 

1. I know there's maybe a sequence of events where that flag with Wedge does not get reset, and lo and behold,  indeed it was the last sex for caps session with wedge before betrayal was not properly resetting this flag) . 
AND 

2. I can tell you that probably all you need to do to correct your situation is go in console and do
set MSMA_SanctBimboInSession to 0.0

Edited September 14, 2025 by MSM_Alice

[MSM_Alice]

@Slip0213 Here is a version where that problem should not begin anymore.
If it has already happened then a 

Set MSMA_SanctBimboInSession to 0.0

Should be all what is needed to set it right.

(And the version above so it does not happen again when you visit Wedge for caps again ) it was a 100% occurrence if you were visiting Wedge past that last visit for caps alone (after building the generator) but rarely enough as not to trigger Piete's betrayal. 
Piete's betrayal would set it right again.

It is corrected now for all paths.

 

Edited February 19 by MSM_Alice

[Slip0213]

Thanks Alice.  This is good to know and I appreciate you looking at it.

 

How do I get the betrayal to fire?  I've tried a few times but no luck.  I think my strongest showing was 8 days in a row.

 

A side note: in my new game, the Vault Tec Rep hung at the door again.  Not really an issue but thought you might want to know.

[MSM_Alice]

8 minutes ago, Slip0213 said:

Thanks Alice.  This is good to know and I appreciate you looking at it.

 

How do I get the betrayal to fire?  I've tried a few times but no luck.  I think my strongest showing was 8 days in a row.

 

A side note: in my new game, the Vault Tec Rep hung at the door again.  Not really an issue but thought you might want to know.

0.7832 coming right up
Betrayal has a 50% to fire if you visit more than twice a day. ( but since one can't visit more then once every 6 hours so one should really insist )

Edited September 14, 2025 by MSM_Alice

[MSM_Alice]

Here it is, this one might even make it to the main page , if the salesman is fixed
Edit: Nevermind, I need to do more digging.
Probably some errant topic somewhere.

 

Edited September 14, 2025 by MSM_Alice

[MSM_Alice]

Here it is, should be sorted. Vault Tech rep should be talking again.
@Slip0213


Somehow Codsworth's craving management quest and its high priority Greeting lines were are problematic in pre war ?!?! 
I don't know how because they are conditioned clearly to only post war Codsworth, so I see no logical reason why they would block the Vault Tech guy to be talking from all people.
But when I reduced their priority all of a sudden the Vault tech guy was working.

Maybe to be extra safe I'll just key the Craving Cosworth integration entry points the Charm/Prostitution key, and delete those greetings lines altogether.

 

Edited February 19 by MSM_Alice

[MSM_Alice]

it could me more complicated than this. it could be that it works on some runs but not on others.

It is unclear to me what the issue really is with the Vault sales rep in prelude.
I don' t feel I get a clear view of what triggers that situation.

 

At any rate one can simply activate the mod after they get the pre-war prelude. 
I am still hunting for something that feels more definitive,

Edited September 14, 2025 by MSM_Alice