-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would card prediction be accepted? #263
Comments
This (or at least this direction) is something I would really like to add but honestly I'm not sure how accepted this would be by a lot of users. It does certainly tip the scales towards an "unfair advantage" quite a bit. Also I think just using sheer numbers and not taking deck types / meta (changes, existing less in lower ranks, ...) into account will not yield any good results (in the long run). |
Got this implemented Nextcardpredict #274 |
So this might be taking it a step too far and blizzard could end up at least taking a stance on this. |
Here's a text file with all the predictions. Judge for yourself. https://github.com/anonymous555/Hearthstone-Deck-Tracker/blob/nextcardpredict/allpredictions.txt |
I still think it's get a lot less useful after turn 1 without taking deck types / meta into account. And the problem is, if we get it to a point where it does that it get's too good. So far one of the main points when reasoning why this tool is "okay" is that you can theoretically do it all on paper. Combining this with deck prediction (based on popular deck lists) would be probably extremely cool, but for another project :(. |
Just curious if this would be accepted or rejected before working on it.
For all the games archived in xml, construct counts of the following
for each deck
{
for each turnnumber
{
for each enemy currentcard
cardcounts[enemyid][turnnumber][priorcard][currentcard] ++
}
}
Store this away as xml
As you play, at the beginning of a turn
Display the percentages and card names/graphics for the top n expected cards
cardcounts[enemyid][turnnumber][priorcard][predictedcard] / cardcounts[enemyid][turnnumber][priorcard].size
Or if you wanted even simpler, we could forget of the prior card, and just look at all cards typically played on a given turn.
The text was updated successfully, but these errors were encountered: