So I learned something new today...

[Trykz]

if you don't want to break SexLab (and most anything else sex related), DO NOT add the *actortypecreature* keyword to your race mod! I spent 3 hours yesterday trying to figure out why my newest race wouldn't fire off SexLab animations. And now I know why LOL

 

Not expecting a fix within SexLab or anything, just wanted to give others a heads up, and warn anyone who may be working on creature interactions for future SexLab mods 

 

Trykz

[Ashal]

That reminds me; I keep forgetting to update SexLab to also check for dwemer keyword in addition to actortypecreature to fix mods trying to start sex with centurions. I should probably do that...

[Trykz]

Ashal, is there a list of keywords that SexLab checks for somewhere? Something I could use as a reference when building custom races? I try to test my mods with as much as feasibly possible, but sometimes it's easy to miss something you wouldn't expect to cause an issue. Thanks 

[Ashal]

Only keywords it will check is ActorTypeCreature and ActorTypeDwarven (as of 20 minutes ago.) It also checks for IsChild(), which is a function and not a keyword. If it passes any of those it rejects the actor as a candidate for sex.

[Trykz]

Thanks..... I'll keep a running list as SexLab evolves, so I know what not to use in the future. I imagine at some point the actortypecreature keyword check will be removed for bestiality mods built under SexLab? Or will the mod itself need to use some sort of override function? Just wanna stay on top of things as much as I can.

 

Thanks again