Whooo! I had no idea that this was such a contentious issue. Boy, am I ever learning about SL fast! Having read the thread and Cubey's suggestion about extending the tools up to 768metres it means you're stuffed if you happened to be flying thru clear blue sky below someone's sky box. Maybe if it were possible to tint the sky in a restricted volume so you've at least got some time to turn before you hit it.
And on the ground I keep on walking into my neighbour's security system: those ugly red lines. But thanks to everyone for your replies. It's certainly opened my eyes to things I had no idea were happening in SL.
Welcome to the Second Life Forums Archive
These forums are CLOSED. Please visit the new forums HERE
BZZZZ-ZAP! Ouch!!! |
|
|
Alazarin Mondrian
Teh Trippy Hippie Dragon
Join date: 4 Apr 2005
Posts: 1,549
|
04-19-2005 07:50
|
|
Robin Peel
Registered User
Join date: 8 Feb 2005
Posts: 163
|
04-19-2005 09:48
Basically what we're looking at is a growing number of users who buy an ejection script, set it to the maximum, and have a good laugh at people who try to fly *past* their land. It's clearly against the rules to prevent someone from flying through open airspace hundreds of meters over the ground. I know people who have security on their land, they don't sit on the porch and watch people get bounced out and have a merry laugh about it. God that is a really pathetic thing to say! Most people buy them because of griefers that came on the land to do stupid stuff, that was their reason. Simply banning them from the land doesn't do nothing. They simply can't land. They don't like the red flags around their land because this looks bad. So the security script. If you give them warnings then they still can come on and annoy you until teleported or ejected. Myself, since this is property that is owned from the ground to the heavens, the owner has a right to make it private if they so desire, with a script or whatever. They after all are spending the money (Property Tax) to own land. |
|
Jillian Callahan
Rotary-winged Neko Girl
Join date: 24 Jun 2004
Posts: 3,766
|
04-19-2005 09:54
I know people who have security on their land, they don't sit on the porch and watch people get bounced out and have a merry laugh about it. God that is a really pathetic thing to say! Most people buy them because of griefers that came on the land to do stupid stuff, that was their reason. Simply banning them from the land doesn't do nothing. They simply can't land. They don't like the red flags around their land because this looks bad. So the security script. If you give them warnings then they still can come on and annoy you until teleported or ejected. Myself, since this is property that is owned from the ground to the heavens, the owner has a right to make it private if they so desire, with a script or whatever. They after all are spending the money (Property Tax) to own land. What is fundamentally wrong here is that everyone else is spending money for the opportunity to use the *grid*. You do not own the land to the heavens. According to the TOS, I have the right to pass. That is why there isn't enough Linden-protected land to get everywhere on the grid. Now, a PROPERLY USED AND CONFIGURED security script can BOTH blast greifers out of your hair AND let me pass over your land. If those using these scripts would bother to take the time to learn to use them properly, this thread would not even exist. No one would be worried about them. _____________________
|
|
Jeffrey Gomez
Cubed™
Join date: 11 Jun 2004
Posts: 3,522
|
04-19-2005 11:10
Added a simple solution to this problem in Feature Suggestions. Here's a photocopy of what I wrote there:
I've been working on an autopilot script on and off for the past couple of days. Works great. Since I can easily create an autopilot that'll navigate several sims with ease, why aren't we able to create ones that avoid abusive sensor bubbles for ban scripts? I propose the following two solutions to that problem: llSensorList(vector offset, float time, integer type) Lists the last fifteen sensor events at current position plus offset within a maximum 60-second time interval. Returns information as based on the following constants for "type." SENSOR_POSITION - sim-relative position of sensor object. SENSOR_ARC - scanning arc of this sensor. SENSOR_ROTATION - Rotation of sensor, to make the arc relevant. SENSOR_RADIUS - Scanning radius of the sensor. SENSOR_TIMER - Returns number of seconds since last event by this sensor. Multiple events are truncated. SENSOR_KEY - Returns key of object calling the sensor. SENSOR_SIM - Returns sim of sensor if able to detect cross-sim. SENSOR_TYPE - Returns constant scanned for: AGENT, ACTIVE, PASSIVE, SCRIPTED, or the combined bits thereof. As stated, multiple calls from the same object are truncated. Additionally, how about an event when an object is sensed? sensed(integer total_number) Thoughts? Is this abusable? I know if we had this sort of event, pathfinders and autopilot scripts could navigate around many of the encroaching "ban everything that moves" scripts on the grid. Furthermore, since much of this information is already kept at the sim level, additional sim load would likely be minimal. _____________________
---
|
|
Cocoanut Koala
Coco's Cottages
Join date: 7 Feb 2005
Posts: 7,903
|
04-19-2005 15:36
Right to passage is a fundamental thing, come to think of it. Seems to me this game has not handled that right at all well.
Imagine if you were driving to the grocery store irl, and you were using the streets given you to use (as we use the air here). But - unbeknownst to you - some guy with a privacy fetish (or, more likely, some guy on a power trip) just bought the house down the street, and as you pass it, you get bounced OUT of your car and clear out of the neighborhood. Maybe into the next town. Doesn't seem quite right. coco _____________________
|