Would slot price be feasible?

I know there's a 'default' slot price and that users can price their items at or above that when slotting/selling in cw shops (for 100% valid reasons). Knowing the original price would be helpful when buying/selling and it can be hard to find.

If it's not feasible though, no worries. xD

I think it would be feasible to display what category it was submitted under, which you could then use to calculate the minimum slot prices if you really need them.

I think knowing what category items are submitted under might help new submitters figure out what category some of the trickier items fall into rather than slot price.

I know some jewlery and accessories and even some clothes that are kinda on the edge of different categories I’ve submitted and had to go back to the FAQ and pretty much guess which was closest to what I was submitting.

It’s a wonderful FAQ guide but having that information available may help new submitters who really aren’t sure what category to use

I'm not subscribed to this thread. The ping went through for me. My former post here had ideas that were general and weren't addressed by anyone so there was nothing to add.

has shown us Wardrobe V4 and it doesn't have a CW that's done all of its batches excluder, which is the thing that I really want. This is not so much a big deal as it was when I originally posted: as long as the loooong original item load is only done once and stays that way. If he adds a "you can't touch this" excluder in, it doesn't matter if it's in the hover. If he doesn't, I want it in the hover.

This topic is about the item directory. If you have requests about the v4 wardrobe, you will have more success posting about it on Keith's topic where he will see it :)

Yes, I know that and was about to do that when you pinged me.. But that's the thing. Whether I want to have it in the hover (which is what you are doing now) is dependent on what he is planning to do. So what matters is if you know what he's planning to do.

How will items that have been submitted before the artist field was added be handled? Will we be able to specify the artist for our own releases?

This topic is also not about item hovers... I think there is a misunderstanding here lol. This topic is for a revamp of the Item Directory Building in Centropolis. In addition to a revamp of what it currently is, we are going to add a section just for information on CWs.

The artist would just be listed as blank for those items, since there won't be any data there. I will speak with the CW Admins about whether it's possible to allow people to fill this in retroactively, but I think that might be outside the scope of this revamp.

I did have a wording fail, didn't i?

I believe it's useful to me and to other users if in the Item Directory that it says whether the CWs item has finished its batches. (runs off to fix other post in Wardrobe V4 beta thread)

I'd love to see the Releaser, Batch Limit, Retired, and (if feasible) Recolors listed.

