Hot on the heels of The Enforcer 1.0, I will soon be releasing Mesmerizer 1.5. This is only a minor version update, with the significant new features being the randoutfit, menu, menu2, maygroup and getgroup commands described earlier. In addition to these new features, the on-text event now sets a variable called text when it's invoked, and there are a couple of bugfixes to the RLV relay.
I hope that the Mesmerizer 1.5 release goes more smoothly than The Enforcer 1.0. For the latter release, I found two late-breaking bugs that I'd introduced in my performance enhancements, that meant I had to take down The Enforcer from MP and the vendors while I fixed them. The good news is that, in this week's rolling restarts, LL seems to have addressed the script performance issues that were introduced a few weeks ago, and which forced me to delay the 1.0 release of The Enforcer while I made compensating performance improvements. Now that raw script performance seems to be back to more-or-less how it was originally, with those performance enhancements The Enforcer simply flies - in fact it runs so fast that after the restart I had thought at first that it was completely broken, because contexts were completing and disappearing before I noticed them.
If you enable statistics on The Enforcer ("Stats On" in The Enforcer's menu), it will display and continuously update some information in hovertext above The Enforcer. The first line of this hovertext gives the name of The Enforcer, and you should probably change this from simply "The Enforcer" to something more specific. That will simplify things in the future if you ever find a reason to rez a second Enforcer (for example, to share traffic). The second line of the statistics display shows how many Hubs are being monitored, and how many users are currently logged in across all those Hubs. The third line shows the number of contexts and the number of namespaces being maintained.
I've discussed namespaces in previous posts. The statistics display shows the total number of namespaces (persistent plus transient). Contexts are the objects that The Enforcer uses to represent a notecard that's currently being executed. So when The Enforcer is idle, the number of contexts shown should be 0, and the number of namespaces shown should be just the persistent namespaces that have been created, although there is a small delay between a context terminating and the associated transient namespace being deleted.
I have posted a reference guide to programming The Enforcer in the stickies to the right. I intend to do something similar for the Mesmerizer, although because the Mesmerizer has a huge number of commands it will take a while to put them into a sensible structure for documentation. In the mean time, also in the stickies is the "Useful Blog Pages" link, which includes a live query that will return all the blog pages flagged as containing Mesmerizer command documentation.
Once Mesmerizer 1.5 is out, I expect the next version of the Mesmerizer to be mostly a performance update. I also plan to add at least the randoutfit and maygroup commands to the Owner HUD. And in the next release of The Enforcer, I intend to add a scheduler, so that you can cause scripts to run at specific times, rather than just in response to external events. Those are my current plans; in almost all previous releases, I've ended up inserting additional functionality as a result of continued use of the current versions of the CHAOS products, and in response to user requests. If you have an idea for a feature, please tell me about it in an IM in-world.
No comments:
Post a Comment