Adding a mesh body filter for apparel
tracked
nathkyo Resident
Giving mesh body creators the ability to add their body to the filter for clothing and apparel. Shopping for clothing can be somewhat hard now with the numerous amount of mesh bodies that have been added over the years. giving creators the ability to add their body as a subtype that can be easily added to a filter for the products would be a great way to make shopping on second life easier. Khara ,Legacy ,Maitreya ,Reborn And many more that have different shapes and different fittings Making it sometimes difficult to find clothing that will fit your particular body. this also can be done for heads and other and accessories making it a lot easier for creating avatars as Second Life has changed in the years since the marketplace was first created.
Log In
Spidey Linden
tracked
Issue tracked. We have no estimate when it may be implemented. Please see future updates here.
nathkyo Resident
An idea for it would be to put a special field in the upload where you could add the mesh body type for other stores or newer bodies. This would actually be perfect, because you could have the system set up after a certain number of submissions from different stores. It would add it as a subcategory. Which wouldn't be showing favoritism? As this all would be done automated
Rockridge Constantine
The list of mesh bodies, especially for female avatars, seems to be constantly growing and/or changing. I would anticipate that the sub category would do the same. How do you build that list without showing favor or endorsement of one body over another? User tip: Just add the name of the body as a keyword when you search for a particular clothing item. Creators already put the body types in their product descriptions which helps in searching.
KyliaDaden Resident
Rockridge Constantine Can be made into a comma-separated field with auto-completion offer. Just like how many sites with custom tagging implements it.
So, say you type in "mait" then the pop up will offer autocomplete of "maitreya lara classic", "maitreya laraX", "maitreya laraX petit". If any of the autocomplete offering is selected, then the name is "locked in" and turns into an uneditable tag (with an X to delete). But don't stop people from typing in a different name (for instance, just in case there's a new body that hasn't been added into the autocomplete yet).
Rockridge Constantine
KyliaDaden Resident i am aware of all of these search techniques. But i really don't think we need to have specific search filter or toggle for specific bodies.
Soxy Whisper
KyliaDaden Resident has just highlighted a problem. There is no Maitreya "Classic" There are the two latest bodies. Maitreya Lara 5.3 and Lara X. Names like "Old Lara", "Maitreya", "Lara", and "Lara Classic" don't exist and worse, are confusing. Today, we might assume "Old Lara" or "Lara Classic" refers to Lara 5.3, but what happens when Maitreya comes out with a new body after Lara X? Then what does "Old Lara" or "Lara Classic" refer to?
I agree wholeheartedly that this classification system would be great not only for bodies, but also for heads and any other products that have dependencies, but for it to work, the creators who make the products you want in the drop downs would need to approve the names AND you have to get clothing creators to use them.
Gwyneth Llewelyn
KyliaDaden Resident not to forget how creators are absolutely inconsistent in how they label the body names. These are actually brands and should be respected as such, but content creators have to take into account their own users and their audience and the way they like to set up things — usually knowing that
their
customers expect
things to be named in a certain way.This leads to creators labeling the Maitreya Lara as "maytreia" — because at some point in the past it was misspelled, and now, to make it consistent, they keep the name badly spelt forever. So searching for "mait" will get zero results.
Then you have those who name the Maitreya LaraX as "MaitreyaX". Why? Because originally there was just
one
body type from Maitreya, namely, Lara; the brand Maitreya
, however, was well-known way before they launched their first body. So creators prefer to call the body type "Maitreya" because, well, their older customers (possibly also the most faithful ones!) expect
the body type to be called, well, "the body type that Maitreya does".But "MaitreyaX" is
not
a brand name.Others prefer abbreviations, and here the levels of creativity are simply extraordinary. Take an example from a creator used to sell their clothes for Legacy, Belleza, and Waifu (a stupid selection, but that's irrelevant). Their respective clothes will just have
[L]
, [B]
, and [W]
after the name. Easy and clear — no problems there.Then, say, you have a Perky variation for Belleza (I'm inventing things), and they decide to tweak their mesh a bit. Hm. How to name it now? Why,
[P]
, of course, because that's the only one that starts with P. So far, so good.But then Waifu introduces the Waifu Petite, and it's worth supporting. So, now, this system of one letter won't work any more. How should this be called? Well, let's bump Belleza and Waifu to two-letter acronyms: "BP" is Belleza Perky, "WP" is Waifu Petite, and
L
, B
and F
remain as the original
version.And finally, they decide they cannot ignore the Maitreya Lara body type any longer. So, well, this one can't be
[L]
since that one is already taken for Legacy; therefore, let's call it [ML]
. Makes sense, right? Still just two letters to figure out.Gwyneth Llewelyn
Then silly Maitreya comes out with their Lara Petite offering. Hrrmpf. That means calling this new type
[MP]
... no, wait. Shouldn't it be [LP]
for L
ara P
etite? No, let's stick with [MP]
for now, since that seems more logical.Alas. Now LaraX comes along. What now?
[ML]
is already taken. [MX]
? Well, let's go with that one. Or maybe [LX]
, since, technically speaking, Maitreya is the brand
, LaraX is the product nam. But then this can be confused with the Legacy X — which the creator might not support yet... but might in the future! So, let's bump Legacy to [LG]
, and if Legacy X comes along, it will become [LX]
, while Maitreya Lara remains [ML]
and LaraX becomes [MX]
. There you go! Now all are unique, two
-letter acronyms. Easy!Uh-oh. What are those guys releasing next?
- Waifu now has the Waifu Perky and Waifu Curvy, on top of the existing "standard" Waifu and Waifu Petite. Now is [WP]Waifu Petite... or Waifu Perky?
- And, of course, Belleza now also releases Belleza Petite. So, [BP]can mean either of them. That can't be!
- Worse: Legacy introduces the Legacy Giga, for giant avatars, and the Legacy Mini X, their own extended version of the Legacy X, but in petite size. Grr. So, standard Legacy remains [LG], ok, but what about the other two? LG cannot be used for Legacy Giga; and[LM]for Legacy Mini X? That's confusing, since people may mix it up with Maitreya Lara, the reverse acronym. Argh. And[LX]is taken, so, maybe,[LP], where P stands for Petite, even though the product name doesn't have "petite" in it, but itisa petite variant, so... wait, how was the Lara Petite named again?... ah, we stuck to[MP]for that one, so we're good.
- And finally... Maitreya introduces the LaraX Petite, Legacy has now added the GigaX to their offerings, and Waifu is mergingtheir Curvy & Perky offerings, by popular demand, into asinglenew body which also has a new HUD, allowing combining those two body types together... and the new name? Why, WaifuX, of course!
At the end of the day... that creator has no choice but to include a notecard with all the corresponding acronyms.
Then you buy an outfit from the shop next to them in the same region. And, surprise, surprise — although the two collaborate often togethtog together,
they use different abbreviations
! Gahhhhh!!...Gwyneth Llewelyn
Note:
Most of the name above are invented, of course, but the pain is
real. I wish to search for those outfits that work for the Maitreya LaraX. How
should I do a search to get them all
?... well, of course, the answer is, "you can't", unless I rename them, one by one, something which may not
work for scripted, non-mod items. Sigh...I've upvoted this feature request. Somehow, things
should
be easier.