File: D:/hMailServer/Data/showfile.com/admin/D9/{D9C8973A-1FE2-47D3-AB1C-0D83A395D219}.eml
From: <admin@showfile.com>
To: "'Jason Wong'" <jason@async.art>
References: <CANXxcc3fDavqcaX47LotkYRLV1JjFgHnWaAgSoAnR633do_nSA@mail.gmail.com> <003901d81106$45aaff60$d100fe20$@showfile.com> <CANXxcc190+9XaDM0BXdpv2Y0ZLR_jnpb_8RFk5oo0P3A6xhjbw@mail.gmail.com>
In-Reply-To: <CANXxcc190+9XaDM0BXdpv2Y0ZLR_jnpb_8RFk5oo0P3A6xhjbw@mail.gmail.com>
Subject: RE: Async Blueprints: Legendary Issues w/ Unperfect Actors by Enzo Roff
Date: Mon, 24 Jan 2022 17:57:18 -0000
Message-ID: <006601d8114b$d53613a0$7fa23ae0$@showfile.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0067_01D8114B.D539BD20"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDV68S/Lj4pG+PkW5kG6fBAus4iCwFCItMwAeEI6LMCkMUapA==
Content-Language: en-gb
X-OlkEid: 000000003E905BC03AE8234FA6F716356A1D0EE50700C3B68E10F77511CEB4CD00AA00BBB6E600000000000E0000071B2F9BB1DDB643A732EE9F1BEE430D000000006847000070D2CFC5863134448BEA89F294E0C15C
This is a multipart message in MIME format.
------=_NextPart_000_0067_01D8114B.D539BD20
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Hi Jason,
The only way that I can think of to make Legendaries would be to add a new
fifth element to them.
This feels like a flaw to this system, I’m really not convinced that
Legendaries are necessary, they seem to remove the egalitarian nature of the
work. Please convince me that I’m wrong!
Enzo
From: Jason Wong <jason@async.art>
Sent: 24 January 2022 17:44
To: admin@showfile.com
Subject: Re: Async Blueprints: Legendary Issues w/ Unperfect Actors by Enzo
Roff
Hi Enzo,
Elements from the Editions can be used for the Legendaries but Legendaries
should not be able to be assembled from the existing Types. It appears some
of your legendaries could potentially be assembled using assets from your
Editions. When this is the case, there is a small possibility of duplicate
pieces. One version from the Editions and the other being a Legendary. This
could become an issue in the secondary market so we wanted to flag it.
Legendaries are best being entirely different images in of themselves, we
also support mp4 for Legendaries as well.
Hope this clarifies.
On Mon, Jan 24, 2022 at 1:39 AM <admin@showfile.com
<mailto:admin@showfile.com> > wrote:
Hi Jason,
Thanks for finally getting back to me.
I’m not sure I understand, are you intending that the Legendary pieces don’t
contain any images from the main piece. If this is the case, I will need to
create 40 more elements to achieve 10 Legendary pieces, they will have
little or nothing to do with the concept of the full piece. My style of
figurative photo realism takes a very long time to produce and if I were to
create more images, I would rather incorporate them into the final random
selections.
Please let me know what you mean.
Enzo
From: Jason Wong <jason@async.art <mailto:jason@async.art> >
Sent: 23 January 2022 17:52
To: enzo@showfile.com <mailto:enzo@showfile.com>
Subject: Async Blueprints: Legendary Issues w/ Unperfect Actors by Enzo Roff
Hi Enzo,
It appears as though some of your Legendary pieces can be recreated in your
collection. Legendaries should be completely unique to avoid the situation
where there are duplicate editions with the same images but a different
rarity. Please resolve this before resubmitting. Your work has been returned
to Edit Mode.
Thanks! Let us know if you have any questions,
Jason
------=_NextPart_000_0067_01D8114B.D539BD20
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'word-wrap:break-word'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>Hi Jason,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p> </o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:EN-US'>The only =
way that I can think of to make Legendaries would be to add a new fifth =
element to them. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>This feels like a flaw to this =
system, I=E2=80=99m really not convinced that Legendaries are necessary, =
they seem to remove the egalitarian nature of the work. Please convince =
me that I=E2=80=99m wrong!<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p> </o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>Enzo<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:EN-US'> =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p> </o:p></span></p><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US>From:</span></b><span lang=3DEN-US> Jason Wong =
<jason@async.art> <br><b>Sent:</b> 24 January 2022 =
17:44<br><b>To:</b> admin@showfile.com<br><b>Subject:</b> Re: Async =
Blueprints: Legendary Issues w/ Unperfect Actors by Enzo =
Roff<o:p></o:p></span></p></div><p =
class=3DMsoNormal><o:p> </o:p></p><div><p class=3DMsoNormal>Hi =
Enzo,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p> </o:p></p></div><div><p =
class=3DMsoNormal>Elements from the Editions can be used for the =
Legendaries but Legendaries should not be able to be assembled from the =
existing Types. It appears some of your legendaries could potentially be =
assembled using assets from your Editions. When this is the case, there =
is a small possibility of duplicate pieces. One version from the =
Editions and the other being a Legendary. This could become an issue in =
the secondary market so we wanted to flag it. Legendaries are best being =
entirely different images in of themselves, we also support mp4 for =
Legendaries as well. <br><br>Hope this =
clarifies.<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p> </o:p></p><div><div><p class=3DMsoNormal>On =
Mon, Jan 24, 2022 at 1:39 AM <<a =
href=3D"mailto:admin@showfile.com">admin@showfile.com</a>> =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi =
Jason,<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks for =
finally getting back to me.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I=E2=80=99m =
not sure I understand, are you intending that the Legendary pieces =
don=E2=80=99t contain any images from the main piece. If this is the =
case, I will need to create 40 more elements to achieve 10 Legendary =
pieces, they will have little or nothing to do with the concept of the =
full piece. My style of figurative photo realism takes a very long time =
to produce and if I were to create more images, I would rather =
incorporate them into the final random selections.<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Please let =
me know what you mean.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Enzo<o:p></o=
:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-US>From:</span></b><span lang=3DEN-US> Jason Wong <<a =
href=3D"mailto:jason@async.art">jason@async.art</a>> <br><b>Sent:</b> =
23 January 2022 17:52<br><b>To:</b> <a href=3D"mailto:enzo@showfile.com" =
target=3D"_blank">enzo@showfile.com</a><br><b>Subject:</b> Async =
Blueprints: Legendary Issues w/ Unperfect Actors by Enzo =
Roff</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi =
Enzo,<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>It appears =
as though some of your Legendary pieces can be recreated in your =
collection. Legendaries should be completely unique to avoid the =
situation where there are duplicate editions with the same images but a =
different rarity. Please resolve this before resubmitting. Your work has =
been returned to Edit Mode.<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks! Let =
us know if you have any =
questions,<br><br>Jason<o:p></o:p></p></div></div></div></div></blockquot=
e></div></div></body></html>
------=_NextPart_000_0067_01D8114B.D539BD20--