Skip to main content

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

Can I have a beta (Restricted) project and production (Public) project of my game?

A topic by blastoboom created Jun 29, 2023 Views: 387 Replies: 4
Viewing posts 1 to 3
(1 edit)

So the idea here is two Itch.io projects for a single game.

Production/Public: This is where players would go to play/buy my game. It would be the most stable game version and be publicly accessible.

Beta/Restricted: This is where I'd release new versions of my game first and have it restricted to a beta set of invited players only. The beta players can test the game version to find issues and provide feedback. It would be free. 

Once the game version seems stable in the beta/restricted project, I would then upload it to the production/public project.

It's unclear to me if the above violates the Content creator quality guidelines.

Avoid uploading ‘reskins’, or many project pages for minor changes
Do not create multiple project pages for projects that are essentially the same but with minor adjustments. If the code or asset changes are substantial it’s okay. Additionally, if you're trying to preserve different versions of the project, eg. jam versus final, it’s okay.

While having different project pages for different versions of a game is irritating in some cases, this quality guideline does not apply imo.  And if you double read it, it actually states different versions of a project. 

I often see demo and full version as different projects. Given the rudimentary mechanics provided by itch, this is almost necessary in some cases.

While you can set your price to pay what you want     and make the stable full release  threshold x amount, you might not want to give out the testing version to everyone. Or more importantly, deal with the comments about all the bugs in the stable branch. But you could also set up comment system and make a sticky  with bugs.

The more important thing for me as a player would be, why not just have public beta testing. Unless you provide a demo version or this is a web game, there are freeloaders that will never buy your game,  but might point out bugs. Or other people that might buy your game, but shy away, because they could not play a demo of it.

(1 edit)

So I definitely want a demo which is always free and always publicly accessible. I might need to do an open beta initially but once the paid game is released, I don't want any one to be able to play the beta version (which is free) as it would be the full game essentially.

Thank you for your feedback!

Moderator(+1)

Beta/Restricted: This is where I’d release new versions of my game first and have it restricted to a beta set of invited players only. The beta players can test the game version to find issues and provide feedback. It would be free.

My understanding is that the rule is mostly to avoid people flooding the search with copies of the same project. Your case seems to be that one project will be public, and one will be private.

I don’t think that will be an issue.

Thanks!

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