Outside the API: 1) no 2) no. 2 can be partially addressed with some Stylish changes to make the cards appear much larger, or with a bookmarklet. Here's a bookmarklet that makes cards 400px wide: javascript:(function(){$('<style type="text/css">#showndecks {width:400px;} #showndecks .deckstack {width: 400px;} #showndecks .card {width:400px;}</style>').appendTo('head');}()) Stylish could be used to make that always the case locally. With the API: 1) I have an API script that will let you set the order of a deck, provided all the images are in a user library and not from the marketplace. You could use that to reset the correct order each time after shuffling. Because of how the decks work, it technically does not change the order, but rather changes all the cards so that whatever card is first will have the properties of the card you want first, etc. That means it would change cards in peoples hands as well. 2) The API could certainly find a card by name, but there aren't mechanics (currently) for drawing or dealing it. If it's image isn't from the marketplace, it could be created on the table, but it would still be in the deck and could be drawn.
