Post by cake-icing in Exporting Decks?

Viewing post in Exporting Decks?

I'd want to bump this question again. Maybe there are new developments. Saving a deck as an HTML file is neat, however, the web version of Decker struggles with cards where there are multiple animated widgets – it's just super slow. So, I was pondering on the same question as the author – how can I bundle my decks as a single _windows_ executable. I've heard that people release games made in Decker on Steam – so it should be possible.

I experimented a bit with the Enigma Virtual Box – it lets package an executable (Decker) + virtual FS (with a deck file) as a single exe file. But I wasn't entirely successful. It's also a pain to run windows software on wine in MacOS (I know, it's self-inflicted pain, but I have what I have :) ).

Internet Janitor2 days ago(+1)

The simplest approach to distributing "standalone" decker executables is to take advantage of the "start.deck" mechanism, which you might be alluding to using in your virtual filesystem experiments.

See also this more recent discussion: https://itch.io/post/12903659

As a side note, if you're having severe performance problems with multiple animated widgets on a card, make sure the animated widgets are each handling the view[] events they are being sent, and not bubbling them up to the surrounding card. I've seen examples in the past where this type of programming mistake lead to games executing their "main loop" logic dozens of times per frame instead of once, with corresponding performance impact. Lengthy deck-level scripts can also add overhead to event processing; moving the bulk of these scripts into a module is one way to reduce this overhead.