You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am the author of yugioh-deck-tool, a web application that more or less mimics the deck builder of EDOPro.
I was wondering if there is some form of loose specification for Base64 Deck URIs EDOPro uses (The structure of ydke://foo!bar!fizz) so that myself and authors of different tools which currently consume .ydk files can make use of those URIs as well.
ydke structure is pretty simple, it consists if 3 base 64 strings identifying relatively deck, extra and side, separated by ! (as it's not part of the base64 alphabet, those base64 strings represent an array of ints consisting of the card codes, you can find a ts implementation of the parsing here
Just for the record, I don't have any issue with that code being used as a reference. 👍 The relevant bit is the ToPasscodes function, once you've extracted the three segments.
I am the author of yugioh-deck-tool, a web application that more or less mimics the deck builder of EDOPro.
I was wondering if there is some form of loose specification for Base64 Deck URIs EDOPro uses (The structure of
ydke://foo!bar!fizz
) so that myself and authors of different tools which currently consume.ydk
files can make use of those URIs as well.Only somewhat related, but I currently have a similar feature which however only targets encoding to individual URL query parameters (https://github.com/FelixRilling/yugioh-deck-tool/blob/development/packages/core/src/core/business/service/DeckUriEncodingService.ts).
The text was updated successfully, but these errors were encountered: