You are not the first to randomly discover this, but it is actually a part of the game since the very start.
Blizzard has the possibility to tag every card with a race or Tribe, and it includes basically all the older races, including Blood Elf and Draenei, but that same option also includes mechanical, murloc, dragon, etc. etc.
So I suspect that this is just part of systems that Blizzard at some point maybe toyed with and half implemented and then never did anything with once they settled on the game as it came out at first.
Rollback Post to RevisionRollBack
If you see a bad post on the forum use the report function under it, so I or someone else of the moderation team can take care of it!
You are not the first to randomly discover this, but it is actually a part of the game since the very start.
Blizzard has the possibility to tag every card with a race or Tribe, and it includes basically all the older races, including Blood Elf and Draenei, but that same option also includes mechanical, murloc, dragon, etc. etc.
So I suspect that this is just part of systems that Blizzard at some point maybe toyed with and half implemented and then never did anything with once they settled on the game as it came out at first.
My take is that they already have every race tagged and attached to a tribe, just in case it's needed for specific synergies on the feature, and they create every card with these tribes, but with a "visible" flag set to false. Code wise, this is the most scalable solution. Whenever they want to, they can release it. It saves them lots of hours of work whenever they want to add "new" tribes, since they would have iterate over every god damn card. The bug is that probably the Amalgam is not looking at that flag.
Hi guys.
I was just messing around with my collection looking some cards and I noticed something. I'll put some images, it's better than a thousand words.
It seems amalgam is showing tribes that are currently unavailable but somehow mapped by it. You can test it with the following searchs:
We can try different words for testing if this is more of a random issue or it's consistent. For example, treant doesn't triggers Circus Amalgam.
Kinda funny, I guess they have all of these hidden tribes waiting for the moment of being released.
You are not the first to randomly discover this, but it is actually a part of the game since the very start.
Blizzard has the possibility to tag every card with a race or Tribe, and it includes basically all the older races, including Blood Elf and Draenei, but that same option also includes mechanical, murloc, dragon, etc. etc.
So I suspect that this is just part of systems that Blizzard at some point maybe toyed with and half implemented and then never did anything with once they settled on the game as it came out at first.
If you see a bad post on the forum use the report function under it, so I or someone else of the moderation team can take care of it!
It works with "fire" too, but not the other spell schools
My take is that they already have every race tagged and attached to a tribe, just in case it's needed for specific synergies on the feature, and they create every card with these tribes, but with a "visible" flag set to false. Code wise, this is the most scalable solution. Whenever they want to, they can release it. It saves them lots of hours of work whenever they want to add "new" tribes, since they would have iterate over every god damn card. The bug is that probably the Amalgam is not looking at that flag.