I still must agree with stam (and myself) that SVGs are far preferable to .png images.
As Richmond found -- and I'd mentioned previously regarding an email exchange with Paul McClendon -- LC does not currently handle font glyphs, so that in SVGs of playing cards on the net these elements need to be rendered as outlines (using Inkscape or AI) then the modified SVGs resaved. But why "reinvent the wheel" when Paul has already done this work for us? (As I understand his very generous GPL license, these are available for us to access and use.)
I've created a stack modeled upon Paul's code that displays the SVGs that he encoded into a script-only LC stack. Once you load the script-only stack into the mainstack, you need only specify the array key for a given playing card to display it at three different sizes, which look so much nicer than do resized bitmap images. His array keys are named sensibly: e.g., QD for "Queen of Diamonds" or 7H for "Seven of Hearts."
It's important to note that he used playing cards only to illustrate how his "SVGCompiledArrayLibMaker.livecode" utility can be used to create a script-only library stack that encodes any number of SVGs in an array. So, for example, if the game that Zax intends to create employs images different from the conventional playing cards, Paul's utility can create a library stack from any set of SVGs.
Anyway, here's the stack that demonstrates this. (At 2.7 MB -- owing to the inclusion of Paul's library script -- even the .zip is apparently too large for a forum attachment, so available only for a few weeks on my webserver instead):
https://newpsyc.com/SVG_CardDemo.zip
jeff k