I can’t get progress on type spell quest (play 10 fire spells, fireballs don’t count even though they are clearly a fire spell) when playing in classic mode.
Classic recreates the original environment, before spells had types.
This isn’t a bug.
2 Likes
How it it not a bug? I think its pretty obvious its a fire spell. The only thing this would change is giving players proper rewards instead of trying to make players spend more money on packs.
Because the original environment didn’t have types. Now, it’s a Fire Spell, back then, it wasn’t. So while in Standard and Wild it’s a Fire Spell, in Classic, it’s not.
2 Likes
Where does it say it’s not a fire spell so I can see? It seems like the quest is referring to spells made of fire, not a specific mechanic.
It’s looking for spells under a specific subcategory.
See the “Fire” label on the bottom of the card? That’s the subcategory. It’s not present on the classic cards, so they can’t trigger the quest. This isn’t a bug.
2 Likes
Fire spells could 100% still trigger the quest even without the tag on the card. Still seems like a bug to me. Idk anything in blizzard history that suggest fireball isn’t a fire spell outside of this one bug. Older cards not having the label on them doesn’t make it not a fire spell. Is there any evidence anywhere that it wasn’t a fire spell outside not explicitly writing fire on the original card?
No, because if it doesn’t have the tag, it’s not a fire spell. Just like a minion that doesn’t have the pirate tag isn’t a pirate. That’s why it does have the tag in Standard and Wild, but not in Classic, because it’s not a fire spell since spell types didn’t exist yet.
If you go to the Hearthstone Site and check the card database under Classic, you’ll see that Fireball does NOT have the fire tag, while the version in Wild does have it.
1 Like
The reason it didn’t have a tag in classic was because there was no reason to tag it, right? Hence it getting a tag when there was a reason. Blizzard most likely didn’t think of the quest not affecting classic cards or they would have added a hidden tag. Is there anything that shows it wasn’t a fire spell before or it just wasn’t tagged with the new art? They could achieve the same effect by adding a hidden tag or just checking if a certain spell was played. You can’t argue things not tagged with fire aren’t fire spells when the reason they aren’t tagged is because the tag didn’t exist.
Yes, now we’re getting somewhere! There was no reason to tag it, because there were no spell types. All spells were just spells. No special distinction between them. A Fireball was just the same as a Shadowform or an Iceblock. It was a spell. Now, however, there are cards that interact with certain types of spells, so those spells got a type. Back then, it wasn’t needed, but now it is. So, what didn’t exist before, exists now, but in Classic, it still doesn’t exist.
Or maybe, the fact they didn’t add a hidden tag was because they didn’t want the Classic cards affecting the quest.
Yes, the fact that it doesn’t say “Fire” at the bottom of the card and the fact that the artwork didn’t change. It’s exactly the same spell, except now it’s a Fire Spell while back then it was just a spell.
Yes, you can, because if you change something retro-active, you only change it in the present, not in the past. And Classic is based on the past.
2 Likes
Do you have any proof of any of this? It all seems logically inconsistent. Fireball is clearly a fire spell. You say it wasn’t a fire spell but you offer no proof other than they didn’t explicitly state it was a fire spell. You say they would have labeled it a fire spell if it was but there was no label for it.
You actually don’t have to change anything about the spell to make the quest work properly, you just have a check to see if a certain spell was played.
Yes, yes I do.
See? There’s your proof. If it was a Fire Spell, then the quest would have progressed.
You need to play Fire Spells, which means spells with the Fire tag. Classic Fireball doesn’t have the tag, so it doesn’t progress the quest. Something is only a type if it has a tag, such as Murlocs, Pirates and Beasts. If it doesn’t have the tag, it’s not that type.
Blame bureaucracy, but it’s not a bug. I know, it walks like a duck and quacks like a duck, but because it’s not labelled as a duck, it doesn’t count as a duck. Because they didn’t count ducks yet back then, only birds!
1 Like
Exactly my point! They didn’t count ducks back then. Its still a duck, they just don’t have the duck label on it. That’s what we in the dev biz call a bug. You can’t argue somethings not a bug or the bug wouldn’t be there…
Yes, you can. If it’s not a bug, the bug’s not there. Because it’s not a bug!
If a spell doesn’t have a tag, it’s a general spell. The quest doesn’t ask you to play general spells, but spells with a tag. Classic doesn’t have tags. If there was a quest that required you to play general spells, all spells in Classic would apply, because they have no tags. If they wouldn’t count because they have a tag now, that would be a bug. And if you dare say “there’s no such quest” I tell you there’s no such quest YET. What if in the future they add such a quest? Because that’s what they did with tags. There weren’t any for spells, and then they added them.
1 Like
You’re clearly just trolling now. Bugs are created by accident, thats why you can’t say them existing means its not a bug but I know you know that. Have a nice day, go troll another post or offer one piece of evidence if you actually want to discuss it.
I’m not trolling! The card doesn’t have a tag, so it doesn’t count as a card with that tag, just like a minion that doesn’t have the pirate tag counts as a pirate. I don’t know how else to make it clear. It even makes me think you’re the one who’s trolling me!
1 Like
You offer no proof that fireball isn’t a firespell… you just say well they didn’t use to explicitly label it fire so it isn’t fire. And when I ask for proof, you point to the bug I reported as your only evidence. Clearly you’re trolling…
We gave you proof! We told you that Fireball isn’t a firespell because it doesn’t have the tag “Fire”. You wanted more. Well, the fact that it doesn’t count for the quest is also proof. What else do you want?
Every spell with the tag “Fire” works for the quest. The only ones that don’t work are the versions that don’t have the tag “Fire”.
1 Like
So my bug existing is proof its not a bug. Ok buddy, go troll elsewhere and come back when you feel like providing evidence instead of trolling.
Two other people have told you it’s not a bug, giving you the explanation. No one has said that you were correct.
Tell me, what other proof do you want? Because all I can give you is the evidence at hand and that clearly is not enough.
1 Like