I tested this idea with a few people and they seem to like it.
I think it would be neat if we could submit CWs ourselves and later on 'transfer' them to another user. Say I draw a little cupcake wig and submit it, later on I could decide that I want to take care of the cupcake wig so I transfer it to her and she can slot the second batch.
This is just an example but tbh there are several occasions when this would be useful:
-Designs that are birthday gifts -Collabs between two artists -Joint releases -People going on hiatus who want their items distributed
Obviously people would do this at their own risk and original rules (number of batches, public/private etc) would have to be upheld. I don't think that would be too hard honestly since most of us can already tell you that X item released 3 years ago was a 3 batch public.
Where it's tricky imo is when it comes to recolors. I think it would be complicated to have recolors all over the place so maybe all of them would have to be transfered? I don't know honestly you guys are welcome to weigh in on this.
A fee could be charged when transferring a design as a deterrent to people abusing this and also as an added revenue to the site.
Do you guys think something like this could be useful?
- I think something like this could be extremely useful. Seeing as how I am dealing with a severe health issue and spend nearly half my day in a doctor's office, I don't have as much time to release things the way I used to. Tried to get my sister to do it but she's so half-ass about it, its annoying. If there was a way for this to be implemented, I'm down for it! :)
i would love for this to be a thing maybe when you submit you can have the option of designating one user in advance who you could transfer it to
Obviously people would do this at their own risk and original rules (number of batches, public/private etc) would have to be upheld. I don't think that would be too hard honestly since most of us can already tell you that X item released 3 years ago was a 3 batch public. ^ (sorry idk how to quote stuff aaaa)
while some of the older users of this site DO know about the cws released years ago, it might not be so easy if lets say a retiring/hiatus-ing user wanted to transfer ownership to a friend who newly joined.
is there any way that when cws are submitted that the system will notify you how many batches have been or are still able to be released? i haven't slotted a cw before so sorry if i come off as clueless.
Where it's tricky imo is when it comes to recolors. I think it would be complicated to have recolors all over the place so maybe all of them would have to be transfered? I don't know honestly you guys are welcome to weigh in on this. ^
i think this becomes a big problem for items with A LOT of recolours or if they come in a large set. it's easier to keep track of say 5-6 colours/set items, but when it goes into the 20s and more, this would be complicated.
the only thing i can think of is that the submission form (which would have one item/recolour) also have a kind of form at the bottom asking for all the recolours available, and they will have to be approved by staff so that people don't simply throw in all sorts of items.
but then this brings up the question of fee if necessary. do you get charged for every recolour/set item that changes ownership? :T
also your suggestion is a great one, but it does have drawbacks when it comes to sudden hiatuses or transferring ownership to newer people (ie people who joined subeta after the item was released). but that sounds a much easier first step than having an entire cw-transfer system, so there's that too! c:
but THANK YOU for bringing this up in the first place! c:

i was referring to newly submitted cws as i doubt this would get applied to cws already on site since it wasn't part of the form you agreed to when submitting xD the designated user would already be on site at the time of submission c:
IMO the problem is a lot of people submit an item as UL and then just release a limited number of batches, so there might be a lot of confusion about this. Like when people want to make something unlimited for 24 hours and then retire it completely. Tecnically they could still submit batches after that period but ii would be against the rules cause they said it would retire after 24 hours (am I making any sense,lol?) If the item get transferred it owuld be harder to kep track of how many batches were actually released, boards can be edited and some people might take advantage of the confusion. Maybe it would be better to limit this only to UL items?
oh yeah xD i forgot about that. but what about after they change the form and lets say you didnt give any names and released half, yet you suddenly have to take a hiatus and want someone to release the rest? idkidkdk ;A;
OHHHH i didnt realise that hehe. i didnt think about that tbh. i dont think its possible to limit it to UL items because as you said, no matter what the numbers written on the board are, the form itself mentions submitting it as unlimited and therrs no easy way for admins to check if they release more batches. but its too late for me to crack my brain for a solution OTL i shall think about it when i wake up (if i can even). thank you for bringing it up! ^0^

I think this just complicates further and just provokes more drama in the CW community which we definitely don't need more of n.n
While I understand where you are coming from, you want to share designs you submitted as groups, however it was released. But there are too many factors that just complicates this whole process way too much, which you already scratched upon like recolors. Also, how do profits get split? Does one person get it (the original releaser) or does the second person get their share too? What if there are more than one that contributed to the design? And what if one of those persons are on hiatus while the other is still releasing recolors they never discussed before or released more batches of an item. I don't want to be an UA that has to deal with that additional drama, they already have to deal with enough as the system currently is. & given that point, what happens if you are not friends with that person you entrusted your item to, but they are still in control of it? How do you determine who was the original creator, who has the right to release the CW? We've already seen too much drama created by only distributing one COPY of a private CW, let alone the right to release recolors and batches.
I think Subeta has more important issues to focus on, the system works fine as it is right now. I understand that others want to release things even when they were on hiatus, but if you don't have the time/ability to be online and participate with the site and the people, then I don't see a point to program a new feature like this, your files are still there when you return. The demand might not be anymore as the market changes, but that is always the risk we have as submitter.
All of those are already current concerns for group releases and we already deal with them fine (imo).
I think I'd assume people would act as grown ups where if you gave control of your CW to someone and you're not friends with them then I guess it's too bad for you? The current releaser holds control and it's there and they only have to abide by the original rules for batches and public/private.
If only.
This system would be interesting, but I think its pretty low on the list of things that need to be focused on. Recolors would definitely be a muddy issue, especially since right now we don't have a system marking x as a recolor of y. If this did become a feature, I'd like to see it where only CWs submitted to the site after release could be transferred, and I think a little checkbox marking any item as a recolor within the system would help solve the recolor issue.
It still becomes a problem with private, though. Even though they're not officially policed, what's to stop people from evading scamming rules by transferring the CW to another person and having them release more of the item to the public ("Well, X said that they were only releasing 1 copy to the public, but I never said that" or something like that)? This can extend to public CWs the same way, although I don't see it being as big of an issue with batch caps.
I have to agree with Who on there being too many complications for it to be feasible, even if it's cool in concept. Even if group releases are handled okay by groups now, when it's put into the system and people start using it within that system, there's a lot of problems that can arise that have to be handled by rules and UAs. There's too much for UAs to police.
I know I'm way behind on commenting on this, but I didn't want you guys to think I totally ignored it! This is an interesting idea -- but unfortunately at this time just doesn't seem feasible for numerous reasons. The main reason is we'd have to work out a lot of rules regarding previously-released items, under what conditions an item can be transferred, do ALL recolors have to be transferred as well, etc... A LOT of things. And that's not even getting into coding!
It's definitely an interesting thought however, something to ponder on. At the very least maybe some sort of system where you can basically GIFT ownership of a CW to someone when it's submitted? Not change later, but say, User A submits it for User B's birthday present and has rights go to them from the beginning? Something to think about!!
ooh, i like this idea! but if im not mistaken, most gifts tend to be a recolour of previous releases. since i know each recolour can be submitted individually (and thus gifted individually), it wouldnt be a problem coding-wise, but what is the general consensus on different people releasing recolours of the same item? has it been done before? if it has never been an issue, then im definitely down for this idea! c:

I do remember the case of the recolours. The original was released and drawn by , and while the recolours were submitted by the same person, the person who released them is a user who has long been frozen. There's definitely a precedent.
Some gifts being recolours of previous releases is new to me -- at least, the ones I've seen are new items altogether.
I do like Jessi's idea so far -- but it's probably something that has to be weighed very carefully before implementation.