Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Thank you!

Building from source for windows seems like a challenge. I'm on linux.

But, using a normal Decker executable seems like it would be pretty straight forward. Are there any downsides to that approach for targeting Windows and Mac? 

Like what would be the difference for the player's experience between a native decker that auto-loads a deck vs. Decker built from source with a different "tour.deck"? Does it net out to the same thing essentially?

A baked-in tour.deck vs. a startup deck is essentially the same from a user perspective. Startup decks were intended as a simple way to allow people to distribute decks along with a native runtime.