Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register Favorites Keys Review DMs Logout
Community
Telegram ThePornDude
Home Creators Posts Import Register Favorites Logout

Itch Devlogs (Patreon)

Published:
2025-11-28 18:22:47
Edited:
2025-11-28 20:19:29
Imported:
2025-11

Content

Part of my retrospective of this most recent release is the realization that I am not driving enough clicks/engagement for Itch to appease their algorithm. Which of course controls how visible the project is. A few folks have offered advice on the matter (thank you), and one of the suggestions was to do regular devlogs. The only issue I have there is that progress-related stuff is currently a Patreon/Subscribestar tier reward, so I'd rather not take that away by re-posting all the details over on Itch, which doesn't really leave much of substance.

The other possibility is Itch's "long-form discussions", which would basically be me rambling about TNoM and/or development in general. The image attached is of the categories they provide for that type of post.

Let me hear your thoughts on the matter: whether you like the idea (and any topics you'd be interested in), whether you'd prefer some form of trimmed-down status updates like I do with the Discord announcements, or if you'd like to see some combination of both.

Files

Comments

Chris Blaylock

Given that I bought it on Itch, then paid for the Patreon subscription, I'm fine with Devlogs being up to date on Patreon first. But maybe you could do some kind of monthly summary of stats and projected timelines on Itch to keep everyone else interested? Leave the detailed stuff for us on Patreon and Discord. That way, Itch folks don't just have to wait until there is news of the next version release. There really is something to the adage "out of sight, out of mind". It's why TV shows used to present a season, then immediately rerun it while waiting for the next season release. Something modern companies have forgotten, which is what leads to low ratings and early cancellations.

Knug Lidi

I guess that there is a difference to me, between an in-depth update, and a quick progress update. The former would be Patreon gated, and the latter would be for Itch and/or other 'free' locations. Also, your feelings regarding development, all that listed above, is something I would reserve for Patreon folks. Itch folks are looking primarily for 'how's the update going, and when can I get my hands on it' type posts. Mechanical, boring, and simple. Patreons want the more in-depth and detailed stuff, as that is the value for us.

Silas Frost

I don't know that it fits with any of those categories, but I'd love to see more lore expansion stuff. Maybe things related to the world of Eorþe, or the history. Obviously stuff that you know won't be covered in the game in the future, but you came up with anyway while brainstorming.

Zelnaris

I understand not wanting to diminish the purpose of subbing so maybe leave it paid for a week and then release for free? most people that pay now will still pay for support and to not have to wait.

Hurley

I think I would agree with the consensus that perhaps some form of stripped-down or delayed status update on Itch would be a decent way to keep the Machine Gods fed.

Hurley

I also love that kinda stuff, but I'd say those should probably be done as a Patreon perq more than something to be released on Itch.

RMZ

You could just post them later on itch so it's still a benefit to subscribers

netcov

Just going from what interests me most in looking through the steam store / library and influencing my buying behaviour: 1. If it's a game in progress I love to see roadmaps either for the full game scope or what the yearly goals and milestones are. 2. Q&A / Patch notes elaborating on the thought process of certain decision on narrative / visual / other development choices being made 3. A behind the scenes is always a nice read to see what the process behind the game is like (especially since it can serve as a personal retrospect on your workflow and might highlight blindspots while writing it)