There’s something I’ve been putting off, and I need to get it done before modders go writing any Python mods. Fleshcult is currently written in Python 2, which is no longer supported. There’s a code library I’d like to use to talk to Steam that requires Python 3, so upgrading is suddenly a priority. In any case, it’s better done sooner rather than later because I don’t want to break code mods.
Translating code from 2 to 3 is mostly automated, but it’ll require some manual intervention here and there. It’s hard to say how long it’ll take, but hopefully it’ll be a non event. As a spin off, it might be better behaved with unicode install paths – Python 2 is notoriously error prone for that.
In the Steam beta branch and on Itch, you can now download a special v1.07 release of Fleshcult that has the first phase of mod support.
Steam Workshop isn’t supported just yet, so it’s not very interesting if you just want to play mods, but if you’re interested in creating them there’s new stuff to tinker with. So far it supports HTML/CSS mods for changing the way the game is presented. The ability to change the gameplay is something I’ll be working on next year.
To learn more about creating mods, you can consult the new Fleshcult Wiki which has a modicum of technical documentation. Feel free to add stuff I’ve glossed over. You’re also welcome to add info about playing the base game if you like. Happy holidays!
I’ve been making a lot of progress building the mod system and adding HTML/CSS modding specifically. I expect I’ll have something for modders to experiment with before Christmas, but hooking it up to Steam Workshop will have to wait until the new year. Changing the underlying behaviour of the game will arrive later.
I’m mindful that after I expose something to modders, doing a big refactor on it will break everybody’s stuff. So whenever I delve into the details, there’s a pressure to get things right the first time. That said, I suspect the smarter approach is probably getting something rough out quickly and then reacting to what people actually need.
One thing I’m over-engineering the fuck out of is giving modders lots of ways to add their stuff without overwriting stuff from other mods. Maybe if I pull that off Fleshcult modding won’t be a shitshow of bugs and load order tweaking? Time will tell.
What’s your favourite host for gaming wikis? I need somewhere to keep modding documentation.
And no, there’s no danger I’ll pick Fandom/Wikia. I hate them too.
I’ve been taking some time off the last week. I didn’t pace myself very well during October so I’m pretty fatigued. My apologies if you’re waiting on help with technical problems. I haven’t forgotten about you, I’m just tired.
Speaking of problems, there’s been a bunch of anti-virus false positives due to PyInstaller as I feared. Most of the major consumer brands have been OK except for BitDefender, which consistently causes problems. I’ve you’re seeing fleshcult.exe disappear, it’s almost certainly anti-virus related.
I’ve been poking around with different PyInstaller options, but the long term fix here is to use the relocatable version of Python so I can distribute the interpreter without doing anything weird to an exe’s contents. Unfortunately that was introduced in Python 3 and Fleshcult is on 2.7, so I won’t be able to address that in the short term.
- Bug fixes
- Mac version
Downloadable Fleshcult is out and aside from some weird crashes I’m still tracking down, the pressures of launch are starting to settle down. I’ve been ducking a lot of questions about whether I’ll be producing more content by saying it depends on sales. Based on how things are going, I can commit to a Mac version and mod support.
Mod support is gonna come in stages. Letting people change the look of the game and add more graphics is relatively easy. The game would load an extra CSS stylesheet out of the mod folder, and with a few extra hooks from me and the magic of pseudo-elements, you’ll be able to add artwork with a high degree of flexibility. I’ll supply examples for the CSS, so try not to let terms like “pseudo-element” disconcert you.
Modding the HTML isn’t gonna be too bad either. Some enterprising individuals are already doing it, though this will get overwritten every time I update, so you really do need that mods folder in the long run.
Allowing new characters and tomes and so forth is gonna take some doing. Ideally these would be loaded from data files, but at the moment it’s all in code. Conceivably I could run Python scripts out of mod folders and let them monkey-patch the game, but that’d be total chaos with multiple mods involved! There’s a fair amount of ground work to be done here and this is the task I have the most uncertainty about. It’ll probably come last.
As for Steam Workshop, I had a notion that it’d just need a game that knows how to load mods out of a mods folder. But no, I’ve gotta delve into the Steamworks API to make that work. Once again, it’ll take some time, but it’s looking pretty feasible.
This is a bug fix release for Steam and Itch versions. The changes are:
- Fixed crash at start up when there’s non-ASCII characters in the game’s install path, or the player’s Windows username.
- Fixed inability to save game when there are underscores or non-ASCII characters in the player’s Windows username.
- Better error message logging.
ON INTERNATIONAL CAPS LOCK DAY 2020, PLEASE ENJOY FLESHCULT FOR STEAM AND ITCH
EDIT: IF YOU HAVE TIME, I’D APPRECIATE ANY RATINGS OR REVIEWS YOU MIGHT HAVE FOR STEAM AND ITCH!
I’m planning to turn off the server for the web version on October 29th. If you’re in the middle of a game there, I recommend finishing up soon!
If you can’t afford to move to the Steam version, never fear; the Itch version is Pay What You Want, and that includes free.
If you’re on Mac, I’ll be looking at doing a port after the release crunch dies down. Mobile users, I’m sad to say, are entirely out of luck. Sorry about that.