Creating a SIM wide security scan

I am trying to modify the usual security orb type script to manage a sim wide scan, either by using networking (chat/email) or alternative. I have a resident who has been terrorised by an av who has been stalking her for weeks now, and though we ban each new alt he brings to the sim, we simply cannot do so and successfully protect her as we always react to the problem after she has been hit yet again. Abuse reports have been filed, but I felt it my part to get a scripted protection in place that bans all new avs outright in her specific residential sim. Currently my problem is the 96m limitations of course, and I am wondering if there is an estate specific data set I can look at to use that allows me to scan for avs less than x days old and return them to home. Any ideas? I am a flunk with code and am more of a code user so my apologies for the basic explanation of the issue. I just feel strongly about this issue and think if I keep at it I should be able to turn out something that works. I would appreciate any advice.

/me is not sure she gets it.

How will a full-sim security system help if you don't know who to scan for? Why not restrict the sim to only certain avatars instead?

Hi Meade, sorry, I realize my post was not too clear here. We have tried blocking each new ALT he has created to track her down with (all born same day or no older than one week), and we have simply not the ability to keep doing that. With ALTs its impossible for me to find the original AV, though we hope that LL will soon be able to somehow find the culprit. My idea for the short term was simply to try and create a sim wide scan for new accounts, and banning them since the sim is residential, most residents older than 3 months, and all agree that we should try and do something to assist. My inexperience may be the main issue here. Blocking access for new accounts may be using a hammer for a fly, but I did not know any other method.

I understand now.

This might be tricky since things like llTeleportAgentHome and llEjectFromLand require that if the object is on group land, it must be deeded to that group. If this sim is split into a bunch of different parcels, each owned by a different group (or a bunch of groups), you're going to need to bunch of separate objects, just to punt the newbies..

