:/ let us color the genes our dragons have plez.
i wondered why the heckle i couldn't find banescale accents that worked with porcupine, decided to make my own, and then when i opened the .psd to get started realized why.
then i read through the gaoler template release thread and there's just like 8 pages of people being disappointed. i am now one of them.
i have several ancient dragons with linebreaking tertiary genes and knowing, now, that i literally will not be able to make skins for them nor find or commission skins from others for them--despite the fact that they can't wear apparel--really harshes my mellow. (sidenote: i understand that i can make or buy skins/accents that work 'around' them but this just seems needlessly restrictive, especially in the case of my wintercoat gaoler, whose fluff i would have loved to slap a pattern on since i can't exactly dress him up)
a quick AH search or scroll through the forums will show that QA doesn't seem to mind accents that make dragons look like they have genes they do not. (Gembond, bee, glimmer, underbelly, etc. etc. etc.) so that's clearly not the reason--or if it is it feels very inconsistent to me. i understand for genes like spines & firefly we're expected to work around them, but they're small, unobtrusive genes and we can cover those dragons with clothes to customize them. ancients' genes literally affect sometimes almost 50% of the dragon and they can't be dressed.
what if i want my banescale girl to have gold-capped quills? if i can't breed her except with another bane, can't put apparel on her, and am willing to pay USD to acquire gems for a blueprint and put the work in to do up the skin i should be able to do that, no?
if there's concern about linebreaking in places like with spines then perhaps only accept it for ancient breeds? since skins are submitted by breed anyway and it will be easy to dismiss any that aren't. (oop, this goes outside the lines on a fae, sorry, nope! as is procedure currently.)
if the issue is 'accents that look like genes that aren't on the dragon,' it seems unfair to only start enforcing it now, 7 or so years down the line now that there are so many accents for non-ancient breeds that do just that on dragons that can also wear clothes and can interbreed. (i know that's a weird point to bring up but i dislike male banes and would have to have one in my lair if i want to breed one of my girls lol so it IS a downside to ancients for some people, however minor). some of this issue is also offset by the fact that the original lines and shading of the dragon need to stay visible, so you wouldn't be able to slap a gnarlhorn accent on a non-gnarlhorn gaoler without it looking ridiculous.
especially since UMAs are a feature people pay USD to use it just seems like we should be able to customize our dragons as much as possible to offset the fact that we can't individualize them with apparel.
idk. just my two cents as someone who has fallen back on creating UMAs time and again.
Edit to add:
if the issue really is 'genes the dragon doesn't have' then maybe put some kind of 'check' in place to keep it from going on a dragon that doesn't have that gene? you can't put a coatl F skin on, like, a tundra M, because there's a provision for that. perhaps a provision could be made that makes that tert a pre-req to apply the skin and just have an extra checkbox on the skin/accent submission form that a person has to click when they select the species.
Like so:
--
yessss!!! this is what i was trying to get at with my mockup. i don't think it would be super hard, either? just an extra couple lines in the coding and the number associated with the gene attached to the skin like that so that it checks for it the same way it does breed & sex.
like for a male banescale wraith-only accent (tert ID 48) it would require the breed value (18), the sex (0), and the tert ID (48) to apply the skin.
edited to clean up some goofy sentences
i wondered why the heckle i couldn't find banescale accents that worked with porcupine, decided to make my own, and then when i opened the .psd to get started realized why.
then i read through the gaoler template release thread and there's just like 8 pages of people being disappointed. i am now one of them.
i have several ancient dragons with linebreaking tertiary genes and knowing, now, that i literally will not be able to make skins for them nor find or commission skins from others for them--despite the fact that they can't wear apparel--really harshes my mellow. (sidenote: i understand that i can make or buy skins/accents that work 'around' them but this just seems needlessly restrictive, especially in the case of my wintercoat gaoler, whose fluff i would have loved to slap a pattern on since i can't exactly dress him up)
a quick AH search or scroll through the forums will show that QA doesn't seem to mind accents that make dragons look like they have genes they do not. (Gembond, bee, glimmer, underbelly, etc. etc. etc.) so that's clearly not the reason--or if it is it feels very inconsistent to me. i understand for genes like spines & firefly we're expected to work around them, but they're small, unobtrusive genes and we can cover those dragons with clothes to customize them. ancients' genes literally affect sometimes almost 50% of the dragon and they can't be dressed.
what if i want my banescale girl to have gold-capped quills? if i can't breed her except with another bane, can't put apparel on her, and am willing to pay USD to acquire gems for a blueprint and put the work in to do up the skin i should be able to do that, no?
if there's concern about linebreaking in places like with spines then perhaps only accept it for ancient breeds? since skins are submitted by breed anyway and it will be easy to dismiss any that aren't. (oop, this goes outside the lines on a fae, sorry, nope! as is procedure currently.)
if the issue is 'accents that look like genes that aren't on the dragon,' it seems unfair to only start enforcing it now, 7 or so years down the line now that there are so many accents for non-ancient breeds that do just that on dragons that can also wear clothes and can interbreed. (i know that's a weird point to bring up but i dislike male banes and would have to have one in my lair if i want to breed one of my girls lol so it IS a downside to ancients for some people, however minor). some of this issue is also offset by the fact that the original lines and shading of the dragon need to stay visible, so you wouldn't be able to slap a gnarlhorn accent on a non-gnarlhorn gaoler without it looking ridiculous.
especially since UMAs are a feature people pay USD to use it just seems like we should be able to customize our dragons as much as possible to offset the fact that we can't individualize them with apparel.
idk. just my two cents as someone who has fallen back on creating UMAs time and again.
Edit to add:
if the issue really is 'genes the dragon doesn't have' then maybe put some kind of 'check' in place to keep it from going on a dragon that doesn't have that gene? you can't put a coatl F skin on, like, a tundra M, because there's a provision for that. perhaps a provision could be made that makes that tert a pre-req to apply the skin and just have an extra checkbox on the skin/accent submission form that a person has to click when they select the species.
Like so:
--
cantrip wrote on 2020-01-06 22:58:35:
J///emadar wrote on 2020-01-06 22:39:24:
It would take a bit of coding, but if they truly wanted to, they could code simple checks so that a skin/accent can only be applied to a dragon with a particular tertiary (though this could also get confusing on the skin template, though it could just say it right out: This skin can only be worn by a 'Sex' 'Ancient Breed' with the 'Hugely LineBreaking Tert'.). That way you wouldn't have 'floating' pieces when people apply skins created using the line breaking tert templates to dragons not using those terts.
yessss!!! this is what i was trying to get at with my mockup. i don't think it would be super hard, either? just an extra couple lines in the coding and the number associated with the gene attached to the skin like that so that it checks for it the same way it does breed & sex.
like for a male banescale wraith-only accent (tert ID 48) it would require the breed value (18), the sex (0), and the tert ID (48) to apply the skin.
edited to clean up some goofy sentences