I think the Artist, while good info, is not exactly necessary (and if it's included - same with releaser - it should be tied to User ID please since folks love to change their UNs haha). It would be cool to have it, but if it's extra strain/data, it's less important since (theoretically) we can go to the releaser and ask who made it for them.

Recolors, if not realistic to list/link to, could just be a number count as well listed with it (like x recolors).

So...a thing that says if it's retired or not, along with how many batches were submitted? Like Bug mentions in the post you were pinged to? Like that?

would recolors be tied to the recolor function we have in submission where we have to assign them and such?

CWs that are not batched can be available or unavailable, as the CW creator wishes. Sometimes, this is true even if the CW is batched, the CW creator simply makes the ones in their shop unavailable to anyone.

Is this different from retired? I ask because I want to be able determine if I want to see a CW or not or whether I would like to ask Subetalodge to make a toggle or not. Difficult to acquire or impossible to acquire CWs (for any reason, and for any word descriptor) I do not want.

I see. Yup, that sounds like it would be useful. c:

How, exactly, would you like staff to keep an updated list on whether or not every single item is actively priced in a shop or is going to be rereleased at a later date or has some other special restriction on slotting?

That's the most absurd request. And I can guarantee we're not gonna do that at SL either.

Retired (all copies sold and/or manually selected to be retired by releaser) or Not Retired will give you the info on whether there are available unfilled/unsold copies on site.

Batch limit numbers will tell you how many copies are/were potentially available.

Releaser will tell you who you need to ask if there are unclaimed copies or if there are/were any restrictions on release. (And if you're polite, 99% of the time releasers are happy to let you know that info).

Staff doesn't have the time or ability to track down and update that information every second. It's not that hard to be even slightly proactive if you're the one who wants an item. Bug is making a database with some base information so everyone isn't stumbling around in the dark entirely - asking them to go hunt through every forum post and sMail and comment etc to find out release restrictions and plans for future potential releases is ridiculous and isn't gonna happen. Not from Subeta staff, not from SubetaLodge staff. If you want to talk to every releaser for every single item and then watch sales and keep updated numbers of available copies all day long, go ahead, but asking people to do that for you is ridiculous.

the site of Subeta has to be able to tell if something is password protected or not, otherwise the site wouldn't be able to enforce it. The site of Subeta has to be able to tell if there's an item in a shop, otherwise they wouldn't be able to sell the item to you on behalf of the CW creator.

Somewhere somehow, these fields must exist in a database.

Unless you are a coder or staff for Subeta, I don't think you know for sure how hard it would be to code. As for SubetaLodge, well I don't pay for it so I guess I am sad you are so adamant and don't insist. ? but it's still a great resource. If SL will not do anything like this ever under any circumstances, then it's even more useful to me to be able to filter it all out. There's a TON of CWs out there.

Right now, the ID and the W4 do take a long time to load, even with the improvements. I just messed with W4 to see the new contour in the new set and this made it load the whole honking thing all over again. So removing non=available non-retired CWs is non-trivial IMO.

Just because an item is locked doesn’t mean it’s private or unobtainable either... So your suggestion wouldn’t work completely anyway since many people only temporarily lock items until certain copies are picked up by people who slotted on them...

In order to do what you’re asking they’d have to change the database every time there’s a change in an items status whether it has a password or not. That just seems absurd.

If you don’t have the time or patience to ask the releaser if something it private because it’s locked that’s your choice but as staff does NOT recognize privates I can’t see them actually taking the time to figure out the status on all 30,000+ cws just so you can know what’s obtainable or not. That’s really not their job.

Releasers are in charge of their cws not staff so your best bet is to ask the releaser of the item you want

Password protected doesn't always mean private. Sometimes it means "letting the unfilled batch slotters get their copy."

In a shop doesn't mean priced. Shop search answers this for you - just like it does for site items. Asking every releaser to explain every single release nuance for every item upon approval so the table can be updated with not easily retrieved information is ridiculous. The other information Bug actually asked about? Easy to automatically run scripts to retrieve and have the data held. Subjective data can't be done like that.

This is an item database. Looking at the current one for site items doesn't show you if an item is available currently in a shop or not either.

You understand that SL is a labor of love right? That it runs at the cost of the site owner? That none of the staff is paid and everyone works other jobs? Our programmer had made some super useful information, but determining release information requires actually talking to every releaser about every release they've done. That goes for subeta aslo. You can't assume that just because something is in a shop unpriced that it will be priced later. Or that every locked item is private. You have to ask people all of the specifications to make the kind of list you're doing. Which you are welcome to do yourself. This isn't necessary information at all.

Also - you don't need to run the wardrobe with showing every single item ever made. Plenty of site items are not available and retired. Are you calling for all of them to be removed as well?

And lots of people actually do like to make HAs with those things.

Aaaand. As Bug pointed out to you repeatedly: this information has nothing to do with the W4. This is solely for an item database just like the main item database. That current database excludes CWs entirely. So Bug is making one for them. It has no bearing whatsoever on hover information or on what will or won't appear in W4. It's only an information repository.

Like, you've wilfully ignored the times Bug replied to you telling you that this has nothing whatsoever to do with where you want this information to appear (hovers and W4) and yet....you still don't seem to grasp that it's not going to inform either of those places.

Can there be a private notice either here or on the application.

As an artist I would love for items to have that information available for everyone (it would help us A LOT to be comissioned if people likes our style), and I would like to be able to ask to be credited on my items in case the releaser forgets to do it. I agree with that it should be tied to userID. <3 Thanks for the hard work.