Miscellaneous Updates

As mentioned in a previous post, I've been working on a bunch of enhancements to the Mesmerizer, which I hope to have completed soon after Thanksgiving, ready for a December release.  These include "bound poses", that will work with LockGuard-compatible collars and cuffs to draw chains where appropriate, for both binding and leashing, as well as scripts, which allow sequences of Mesmerizer commands to be stored either dynamically or in notecards and played back by a single command.

In addition, I've been working on some enhancements to the Communications Hub.  These include both minor usability features, like allowing the user registry to be stored in a notecard for safety, and significant new features, the most important of which is web access.    This allows the Hub's owner, as well as users they authorize, to connect to the Hub from the Internet via a web browser, and take part in Mesmerizer chat, or issue Mesmerizer commands to in-world users.  Like the communications mechanism itself, all processing is done in the Hubs, which means that there is no dependency on any external database or web service for any of the Mesmerizer features.  I was originally intending Web Access to be an add-on product, but I have now decided that it should be a standard Hub feature.  If you want it, all you have to do is turn it on in your Hub.

I also have a brand new CHAOS product under development, that I'm provisionally calling The Enforcer.  This is a monitoring device for one or more hubs, that will allow for the automatic playback of commands in response to Hub events, such as a user logging on, or moving to a different sim.  In effect it provides centralized event processing for multiple Mesmerizers.  You can use it for anything from displaying a message of the day (or image of the day) to your Mesmerizer users on login (or at random times), to centrally enforcing sim or other restrictions.  Another useful ability is that it can be set to send notification emails when a connected Hub changes its http address, which will happen whenever the Hub's sim is restarted.

Finally, I have been contemplating an "Owner's HUD", that would simplify the use of the Mesmerizer command interface.  There are two "levels of integration" at which such a HUD could be implemented.   The first would be simply as an alternative to issuing Mesmerizer commands directly, so that the HUD would mostly serve to avoid having to learn the different commands and their parameters.  Any communication back from the Mesmerizer would still come to the owner, rather than the HUD.  Allowing the HUD to receive and process responses would be the second level of integration, and would require enhancements to the communications protocol (and therefore both the Mesmerizer and the Hub).  I'm still weighing up the pros and cons of each approach, although it doesn't have to be an either-or decision - I could release an Owner's HUD that initially only transmits commands, and then add the communications enhancements to support a response channel in an update.

Mesmerizer Command Reference, Arousal

Arousal play is a staple of RL erotic hypnosis.  The Mesmerizer integrates with worn Xcite! genitals, allowing this type of play to be simulated in SL.  The Mesmerizer will automatically detect whether Xcite! genitals are worn, and whenever the genitals report a change in arousal level, will update the built-in variable arousal (which runs from 0 to 100) and trigger an on-arousal event.  If the genitals report an orgasm, the on-orgasm event will be triggered.

Here are the commands relating to setting arousal level:

Command	Params	Description
arouse	1	Add to the sub's arousal.  <p1> is the amount to add, capped at 10.   Use a negative number to decrease arousal.
arouseb	2	Add to the sub's arousal, bounded.  <p1> is the amount to add, capped at 10.   Use a negative number to decrease arousal.  <p2> is the maximum level the arouseb command can cause the arousal to rise to.
arousebt	3	Add to the sub's arousal, bounded, with text.  <p1> is the amount to add, capped at 10.   Use a negative number to decrease arousal.  <p2> is the maximum level the arouseb command can cause the arousal to rise to.  <p3> is a text string that the sub's genitals will emote.
arousebtk	4	Add to the sub's arousal, bounded, with text and kink.  <p1> is the amount to add, capped at 10.   Use a negative number to decrease arousal.  <p2> is the maximum level the arouseb command can cause the arousal to rise to.  <p3> is a text string that the sub's genitals will emote.  <p4> is the name of an Xcite! kink that the arousal will depend on.
cum	0	Make the sub orgasm
chaste	1	Prohibit/allow the sub to orgasm.  <p1> is "yes" to prohibit orgasm, "no" to allow it.  The cum command will work regardless of the state of chaste.
minarousal	1	Specifies a minimum arousal level.  The Mesmerizer will continuously add arousal when the level is below <p1>
maxarousal	1	Specifies a maximum arousal level.  The Mesmerizer will continuously subtract arousal when the level is above <p1>

Mesmerizer Command Reference, Teleport

The Mesmerizer supports teleporting of the sub, both by an explicit command, and by allowing auto-acceptance of TP requests.  The following commands relate to teleportation:

Command	Params	Description
tpto	1	Teleport the sub to a specified location.  <p1> is an SLurl or map reference.  For example tpto "Help Island Public (125, 124, 27)" or tpto "http://maps.secondlife.com/secondlife/Help%20Island%20Public/128/128/27"
autotp	0	Makes the sub auto-accept future teleport offers from the command issuer
noautotp	0	Removes the command issuer from the list of people whose teleport offers will automatically be accepted
autotp1	1	Makes the sub auto-accept future teleport offers from a specified avatar.  <p1> is the key of the avatar whose requests are to be auto-accepted.
noautotp1	1	Removes a specified avatar from the list of people whose teleport offers will automatically be accepted.  <p1> is the key of the avatar whose requests should no longer be auto-accepted.
listtp	0	Lists the keys of avatars from whom teleport offers will automatically be accepted.

Mesmerizer Command Reference, Roleplay Names

As discussed in the Overview Guide, the Mesmerizer can maintain a list of "roleplay names", any of which will match the pattern "$rpname" in a trigger-phrase.  So if the sub frequently role-plays as several different characters, you can add those character names to their Mesmerizer, and define triggers that use $rpname instead of their actual name, to allow those triggers to be directed to any of their characters.

This is also useful if you want to create triggers that can operate for either individual subs, or a group.  Assume you have a group of female subs Alice, Barbara and Christine, and you want to create a "go home" trigger for each of them that will teleport them back to your home.  The obvious way would be to give Alice a "go home alice" trigger, give Barbara a "go home barbara" trigger, and give Christine a "go home christine" trigger.  An improvement would be to use a "go home $rpname" trigger for each of them, and define Alice's role-play name to be "Alice", Barbara's to be "Barbara" and Christine's to be "Christine".  If in addition you give them each a role-play name of "girls", then you will be able to teleport them individually by name, or to say "go home, girls" to teleport them as a group.

Command	Params	Description
names	0	List the sub's roleplay names
addname	1	Add a name to the sub's roleplay names.  <p1> is a name, or a comma-separated list of names to be added
delname	1	Delete a name from the sub's roleplay names
setname	1	Set the sub;s roleplay name(s).  <p1> is a name, or a comma-separated list of names