Sexlab Submit 01SEP14 1133

[id8888]

I want to say is encountered on the wild animals or undead creatures to fight,pressed the Submit Key by mistake,causing followers will follow you, but do not participate in combat, even if the attack does not fight back.
I think the reason may be followers surrendered to the enemy.

[dkatryl]

I want to say is encountered on the wild animals or undead creatures to fight,pressed the Submit Key by mistake,causing followers will follow you, but do not participate in combat, even if the attack does not fight back.

I think the reason may be followers surrendered to the enemy.

Okay, I understand.  That is not intended, and I thought there were sufficient ActorNPC checks made, but I guess not!

 

I'll look into it, fix if needed and it will be a part of the next update.

 

Edit: Okay, looks like that fixed it.  Added a temp Alias for the interim step between hitting the button and actually doing the player surrender.

 

I did a test run into a random cave.  Ran into skeletons at first, hit the surrender, the player didn't do anything naturally, and my follower momentarily did a StopCombat, (better safe than sorry), but since the player didn't officially surrender, my follower immediately drew her weapon again and start smashing skelly face.  Ran further into the cave, found some random necro dude, hit the surrender again, my follower StopCombat, but then, since the player officially did the surrender now, my follower took the full follower surrender alias, and we both went through the regular surrender stripping/debasement.

 

So, yeah, that should take care of that.

[jdods13]

 

 

I've got a very strange  but... SUPER strange... never had this issue before but I re-installed skyrim and started a new game and well... When ever I initiate sex with a woman through sexlab submit my character is transported to a giant camp about 300 feet in the air... My character is still playing the sex anim while he plummets to his death... I can ONLY have sex when I use a bed otherwise...loading screen, giant camp...and then splat!... WTF!?!?!?

 

Load order...please help me:

 

 

Skyrim.esm

Update.esm

Dawnguard.esm

HearthFires.esm

Dragonborn.esm

ApachiiHair.esm

RaceCompatibility.esm

Schlongs of Skyrim - Core.esm

HentaiPregnancy.esm

SexLab.esm

ZaZAnimationPack.esm

HighResTexturePack01.esp

HighResTexturePack02.esp

HighResTexturePack03.esp

unofficial skyrim patch.esp

RaceCompatibilityUSKPOverride.esp

unofficial dawnguard patch.esp

unofficial hearthfire patch.esp

unofficial dragonborn patch.esp

unofficial high resolution patch.esp

Chesko_Frostfall.esp

SplashofRain.esp

mintylightningmod.esp

fantasy music overhaul.esp

fantasy music overhaul - unique town music.esp

StaticMeshImprovementMod.esp

StaticMeshImprovementMod-DragonbornTernFix.esp

StaticMeshImprovementMod-FurnitureChestSnowFix.esp

Economics of Skyrim.esp

Economics of Skyrim - Dawnguard.esp

BirdsHFclean.esp

Birdsofskyrim.esp

CalienteVanillaArmorTweaks.esp

chesko_wearablelantern.esp

Dead Body Collision.esp

Real Clouds.esp

skyBirds - Airborne Perching Birds.esp

Smoking Torches.esp

Convenient Horses.esp

Character Creation Overhaul.esp

Footprints.esp

Footprints - Ash.esp

RaceMenu.esp

RaceMenuPlugin.esp

WetandCold.esp

WetandCold - Ashes.esp

SkyUI.esp

SexLab Submit.esp

iHUD.esp

Berserk Black Swordsman Armor.esp

Golden_Age_Arc_Sword.esp

Remodeled Armor - Vanilla Replacer.esp

Remodeled Armor - Vanilla Replacer - Dawnguard.esp

Remodeled Armor - Vanilla Replacer - Dragonborn.esp

Remodeled Armor - Underwear.esp

throwingweapons.esp

Throwing_Weapons_Misc_Plugin.esp

Throwing_Weapons_PerkTree_Plugin.esp

throwing_weapons_quiver_plugin.esp

