AutoCouple

Script Name

+Deciduan_AutoCouple (includes "+" prefix to ease locating within objects with large inventory)

Current Version

v3914135, released 2014-03-18

Purpose

Allows a scripted bed or other poseball-managing object to automatically couple users' Deciduan HUDs depending on which pose they're in. Recall that coupling is the Deciduan HUD's means of determining whether insemination is possible.

The script is currently compatible with AVSitter2, SexGen, and jPose/MLPV2 (Multi-Love Pose, version 2) devices.

Setup

• 1. Place a copy of the script (-Deciduan_Autocouple) into the root prim of the bed, couch, bench, etc. that you want to enable autocoupling for.

  2. Place a new notecard named "-Deciduan_Pose_Config" in the root prim

Configuration

The configuration notecard has three directives. You may place comments in the notecard provided the first character of the line is a hash mark (#)

autocouple=0/1

Controls overall behavior of the rest of the configuration.

If autocouple=1, then a seated couple will autocouple whenever both are seated unless one of their poses is listed in the nocouple_anim list

If autocouple=0, then a seated couple will autocouple only when both of their poses are listed in the couple_anim list

couple_anim=anim,anim,...

When autocouple=1, if two participants are using animations in this list, they will be autocoupled. For example, if you have a 3-some pose, you would list only the poses involved in vaginal penetration here. This will prevent the "third party" from being coupled.

You may specify this directive more than once -- the additional animations will be added to the list.

Note that you must use spaces only as required to identify the pose names. Do not use a space after the comma, or it will be assumed that the next pose begins with a space.

nocouple_anim=anim,anim,...

This is the inverse of couple_anim. If a pose is listed here, it will be not be a candidate for autocoupling. This is handy in conjunction with autocouple=1, where most of the poses in the object are vaginal penetration, but a few are not. You need list only one of the male/female poses to effectively prevent autocoupling.

You may specify this directive more than once -- the additional animations will be added to the list.

Note that you must use spaces only as required to identify the pose names. Do not use a space after the comma, or it will be assumed that the next pose begins with a space.

Example Configuration

In this example, a bed contains a mix of poses for both two and three participants. Most are "cuddles," but two poses permit vaginal penetration, and are therefore appropriate for autocoupling. Specifically, a missionary position, and a 3-some position with two females and one male, where the male is penetrating one of the females from behind, and the females are kissing:

autocouple=0

couple_anim=m_missionary,f_missionary,m_3some,f_3some_middle

# A third pose, f_3some_kiss, is not included

Configuration Help

You can get a list of the poses in use by saying, in open chat: /57a

This will give you a list of poses that you can cut and paste into the configuration file (there's no extra spacing)

Notes

• • MLPV2 systems only report poses in use when someone is seated on the ball, and has granted animation privileges

  • If you reconfigure or reset the script while avatars are seated, they must stand and re-seat themselves before autocoupling will work properly again.