The deck had no duplicates (neither own or generated or the opponent’s), and it didn’t do the card’s effect (it didn’t glow either in-game).
Replay(remove/replace “DOT”): replays.firestoneapp [DOT] com/?reviewId=40ad678c-6205-48de-9387-34adfeb546b6&turn=0&action=0
[ PS this was later exposed to be either a Firestone bug or a logging bug at the most ]
How are you so sure that your deck had no remaining duplicates ? The replay doesn’t show what were your 4 last cards in deck, and you were running duplicates throughout the game.
I use firestone: it has live tracking and the deck had no duplicates.
The Devs record all games and can see the full data at a timestamp anyway so it’s not critical to have all data in a bug report other than the exact account and date/time.
PS I suspect it bugs because the card is pulled by a Paladin from another class and it probably has a hard coded “require Class” unlike other cards from The Countess.
PPS Or it bugged if it’s part of the copying-of-cards[“that didn’t start in your hands”] another card did earlier.
Ok but that is not in the replay so it’snot really helpful
I’ve heard the exact opposite of that everytime on this forum.
People guess and they guess nonsense. The Devs record all games and they announce it every time there is a balance patch: “we looked at the data of games and…”.
PS they also openly announce that they record [other games like] World of Wacraft’s activity (that goes back for a long time before it’s deleted (if it’s ever deleted)).
Collecting aggregate stats is a far cry from “recording games”.
Then show us your decklist, and show us what Firestone displayed as the last four cards.
Clearly that deck is not made for a no-duplicate trigger , and there are key card missing like
that are usually played with Countless limitations.
Trust me they definitely record all games, because they can, and because it’s very cheap at data storage.
PS @Cece The report has nothing to do with deck optimization[it was a fun deck for the lols]. By the way The Garden’s Grace is deleted/dusted because it’s rotated out and it was refunded at full price/dust[it was nerfed recently].
PPS no-duplicate cards work on initially-duplicate decks after you draw all duplicates
Um, ok sure.
No dev has ever posted here to confirm or deny a bug based on a recording, so if they ARE recording games, they’re keeping it to themselves.
They may try to be polite, but trust me it’s expected by any programmer that understands how the industry works. Besides they routinely say “we looked at the data” for the new balance patches and they do the same for all other blizzard games too.
PS it is not against their terms of service and it’s very cheap at data storage too
And I’m sure they do collect all sorts of data.
How many games were played with a deck that contained card X?
In how many of those games was that card actually played?
How many of those games did that deck win?
etc etc.
It is entirely possible to keep these stats, without keeping full game recordings.
But, you go on believing whatever you like.
Also, we’re still waiting to see your decklist, and see what Firestone said the last four cards were in your deck…
They don’t HAVE to limit it to basic stats of that sort. That would make sense only if they had a storage issue and Hearthstone games are EXTREMELY low at data (it’s just a few bytes every entire game) [your local drive at home can probably record their ENTIRE YEAR of games data].
Unless you find a legal obligation of them to not record and I doubt there is especially since the Terms of Service of games usually prepare you that they do record the games.
[PS it was probably this deck: AAECAZ8FBrCyBIbiBISWBYWlBfboBY3+BQzHoATJoATi0wS/4gTM4gSBlgXBxAWU9QWV9QW8jwa1ngaSoAYAAA== ]
Probably?
You don’t even remember which deck it was, and yet we’re supposed to trust that you’re DEFINITELY REAL SURE that the deck had no dupes left.
Ooookay.
Dude literally go do something else. These bug reports are for DEVELOPERS.
Why are you even trying to “help”?
[ PS developers who have the games recorded AND THEY DO NOT NEED YOU ]
It makes perfect sense because those are the stats they actually CARE about.
Is a specific card getting a lot of play, or hardly any?
Do decks tend to win (or lose) when they play a specific card?
Those stats help them decide if a card is balanced.
I suggest you take a break from the bug report forums. You need education on the basics of Computing and it’s a place for bug reports for actual Developers.
You also have no clue about the basics of Statistics because the overall stats are ABSOLUTELY AND DEFINITELY NOT the only useful data in games.
[ PS it would also be kinda wasteful to collect stats BEFORE the games are recorded and that is pretty self-evident to any Developer ]
If they really wanted something directed towards developpers only they would make a ticket system without reply system.
Sadly for you you’ll have to accept that unexpected users of this forum can reply to your posts.
Because this is a public forum, and players are eager to help bug reporters to understand behaviors they are reporting that are perfectly normal.
For example : a player reporting an issue when playing a card with the no duplicate rule, while they still have duplicates in their deck, and reporting this on the forum, expecting developpers to take their time to invest it.
Players can help filter these issues out to soften their work.
And guess what ? You’re an example of that.
According to the replay you provided, and the decklist you provided, you just have to follow the turns to see that your last 4 cards were
Blood Matriarch Liadrin
1 Boogie Down
AND TWO Mining Casualities
Dun dun dunn!!!
And the culprit is revealed.
I’m waiting for his explanation!
Who am I kidding, we’ll never see him again.
You are right, which implies Firestone has a bug because the initial reason I made the bug report was that Firestone in its ingame overlay clearly had no card in the deck with a “2” next to it (as it is usually shown) (perhaps something with all that nonsense of The Countess AND a minion duplicating the Countess related-generated legendaries is related).
HOWEVER: I still don’t think you help the devs too much mainly because: I doubt they even BEGIN reading bug reports unless they actively search for it as in “google” it after it’s in their radar (at least in most cases) since I suspect their hands are full with bugs they either initially detect themselves or they first get multiple reports from many others.
[PS I had also checked manually a few minutes ago that I actually DID use that deck because when I had first posted it above it was unclear (but I cross-referenced the date/time in Firestone’s log with the decks it had there (they should actually link the deck next to their replays to make it easier)]
[PPS there is a remote chance a bug report is valid here; there may be a quirk with the log file third party apps read; but I doubt this thread can serve that purpose without being rewritten differently]
The fact you only came to whine and personally attack, without having any clue about my real behavior, says more about you than me.