Dr_Bandolier.esp

Lock Overhaul.esp

DeadlyDragons.esp

DeadlyDragonsArmory.esp

DeadlyMonsters.esp

run for your lives.esp

when vampires attack.esp

360WalkandRunPlus-RunBackwardSpeedAdjust.esp

CCO - Oblivion Carry Weights.esp

CCO - Permanent Birthsigns.esp

crossbows for the empire.esp

crossbows for the stormcloaks.esp

Distant DetailHF.esp

Headtracking.esp

Mercy.esp

Schlongs of Skyrim.esp

SOS - Smurf Average Addon.esp

SkyFalls - Distant Waterfall Overhaul.esp

SkyTEST-RealisticAnimals&Predators.esp

dD - Enhanced Blood Main.esp

dD-Dragonborn-Dawnguard-EBT Patch.esp

SaturationBoost.esp

Brevi_MoonlightTales.esp

WerewolfMastery.esp

HitStop.esp

dovahkiinrelax.esp

DeadlyCombat.esp

DragonCombatOverhaulDragonborn.esp

more dynamic injuries.esp

The Dance of Death - Ultimate Edition.esp

TKDodge.esp

CCO - Dynamic Skill Progression.esp

ABT - Loot Arrows +100%.esp

ABT - Faster Bolts Improved +100%.esp

ABT - Faster Arrows Improved +100%.esp

ABT - Merchants Arrows +100%.esp

ABT - Increased Bolts Damage (Vanilla) +150%.esp

ABT - Increased Progressive Damage (Vanilla) +150%.esp

ABT - Recover +50% Arrows and Bolts.esp

Stealth Skills Rebalanced_COMPLETE.esp

HeartBreaker.esp

TheEyesOfBeauty.esp

3DNPC.esp

RealisticNeedsandDiseases.esp

FAMP2.esp

RND_FAMP.esp

RND_USKP-FAMP.esp

RND_Dawnguard-Patch.esp

RND_HearthFires-Patch.esp

RND_Dragonborn-Patch.esp

TouringCarriages.esp

AmazingFollowerTweaks.esp

random alternate start.esp

argonianraptor.esp

CCO - Diverse Races And Genders.esp

CharacterMakingExtender.esp

DeadlyMutilation.esp

dD - Realistic Ragdoll Force - Realistic.esp

EnhancedCharacterEdit.esp

Flowing Cape.esp

BLEED.esp

PrivateNeeds.esp

PrivateNeeds-RND.esp

PrivateNeeds-Sexlab.esp

LPSleep.esp

SBF All In One + DLC v1.7.esp

Realistic Teeth Dawnguard Serana Vampire Fix.esp

followers_stealthkills.esp

zzEstrus.esp

Estrus Chaurus.esp

Estrus Chaurus DG.esp

HPSoulGemBirth.esp

SexLab Vanilla Voices.esp

enb_reference.esp

ENB Snow FX.esp

Brawl Bugs CE.esp

 

 

Please don't post mod lists.  I am not going to go through it, and it's very spammy by nature.  Or, at the very least, put the list inside the spoiler tags.

 

As to your issue, teleporting like that is not my mod, is an issue with the SSL Framework itself.  I simply make a StartSex() call, which is a Framework function.  Its generally very seldom, but it happens.  In fact, it happened to me once earlier tonight when trying to test the re-agro bug solution earlier.  Very annoying, but it happens.

 

But more to the point, it's a result of the Framework, not Submit.  I would suggest checking your SSL install and other relevant things regarding that.

 

 

Thanks for letting me know! Sorry about that

[PFK]

I noticed these errors in the papyrus log after fresh-install of SexLab Submit.
maybe it's nothing

 

 

