The Stepford Implant talks autonomously when, for example, dirty talk is enabled and you bump into someone, or are intimately close to someone. The text phrases it uses are now customizable using the auto-talk loader feature. The loader script work with implant versions 4.5+.
You have to acquire the Stepford API script. [Marketplace]
You have to acquire the auto-talk loader kit from Second Life Marketplace. The Stepford API is not included in this kit.
In the package you will find:
A script called stepford-autotalk-loader.lsl. The script uses the Stepford API to communicate with the implant.
An example notecard to create your text content.
The general format of the content notecard looks like this:
[context 1]
text line 1
text line 2
[context 2]
text line 1
text line 2
Each context refers to a feature of the implant. Every line under a context (ending with line feed) will be one of the random phrases the implant uses to auto-talk with that feature. Empty lines and lines starting with a #-character will be ignored.
Keep in mind that LSL script memory is very limited (64 kilobytes). When testing your content HUD, the implant will tell you its free memory after loading. Once you get under 10000 bytes, tread carefully.
Once you have completed your content notecard, create your loader HUD with these steps:
Create a basic box object on the ground. This step is necessary because the HUD must be created by you.
Make sure the box object's permissions for the next owner are no-modify, copy and no-transfer. The recommended dimensions (size) of the box are 0.1 meters in all directions (X, Y and Z).
Drop the Stepford API script into its contents. If the API tells you that it doesn't work when not attached, that's okay.
Creator's Edition only: Remove the transfer permission for the next owner from the script.
Drop the stepford-autotalk-loader.lsl script into the contents too. The box will now change its texture to a silver DVD.
Creator's Edition only: Remove the transfer permission for the next owner from the script.
Drop the notecard into the contents. The script will then determine the notecard's UUID and delete the notecard from the HUD inventory after that.
The HUD is now ready to be attached (preferably Center or Center 2). The loading starts when the attached HUD is being touched.
In order to protect your intellectual property, your notecard will not be stored in or distributed with the HUD. Furthermore, the UUID of the notecard will not be disclosed to the user.
Note that before distributing your content HUD you still need a one-time approval from Lava Babii (see API Disclaimer).