Yamete! (Abandoned)

[semper_solus]

3 hours ago, Scrab said:

Though when semper isnt a tester as terrible as I

 

Not sure what you're talking about, I've got gremlins in my mod list that messes up all combat sex related mods. Half of my outcomes are mysteries to us all.

 

2 hours ago, Scrab said:

V4.B3.1

 

Tested this out, same as before.

 

Armor works great.

 

Knockdowns are... different... but they still fire it seems. Now they go right into bleedout, and THEN the scene triggers, but that's it.

 

Does the More Rounds and Reverse option only work in Traditional right now? That wasn't firing during Rushed. (As you can tell, I like it Rushed  )

[Scrab]

29 minutes ago, semper_solus said:

Knockdowns are... different... but they still fire it seems. Now they go right into bleedout, and THEN the scene triggers, but that's it.

What do you mean "different"? Like in a good or a bad way? Ayah..

I did a couple of things which I hoped would smoothen things out:

1. The gathering of an Actors strippable Armor should be (a lot) faster & lighter than before (suprise )
2. Type0 now respects the custom Bleedout Setting in the MCM. Though not sure if that stays, it looks a bit weird since there is no actual "enter" Animation, huh..
3. BleedoutExit now only staggers when you are holding a Bleedout Mark, rather than always

 

38 minutes ago, semper_solus said:

Does the More Rounds and Reverse option only work in Traditional right now?

nop, this is primarily intended to be a final bugfix release for Rushed

[semper_solus]

On 9/11/2021 at 6:01 PM, Scrab said:

What do you mean "different"? Like in a good or a bad way? Ayah..

 

Not bad, just instead of the Followers just standing and then SL putting the scene together and then activating, they instead now drop to bleedout, and then SL puts the scene together and runs it.

 

On 9/11/2021 at 6:01 PM, Scrab said:

nop, this is primarily intended to be a final bugfix release for Rushed

 

So More Rounds and Endless are supposed to be working with Rushed now? Because I haven't been seeing that happen

 

Edited September 13, 2021 by semper_solus

[Scrab]

8 hours ago, semper_solus said:

So More Rounds and Endless are supposed to be working with Rushed now?

nop  

Resolution in Rushed isnt a bug, its a Feature Request that Ill start working on now

 

==

 

I assume Someone still has HasKeyword() issues btw?

[Someone92]

18 hours ago, Scrab said:

Talking about Reapers Mercy being OP

Poll:
I cannot vote.
Most likely people who already voted in the first poll cannot vote in the second poll.

Regarding the poll.
If I understood correctly that is about the PC being the aggressor. For the time being I have no interest in that.
However if I play as a succubus-like character that sucks their victims to death during sex / rape what I would be looking for is a power that I need to manually activate (so now auto activation from regular attacks). IT has a random chance to succeed, and the chance is increased if it was a sneak attack, if I attacked from behind, and by little renaming health the target has (as a percentage of their maximum health). For such a purpose I do not like being gated from options the mod provides.
Not sure if that is even the direction you plan to go for your mod, though.

 

On 9/11/2021 at 9:46 AM, Scrab said:

Thats expected behavior, it show Rushed works (unless I misunderstand)

It was a quite test to see if the very same actors are valid aggressors in the Rushed scenario. Cause for me it didn't make sense that the mod checks if an actor is a valid aggressor in Rushed scenario differently than in Traditional scenario.

Guess I was wrong.

 

.

 

Regarding the dialog options:

If you ever plan to expand on the dialogs you already have included, what I would love to see is:

- NPCs comments are saved in a .txt file so they can easily be edited / expanded / exchanged by the player(s)

- Context-sensitive dialogs, e.g. a male aggressor with a female victim would choose his line from a different pool of comments than a female aggressor with a female victim, female aggressor with a male victim and so on

- Spectators would sporadically comment during the animation, and again, context sensitive; female spectator / male spectator, F/M scene, F/F, M/F or M/M

 

.

 

15 hours ago, Scrab said:

 

• Added "Reverse Rape Algorithm" Option under Resolution -> Rape

Does the percentage chance then indicates the chance for the aggressor being satisfied, or unsatisfied?

From a single test it seems to be satisfied, but unsatisfied makes more sense, as a higher percentage would then mean more assaults, just like a higher percentage in the "normal" setting.

 

2 hours ago, Scrab said:

 

I assume Someone still has HasKeyword() issues btw?

Had to work the last two days, couldn't test.

Tested Yamete!_V4.B3.1, it has gotten even worse.

 

First test with filtering all creatures out. Stuck at bleedout.
Second and third test with allowing all cretures. Stuck at bleedout.

 

Those three tests were done with the same savefile as Yamete!_V4.B3.0 iirc.

 

 

 

Tried a new game, this time without Deadly Wenches.

 

Used OBIS and Womanized Leveled List for OBIS with Deadly Wenches

This time around it worked as intended. No sure if it works now because no longer Deadly Wenches or because of update + new game.

Papyrus.0 - No Creatures.log Papyrus.0 - Creatures - No success.log Papyrus.1 - I think this was the third try with creatures and no success.log Papyrus.0 - OBIS vanilla questionmark NPCs.log

[Scrab]

1 hour ago, Someone92 said:

This time around it worked as intended. No sure if it works now because no longer Deadly Wenches or because of update + new game.

You should always play on a new game when testing out those betas. Im not interested in caring for Backwards compatibility in the slightest. Most of them will break if playing on an existing save

Am I assuming correctly though, that the last try with a new game worked as expected?

 

1 hour ago, Someone92 said:

Does the percentage chance then indicates the chance for the aggressor being satisfied, or unsatisfied?

From a single test it seems to be satisfied, but unsatisfied makes more sense, as a higher percentage would then mean more assaults, just like a higher percentage in the "normal" setting.

Its the Chance that they are satisfied. I may update the Highlights to clarify this more

 

1 hour ago, Someone92 said:

Not sure if that is even the direction you plan to go for your mod, though.

Basically the Question is if Reapers Mercy should be treated the same way as an regular NPC Knockdown is with the settings n everything or if people would prefer it if the Feature would be created seperated from it, with its own Systems, Conditions, Features, beyond just a basic knockdown

Basically creating an individual Reapers Mercy together by collecting "building Blocks" which for example define the threshold for an HP knockdown or add new unique ways of knockdowns which I want to avoid implementing into the main knockdown algorithm as they would either be too complicated (e.g. stacking up a Weakening Debuff that you need to stack and on max stacks the Victim would be claimed) or too random (e.g. a random hit chance)

Edited September 12, 2021 by Scrab

[Someone92]

Bug:

The third actor in 3p anims do not respect filter settings. Had a male NPCs in a FFM anim.

 

Bug:

You can cause a traditional scenario to end prematurely by running away. The victors run after you, and after some time the PC plays the hitstun anim, and when you then run towards the victors, they all get into a hitstun anim and the scene ends.

 

Also, I forgot to write down at which of my tests it happened, but sometimes the victors are afraid of the PC after the traditional scenario.

I assume interacting (trying to speak to them repeatably, attacking them) with them while the are still forced to be friendly by the mod breaks their AI.

 

  

8 hours ago, Scrab said:

Basically the Question is if Reapers Mercy should be treated the same way as an regular NPC Knockdown is with the settings n everything or if people would prefer it if the Feature would be created seperated from it

Personally, I do not think PC as aggressor works with a on-hit based system.

 

edit:

I completely forgot, I did two test run.

In the first one a wolf managed to cause a knockdown even though animals were disabled.

 

In the second one, a male joined in one a FFM anim.

Papyrus.0 - Wolf caused knowdown.log Papyrus.1 - Male NPC.log

Edited September 12, 2021 by Someone92

[Scrab]

5 hours ago, Someone92 said:

In the first one a wolf managed to cause a knockdown even though animals were disabled.

Youre using a selective filter, right? If so, anything can knock you down, even stuff that isnt valid. Thats what selective does - no checks upon hit

 

the other one would come back to the not filtering out actors, eh?

[Scrab]

V4.B3.2

 

Yamete!.7z

• Resolution Rape
  • Updated MCM Documentation
  • Repeated Assault Chance with an Reverse Algorithm now dictates if an aggressors stays interested instead of whether or not they lose interest
  • You can now always set the Max Rounds to 0 to negate the round-limitation
• Rushed
  • Integrated Resolution into Rushed
    Be aware that the robbing Consequence while properly pretty fun in Rushed I can imagine, will cause Actors far away to port to the Victim after a short delay which may seem weird if the aggressor is sitting on the other side of the map (like an archer)
  • Rushed now respects Gender & Race settings in a Selective Algorithm
  • After Rushed ends, Actors will be properly standing up again from Bleedout
• Traditional
  • Fixed an issue with Adult Scenes after the first no longer respecting Gender Settings
• Actors (including the Player) are no longer able to move around between Yamete! controlled adult-scene-loops
• Fixed an issue with the Flee Mark affecting NPC that arent bleeding out

[semper_solus]

1 hour ago, Scrab said:

V4.B3.2

 

Haven't started testing Traditional yet.

 

As for everything else, working as before..... .... except for scenes not triggering after knockdowns  I get the notification of knockdown, but they drop into bleedout and stay that way til after combat.

 

Same settings as before.

 

Papyrus.0.log

[Someone92]

1 hour ago, Scrab said:

Integrated Resolution into Rushed

So basically Traditional scenario with 1 victor, judging from my tests.

 

Can it be that Yamete takes a few seconds to register a fight and make the player Essential and track hits? Cause I did multiple times during Combat.

Some further testing seems the script load after loading is so big Yamete does not register hits for half a minute or so.

 

From testing, Rushed seems to put the PC into bleedout after the anim finishes way quicker than Traditional. So attempting the same glitch as with Traditional is seemingly impossible.

May that be because the mod first checks if there are valid victors in Traditional, and only then put the PC in bleedout?

 

  

11 minutes ago, semper_solus said:

 

As for everything else, working as before..... .... except for scenes not triggering after knockdowns

Because I made the mistake as well:

HAve you started a new game trying the new beta? Cause that is what made the mod not work in my previous tests.

Edited September 12, 2021 by Someone92

[Scrab]

18 minutes ago, semper_solus said:

except for scenes not triggering after knockdowns

Did you remember to let SL run its installation stuff?

 

7 minutes ago, Someone92 said:

So basically Traditional scenario with 1 victor, judging from my tests.

Basically yes. No Dialogue, only 1 Victoire but it all happens mid combat

 

7 minutes ago, Someone92 said:

Can it be that Yamete takes a few seconds to register a fight and make the player Essential and track hits? Cause I did multiple times during Combat

Yamete only turns you essential while the Combat Quest is active. Thats controlled by the engine, if the Quest start is delayed by something then the Essential Flag will also be, ye

 

7 minutes ago, Someone92 said:

From testing, Rushed seems to put the PC into bleedout after the anim finishes way quicker than Traditional. So attempting the same glitch as with Traditional is seemingly impossible.

May that be because the mod first checks if there are valid victors in Traditional, and only then put the PC in bleedout?

There is in fact a 1 second delay before an Actor is put into Bleedout in Traditional. Not entirely sure why that is there though. Ill remove it with the next upload

Edited September 12, 2021 by Scrab

[semper_solus]

7 minutes ago, Someone92 said:

Because I made the mistake as well:

HAve you started a new game trying the new beta? Cause that is what made the mod not work in my previous tests.

 

I have a testsave set aside with no defeat type mods active and I've used it successfully thus far. This is just a normal round of testing for me, everything works except one thing.

 

 

Also, mildly unrelated question... as the Author of SL Consequences, do you have or know of an SE mod like it. I want to regain my Magicka by sexing my followers.

[semper_solus]

Papyrus.0.log

 

Went for a second go around. Bandits/Humans work fine. But Creatures are borked.

[Scrab]

8 hours ago, semper_solus said:

Bandits/Humans work fine. But Creatures are borke

What does borked mean

 

Based on the log, the reason why Animations dont start at the end is because SL doesnt deem the combination valid. You do have Creature Anims enabled & got fitting ones installed?

[semper_solus]

9 hours ago, Scrab said:

What does borked mean

 

Based on the log, the reason why Animations dont start at the end is because SL doesnt deem the combination valid. You do have Creature Anims enabled & got fitting ones installed?

 

Everything is the same as all my other attempts. It's like what happened last time when I had "Use List" minus Dragons but half the creatures wouldn't animate. So, once I put it on All, it worked, but now it is not. Nothing else is different.

 

All other mods involving Creature animations work, and the previous Beta works (Previous beta used on completely different save, if/since that likely needs to be clarified)

Edited September 13, 2021 by semper_solus

[Scrab]

20 hours ago, semper_solus said:

It's like what happened last time when I had "Use List" minus Dragons but half the creatures wouldn't animate. So, once I put it on All, it worked, but now it is not. Nothing else is different.

YamSexLab.pex

 

