Talk:Magic The Gathering card deck of programming language

From Esolang
Jump to navigation Jump to search

This could be an interesting idea, but I'm not sure what you mean. I've thought about MTG and programming myself because of its reliance on the Stack, but haven't really come up with anything interesting.

How would the deck calculate something? Just putting together a deck is not deterministic as it relies on the player to choose the order in which the cards are played. You would need some rules to say what cards should be played. And how about the opponent player(s)? --Rune 22:27, 18 Apr 2006 (GMT)

Yes you need rule what card you would play, such as: Always play the first available card from your hand, and the first permanent with a tapping ability that can be played. Also maybe you need to make up some cards for this. --Zzo38 15:19, 19 Apr 2006 (UTC)

I look at the example given, but doesn't both Phytohydras damage each other at the same time? I think it wouldn't do that if whichever one is attacking has first strike and the blocking one never does. Or maybe I am wrong about the rules.. but last time I checked I think these are the rules --Zzo38 14:50, 26 Aug 2006 (UTC)

I corrected it by adding Reflexes to one of the decks. --Zzo38 17:36, 26 Aug 2006 (UTC)

Most simple way to turn MtG game into a computation machine is to limit scope of consideration to cards in play (i.e., permanents) and objects on stack, assuming that players and objects in other zones of game do not interfere with game state. In this case, the "source code" would be the starting game state, and results of running it will be expressed in form of game state at some predefined moment (victory of one of players, for example).

Building on this, we can associate elements of players control over game state with runtime input.

That's, no time to log in just now :)