Security Scripts Suck

Please do something about security scripts that immediatly return your vehicle to lost and found, and leave your avatar drifting throught the terrain, youre only recoruse it to log off. This happens at all altitudes, with no prior warning.

This was never so prevelent prior to the last update, so possibly something there in affected this.

For someone you enjoys building and using vehicles, this is a serious game play issue. Please address this.

Security scripts can't return objects, vehicles or otherwise - is the problem just autoreturn?

Sure after being dismounted by the security script. SL is wonderous in this and after they dismount you from your vehicile they are mad because you dont drop everthing to retrieve it.

There is someone out there who is writing security scripts who is a complete and utter loser.

OK, you have someone flying over your land. You don't want him there. What do you do?

1. Warn him to get off within 15 seconds, wait 15 seconds, then if he's still there unsit and eject him. In almost every instance, he will only have been over your land a couple of seconds anyway because he's flying a plane.

2. Unsit him, warn him to get off in 15 seconds, then in 15 seconds eject him without bothering to check if he's still in range. He'll probably need all 15 seconds to get back to his plane and pick it up, and he can't do it from outside the security zone because he'll be ejected anyway even if he'd obeyed the warning.

Option 1 is clearly better, since option 2 guarantees that people will spend *more* time messing around on your land than if you didn't have a security script at all.

On top if this, someone (for all I know, the same person) is selling security scripts that try and orbit people and telling the buyer that this is not against the TOS. He's also doing it using impact as well as push because I got thrown halfway across the sim by one of these when I was on my own land... which had third party push disabled... I couldn't have been on *his* land because he had access controls set up.

I think that it's getting to the point where we need some kind of approval process for security scripts. Not that running unapproved scripts should be illegal, but if you do it and someone complains you should be required to get approval. Either that, or Linden Labs needs to implement REAL security (for example, "parcel basements" or the "phantom zone" idea) and ban security scripts completely.

Griefers complain about any security system that bans them. Result : security systems of those places get suspended pending approval, and LL drowns in paperwork of maintaining an 'authorised' list of security systems.



Yeah, same old debate. I'd go for what I *think* you call 'phantom zone'... it'd render security scripts useless by comparison and thus their usage would naturally stop without needing to ban them.

Security scripts can now use the ban-line system to remove people more dependably if eject isn't enough. Rather than using dumb pushes, but yes, they need sensible messages and timing.

Mine runs every 30 seconds and warns first, telling people on the allowed list for the script, and are currently in the house, that someone new has arrived or is floating around outside within earshot. Allowed users can then kick offending users, or the script will automatically kick after two warnings (ie one and a half minutes) if there is no-one home to decide.

I didn't say that you'd be suspended pending approval, that's your inference. You're assuming the worst possible design here (one where unverified claims are sufficient for LL to take action, and LL doesn't give makers of scripts time to get approval before implementing it, and so on...) which is a great debating tactic but it's not actually very useful in getting people to agree.

I mean, the current situation is so bad that just getting LL to enforce the TOS when people use push or impact weapons would be a huge improvement. I had someone walking around on my land shooting people and physical objects. I asked them to stop, and then when they were rude I banned and ejected them. that, by the way, is only the second time I've used "ban" in the 8 months I've owned land. They hit me with some kind of impact weapon that knocked me off my land then pushed me two sims away.

I had perfect information for an abuse report. Open and close case. Logs, the whole thing. Never showed up on the police blotter.

They say push scripts are against the TOS for security. Has that ever been enforced? If they're not enforcing direct abuse by random wandering users (abuse, by the by, that no security script could possibly defend against) I can't imagine they're doing anything against paying landowners. At any rate, people using push scripts for security don't seem to either care about it and don't seem to be stopped.

So right now the situation is so bad for fliers, and security scripts are so ineffective against real abusers, that there's no end of options between your "worst case" scenario and where we are now.

With the ability to look across the sim, there really is no point from keeping them from hovering over your land.

The security system I use only scans inside of the building and then tp's home and bans anyone that owns a moving scritped object that is inside of the building.

It's a pain having to deal with the false triggers from pets, moving particle emitters and other stuff that some people bring into the place, but it does reduce the shootings.

Why be anal about someone hovering around when they could be anywhere on the grid when they launch a scritped atack to return your building. *sorry, I won't talk about exploits on the forum*

Every time the topic of security scripts come up, the conversation seems to go around in the same circle. Its important to make the distinction between whitelist and blacklist security systems when discussing their use.

Whitelist systems ban *everyone*, and only allow certain people. Typically used for privacy. Whitelist systems must give a warning to be TOS compliant.

Blacklist systems ban *certain people*, and allow everyone else. Typically used for griefer control. Blacklist systems do not require a warning to be TOS compliant.

It is Whitelist systems that are the major irritant to travellers, and agreed that if you're going to employ one, you must give a warning first.

And there's some really awful whitelist scripts out there.

That don't give a warning, and trash planes.

And abuse reports about them lead to Linden responses that "this has been resolved".

With the script left in place.

So either they don't need a warning to be TOS compliant, or breaking the TOS doesn't mean anything when it comes to security scripts.