Skip to main content

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

Updated Bundle does not allow existing users to access updated content.

A topic by RefresherTowel created Feb 01, 2026 Views: 397 Replies: 5
Viewing posts 1 to 3

I have updated a bundle I have made to include new items. However, I've received a message from someone who purchased the bundle a while ago saying that they can't access the new content (it's acting as though they don't own it, when they should, since they own the bundle and the new content is now included in the bundle) and furthermore, it's also acting as though they don't own the bundle anymore (when they got to the bundle page, it shows the "Buy all" button instead of the "access content" button or whatever). Is this how bundles are supposed to act? That seems less than ideal if so. How can I give existing users new content if this is the case? I'm kinda worried that I'm going to have to send out new keys to every individual existing buyer whenever I update the bundle to add more content...

(+2)

Another creator tested this here and unfortunately this just seems to be how Itch handles bundles. I've also experienced this when buying bundles, new/future items just are not included if the creator adds more to the bundle.

Well, that's really annoying, lol. A lot more work for me =(

(+1)

Are there game stores that do such? Selling a bunch of items and give ability to change the content of that bundle of items at a later date?

One does not need an account to buy on Itch, so they have to create an entity that holds the purchased items together. On Steam if you get a "bundle", you just attach the items to the account, no matter where they came from. There is not even a possibility to change the "bundle". There exists none.

You treat a bundle like a project page, so using a project page would be the way to do what you want. I am not sure though, if you can transform the bundle content and projects in a way to 100% reflect what you intend to do. On the one hand, you seem to want to give access to new content for previous buyers. On the other hand, if you transform one of the projects into a get-all-items-for-a-discount project, you would give access to all the other items to people that only bought that item. But it might be the easiest way. And it would ensure that future updates to the "bundle" would reach previous buyers.

What I do not get, why they even allow to recycle a bundle, including the name of the bundle, without big bold letters to the developer that this will not change what previous buyers bought. And it does get confusing. The buyer will see the old bundle in the purchased section in the library. With links to the purchased items. But it will also have a link Visit bundle page which will point to the current bundle that will have different items.

But if you think about it, if you were able to change the bundle and add items, you could also remove items and thus access after the purchase.

(+2)

Yeah, it makes sense, but I really think itch should outline it more clearly. Having "future pass" sales definitely isn't a very rare thing, and bundles just seem like the natural way to do it ("I can just update the bundle sale as I add more items"). Having to utilise project pages feels more hacky, even though apparently that's the intended user flow for that kind of use case, lol.

(+2)

Yes, absolutely. They need to show this at several places, including the buttons you need to click when changing a bundle.

This topic has been auto-archived and can no longer be posted in because there haven't been any posts in a while.