The LorDeckCodes library can be used to encode/decode Legends of Runeterra decks to/from simple strings. Below is an example code for a Ionia/Piltover & Zaun deck.

CEAAECABAQJRWHBIFU2DOOYIAEBAMCIMCINCILJZAICACBANE4VCYBABAILR2HRL

These strings can be used to share decks across Legends of Runeterra clients. Just remember: you can't netdeck skill.

Every Legends of Runeterra card has a corresponding card code. Card codes are seven character strings comprised of two characters for card set, two characters for faction identifier, and three characters for card number.

01DE123
│ │ └ card number - 123
│ └ faction - DE
└ set - 01

The deck code library accepts a Legends of Runeterra deck as a list of CardCodeAndCount objects. This is simply the code and an associated integer for the number of occurences of the card in the deck.

Decks are encoding via arranging VarInts into an array and then base 32 encoding into a string.

All encodings begin with 4 bits for format and 4 bits for version. Currently this is only 00010001.

The list of cards are then encoded according to the following scheme:

1. Cards are grouped together based on how many copies of the card are in the deck (e.g., cards with three copies are grouped together, cards with two copies are grouped together, and cards with a single copy are grouped together).
2. Within those groups, lists of cards are created which share the same set AND faction.
3. The set/faction lists are ordered by increasing length. The contents of the set/faction lists are ordered alphanumerically.
4. Variable length integer (varints) bytes for each ordered group of cards are written into the byte array according to the following convention:
   • [how many lists of set/faction combination have three copies of a card]
     • [how many cards within this set/faction combination follow]
     • [set]
     • [faction]
       • [card number]
       • [card number]
       • ...
     • [how many cards in this next set/faction combination follow]
     • [set]
     • [faction]
       • [card number]
       • [card number]
       • ...
   • [repeat for the groups of two copies of a card]
   • [repeat for the groups of a single copy of a card]
5. The resulting byte array is base32 encoded into a string.

Factions are mapped as follows:

Members of the community have graciously created implementations of this library in various languages. The following is intended to assist in choosing the implementation that works best for you. If you're a developer and would like to include your implementation in this list, please create a pull request and add a row to the README.

*Version refers to the MAX_KNOWN_VERSION supported by the implementation.

Apache 2 (see LICENSE for details)