How to identify the opponent's archetype?

[yurifw]

I cloned the project and was messing around with it, trying to get familiar with the code. The reason I cloned it, is that I would like to try to implement a stat to show the winrate against each archetype the deck has fought.

In order to do this, I think the biggest challenge would be identifying the opponent's archetype. We have a small subset of the opponent's deck, how to get the archetype from this subset?

The first thing I need is an updated list of the archetypes in the meta. Do you know if any of the net decking sites such as Mobalytics or Decks of Runeterra have an API I could consume to get this data? If such an API doesn't exist, how viable is it to keep this data locally (and updated)?

I understand this is more of a discussion that I'm starting and perhaps this isn't the best place to do this, but I just couldn't think of anywhere better, if you want to move it or delete no problem

[sethjwilliamson]

I don't think it's really possible to accurately categorize opponent decks into archetypes without knowing their deck code.
With that said, there are ways of getting the opponent's deck code using the Match History API. I'll be working with that API in a few months but nothing is implemented at the moment.

As far as Mobalytics / Decks of Runeterra, I'm not aware of any APIs; I haven't really looked though.

[yurifw]

I think I'll work on something simpler and just try to implement a win rate by region instead, in the future we can use the Match History API to get the deck code to build upon it and implement win rate by archetype

[TheMusicMeister]

It seems like Mobalytics' system has the player identify the Regions and Champions in the enemy deck (which is open information visible in the client) and then compares those and the cards played so far in the game to suggest which potential popular deck the opponent could be using. Something similar could be implemented for LoRTracker if that's something people would be interested in using. It seems to be a fairly useful feature, at least for general prediction of what to expect.

I believe actually using an actual deck code from the opponent (guessed/predicted or not) would likely be close to if not actually infringing on ToS for 3rd party apps, so I would not recommend such a feature personally.

I'm branching the code right now, so when it's done and I get my devenv up and running I'll check out what it would take to implement some user-input-fueled predictions of deck archetypes.