The first time I ran into that it was with WPF , so the interface was discarded anyways as soon as the result was bound to a UI control . <| sep |> I saw an ad for some Google VR device recently . <| sep |> edit To put a finer point on it , the problem wasn ' t that Gathan Raiders was broken , but that it warped the format around itself in undesirable ways . This has always been the biggest problem with Morph in limited . The ability to have the option to play your cards as colorless Gray Ogres is really good for limited , but getting blown out sometimes by something you have no control over leads to some unfun moments . Khans really did a good job of intentionally making all early game morphs have either less than two power or less than three toughness , so you wouldn ' t feel bad about being blown out in combat early due to sheer chance . Gathan Raiders randomly blowing you out was unfortunate , but I think Onslaught limited was even worse . At least with Gathan Raiders you could choose not to block the morph if you weren ' t comfortable with it randomly becoming a 33 . The following scenario was way more common in Onslaught limited than you would expect . Your opponent is playing a red deck . On turn 3 he plays a morph . You play a morph on your turn 3 . Your opponent untaps and attacks you with his morph . What do you do ? If you block , surprise ! His morph was Battering Craghorn and your morph just died for free . If you don ' t block , well too bad . It turns out his morph was actually Skirk Commando and your morph just died for free . The situation described above was basically a 5050 guess where the winning outcome is you breaking even and the losing outcome is a pretty big blowout which you had no real control over . The fact that both Battering Craghorn and Skirk Commando were quality red commons didn ' t help things either .