HSOrb: Testing Improvements to Avatar Script Time checking (13.037beta)

Requirements: PDS HomeSecurity Orb v13.037beta
IM psyke.phaeton if you wish to be a tester.

SUMMARY:

• Avatar Script Time Limits was added to v13.036 PDS HomeSecurity Orb, with 10.037beta I am trying to improve it.
• /8slt and /8slw without parameters prints the current settings. (new)
• /8slt and /8slw now have a fourth parameter called scripttimecount. This represents how many sequential scans the avatar’s script time can be over before action is taken. (new)
• Parameters left off the end will remain unchanged. (new)
• -1 is used to disable any parameter. (same)
• * is used to keep any parameter at the current setting. (new)
• /8stmon command will toggle on and off script time Whispers – 10m range (new)

UPDATE 2012-10-11 (13.037.1beta)

• Script Time was incorrectly ignored if neither Script Count or Script Memory was being used. (fixed)
• /8slt now has a 4th parameter which represents how many consecutive checks an avatar’s Script Time usage has to be over the Script Time Limit before they get Teleported Home.
  Command format: /8slt scriptmb scriptcount scripttime scripttimecount
  Ignoring scripttimecount causes it to default to 10 15 (changed to 15 in v13.037.6beta). When someone arrives it can take a minute or two for their Script Time to settle down.
• New command: The /8stmon command will toggle on and off Whispers (10m) from the Orb about avatars with script time above Warning or Teleport Limits as it processes them. You can use this information to fine tune your Script Time settings for your area.
• At this stage I recommend something like 500-1000 (µs) for scripttime and 10 15 for scripttimecount for /8slt.
  e.g. /8slt -1 -1 1000 15
• No equivalent work has yet been done on /8slw yet in this beta test.

UPDATE 2012-10-19 (13.037.6beta)

• /8slw (Script Limits Warning) equivalent of the above has been added. The default slw scripttimecount is 10.
• /8slt (Script Limits Teleport) scripttimecount default is now 15.
• The commands /8slw and /8slt without parameters now print the current parameters without changing them.
• Substituting any parameter with * will keep the original value. e.g. /8slt * * 1000 15
• When a parameter is missing or has * then the value is now left unchanged.

UPDATE: 2012-10-23 (13.038beta)

• /8stmon incorrectly whispered and tracked every visitor when either slt or slw was off. Fixed.
• When attacked due to avatar age too low the avatar gets his age and the age requirement in their notification message.
• AvLimits menu now shows “Ignore Time” rather than “-1µs” when Script Time checking is off.
• /8age command where duration was between 0.0 and 1.0 hours resulted in maximum duration rather than the expected fraction of an hour. Fixed.
• Clarified how Weapon/NotifyOp (3Weapon) and Scanner/VisitIM (81VisitorLog) send messages to the Operator.
  • NotifyOp enables/disables notices for:
    • Attacking unauthorised avatars
    • Attacking fake Operator Display Names when AvLimits/DispProt is on.
    • Attacking excessive script limits when /8slt is used.
    • Attacking when avatar age too low when /8age is used.
    • VisitIM enables/disables IMs for:
      • Avatar entering
      • Avatar leaving
      • Avatar Display Name similar to an Operator’s name warnings
      • An Operator uses the command: /8lb hours user.name
      • An Operator uses the command: /8tp user.name
      • Failed attacks

UPDATE 2012-10-26 (v13.038.9beta)

• Added “Warn” and “Attack” feedback whispers to /8stmon
• Stopped Warn pop-ups from being sent more than once for every scan that they are over the warn limit.
• New Settings Notecard entries: script_time_warn_maxcount and script_time_teleport_maxcount.
• Changed spare memory buffer from 10kb to 8kb to stop new code from reducing name storage.

HSOrb 13.036 Medium:Clearer Attack & Age msgs+profile links;Pop-ups when add/del names;Faster Update;Avatar Script Time checks #secondlife

SUMMARY:

