It's been a while since my last post, but I haven't been idle. The Enforcer is very nearly ready for release - it has been running continuously now for several months, letting me know when my Hubs' addresses change, so I can maintain Web Access after a sim restart without having to log into SL to find the Hubs' new address. I've also used the bridging capability on a number of occasions. There are one or two more features I want to add, but I don't think I need to hold up the initial release for those.
I've been somewhat side-tracked with a major update to the CSD Stasis Tube. I'll go into the details of this in another post, but it's a significant improvement in functionality coupled with a huge cosmetic improvement. This should be released soon too, and will be available as a free upgrade to purchasers of the original tubes.
There is a Mesmerizer update in the works too. As mentioned earlier, this will have the new signal command, which allows a Mesmerizer trigger to generate an Enforcer event. It will also include a feature I've been intending to add for a while, but hadn't got around to until it was requested recently by a user. This allows Mesmerizer triggers to be defined by devices like the HoloTrainer and the Enforcer. You can do this today, but they will be added - so if you create a HoloTrainer trance that adds a trigger, and someone runs that trance more than once, they will end up with multiple instances of the trigger defined in their Mesmerizer. The new update of the Mesmerizer will allow for an alternative syntax for defining triggers that allows the trigger to be given a name, and adding a named trigger will replace any existing trigger with that same name. You will eventually also be able to delete named triggers by name and to name or rename existing triggers, although that capability may not make it into the next update.
No comments:
Post a Comment