Limited Resources 226 – ROTTY And Application of Tools

This week on Limited Resources Brian and Marshall revisit a core tenent of the LR philosophy: Don’t Be ROTTY. Results Oriented Thinking is the downfall of many Magic players, and the guys go into depth about how to analyze and fix the problem. Also discussed is the concept of how to actually apply the tools talked about on the show week in and week out. 


Limited Resources is proudly sponsored by Card Kingdom! Check out for competitive prices and top-notch service.


Contact Marshall_LR on Magic Online if you’d like to join the Limited Resources clan.


Your Hosts: Marshall Sutcliffe and Brian Wong

Marshall’s Twitter:

Brian’s Twitter:


Check out this episode!

4 thoughts on “Limited Resources 226 – ROTTY And Application of Tools

  1. Very funny closing, love it. Keep up the good work guys, I am getting better. Last three FNM’s have been 1st, 2nd, 2nd for me……all because of your podcasts/videos/articles and streams.

  2. I had a simple example of the luck vs plan segment of he podcast a little while ago. I was in a draft against a white splashing red aggro deck and I was playing a blue/red midrange deck. Game one I used nullify on an elite skirmisher. Well, the next turn he drew and played brimaz. I won he game, but only by attacking into his brimaz, banking on him blocking and killing my creature, and finished it off with bolt of keranos afterword. I had to two for one myself because I didn’t have any removal spells in the deck to kill such a big threat outright, and I had to bank on my opponent making a bad play. So game two, instead of hoping he didn’t draw brimaz, I consciously decided not to waste a nullify on any creature I have other outs for and save the nullify for brimaz. Turn 3 he played skirmisher again, and I had nullify open and let it live. Three or four turns later, I nullified brimaz, and his deck fell apart. Was that the best decision or plan? I don’t know, but at least I tried to use logic to make it.

Leave a Reply

Your email address will not be published.