• Experimental third parameter added to /8slw and /8slt for checking avatar script CPU time usage.* Click for more. (Initial testing shows that a newly arrived avatar can have a large spike in script time usage before it drops down. The Orb may need further refinement to ignore this initial spike. See v13.037+ above)
• Floating text display shows script memory/CPU time usage in µs (micro-seconds).*
• UpdateDisk must be within 10m of an Orb to update it (was 20m)
• Clearer messages about why someone was attacked.
• Add/Del’ing names causes a pop-up dialog reply because many people are now using Orbs from far distances due to one Orb covering a whole region.
• Notifications now include SL Time (SLT) and link to profile.
• Updates after this one will back up and restore names 7 times faster.
• Script memory check uses decimal point numbers.
• Log records attack reason also.
• A single attack notification sent now. Not two.
• Web page shows Script Limits, Teleport properly.
• Visible/Invisible fixes.

* A simulator under ideal circumstances produces 45 frames per second ≈ 22,222µs (micro-seconds) per frame. A portion of this 22,222µs is devoted to running scripts. An avatar who has a script time of 1000µs would be using 4.5% of the simulators processing time.

DETAILS:

PDS HomeSecurity Orb V13.036:

• Web page shows Script Limits, Teleport properly.
• Visible/Transparent minor bug fixes (/8visible)
  • Visibility of floating text and texture transparency will be preserved in the scripts memory for all updates following this one.
  • Turning off/on/updating the Orb obeys the Visibility state.
  • If your Orb has visible floating text and invisible prim try /8visible (or /8v) a couple of times to clear it.

PDS HomeSecurity Orb V13.035:

• Removed obsolete Twitter code from VLog.
• Fixed minor bug where Script memory checks were using integer rather than float. i.e. ignoring numbers after the decimal place.
• Improved AvLimits menu to show decimal memory usage.
• VisitorLog records attack reason along with attack type.
• VisitorLog no longer sends unneeded Attack messages to Operator when Scanner>VisitIM is on. (Weapon only should send messages to the Operator about a Target being attacked when Weapon>NotifyOp is set to IM or Menu.)
• Changed Script Limit, Warning pop-up to say “Preferred <” and Script Limit, Teleport to say “Limit”
• Script Limits checks avatar’s running script count now rather than total script count. i.e. Stopped/crashed scripts are ignored.
• /8slw and /8slt now accept a third parameter for scripttime in µs (micro-seconds) per sim frame.*
  The new format is: /8slw scriptmb [scriptcount] [scripttime]
• Floating text display has replaced avatar script count with avatar script time in µs (micro-seconds) per sim frame.*
• Added “script_time_warn” and “script_time_teleport” to Settings notecard. NOTE: these use decimal point seconds (not micro-seconds).

PDS HomeSecurity Orb V13.033 beta:

• Removed some debug code from Command Log script
• Changed UTC Time to SL Time for Weapon Attack messages (IM or Pop-up).
• Changed UTC Time to SL Time for Visitor Log IMs.
• Adding a name causes one notice not multiple notices. e.g. Adding an Operator causes a notice and also adds to Friends List, however only adding to Operator causes a message.
• Name backup and restoring, during updates, now 7 times faster. (yay!) This won’t show until the updates following this one.
  Unintended  consequences:
  • Settings notecard could take multiple comma delimited friend=, target=, operator= and network= values on the same line. e.g. “friend=psyke.phaeton,another.name“
  • /8add[f|g|o|n] commands could take comma delimited names. e.g. /8addo psyke.phaeton,another.name
  • Using comma delimited names is not recommended because sanity checking is not done. (For example; adding someone as an Operator/Friend/Guest will not remove them from Target List and vice versa, checking for duplicate names does not occur, etc.)
  • You cannot delete multiple names at the same time.
• Moved Friend/Guest backup to before Target backup so that should there be a memory shortage a Target is dropped rather than a Friend/Guest.
• Added “Full” message to pop-ups when adding names but memory is full.

PDS HomeSecurity Orb v13.031 beta:

• Over time the Orb’s tasks have moved on from the simple black-list/white-list. The Orb can also remove people because of display names, script usage or avatar age. However attack messages have remained unchanged and therefore unclear. I have changed the Notify Target and Notify Operator messages to clearly state what has occurred and why.
• Since 1 Orb now covers a whole region, shouting commands to add and remove names is more common. Since the Orb only llSay‘s back (20m range) Operators past 20m get no feedback. Now the Orb llSay‘s and sends a pop-up to the Operator. These new pop-ups only apply to adding and removing names/networking.
• Changed messages regarding Avatar Age to more obviously show: less than and equal to X days old avatars are removed.
• New command: hide “Operated by: Name” in Notify Target pop-ups: /8nthop on|off 
• Tidied up Weapon script to avoid duplicate messages.
• (Weapon) Notify Operator by pop-up now has a “Name (user.name)” and a link to target’s profile (shows in version 2+ based SL clients).