Removing parts of the race analytics, I guess worst case here is that SL wont be playing an Animation, which doesnt really matter too much

In fact unless youre having a fight in which storm, flame, a necromancer and a wolf all try to rape you simultaneously, that check wouldnt return false anyway - if it were working that is, so meh. Cant trust Papyrus anymore, like even less than you already should

Edited September 14, 2021 by Scrab

[semper_solus]

Good news is that creatures are now triggering. More Rounds is working for humans and creatures alike.

 

Then I tried Endless...  

 

It worked with one of my Followers, the others got 1 round and then combat reengaged like normal.

It even stopped the scene when I blasted the Troll with a firebolt, excellent.

But after I killed that Troll, Combat wouldn't end and the other Followers were stuck in bleedout (the one stuck in Endless went back into Follower mode, so that works)

 

Not sure how much of Endless you had but a lot of it seems to work as I would hope... with a few minor details needing ironing out.

 

Papyrus.0.log

[Scrab]

Endless is still WIP, or I dont know if its WIP or not tbh, I didnt test nor detail it yet. Kinda forgot about it, nyaa

 

1 hour ago, semper_solus said:

It worked with one of my Followers, the others got 1 round and then combat reengaged like normal.

Thats because theres only 1 Thread. Endless is limited to a certain amount of Threads which have to be created inside the esp

 

1 hour ago, semper_solus said:

But after I killed that Troll, Combat wouldn't end and the other Followers were stuck in bleedout (the one stuck in Endless went back into Follower mode, so that works)

Combat didnt end because the Endless Thred doesnt actually reset the Thread in the Combat Quest and thus Combat never closed

The Endless Thread has its own Cleanup Algorithm, thats why that follower specifically had no issues but he was still marked as claimed in the Combat Quest

 

Was the Follower being stuck in Bleedout expected behavior?

 

1 hour ago, semper_solus said:

with a few minor details needing ironing out.

What minor detail, only the bug above?

Edited September 14, 2021 by Scrab

[semper_solus]

11 minutes ago, Scrab said:

What minor detail, only the bug above?

 

All I can think of is Endless only triggering just once, and the other Followers stuck in bleedout.

I mean, it worked pretty well for something you haven't really been working on

[Scrab]

1 hour ago, semper_solus said:

All I can think of is Endless only triggering just once, and the other Followers stuck in bleedout.

I mean, it worked pretty well for something you haven't really been working on

Im just going to trust your testing then:

 

V4.B3.2.1

Yamete!.7z

• Removed Creature Race analytics from SL Animations as those seem to cause more issues than preventing them
• Endless Threads in Rushed now properly unclaim that Victim, no longer causing the Combat Quest to get stuck
• Increased Endless Thread Count from 1 to 5

 

==
 

Regarding Reapers Mercy since the tendency goes heavily into the Direction of Progression Systems, and Skill Tree;

I was thinking about how to properly implement Reapers Mercy since the old System sounds kind of annoying to manage if its really just unlocking new highs. I think what I want to do instead is turning Reapers Mercy more into a passive Ability that you can keep active for majority of your playtime, and was thinking following this design moreso than a simple conditioning one:

• Reapers Mercy has a Base Chance to knock Actors down with each Hit. At the beginning this Chance will probably be something like 2%
  (This sounds low ik but the OnHit Event is weird, sometimes firing multiple times in one hit and when keeping it active for a longer while should trigger regulary, rather than just making it this thing you use to get a specific Actor once and then never using it again)
• You may increase this Chance with Points, 2/4/6
• Abilities will focus on increasing this Chance, rather than giving new ways to knock targets down:
  • Frail Feed -> Knockdown Chance is increased if the Target is below 30/60/90% Health
  • Lurking Shadows -> Knockdown Chance is increased if the Target isnt detecting you
• Or support you in giving you certain utility
  • Shadows Captive -> An about-to-be-claimed target cannot by killed by your hand if its not detecing you
    (To allow high level assassins to claim victims through stealth kills)
  • Reapers Gaze -> 1/day; Mark a Target for Claiming, if its Hp fall below 30/60/90%, claim it. Maxing out this Ability allows you to see this target through walls; furthermore, affected targets cannot draw their weapons, the target wont be alowed to die either
  • Reapers Command -> Enslave claimed Victims
    • A Claimed Target cant move but can still be raped, killed, drained but to take it with you, you will need Reapers Command

 

 

 

 

Edited September 14, 2021 by Scrab

[johnhamm]

I'm getting an issue where my follower won't drop armour when getting hit. I have her set to the scorpion profile with a 100% chance to drop something but nothing happens. It worked fine at first, but now it doesn't seem to work at all. I think it is related to her being a follower, because when I dismissed her it was possible for the armour to be knocked off, but I have the settings for NPCs and followers exactly the same, so I don't know why it's different. I am using Nether's follower framework, and the follower is Yuriana from the buxom wenches mod

[semper_solus]

3 hours ago, mystic065 said:

I am using Nether's follower framework, and the follower is Yuriana from the buxom wenches mod

 

I've been having Nethers issues. I'm currently using Simple Follower Extension, and it works well with this mod. Only downside is that it teleports Followers to me at a certain distance, and if they are in the 'More Rounds' or 'Endless' mode, they teleport to me between scenes and its awkward (I was testing that feature out)

 

Did they fix the Buxom Wench mod? I had to uninstall it mostly because Yuriana's voice pack was off when she was a Follower; bouncing between two voice types in certain dialogue threw me.

 

3 hours ago, Scrab said:

V4.B3.2.1

 

As mentioned above, I was having teleportation issues not related to Yamete but it was both annoying and humorous.

 

Anyway, things went really well overall, with just some minor hiccups:

 

1st wave - Trying out More Rounds

 

Went perfectly. Only complaint is damaging them didn't break the scene and I had to wait through the multiples (not a huge issue and probably not part of the script, just an observation of very mild inconvenience)

 

2nd wave - Trying out Endless.

 

Went very well. Some knockdowns didn't trigger assaults at first, but eventually all Followers went into scenes and all scenes stopped when I attacked. (A brief intermission happened as a passing patrol of Imperials also broke up some scenes, but that was fine. Glad helpful NPCs were nearby)

 

3rd wave - Trying out Endless with me leaving the area

 

Started off well, but as I left, the Simple Follower Framework kept teleporting them to me between scenes. This may have caused the following issue but it happened last time as well: 2 of the Followers dropped into bleedout but the Assailants were killed before the Assault started and they got stuck in bleedout after Combat ended.

 

Papyrus.0.log

 

I'm going to try out the Reverse Algo but I'm also *sigh* looking at trying to make Nethers work again... just because of that teleport... maybe

 

Edit: Got a whole new save up and running with NFF, everything else the same. Seems to be working out well. Guess my issue seems to be Custom Followers... never again  

Edited September 14, 2021 by semper_solus

[Scrab]

4 hours ago, mystic065 said:

I'm getting an issue where my follower won't drop armour when getting hit. I have her set to the scorpion profile with a 100% chance to drop something but nothing happens. It worked fine at first, but now it doesn't seem to work at all. I think it is related to her being a follower, because when I dismissed her it was possible for the armour to be knocked off, but I have the settings for NPCs and followers exactly the same, so I don't know why it's different. I am using Nether's follower framework, and the follower is Yuriana from the buxom wenches mod

The code is the same for both

I remember there being a bug in the Vanilla Game that if you dont add armor before equipping it, that armor would still be equipped to an Actor but not be registered as "equipped". If Nether is recreating this bug in its code, then thats probably the issue

 

It would work the first time as the Armor would be properly equipped, but on the 2nd attempt when Nether enforces the Armor again, it wouldnt be properly registered as "worn" and thus my Functions dont recognize it, returning an empty array and never thus never stripping anything

 

2 hours ago, semper_solus said:

Edit: Got a whole new save up and running with NFF, everything else the same. Seems to be working out well. Guess my issue seems to be Custom Followers... never again  

All I can do is set Followers to be waiting for the Player. Im fairly sure Im doing this, Im even removing the Teammate Flag, cant do much more. Would expect the mods implementing those features to respect this too tbh, my pardon

[semper_solus]

5 hours ago, Scrab said:

All I can do is set Followers to be waiting for the Player. Im fairly sure Im doing this, Im even removing the Teammate Flag, cant do much more. Would expect the mods implementing those features to respect this too tbh, my pardon

 

Nothing to do on your end. This was in reference to over a week ago when I axed both NFF and Custom Followers from my mods because of the consistently buggy issues I was having at the time regarding Followers not being handled or tracked properly. As much as I like Sofia, she's a Follower that doesn't play well with mods that interact with Follower related things... I've had many issues in the past trying to use her without incident.