• 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.
MAINTENANCE ANNOUNCEMENT - JIRA will undergo maintenance starting 1:00am PDT through 3:00am on Saturday 2010.03.20. Please do not enter issues during this time as the system maybe restarted.
Issue Details (XML | Word | Printable)

Key: SVC-2575
Type: New Feature New Feature
Status: Closed Closed
Resolution: Won't Finish
Priority: Major Major
Assignee: Unassigned
Reporter: Cotytto Bonetto
Votes: 2
Watchers: 0
Operations

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

Add a Beacon for chatty objects

Created: 26/Jun/08 05:33 PM   Updated: 05/Sep/08 10:44 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Relates
 


 Description  « Hide
There is a major lack of tools for identifying and finding objects that send out chat messages. These are often used by griefers to flood the chat over large areas. When one of these is placed in a sandbox you often see even experienced players spending a lot of time hunting them down. Searching for the object by name is usually ineffective because the object changes names with each message.

A clean, simple solution would be to add a beacon for chatty objects. That would make it quick and simple to find and identify such objects to mute the owners, file abuse reports, or return the objects to the owner.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ezian Ecksol added a comment - 27/Jun/08 12:32 AM
Start in these cases a script that reports the name of the owner and the position of the chatty object(s), so one can mute the owner. Not really necessary to implement a beacon.

Cotytto Bonetto added a comment - 27/Jun/08 11:38 AM
Sorry, Ezian, but by that argument we should remove about half the user interface and replace it with various scripted objects.

It isn't just about "I muted it for me, problem solved." If that were the case we wouldn't need to find it. It is more important to report it so the abuse team can not only deal with this particular problem but also see patterns of behavior by particular individuals and take furher action if needed. This sometimes includes more than simply the owner of the object. It is sometimes helpful to see the creator as well. The best way to file such a report is to click on the actual object to automatically enter the data in the report.

One case I ran into on Sandbox Island just yesterday involved such a chatty object, buried in a huge pile of scripted objects. Even though I was the first to get the owner's name and exact location of the object, I never found it. It was impossible to get to through all the scripted junk. If I had had a beacon for chatty objects I would have found it in seconds.

Many of the users of sandboxes are new people who don't have access to advanced defense scripts. The more experienced users are using the workaround of rezzing big red arrows pointing to the object (once they find it) and giving the name of the person who needs to be muted. This is, at best, a really poor patch that simply illustrates that better tools are needed to deal with this. It seems to me the quickest and most effective would be a beacon.