So here is a list of the features that are new in 0.98l:
- The SD Entrancer plugin. This ships installed, but can be uninstalled if you don't need it and want to reduce your script count by 1.
- Stored scripts (both static and dynamic) to allow trances and command sequences to be replayed from the Mesmerizer's inventory or memory. This is like having a MesmerX built in to the Mesmerizer.
- Chaining. If you wear attachments (for example a collar or cuffs) that support the LockGuard chaining protocol, the Mesmerizer can now draw chains or ropes from them. Chains can be drawn between LockGuard attachments (to chain two cuffs together, for instance), from a LockGuard attachment to another object, or, in the form of a leash, from a LockGuard collar to a leash-holder or in-world object.
- Binds. These are rather like a combination of Modes with Chaining. They let the Mesmerizer tie the sub up using LockGuard chaining. As mentioned above, 0.98l ships with just a single bound pose - a hogtie - but I intend to add more before the final release.
- Rezzable objects. You can now put objects into the Mesmerizer's inventory, and have it rez them on demand. This is intended for things like cages, but the possibilities are pretty wide-open. There is a simple protocol between the Mesmerizer and the object that tells the object who caused it to be rezzed, and is extensible so that other commands could be send to the new object through the Mesmerizer. 0.98l ships with a single demonstration rezzable object, cleverly disguised as a plywood cube, which lets you see how to interpret the protocol; I intend to include at least one "useful" rezzable object in the final release version.
- The find command that searches #RLV for a folder whose name contains a sub-string now sets a variable called rlvpath with the result of the search. I got fed up with doing a find cuffs, and then having to copy and paste the returned folder-path into the follow-on wearoverall command. Now you can simply do:
wearoverall "$rlvpath"
- on-emote and on-chat events to allow the sub's speech and emotes to be grabbed. To avoid firing events unnecessarily, you have to turn on these events with hookchat yes or hookemotes yes (and with a parameter of no to turn them back off again). Both events are passed the text the sub said or emoted in the message variable.
- lmlist command to list the landmarks stored in the Mesmerizer's inventory.
- xcheck command to force a rescan for Xcite! genitals. If the sub adds their genitals at some time after wearing the Mesmerizer, it may take a few minutes for the Mesmerizer to notice by itself; this command nudges the Mesmerizer into checking right away.
- tptype command, which indicates whether the sub has granted TP permissions to the Mesmerizer, or is relying on the RLV teleport capability.
- textcolor command to set the color that subsequent text commands will use. It takes a single parameter which is either an SL color vector (e.g. "<1.0, 0.0, 0.0>" is a pure red color), or a named HTML 4.01 "web color", one of the following: white, silver, gray, black, red, maroon, yellow, olive, lime, green, aqua, teal, blue, navy, fuchsia, purple. Because I can never remember how to spell it, "fuschia" is accepted as a synonym for "fuchsia".
- A number of miscellaneous bugfixes
I will be writing follow-on posts with proper documentation for the new features and their associated commands. The help command describes them all now, but it is fairly terse, and intended more to remind you of what the command name is than to let you browse through all the commands.
I will be reaching out to existing purchasers to notify them of the new version, but if you want to get an update early, just send me (Nue Broome) an IM requesting one. If your Mesmerizer was bought for you as a gift, please include the name of the actual purchaser in your IM.
Now that the Mesmerizer update is out, I'll be hard at work to get the new Hubs out too. In many ways the new Hub functionality is the most exciting thing in this round of updates, as it enables Web Access, and also puts in place the groundwork for the Enforcer.
No comments:
Post a Comment