Save BoM Tattoo/Layer Ordering as a reusable preset (similar to Shapes)
tracked
Bound Harmony
Hello Linden Lab Team,
I’d like to suggest an improvement that would provide a significant quality-of-life benefit for many users, especially those who frequently change outfits and use wardrobe tools.
Problem:
The ordering of BoM tattoos (and classic wearable layers in general) can be adjusted in the Appearance/Outfit window under Details (wrench/key icon).
However, the layer ordering is currently only saved within the specific outfit that was stored.
This means:
even if a user wears the exact same set of attachments and the same BoM tattoos, the ordering can still be wrong when the outfit is worn through external wardrobe tools (e.g. CTS Wardrobe or similar systems), or when parts are rebuilt from inventory.
As a result, users often have to manually fix tattoo ordering again and again.
Suggestion:
Please add a way to save BoM tattoo/layer ordering as a standalone preset, similar to how Shapes are saved as separate inventory items.
For example:
- A new inventory asset type such as “Layer Order Preset”
- This preset could then be included when saving an outfit, and also manually applied when needed
Benefits:
- Much faster outfit switching for users with complex BoM setups
- Less frustration and fewer manual corrections
- Better compatibility with wardrobe/dressing tools that many residents rely on
- Improves usability for roleplay, creators, and users with multiple style variations
This would make BoM-based styling more reliable and bring it closer to the workflow quality we already have with Shapes.
Thank you for considering the suggestion!
Photo Viewer
View photos in a modal
Log In
Spidey Linden
marked this post as
tracked
Issue tracked. We have no estimate when it may be implemented. Please see future updates here.
Beatrice Voxel
I use Whim's "Closet" feature and have to break tat layers up into categories so I have some control of the order in which they're applied. If something changes (like a linea negra or other pregnancy detail gets autoapplied during a pregnancy cycle) then i have to remove all of the layers that it shouldn't obscure, and re-apply them to get the order straight. So having some kind of pre-saved "stack" would be lovely, instead of applying single layers and then hoping things work, I could build layer stacks for various stages, and apply them /en entire/.
If these layer stacks end up being 'prebaked' together and applied as one layer, that would also help with a rather interesting issue - once you're past a certain number of tat layers, inventory stops reporting that a layer is applied (it doesn't turn bold in inventory, you cannot remove it either) until something else is removed and you're below the limit. Frustrating when you've a lot of small tat layers making up a whole.
Jennifer Boyle
Beatrice Voxel, prebaking multiple layers into one is an awesome idea.
Bound Harmony
Beatrice Voxel
Thanks, that’s actually a really good point - especially the “stack” concept and the issue where wearables stop showing as worn once you hit a certain amount of tattoo layers. I’ve seen that too and it’s incredibly frustrating.
My original idea is intentionally a bit simpler in scope:
the goal would be to let everyone save and re-apply the current BoM layer ordering state, similar to how Shape files only store body measurement values. A BoM layering preset would simply store the order/priority of the BoM stack as numerical layer positions.
A prebaked/merged “stack” layer could be a really smart additional feature depending on the implementation - especially if it reduces UI clutter and avoids the “invisible worn layers” problem at high layer counts.
But I’d personally see that as a separate feature request, because it’s a bigger change than just saving/restoring ordering. i Think this should be adressed as additional feature request too :)
Beatrice Voxel
Bound Harmony You're probably right about it being a new feature request. Here's why I think it goes with your "save the stack order" idea.
1) Saving the stack order still requires that the layers be stacked when you apply that preset. So there's still quite a bit of under the hood 'work' being done, and you've an extra 'item' in inventory to manage it.
2) Saving a prebaked stack does the same thing (preserve the stack order, give you an item to apply) but also eliminates the "bake everything in the stack" step, now your saved item is an actual item and not just a link to a group of items. Plus, it reduces applied item counts.
I think of it similarly to saving a group of attachments as an outfit, or linking the attachments into one attachment that can be worn. The former is more versatile, but the latter is more economical.
Bound Harmony
Beatrice Voxel
That makes sense, and I can definitely see the appeal of prebaked stacks as a “one item to wear” solution - especially for reducing worn layer count.
My only concern is that (at least for how I personally use BoM) it might shift the workload rather than remove it. For example, I often build looks from many small tattoo layers (makeup details, eyeliner, eyeshadow, lipgloss, freckles, beauty mark, wrinkles, etc.). If I want to change just one small part later, a prebaked stack would likely mean rebuilding/rebaking the whole stack again.
That’s why I’m mainly aiming for a simple “order preset” that stores only the layer priority/order (metadata), so I can freely add/remove single layers without needing to recreate anything - it would just restore the correct stacking order.
Also (please correct me if I’m wrong), a prebaked/merged stack would effectively create a new combined wearable. That raises questions about how permissions and transfer rights would be handled in a secure way, so it can’t be abused as a workaround for creator limitations.
Overall I agree both ideas could be valuable depending on the implementation. A “save/restore ordering” preset feels like a solid baseline QoL feature, and prebaked stacks could be a great optimization on top of that - as long as it’s implemented safely.
Beatrice Voxel
Bound Harmony So, with permissions, I think they would have to be, in all cases, no-xfer. Otherwise yeah, people could 'bake' a set of layers and give them away/sell them as if they were their own work. That's not good. So locking these to the avatar that created them would be the most sensible option.
You're right that a stack order list would be much easier to edit/adjust than a prebaked stack itself.
Maybe what's needed is both? One for ease of use, and then the other is a more permanent option once a design has been settled.
I'll have to submit the prebaked stack as a QoL improvement. Thanks for your input!
AlettaMondragon Resident
Beatrice Voxel As for the permissions, it could be done like when you apply a more restricted texture on an otherwise less restricted object, the object inheriting the stricter permissions as long as that texture is on it. So for the baked wearable, if it includes a layer from one no copy, no transfer item, and everything else was full perm, the new item would be no copy + no transfer too, but if you only use full perm items to create it, the new item can be full perm too.
Beatrice Voxel
AlettaMondragon Resident This is a sound way of looking at it, yes. Inherit the most restrictive permissions of any of the components.
(slightly grumpy mood, took the trouble of typing up the prebaked stacks proposal and the Canny AI bot said it was 'similar' to another proposed BOM layers thingy, more like yours, and closed it... nevermind the other one had less votes and no response from the Lindens. This is why I don't like AI making decisions, rather than just 'advising'.)
AlettaMondragon Resident
This is a great idea! Especially if you use modular outfits and don't like to save a whole set of the same layers, changing only a few BOM layers just makes a huge mess that you have to sort out manually. I assume with a "layer order preset" file this could be avoided too, simply adding the preset item to the "modular" outfits to set the correct order of layers.
I'm wondering if they can make this and if it can be reliable, but fingers crossed!
Dreamboy Diesel
This is very much needed!
Bound Harmony
omg what happened :D since yesterday 17 new upvotes. iam so glad that others got the same issue and see the need for it. Thank you all! :)
Katronia Carissa
This is so sorely needed.
Jennifer Boyle
Oh, yes, please! This would save me so much time. I wonder if it could be done by numbering the (58?) BOM layer slots and letting the user optionally specify which slot a particular layer should occupy. I only need this for tattoo layers. Clothing and underwear layers sort themselves well enough. I wear multiple tattoo layers for various skin effects, and they must be in a certain order to look right. After adding a new one, I often have to spend considerable time replacing links in my hundreds of outfits to get the layers in the right order.
Bound Harmony
Jennifer Boyle glad you like my idea. please dont forget to upvote to get priority :3