Skip to main content

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

Is it possible to remove a build from a channel's history?

A topic by mid created Apr 04, 2020 Views: 1,968 Replies: 6
Viewing posts 1 to 3
(+1)

Or must I delete the channel and upload again, losing all builds?

(+1)

It’s not possible to yank a build at the moment. Although, I can see the use case for that and I’ll try to think of a way to make it happen.

In the short term though, nope, sorry.

Okay, thanks for answering.

+1 desire for this feature & subscribed, my team would like to be able to simplify the list of past-version choices for our users, and remove broken versions from being possible to attempt to download (even though no user should be digging around in past versions anyhow)

(+1)

This feature is extremely necessary. There should be a butler unpush or similar, as well as a simple delete button in the web UI. The lack of this feature makes me uneasy to start using butler at all. Not even pushing the same --userversion works to replace it - it makes a new one. This isn’t right - even in git you can force push and move/delete tags if you make a mistake.

Currently there’s no way to fix it if someone makes a grave mistake, right? E.g. push a version that accidentally leaks some sensitive info (like server keys, passwords, emails, real names, etc.), or a full version of a game where it was supposed to be just a demo, etc.

My teacher once said “You’re making software, but you’re dealing with humans. They should be allowed to make mistakes, don’t you think? Undoability is extremely important.”.

(+3)

@Amos, is there any progress on this issue? I'm not speaking on previous version builds in a channel. It looks like it makes every previous build available for a channel's version available for installation, at least from the Itch.io desktop app. I can't think of a use case where someone would want to have them available, as they, at least in my case, are mistake builds (eg "oops, forgot to add a text file", etc.).

Does any non itch.io developer actually want to see previously uploaded builds for a version?

Yank logistical problems aside, perhaps just only show the most recent build under each version.

(1 edit)

It’s precisely because devs can make mistakes that players (specially the ones that pay) should be able to access previous versions. Devs can and do often break something even when trying to fix something else.

However devs should be able to delete versions too, because some serious mistakes (e.g. leaking info) require actually unpublishing.

I will agree that at least when pushing the exact same –userversion number (instead of incrementing it) it should warn, and let you “force” to replace the previous one, thus unpublishing it. This way, devs will naturally tell when they meant to keep a version or drop it.