Add permissions to area search so we can find the problem
BrittanyCash1985 Resident
When we’re building in Second Life, it’s all too easy to accidentally apply a no-transfer, no-copy, or no-modify texture, script, or item without realizing it. We keep building, everything looks great, and then—right at the finish line—we discover the entire build is marked NO TRANSFER. Panic sets in.
Now we're stuck manually checking every single object and prim, trying to track down the one rogue item with restrictive permissions that’s ruining the entire product. It's frustrating, time-consuming, and completely avoidable if we had better tools.
Wouldn't it be amazing if Area Search or the Build Tools had the ability to:
Filter by permission status (e.g., show all "no transfer" items),
Narrow results by creator/owner name, and
Maybe even batch-apply permissions to our content before it's passed to the next owner?
I’ve just spent two hours tearing apart a house trying to find one hidden no-transfer texture. There's got to be a better way. This kind of functionality would save creators so much time and headache — please consider making it a reality. 🙏
Log In
Mari Moonbeam
If you are an active for sale builder , why not pre-sort your textures , scripts etc separating out the "no copy " "no mod" etc and box ,folder or dump them before you start a project? (I use Firestorm viewer)
Isabella Cinder
From what little I understand, all of these could be made client side, meaning these suggestions could become reality much faster in firestorm, catznip or any other third part viewer. This is not a sly on LL, their focus has to be much more on the server-side of things, while third parties have been carrying the client-side innovation since forever (RLV, native translator, embedded AO, spell-checker, "view in inventory", were all born on 3rd part, to name a few)
Rider Linden
You should be able to find the problem objects using a script. Use a sensor or some other way of getting nearby objects then use either llGetObjectPermMask (https://wiki.secondlife.com/wiki/LlGetObjectPermMask) with the MASK_COMBINED flag, or use llGetObjectDetails and request OBJECT_PERMS_COMBINED.
That should help you locate the problem object in your build.
AlettaMondragon Resident
Rider Linden Not everyone is a scripter, some people who are very advanced in making mesh models, textures or assembling objects, even vehicles, have zero scripting knowledge and skills. "You can use a script" is only an option for them if it is ready-made and only requires dragging it into the object's contents. So your suggestion doesn't work for many people.
Isobel DeSantis
And then there's the issue that even after you remove the no transfer item or texture, your build remains no transfer even though every single part of it is now full perm, and you can never sell it.
Logan Elf
Additionally it would be helpful if we could avoid the problem in the first place. Simply adding permission requirement checkboxes to the select texture dialog would go a long way to preventing this issue occurring.