Anyway, to answer your original question, llRegionSay is probably the best (meaning easiest and cheapest) way to do communications between objects spread out through a single sim.. (edit: er.. that doesn't really answer your original question, does it?)

edit edit: how about blocking people without payment on file, instead?

Thanks Meade, I'll change and apply. I agree that this remains a hammer and screwdriver approach to the problem - 8 parcels in private ownership on the sim does complicate matters. I will try it and see if it helps the problem. It really sucks for a resident to be so personally targeted, but is a whole new experience for me. Griefers I can handle, but this is nasty.

Oh.. If there's only 8 parcels in the sim, maybe having each one getting a security orb would be the easiest thing.

/me, somebody who really hates security orbs, can't believe she just recommended somebody stick 8 on a sim..

Personally, I too, find orbs and ban lines a bit distaste but, nevertheless, I recently accepted a commission to script a security orb that *may* help, or at least be adjusted to help.

Using llRequestAgentData it determines if the AV is 'No Payment Info on File'. If so, it issues a 30second warning before llTeleportAgentHome. It could quite easily be adjusted to also check the AV's 'Born Data'.

Assuming that a griefing alt usually has no payment info on file, and is less than a certain age you could use this criteria to issue a warning and, if the warning is ignored, teleport the AV home.

The product also has an 'Exceptions' list of AV's who do not need checking, regardless of their payment history.

The functions you will be interested in are:

http://wiki.secondlife.com/wiki/LlRequestAgentData
http://wiki.secondlife.com/wiki/LlTeleportAgentHome

as well as the usual sensor functionality

I think her best bet is moving into a private estate sim which is access restricted to group members only, and manual passes otherwise. Probably hard finding one, but other than that, I think the only real solution is LL finds a way to ban the idiot permanently.

/me misses paid accounts only. :-/

Why doesn't she get a security orb ?

Because the enforcement parts of them (teleporting people home, ejecting, banning) only works if you've deeded the orb to the group that owns the land. Each parcel on the sim would need to have its own orb.

That and sensors can only see things 96m away so, again, it means multiple orbs.

You can still restrict a sim, or a parcel to paid accounts only. Recently they removed the ability to *ban* paid accounts.

Yep.

I know we have talked about this before, Darien.

The 'No Payment Info on File' security orb only adds benefit (in its current form) if the vincity being monitored is higher than the area already covered by the 'Deny No Payment Info On File' checkbox on the 'Ban' tab of 'About Land'.

In the case of this commision, a private night club at 500m that had been subject to a number of homophobic griefing incidents. The rest of the sim is open to everyone.

This is certainly possible, and I believe there may be a few systems out there that already do it, but I'm not sure if they are commercial or what.

Is this a private estate? It sounds like it, since you say you have immediately banned each new avatar as you discovered it. If so, can you setup (or get setup) a more responsive estate management team? Can you allow access to the estate only to those who belong to a set of groups, and maybe give the locals the ability to add and remove people to one of the groups for visitors?

Been away on holiday a bit, so apologies for this late response. My personal thanks to everyone who made suggestions.

Meade, I am going to play around with sim wide comms as you suggested, with some general prims just so I can learn a bit more before incorporating it into the security portion of this project. Would lag not be caused by such a wide grid of communicating prims?

Debbie, the threads you indicated make for interesting reading for sure. Your suggestions are currently the most plausable to try here for the security parts of the project.

Darien, there are many avs who are in SL without premium accounts, so this region/estate option won't work for us. I am only looking to restrict new avs (1 week or younger) from one specific 8 parcel sim.

Hewee, yes it is one of two residential sims in my 4 sim group, and my problem is that though very responsive my team have not been able to keep up with the stalker's attempts to get to the avatar concerned. Added to this is that we only know a bad av once it does something to her, and then its ban ban ban again. Makes for a tough process to keep up long term.

Making the sim private is simply not an option for me, as it negatively impacts everyone else.
A security orb has already been active for some time on her land, but there are many ways to circumvent such security measures and still be harassing.
So age checking seems the better option in the end.

I am currently using the familiar 'av birthday' script I think I originally found in the wiki somewhere, as a basis for checking age and tp'ing home if less than 1 week old. Its still very basic as I just got back, and now I am going to adjust it to use Debbie's suggestions too, as they make much more sense for a workable model.
Once done I will post it here for help to see how best to extend it across all the parcels (other 7 parcel owners have no problem with helping her out).

O, and Hewee, if you have a commercial product like this done, I am all for buying one asap. This is already taking way too much of my time so my wallet will gladly assist me in shortening the process

Hi there. I make commercial products that can help you with this.

They are based on a simscanner that allows modules with a specific purpose to be aded. Once such module could be banning avatars under a certain age.


If there are multiple parcels, each parcels needs to have 1 prim placed on it to act as an intermediate to place the AV on the ban list there.

The problem intrigues me, and allthough this specific module doesnt exist yet, I'm willing to help you and develop it.

Mandy.

SIM wide? Wow, I'll take 4 thank you Seriously, Mandy, if you can help I would greatly appreciate it. I had not realized the time it takes to do this and try and manage four teams across four sims at the same time, plus all the activities going on. I want to try out my own script as it starts shaping, but due to the time it is taking and for this resident of mine's sake, a commercial product that quickly brings relief will be of great benefit right now. IM me in world with a NC of pricing and spec so I can drop you some dosh and we can do the deal

For my own attempt at this, what is the correct use of av banning within a script - 'teleport home' then ban, or just outright ban? I ask considering that this script is going to remove all avs younger than 1 week so I am thinking removing them to home first would be better then banning them first. I just hate having avs bouncing off the edges of my sims after a ban so it seems best to teleport them first. So how would this be stated within a script as I manage to do either the one or the other, but am battling doing both. I just dont have the experience with LSL yet.

Talarus, I was going to suggest that to her as a last resort, but wanted to go the scripting route first as she is such a doll and everyone at Bishara loves her to bits.

One last thing for the day - I had two coffees this morning, hence the many posts - Won't this type of age banning allow estate managers an additional tool to manage griefers? They always seem to me to be a day or so old normally, so pressing a button that teleports them home and then bans them makes a lot of sense. Those innocents (newbies especially) who go along with this wave banning can always contact the manager again and request to be un-banned. A dialog can always give extra options like the age screening plus a 'no payment on file' option. So more accurate screening can be done before pressing that big old button.

Just a thought.