Cargo Query Error: Error: Table Card not found.
is an uncollectible TYPEID card.Cargo Query Error: Error: Table Card not found.Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__Achievements`.`id` IS NOT NULL AND `cargo__Achievements`.`descriptio' at line 1
Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__Achievements`.`id` AS `achievementId`,`cargo__Achievements`.`name` AS `achievementName`,`cargo__Achievements`.`description` AS `achievementDescription`,`cargo__Achievements`.`quota` AS `achievementQuota`,CONCAT("Achievement") AS `type` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__Achievements` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__Achievements`.`rewardListId`)) WHERE AND `cargo__Achievements`.`id` IS NOT NULL AND `cargo__Achievements`.`description` IS NOT NULL AND NOT `cargo__RewardItem`.`rewardType`=10 ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__Achievements`.`id`,`cargo__Achievements`.`name`,`cargo__Achievements`.`description` LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__Achievements`.`id` IS NOT NULL AND `cargo__Achievements`.`descriptio' at line 1 Function: CargoSQLQuery::run Query: SELECT CONCAT("Animated") AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__Achievements`.`id` AS `achievementId`,`cargo__Achievements`.`name` AS `achievementName`,`cargo__Achievements`.`description` AS `achievementDescription`,`cargo__Achievements`.`quota` AS `achievementQuota`,CONCAT("Achievement") AS `type` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__Achievements` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__Achievements`.`rewardListId`)) WHERE AND `cargo__Achievements`.`id` IS NOT NULL AND `cargo__Achievements`.`description` IS NOT NULL AND `cargo__RewardItem`.`rewardType`=10 ORDER BY CONCAT("Animated"),`cargo__RewardItem`.`quantity`,`cargo__Achievements`.`id`,`cargo__Achievements`.`name`,`cargo__Achievements`.`description` LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`s' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__RewardTrackLevel`.`rewardTrackId` AS `rewardTrackId`,`cargo__RewardTrackLevel`.`level` AS `level`,CONCAT("Free Track") AS `type`,`cargo__RewardTrack`.`name` AS `rewardTrackName`,`cargo__RewardTrack`.`rewardTrackType` AS `rewardTrackType`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%H:%i %M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__RewardTrackLevel` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__RewardTrackLevel`.`freeRewardListId`)) LEFT OUTER JOIN `cargo__RewardTrack` ON ((`cargo__RewardTrackLevel`.`rewardTrackId`=`cargo__RewardTrack`.`id`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__RewardTrack`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`startTimeUtc`>="2023-08-01 17:00:00" OR `cargo__EventTimingEvent`.`startTimeUtc` IS NULL) AND `cargo__RewardTrack`.`rewardTrackType`="1" AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__RewardTrackLevel`.`rewardTrackId`,`cargo__RewardTrackLevel`.`level`,CONCAT("Free Track") LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`s' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__RewardTrackLevel`.`rewardTrackId` AS `rewardTrackId`,`cargo__RewardTrackLevel`.`level` AS `level`,CONCAT("Paid Track") AS `type`,`cargo__RewardTrack`.`name` AS `rewardTrackName`,`cargo__RewardTrack`.`rewardTrackType` AS `rewardTrackType`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%H:%i %M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__RewardTrackLevel` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__RewardTrackLevel`.`paidRewardListId`)) LEFT OUTER JOIN `cargo__RewardTrack` ON ((`cargo__RewardTrackLevel`.`rewardTrackId`=`cargo__RewardTrack`.`id`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__RewardTrack`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`startTimeUtc`>="2023-08-01 17:00:00" OR `cargo__EventTimingEvent`.`startTimeUtc` IS NULL) AND `cargo__RewardTrack`.`rewardTrackType`="1" AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__RewardTrackLevel`.`rewardTrackId`,`cargo__RewardTrackLevel`.`level`,CONCAT("Paid Track") LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`e' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__RewardTrackLevel`.`rewardTrackId` AS `rewardTrackId`,`cargo__RewardTrackLevel`.`level` AS `level`,CONCAT("Free Track") AS `type`,`cargo__RewardTrack`.`name` AS `rewardTrackName`,`cargo__RewardTrack`.`rewardTrackType` AS `rewardTrackType`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%H:%i %M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__RewardTrackLevel` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__RewardTrackLevel`.`freeRewardListId`)) LEFT OUTER JOIN `cargo__RewardTrack` ON ((`cargo__RewardTrackLevel`.`rewardTrackId`=`cargo__RewardTrack`.`id`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__RewardTrack`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`endTimeUtc`<NOW() OR `cargo__EventTimingEvent`.`endTimeUtc` IS NULL) AND NOT `cargo__RewardTrack`.`rewardTrackType`=1 AND NOT `cargo__RewardTrack`.`rewardTrackType`=2 AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__RewardTrackLevel`.`rewardTrackId`,`cargo__RewardTrackLevel`.`level`,CONCAT("Free Track") LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__Quest`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`endTimeUtc`>' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__Quest`.`name` AS `questName`,`cargo__Quest`.`description` AS `questDescription`,`cargo__Quest`.`quota` AS `questQuota`,CONCAT("Quest") AS `type`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%H:%i %M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__Quest` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__Quest`.`rewardListId`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__Quest`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__Quest`.`id` IS NOT NULL AND (`cargo__EventTimingEvent`.`endTimeUtc`>NOW() OR `cargo__EventTimingEvent`.`endTimeUtc` IS NULL) AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__Quest`.`name`,`cargo__Quest`.`description`,`cargo__Quest`.`quota` LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`st' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__RewardTrackLevel`.`rewardTrackId` AS `rewardTrackId`,`cargo__RewardTrackLevel`.`level` AS `level`,CONCAT("Free Track") AS `type`,`cargo__RewardTrack`.`name` AS `rewardTrackName`,`cargo__RewardTrack`.`rewardTrackType` AS `rewardTrackType`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__RewardTrackLevel` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__RewardTrackLevel`.`freeRewardListId`)) LEFT OUTER JOIN `cargo__RewardTrack` ON ((`cargo__RewardTrackLevel`.`rewardTrackId`=`cargo__RewardTrack`.`id`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__RewardTrack`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`startTimeUtc`<"2023-08-01 17:00:00" AND `cargo__RewardTrack`.`rewardTrackType`="1" AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__RewardTrackLevel`.`rewardTrackId`,`cargo__RewardTrackLevel`.`level`,CONCAT("Free Track") LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`st' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__RewardTrackLevel`.`rewardTrackId` AS `rewardTrackId`,`cargo__RewardTrackLevel`.`level` AS `level`,CONCAT("Paid Track") AS `type`,`cargo__RewardTrack`.`name` AS `rewardTrackName`,`cargo__RewardTrack`.`rewardTrackType` AS `rewardTrackType`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__RewardTrackLevel` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__RewardTrackLevel`.`paidRewardListId`)) LEFT OUTER JOIN `cargo__RewardTrack` ON ((`cargo__RewardTrackLevel`.`rewardTrackId`=`cargo__RewardTrack`.`id`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__RewardTrack`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`startTimeUtc`<"2023-08-01 17:00:00" AND `cargo__RewardTrack`.`rewardTrackType`="1" AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__RewardTrackLevel`.`rewardTrackId`,`cargo__RewardTrackLevel`.`level`,CONCAT("Paid Track") LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`en' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__RewardTrackLevel`.`rewardTrackId` AS `rewardTrackId`,`cargo__RewardTrackLevel`.`level` AS `level`,CONCAT("Free Track") AS `type`,`cargo__RewardTrack`.`name` AS `rewardTrackName`,`cargo__RewardTrack`.`rewardTrackType` AS `rewardTrackType`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__RewardTrackLevel` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__RewardTrackLevel`.`freeRewardListId`)) LEFT OUTER JOIN `cargo__RewardTrack` ON ((`cargo__RewardTrackLevel`.`rewardTrackId`=`cargo__RewardTrack`.`id`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__RewardTrack`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__RewardTrackLevel`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`endTimeUtc`>NOW() AND NOT `cargo__RewardTrack`.`rewardTrackType`=1 AND NOT `cargo__RewardTrack`.`rewardTrackType`=2 AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__RewardTrackLevel`.`rewardTrackId`,`cargo__RewardTrackLevel`.`level`,CONCAT("Free Track") LIMIT 100 Cargo Query Error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND `cargo__Quest`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`endTimeUtc`<N' at line 1 Function: CargoSQLQuery::run Query: SELECT `cargo__RewardItem`.`cardPremiumLevel` AS `cardPremiumLevel`,`cargo__RewardItem`.`quantity` AS `quantity`,`cargo__Quest`.`name` AS `questName`,`cargo__Quest`.`description` AS `questDescription`,`cargo__Quest`.`quota` AS `questQuota`,CONCAT("Quest") AS `type`,DATE_FORMAT(`cargo__EventTimingEvent`.`startTimeUtc`,"%M %e, %Y") AS `startDate`,DATE_FORMAT(`cargo__EventTimingEvent`.`endTimeUtc`,"%M %e, %Y") AS `endDate` FROM `cargo__RewardItem` LEFT OUTER JOIN `cargo__Quest` ON ((`cargo__RewardItem`.`rewardListId`=`cargo__Quest`.`rewardListId`)) LEFT OUTER JOIN `cargo__EventTimingEvent` ON ((`cargo__Quest`.`event`=`cargo__EventTimingEvent`.`type`)) WHERE AND `cargo__Quest`.`id` IS NOT NULL AND `cargo__EventTimingEvent`.`endTimeUtc`<NOW() AND `cargo__EventTimingEvent`.`region`="Americas" ORDER BY `cargo__RewardItem`.`cardPremiumLevel`,`cargo__RewardItem`.`quantity`,`cargo__Quest`.`name`,`cargo__Quest`.`description`,`cargo__Quest`.`quota` LIMIT 100
Cargo Query Error: Error: Table Card not found.Cargo Query Error: Error: Table Card not found.Cargo Query Error: Error: Table Card not found.
History
Design
Designers Mike Donais and Peter Whalen explain that the card went through numerous iterations before reaching the version seen in-game.[1] The overall design concept for Yogg-Saron was a "top-down" approach, trying to envision "what Yogg-Saron would actually do".[2]
The oldest recorded design was as a 10 mana 10/10 minion, with the text, Your spells cost (1). While this is in your deck, you have 15 seconds per turn. The designers comment:
- "We wanted the old gods to blow your mind when you saw them. We tried some crazy versions that had effects if they started the game in your deck. This one is a mixed blessing, your turns are really short, which can be exciting if you opt into it. As a bonus, once it’s in play, all your spells are 1 mana which can cause some crazy turns."
However, this design was quickly found to be overpowered, leading to some "absolutely ridiculous" combinations, such as Mages filling their hands with 1 mana damage spells such as ![]()
Pyroblast.
Another design was as a 4 mana 8/8, with the text, When the game starts, gain 3 Mana Crystals. You can't gain more. This gave the player a strong initial advantage, but with an even stronger disadvantage once the game got going. Whalen explains:
- "If your opponent got to 6 crystals and could stabilize, they won, and otherwise you could just kill them with 5/4s. It really felt like playing an A.I. where it feels good when you win but really bad when you lose. And it felt kind of boring for the guy who had just 4 mana crystals. Just, 'I'm going to do this thing.'"
The Yogg-Saron player's deck would predictably consist of mostly 4 mana minions, allowing for the maximum output each turn, leaving little room for ingenuity, while the opponent had little choice but to use removal to attempt to survive the first few rounds, with losses feeling decidedly unfair. Although the designers tried varying the exact number of Mana Crystals, ultimately Yogg-Saron games just "didn’t feel particularly good", and the design was scrapped.
Another design featured Yogg-Saron as a 5 mana 10/10, with the text, When the game starts, Yogg-Saron eats your mind. You only have 15 seconds each turn. This design was intended to provide a calculated risk, with the minion itself massively undercosted, allowing for strong early game advantage, in exchange for an equally large reduction in the time available to the player to make their actions each turn. This iteration was ultimately rejected due to technical limitations with synchronisation and lag, potentially causing trouble with such short turns, although the developers were also uncertain about the design.
After myriad iterations, the designers eventually settled on a basic theme: summoning Yogg-Saron would cause it to cast a large number of spells, based on the player's spell-casting that game. However, the developers tried various implementations before hitting on just the right design.
The original version was a 10 mana 8/8, which rather than casting random spells, cast a copy of each spell the player had cast that game. While the targets were still chosen randomly, the control over which spells were cast allowed players to set up devastating one turn kills, potentially making play very uninteractive. Certain cards caused additional problems:
- "Infinite Yogg Saron. It turns out if you play him and you cast

Vanish that game, really, nobody gets to play Hearthstone anymore. You don't always win those games but they're not that fun."
When the spells cast by Yogg-Saron were changed to be random - matching its current design - not only were the results less predictable, but the increased randomness turned playing the card from a guaranteed win to a gamble with frequently hilarious results, exchanging boring but overpowered for risky but fun. After arriving at Yogg-Saron's final card text, the last change was to reduce its stats to a 7/5, making sure its strength lay more in its spells than in the minion itself.
Changes
Initially predicted by many players to be of little value, once released Yogg-Saron quickly became a popular card in ladder matches. While it still had the risk of defeating the player who used it, its average outcome was found to be favourable, being especially strong for Tempo Mage and Token Druid, where it was commonly used as a finisher or comeback tool. The card also saw a large reaction from players and spectators due to its potential for fun and unexpected plays.
In the months following its release the card saw play in a number of major tournaments, where its large impact on the outcome of matches resulted in the playerbase becoming divided over how positive it was for the game, with some calling for it to be banned from tournaments. While its overall effectiveness was not, according to Blizzard,[3] very high, its strong RNG factor led to frustration for many players and encouraged the view of Hearthstone as being determined mostly by luck, rather than skill. Others defended the card, citing its largely enjoyable effect on the game, and pointing out that the start of the new Standard year would see many of the most problematic spells removed from Standard format.
In September 2016 the developers acted, describing the card as "the most controversial card we've ever made", and explaining that "seeing Yogg in tournaments was not where we originally hoped it would end up" stating that "Yogg should be for players who want to have a lot of fun, but maybe not the card you see frequently in high-level tournaments." The card was subsequently nerfed by means of a rule change: where the card would previously continue to cast spells regardless of what happened to the Yogg-Saron minion itself, it would now cease to cast spells as soon as the minion was destroyed, Silenced, transformed or returned to the hand. In addition, a subsequent change with Patch 6.2.0.15181 caused the spells cast by Yogg-Saron to apply any Overload to the controlling player, something which the developers had previously been uncertain whether to introduce. The combined changes acted to nerf the reliability and overall power of the card, with the intention of removing it from top-tier play, while still "maintaining the dream for people who love the card."[4]
The card largely fell out of use after this, as it became too risky to spend 10 mana on a card that may do nothing. Additionally, the rising power level of cards in Wild format meant Yogg wasn't likely to decide the outcome of games even if he survived. In Patch 16.6.0.43246, a little less than two years after Yogg-Saron entered Wild, Yogg-Saron's effect was reverted to its original design.
Lore
Yogg-Saron, as depicted by Dan Scott
- Yogg-Saron is a named Old God, one of the mysterious and dread elder beings that were defeated and sequestered by the Titans during Azeroth's primordial ages. Upon their fall at the hands of the Pantheon countless millennia ago, Yogg-Saron was imprisoned inside a Titan complex within the depths of what would become the continent of Northrend. Yogg-Saron made its first appearance in World of Warcraft as the final boss in the raid dungeon Ulduar, which was implemented in patch 3.1.
In Hearthstone
- Yogg-Saron (yog-suh-RAWN or /jagsʊ'ɹɒn/) is an Old God of many names, each one of them a mouthful. It’s amassed titles such as The Beast with a Thousand Maws, That Which Must Not Be Named, The Fiend of a Thousand Faces, and its personal favorite: The God of Death. For a cosmic horror with an identity crisis (and a taste for forbidding and lengthy nicknames), it’s got a real silver tongue. Lots of silver tongues, probably, since its face is mostly gaping, toothy maws. Anyway, finding eternal imprisonment beneath the continent of Northrend to be a bitter pill to swallow, Yogg-Saron used nothing more than its insidious whispers to corrupt its own jailers. It succeeded in turning them against each other before taking control of them, and the prison complex itself.
- While Yogg-Saron was staging the slowest prison break in history, its oozing vileness was seeping up all over Northrend, sowing strife wherever it was found. Druids, led by

Fandral Staghelm, thought they could halt its spread with a little creative landscaping, but the roots of the World Tree they planted grew deep enough to touch Yogg-Saron’s prison. This monumental misstep gave Yogg-Saron the opportunity to pry open the door into the Emerald Dream. The tree was destroyed, but not before the seeds of the Emerald Nightmare were planted by the Old Gods.
- Yogg-Saron is hideously good at proving that when you’re up against this mouthy monster, you’ve bitten off more than you can chew.[5]
Trivia
- "so how many times have people Pyroblasted themselves in the face in testing with Yogg-Saron?"
- "five. there is a scoreboard on the wall"[8]
Gallery
External links
References[]
- ↑ 1.0 1.1 Shack News - Making a Hearthstone Card: The Madness of Yogg-Saron. (2016-04-29).
- ↑ 2.0 2.1 The Angry Chicken: "The One with Iksar". (2016-05-18).
- ↑ Ben Brode on Twitter. (2016-09-28).
- ↑ Upcoming Balance Changes - Update 6.1.3. (2016-09-28).
- ↑ Whispers of the Old Gods – It's Never a Yawn with Yogg-Saron. (2016-04-07).
- ↑ PC Gamer on Twitter. (2016-04-07).
- ↑ IGN - BLIZZARD ON DESIGNING HEARTHSTONE’S OLD GODS. (2016-06-20).
- ↑ Max McCall on Twitter. (2016-04-07).
- ↑ The Art of Hearthstone Vol. 2, pg. 20


