Dz: Created page with " why is this considered a core feature? I can understand forcing attachments to NPC's in MY region because they cant do more than grief MY space, and asking permission to an N..."

2012-08-10T21:07:21Z

Created page with " why is this considered a core feature? I can understand forcing attachments to NPC's in MY region because they cant do more than grief MY space, and asking permission to an N..."

New page

why is this considered a core feature?

I can understand forcing attachments to NPC's in MY region because they cant do more than grief MY space, and asking permission to an NPC MIGHT be more difficult that this.

Unless that object is unscripted OR is removed when the avatar exits the region or disconnects,
this sounds like a heap of griefer trouble...

What happens when I visit a region where an object scans me, attach a malicious package to me, not inform me,
and then take advantage of the fact that attached objects don't require permissions to ...umm teleport me to a random region
and have the object spew 200,000 prims into someones else space??? Is MY fault I didnt check all of my attachments before and after i TP'd???

C'mon... more than 256 linked objects is "too dangerous" to allow us an INI file config to set our own limits... but this is OK??

Talk:OsForceAttachToOtherAvatarFromInventory - Revision history

Dz: Created page with " why is this considered a core feature? I can understand forcing attachments to NPC's in MY region because they cant do more than grief MY space, and asking permission to an N..."