Line 8: [08/29/2013 - 10:36:47AM] ERROR: Property actorList on script _slsubmittargetselect attached to alias PlayerRef on quest _SLSubmit (29001826) cannot be initialized because the value is the incorrect type
Line 12: [08/29/2013 - 10:36:47AM] ERROR: Property Pages on script _slsubmitconfig attached to _SLSubmit (29001826) cannot be initialized because the value is the incorrect type
Line 13: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorSexPartner on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 14: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorAssailant1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 15: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorBully1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 16: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorGuard on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 17: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorAssailant2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 18: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorBounty on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 19: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorBully2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 29: [08/29/2013 - 10:36:48AM] ERROR: Property actorList on script _slsubmittargetselect attached to alias PlayerRef on quest _SLSubmit (29001826) cannot be initialized because the value is the incorrect type
Line 30: [08/29/2013 - 10:36:48AM] ERROR: Property Pages on script _slsubmitconfig attached to _SLSubmit (29001826) cannot be initialized because the value is the incorrect type
Line 31: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorSexPartner on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 32: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorAssailant1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 33: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorBully1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 34: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorGuard on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 35: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorAssailant2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 36: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorBounty on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property
Line 37: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorBully2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

 

[dkatryl]

I noticed these errors in the papyrus log after fresh-install of SexLab Submit.

maybe it's nothing

 

 

Line 8: [08/29/2013 - 10:36:47AM] ERROR: Property actorList on script _slsubmittargetselect attached to alias PlayerRef on quest _SLSubmit (29001826) cannot be initialized because the value is the incorrect type

Line 12: [08/29/2013 - 10:36:47AM] ERROR: Property Pages on script _slsubmitconfig attached to _SLSubmit (29001826) cannot be initialized because the value is the incorrect type

Line 13: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorSexPartner on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 14: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorAssailant1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 15: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorBully1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 16: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorGuard on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 17: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorAssailant2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 18: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorBounty on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 19: [08/29/2013 - 10:36:47AM] warning: Property Alias_ActorBully2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 29: [08/29/2013 - 10:36:48AM] ERROR: Property actorList on script _slsubmittargetselect attached to alias PlayerRef on quest _SLSubmit (29001826) cannot be initialized because the value is the incorrect type

Line 30: [08/29/2013 - 10:36:48AM] ERROR: Property Pages on script _slsubmitconfig attached to _SLSubmit (29001826) cannot be initialized because the value is the incorrect type

Line 31: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorSexPartner on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 32: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorAssailant1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 33: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorBully1 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 34: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorGuard on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 35: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorAssailant2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 36: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorBounty on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

Line 37: [08/29/2013 - 10:36:48AM] warning: Property Alias_ActorBully2 on script QF__SLSubmit_04001826 attached to _SLSubmit (29001826) cannot be initialized because the script no longer contains that property

 

 

Hrm, interesting.  Thanks for pointing that out.  Not sure why that would be, as I haven't touched QF__SLSubmit_04001826 in forever.  In fact, when I move all of the scripts from my active /Data folder to my /Submit Update folder for easy .7z compression, I don't even move QF__SLSubmit_04001826 with the others, since it is a pain to always go hunting for that one single QF_ script, plus I simply haven't changed it since it was created way back when I fixed the Hotkey.

 

At any rate, those error/warnings may be a result of splitting up *another* script into two smaller ones for easier management.  I'll check it tonight after work.

[PFK]

"One is glad to be of service"

[shinji72]

Yeah I've noticed the papyrus spamming too...

[dkatryl]

Yeah I've noticed the papyrus spamming too...

For reasons I have never been able to figure out, despite following the directions for every single tutorial on enabling the debug output, everytime I check the folder that is supposed to have the data dump, nothing is ever there for me to look at.

 

So that is why I am always oblivious to these warnings until someone posts it here.  It's kind of annoying actually. 

 

Edit: Okay, checked that script, and all of those Aliases referenced are indeed now part of the OTHER half of the script pair that was created when I broke the single one into two smaller ones.  So, I just deleted those references, and everything seemed to still be working just fine.  So that should lessen the erroneous debug spam now.

 

