• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-1615
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: WarKirby Magojiro
Votes: 21
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

New Feature -> LSL -> llFreezeAgent

Created: 08/May/07 11:30 AM   Updated: 22/Jul/08 05:41 PM
Return to search
Component/s: Scripts
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates


 Description  « Hide
The tools provided for landowners are very useful. But we can't always be there to use them, so we write scripted devices to do things for us. But there are a few holes in LSL when it comes to land powers. One is Returning objects, which I alrady made a seperate issue for. This one, is about the Freeze function.

As the adminitrator of a privately owned, (but publicly acessible) sandbox, I deal with a lot of griefers, troublemakers, etc. Some are malicious bastards, but the majority are just confused newbies. Rather than instantly banning, I have a better approach. I freeze them to prevent farther trouble, and explain to them what they have done wrong, what rules they have broken, etc. This is quite often effective, and many have reformed and become good members of the community.

The problem, is that freeze has a 30 second limit, and no notification of when it expires. So I am forced to use cages to prevent people causing farther trouble. This is annoying, and makes me seem like a griefer. It is also escapeable simply by sitting on something, and does not provide the same restrictions as freezing, like preventing of chat, which stops them using many scripted weapons.

I am requesting a script function to freeze an avatar, so that I can use it to hold a target in place while I lecture them.

llFreezeAgent(key avatar, float time);

simply taking the key of the target, and the time in seconds to freeze them for.
This would be subject to the same rules as existing land functions, like eject, tp home and ban. IN that it would only work if the object is owned by the owner of the land it's on, or if the land is group owned, the object must be deeded to that group.

In addition, it would be VERY nice if the function could be used only the object's owner, pehaps if the script is in a worn attachment, regardless of what land you're on. The reason foir this, being that it could be used by roleplay combat systems for when characters "die", to prevent them from moving, speaking and interacting.

The only reason I can think of for this function not existing, is it's possiblity to be used for griefing,. But I counter this with the point that landowners can do whatever they want on their own land, and the target is always free to teleport somewhere else if they don't like it.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
WarKirby Magojiro added a comment - 08/May/07 11:32 AM
Quick edit for spelling mistake.

WarKirby Magojiro added a comment - 01/Jun/07 12:28 PM
Slight edit for clarity

Jag Nishi added a comment - 31/May/08 11:03 AM
I could see this being abused bigtime and I am sure there are reasons behind scripted bans and ejection only. For one, forced traffic could be done by freezing avatars on your land and so forth.

Felis Darwin added a comment - 22/Jul/08 05:41 PM
Jag, the proposed function wouldn't prevent residents from teleporting away, so there's no "forced traffic" to be had. There's an argument to be made that an unaware newbie might not understand what was going on, but so long as there was a giant big notification that popped up when they were frozen – particularly one that listed what they were prevented from doing and what they WEREN'T prevent from doing, e.g. teleporting – I think that'd sidestep the issue.

Anyway, I like this idea; it's a lot more elegant and effective than cages or similar security effects. There would of course need to be a way via script to unfreeze someone, e.g. issuing llFreezeAgent(key, 0.0).