UpdateDisk:

• Time-out now 10mins because names can take longer than 5 mins now to backup or restore.
• Will now update the first Orb to reply to it and ignore any other subsequent Orbs in range. Previously a different Orb could steal the UpdateDisk focus from an Orb during the update. Oops!
• The Orb must be within 10m of the UpdateDisk (was 20m). Updated initial float text to reflect this.
• The UpdateDisk now shows in the floating text which Orb ID is being updated as well as the particle effects.

Thanks to teqi.falta for the reports, suggestions and testing.

Web:

• Changed WordPress “Documentation” link to point to V13 documentation.
• Added /8v short-cut to the /8visible entry in v13 documentation.

To Do:

• Update bulk packs at store and MarketPlace once it is clear this version is stable.
• Forum announcement.

HS Orb 13.021: Medium: More info in ListNear; allow Avatar Script Limits to do Memory Check when Count Check is off.

• ListNear menu now includes script details for detected avatars (same format as the Orbs floating text). [13.014beta]
• If Avatar Script Limits count checking was off then memory checks were ignored. Now either or both checks can be set and the Orb will check either or both. [13.014beta]
• Orb’s Owner never sees Avatar Script Warning/Teleport messages and never gets teleported home. [13.015beta]
• Avatar Script Warning/Teleport pop-up messages only show the problem(s) not all Avatar Script Limit values. [13.015beta]
• SETTINGS / AvLimits menu and Orb Chat corrected to show both Teleport and Warning values rather than just “Off” when Count was set to -1. [13.016beta]
• Script Warnings/Teleports are aborted if the detected avatar is on land owned by a different owner than the Orb’s land. [13.020beta]
• Avatars out of Up/Down range are competely ignored by the Orb. (Previously only Weapon ignored them, now Script checks ignore them too) [13.021]
• Thanks to Ami Thibedeau for the reports and testing.

Old Script Checking behaviour which is unchanged:

• Orb’s Friends do see Avatar Script Warning messages but never see Avatar Script Teleport messages and never get a teleport home.
• In NoAttack mode Avatar Script Teleport messages and teleporting home does not occur, Avatar Script Warnings do occur.
• Changes to Avatar Script Warning checks only apply to newly arriving visitors (not existing visitors).
• Changes to Avatar Script Teleport checks apply all visitors on the very next next scan.

Documentation:

• Corrected V13 Display documentation for ForeignLand Safe off. V13 uses “F”. (Was “FL” in v12 and less)

Other:

• 13.016beta “21Sensor” script lost Mono setting causing it to crash. Fixed in 13.017beta. Thanks Ami Thibedeau.
• Added llGetMemoryLimit() check to Mono scripts to check for Mono scripts with Mono accidentally disabled. [13.018beta]
• Caused changes of Range or Timer to send immediately to 21Sensor. [13.019beta]
• “ArmedRng” button moved to more prominent position and “ScanRange” to less prominent. [13.019beta]

Investigate:

• Web menus: LlSetContentType (ongoing)
• OBJECT_SCRIPT_TIME – Darian Llewellyn (v13.035)
• Change other land owner check to match the Orbs owner not the Orb’s land’s owner. Usually the same but technically more correct.
• Remove )0 from [1)0] float text since Orb no longer processes out of range avatars.
• Web “Script Limits TP: Off” needs updating to new format. (v13.036)

HSOrb 12.024: Bug Fix Medium: Wrong avatar born date collected

I tracked the problem with the Born Date of avatars.

I assumed SL did precedence a certain way and it turned out it was the opposite.

Press Updates on your main menu to get the fix.

Thanks to Nova Straaf and Uriel Aeon for reports.

HS Orb Bug: Incorrect avatar birthdates being recorded

I have multiple reports from one person (nova.straff) in one Region of avatar birth dates occasionally being reported by llRequestAgentData recorded as the current date rather than a real date from years ago. This can lead to people being booted out by the Orb if you use Age Limits when they should not be because SL is reporting oldbies as 1 days old.

