Thanks guys
And what discord? Id love to read up on the data ^.^
Thanks guys
And what discord? Id love to read up on the data ^.^
Does anyone else think that notation looks cumbersome? Maybe something like C+U+U+Sy / C+U+U+Sy+ would be a viable way to indicate the upgraded parts, with the + after each one with the extra modified stats. (e.g original Syldra would be Sy and modified Syldra would be Sy+)
Last edited by Niwashi; 08-28-2019 at 03:59 AM.
This is actually the exact thing we were debating and considering in said Submersible Discord. I think the consensus is to use the + annotation to confer when a part is modified. A fully modified CUUSy would be C+U+U+Y+.Does anyone else think that notation looks cumbersome? Maybe something like C+U+U+Sy / C+U+U+Sy+ would be a viable way to indicate the upgraded parts, with the + after each one with the extra modified stats. (e.g original Syldra would be Sy and modified Syldra would be Sy+)
Also yes, we're still debating between Sy and Y. I'll probably end up converting to Y as well.
In the context of the given content(in ENG at least) I'd say its clear, obvious and as simple as possible whilst still conveying the relevant information.
Nothing wrong with chatting in code in discord, if that floats your boat, but given that the number of people using said discord represent a tiny fraction of the playerbase, and probably an even smaller fraction of the views on this thread I think I'm on pretty solid ground as far as accessbility goes.
A fix, north isle of zozonan unlocks sea of ash 1 and 2, not southern charnel trench (which is covered in the next one)
My vote is for ascii 253Does anyone else think that notation looks cumbersome? Maybe something like C+U+U+Sy / C+U+U+Sy+ would be a viable way to indicate the upgraded parts, with the + after each one with the extra modified stats. (e.g original Syldra would be Sy and modified Syldra would be Sy+)
C²U²Sy²C²
Clear enough to read, but harder to type (especially on a phone)
Besides the spreadsheet issue (which is already enough of a problem), it can also be a bit harder to see the difference.
Succinct, clear, and easy to type. I like that one.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.