And the re-agro suppression fix seems to still be working as intended, I haven't witnessed any wonky unintended side effects, and the fix actually is fairly nonintrusive to how the mod was originally designed to work, so I don't see any reason to hold off on it any longer.  I'll package everything up (that plus the small handful of other fixes) and upload tonight in a bit.

[dkatryl]

• 29AUG13, ~2115CST:
• ***My mod did not create the re-agro bug, I don't know what causes it, I don't know how to remove it, I am only suppressing it.***
• Added temp Alias + AI Package to the Ambush, Grapple, and Shout scripts that, on a successful attempt, should suppress the re-agro bug on the current target.
• Current target will adopt an AI Package that will cause them to ignore combat, stand still, and randomly cower indefinitely*.  This will allow the player to then initiate dialog as designed and do whatever they want.
• This AI Package will only work on one NPC at a time.  Meaning, the current target will adopt the AI Package indefinitely, until you go and target a new NPC.  After you force a new NPC to submit, the previous NPC will no longer have the AI Package.  If they suffer from the re-agro bug, they will once again be hostile.
• You can always make an older NPC that may suffer from the re-agro bug re-submit, and they will once again be the current target and re-adopt the AI Package to make them passive.  This can be repeated indefinitely if the player desires.
• Fixed issue where you could accidentally hit the Submit button when engaged with a non-ActorNPC type, and while the player wouldn't surrender, your follower would go passive and get stuck not helping.
• Fixed issue where the coercion properties didn't get reset when I split the main script in two a few weeks ago.
• Fixed issue where if you used the Grapple/Shout on a NPC *after* you had already raped them once, you wouldn't get the "Now what should I do with you" dialog
• Deleted old Alias references in the QF__SLSubmit script that were associated with the old main script that was split in two.  Should cause less debug papyrus spam now.

Hopefully, the re-agro bug, while not eliminated, will be suppressed enough for people that were having issues to not be overly bothered by it now.  I know my own incident is now resolved, so it should be good for everyone else now.

[dkatryl]

I made a small little edit to the Stamina cost for the Grapple/Ambush to help out lower level/lower stamina characters a bit.  Currently, it costs 50 Stamina per use ever since I moved the Grapple/Ambush to not be tied to the Shout/Powers cooldown.  50 Stamina is pretty hefty for a new character, and will make it difficult to attempt.  Since the algorithm will naturally make it harder for a lower level character to succeed, I feel like making it harder to even make the attempt itself for a lower stamina character is unnecessarily doubly punitive.

 

So, the Stamina cost will now be 20% of your max Stamina up until a hard cap max of 50 Stamina cost at 250+ max Stamina.  Which means for a fresh level 1 character, the cost should be ~20 Stamina, and will progressively increase as your Stamina increases, until you hit 250+, after which it will hit the cap.  Some quick numbers for those that are confused:

 

100 Max Stam

20 Stam Cost

5 attempts with 0 Stam regen

 

200 Max Stam

40 Stam Cost

5 attempts with 0 Stam regen

 

250 Max Stam

50 Stam Cost

5 attempts with 0 Stam regen

 

500 Max Stam

50 Stam Cost

10 attempts with 0 Stam regen

 

1000 Max Stam

50 Stam Cost

20 attempts with 0 Stam regen

 

So, that should make it less punitive for very low level/low stamina characters, while still giving a proper advantage for high level/high stamina characters.

 

I've already implemented this change in my own copy, but I am going to hold off for a day or so before posting this update because I want to wait for feedback on the re-agro bug suppression update and everything from tonight's update.

[RUD3DUD3]

just a one funny pic can also be a glitch 

 

 

 

 

[krusanagi]

just a one funny pic can also be a glitch 

 

 

Screenshot248261.jpg

 

 

hahaha. but seriusly.... i having problem. the npc submit and no longer aggressive but when i try talk to him, so submit or die dialog... no dialog at all. 

[Vivi]