One recent example has SL’s llRequestAgentData the Orb reporting “2011-05-11″ while my.secondlife.com reports “October 24, 2008″.

Region is being rebooted to see if this fixes it. If you have any similar problems please let me know.

UPDATE: JIRA raised. https://jira.secondlife.com/browse/SCR-75

UPDATE2: Uriel Aeon reports llRequestAgentData replies with Born: 2011-05-25 (4 days old) for someone born in 2010 (349 days old) plus other cases.

UPDATE3: Fixed in v12.024.

HSOrb 12.020: Bug: Sold with setting to remove people under 100 days old

I failed to clear a setting before selling the v12.020 Orb. I was testing the ‘ban by days old, for X hours’ feature and left it on when placing it in my vending machines.

To clear the problem type: /8age off

To Do Fix:

• Add /8age off to the /8reset command (v12.022)

Fixed now for both the shop and MarketPlace.

HSOrb 12.013: Guest Warning Message fix.

• Guest/Group warning message (/8gwmsg) was not preserved across updates. Resulting in the undefined Guest/Group warning message being set to ” ” (space) which would cause warning messages to guests to seem to be empty but still override the normal warning message (/8wmsg) text because it was not “” (null). Fixed.
• Guest/Group warning messages shown to non-guests/group members when Orb in Guests mode. Should only show guests warnings messages when in Friends mode and to guests/group members. Fixed.

Thanks to Janey Humphreys for reporting the above problem.

• UpdateDisk warns if it and Orb owners differ rather than trying and timing out.
• Updating ‘Update’ script causes channel numbers to be reloaded so Offline float text after an update does not display “Channel:0″

HSOrb 12.010: Display Name Protection fix

• A typo caused Display Name Protection (DispProt) to not detect complete operator names within non-operator Display Names.
• Added permanent land ban when DispProt is triggered.
• Removed Target List from comparing to Display Names. Caused more problems than it solved.

Thanks Janey Humphreys for the above.

• Settings notecard had inconsistent spelling for Display Name parameters. Changed fake_op_display_names_protection=0 to fake_op_displaynames_protection=0 however the old version will be detected by this update also.
• Fixed V12 Orb displays 0% while updating. This won’t be obvious until the update after this one.
• Rename older “HomeSecurity(TM) Orb” to “PDS HomeSecurity Orb”

HSOrb Update Servers deleted/replaced for PDS HS Orb v6 to v11

The new version 12 PDS HomeSecurity Orbs are unaffected by this.

Updates on versions 9-11 PDS HomeSecurity Orbs will time-out unless you copy and paste this command first while standing next to the Orb. You won’t see any reply from the Orb to the command.

/8server cedd82b1-e1ff-b45f-b35f-d232583c0fac

If you are inclined to /8reset your Orb from time to time then you can change your Settings notecard line to:

upgrade_server=cedd82b1-e1ff-b45f-b35f-d232583c0fac

If you wish to update PDS HomeSecurity Orbs older than version 9 you will need to trade it in for version 12 at a cost of 100L. IM Psyke Phaeton.

Explanation:

During some lag while deleting from inventory and having the server selected it suddenly was no more. The region is still very lagged and some scripts aren’t very responsive. Looks like the lag is caused by griefing.

Version 6 update server was deleted intentionally. Version 6 no longer supported.
Version 7-8 server UUID changed when I duplicated it to make the new version 9-12 server. So it has been deleted also. Version 7-8 no longer supported.
Version 9-11 will need you to enter the server command above before trying an update.

HS Orb 11.046: Medium Priority – Sleep malfunctions fixed

• Sleep had stopped detecting Operators. When I had changed to using capitals for Friends/Operators sleep was still looking for operators in lower case. Fixed. Thanks Lance Corrimal for the report.
• Whilst chasing that bug I noticed the Sleep setting was getting lost during updates. This status is now preserved however you will need to set sleep after this update one last time if you do not use the default value.

Future plans:

• Check RemoteDisplay shows Sleep. (fixed 11.047)
  
• Check Twitter code for unwanted tweets, like Operator coming and going.
• Consider Twitter option for disabling tweeting allowed visitors.