Fleshcult Steam Progress Update

I’ve sent a Windows test build out to testers. On my computers it’s stable and I can play through to the end, but I suspect there’s still many compatibility and polish issues to discover on other configurations.

I’m signed up to Steam as a dev. Signing up is a bit like buying a gun: you can’t release a game until 30 days have passed, to prevent crimes of passion. This puts the earliest possible release date in October. In any case I’ll need some time to dig out and finish off the Infestation Tome, and make allll the marketing assets. Did you know Steam requires 10 logo images, all in different sizes and subtly different aspect ratios? And screenshots – my mind goes blank when I try to think of an exciting Fleshcult screenshot. That’ll be tricky.

So far I’ve been using PyInstaller to produce an exe. I’m unsettled to read reports that Anti-virus programs really hate PyInstaller exes. I guess an interpreter running bytecode embedded inside the same executable looks like fancy footwork to evade detection heuristics. This is not helped by PyInstaller’s lead dev’s pig-headed insistence that it’s not his problem to offer a less suspicious-looking process. I might have to revisit this decision, but we’ll see how it goes.

2 thoughts on “Fleshcult Steam Progress Update

  1. bicobus says:

    Being a python dev myself, I’ve looked to replace pyinstaller. It’s quite a nice piece of software, but the inability to configure where the executable is built in relation to it’s libraries is annoying.

    So after research, I found those alternatives to pyinstaller. May this help you.

    * PyInst: https://pynsist.readthedocs.io
    * nuitka: https://nuitka.net/d

    • jackoekaki says:

      Good to know! I don’t mind about the libraries thing, jamming everything in one spot is what I need for Steam anyway, but hopefully one of those stores the bytecode separately so the bootloader can get whitelisted by AV firms, and stay whitelisted.

Comments are closed.