Gonna test the new version when i get home. This reagro stuff can be really annoying, thats why i had to stop using Sanguines Debauchery as well, those a-holes just kept attacking

[dkatryl]

 

just a one funny pic can also be a glitch 

 

 

Screenshot248261.jpg

 

 

hahaha. but seriusly.... i having problem. the npc submit and no longer aggressive but when i try talk to him, so submit or die dialog... no dialog at all. 

 

Not sure why that would be, I tested it repeatedly on the only NPC that seemed to generate the bug for me (This one stubborn bandit lady on the tower halfway up to Bleak Hollow.  So odd it's ONLY her so far, but it's her EVERYtime I've gone there now) and she goes passive and I can talk to her just fine.

 

Is the NPC just standing there, randomly cowering, weapons not out, etc?

 

I also tested it on *other* NPC's, ones that didn't have the bug, and it worked on them as well.  And once the AI Package was moved to the current target, if I trotted back down the hill to the toiwer with the one bandit lady, sure enough, she'd re-agro, I'd smack her down, and then she would go passive once again.

[dkatryl]

just a one funny pic can also be a glitch 

 

 

Screenshot248261.jpg

 

 

I don't see what the problem is.  You've never fucked a ghost?

 

(Hehe, that reminds me of when I used the Ambush on the Nightingale ghosts during the TG chain and had myself some spectral nookie! )

 

It's not really a glitch, so much as that I can only make it so exclusive before it starts to exclude targets that should be valid.  Apparently, the HH there was classified as an ActorNPC.

[RUD3DUD3]

no way im getting involved in that but its very funny asking a headless horsemen for good times

[srayesmanll]

no way im getting involved in that but its very funny asking a headless horsemen for good times

 

You never know, maybe he gives great head...

 

 

 

 

waaaiittt, I think I see the flaw...

[Thanos]

I know you wrote you probably won't add features to this anymore but since I think this might actually be easy I'll ask anyway:
Could you add a simple: "Follow me"/"Stay Here" command under the "What should I do with you" Dialogue-Tree which adds/removes the follow player package (like when you turn in bandits for bounty).

I came across some (I think) non-respawing enemies which subitted to me and thought i'd be nice to just lead them into a player-home. You know... store them away for later use.

This would probably create strange effects with resetting/respawing enemies, but that's something the player just has to deal with.

[Crate123]

Just updated to the latest version, for reasons unknown the weird bug where NPC's follow me if I have my way with them an even numbered times is finally gone. Hurray!

 

@Thanos

Install one of the slavery mods and do it that way.

[dkatryl]

I know you wrote you probably won't add features to this anymore but since I think this might actually be easy I'll ask anyway:

Could you add a simple: "Follow me"/"Stay Here" command under the "What should I do with you" Dialogue-Tree which adds/removes the follow player package (like when you turn in bandits for bounty).

I came across some (I think) non-respawing enemies which subitted to me and thought i'd be nice to just lead them into a player-home. You know... store them away for later use.

This would probably create strange effects with resetting/respawing enemies, but that's something the player just has to deal with.

Them following you is already effectively done when you declare to turn them in for a bounty.  A "Stay Here" would require yet another Alias /AI Package, or else they would just return to their original spawn location, like when you dismiss a follower.  Which means it would only work on one NPC at a time, because the next one you told to stay would adopt the Alias, removing it from the previous, and the previous would then return to their spawn location.

 

So, meh, maybe.  But it would be nothing more than that.  I am not doing some perma-slavery crap.

[dkatryl]

Just updated to the latest version, for reasons unknown the weird bug where NPC's follow me if I have my way with them an even numbered times is finally gone. Hurray!

 

@Thanos

Install one of the slavery mods and do it that way.

Good to hear!

 

And that was my thinking.  I am not making a perma-slavery system, and there are already mods for that.

[Oversette]

Greetings!

 

I am in doubt about the raped followers feature.
In the mod's description, I see this:

• Followers currently only surrender and cower, getting stripped and giving currently worn gear + gold to random opponent that is abusing the player.

And makes me think followers are not raped, ever, but then I read this:

 

• Followers will not engage in sex with any extra NPC's beyond the first two that take the player, simply because I couldn't get them to trigger properly.

 

Which implies that followers will be raped but only by the same NPCs that the player.

 

And this kinda confirms the previous one:

 

• Removed some of the unnecessary extra Aliases that existed in the Player Surrender function. They were originally created for spillover NPC's to rape your follower, but since I never got that to work, I removed them.

 

So, how does it work?

Are followers raped by the same NPCs as the player (after?), or not at all?

 

And, of course, thanks for the mod. I love the way it integrates with the game. c:

[dkatryl]

Followers are not raped.  The middle one just means the first two will be busy with the player, the rest do nothing.

 

I never got the follower part to work, and I have no plans on going back and wasting more time on it at this point, so the most they will do is cower and get robbed.

[SGTPinback]

I've used your mod (aug15 version) for a couple weeks and had a good time with it on my last playthrough. Thanks And thanks for including the source code. I've been trying to learn some things about Papayrus and that helps a great deal.
I'm currently buliding a clean install for a new game and updated mods. I ran Tes5Edit on my list and noticed a "Found a struct with negative size!" error on the SexLab Submit esp. Checking for errors gives this:

[00:00] Checking for Errors in [03] SexLab Submit.esp
[00:00] Found a struct with negative size! 06A3DE8F < 06A3DE8C
[00:00] Found a struct with negative size! 06A3DE8F < 06A3DE8C
[00:00] Found a struct with negative size! 06A3DE8F < 06A3DE8C
[00:00] Found a struct with negative size! 06A3DE8F < 06A3DE8C
[00:00]                     Type -> <Unknown: 0>
[00:00]                   Above errors were found in :Property
[00:00]                 Above errors were found in :Properties
[00:00]               Above errors were found in :Script
[00:00]             Above errors were found in :Scripts
[00:00]           Above errors were found in :Quest VMAD
[00:00]         Above errors were found in :Data
[00:00]       Above errors were found in :VMAD - Virtual Machine Adapter
[00:00]     Above errors were found in :_SLSubmit "SexLab Submit" [QUST:03001826]
[00:00]   Above errors were found in :GRUP Top "QUST"
[00:00] Above errors were found in :[03] SexLab Submit.esp
[00:00] All Done!

Drilling into it further in the VMAD section, It looks like the 'pages' property on the _SLSubmitConfig script has a type of <unknown> and lots of hex data associated with it on the next line.
So I loaded the plugin up in the CK to take a look and the value for this property was <unknown> so I hit the 'clear value' button and the value changed to <default>.
I then hit 'ok' a couple times and get a large number of compile errors on qf__slsubmit_04001826 (which I didn't touch). I then saved the plugin. The compile errors are probably on my end - can't seem to compile anything in the framework either even though I have all the requirements.

The qf__slsubmit_04001826.psc source file reverts to the version with all the alias properties in it, but the 'properties window is empty on that script.
Anyway I think you've run into a CK bug and those aliases are still floating around in the VMAD data of the plugin. After saving the plugin, Tes5Edit then reports errors about aliases in the quest fragment.

This was all done with a Aug29 version of submit and I tried both Lab framework 1.4 and 1.5

 

Edit:
The compile error was due to missing SKSE .psc files on my end. Apparently the SKSE installer doesn't provide those. With these in place, the quest fragment compiles and all the properties show in the window. Tes5Edit then just complains about the 'actorlist' property, which I can't find.

 

[pringles89]

not sure if it's a bug or just my mods, but when i upgraded from 8/22 to 8/29 version, i lost ability to dimiss and recruit followers.  i had mjoll following me and could not dimiss her even though i see the "follower leaves your service" message. every potential follower (including mjoll) i talked to would have the "it's time for us to part ways" option at the very bottom and not "follow me, i need your help"