Is it advisable to transfer from a public to a private beta when a project nears completion?

As the title states, I have read in these forums that many regard it as common practice to switch to a private beta in the later stages of their work.

What do other people think is the best thing to do? What are the benefits of going over to a private beta in the later stages of development?

Would this means taking a demo off of Dashingdon and arranging another way to access it?

Thanks to anyone taking the time to share their high wisdom stats!

1 Like

It varies depending on the author.

The benefit of a private beta for me was to be able to actually get structured feedback and to preserve the secrecy so less would leak and spoil people for the release. But much of the game was open for everyone, it was just the final stage that I kept private.

I still kept the private beta on Dashingdon and just shared the link on a private discord; some are worried about security and do not. I am sadly aware that if people want the forbidden tasty content they will find it no matter what I do.


As an author a closed beta is beneficial because you can get better access to quality feedback and build anticipation for the release by denying the public the sweet orcy goodness

1 Like

I actually do the opposite.

I extensively test in private the alpha and pre-production copy, get the detailed and in depth feedback, and make all the necessary changes to get to a completed copy.

Then I will be placing the completed copy for the public beta required for Hosted Games, letting the community provide feedback they feel will help improve that final copy before publication.

I know authors that keep everything private with an open invite system and I know authors that keep it open from the beginning to end.

Like @malinryden above, I feel it depends on the author, but I also feel it depends on the project as well.

The work I am writing for the Halloween jam this month I hope to have up in the test thread before the deadline for all who wish to read it if they desire.


@malinryden @Basketball_Fanatic

Reading your posts and the suggested topics the forum gave me, it seems to be near a consensus that authors maintain a public beta for up to 3/4 of their game but keep the final quarter locked up for private testing.

I imagine it is important to find willing, passionate, trusted testers too, for a private beta.

Apart from dashingdon, do people use Google Drive and things like it? I have always tried to avoid the cloud since I am a semi-luddite who feels secure with the tangibility of things.

It sounds like a good idea to hold something back from public testing, following the practice of authors more experienced than I am. At least some orcs relish a visage of mystery, particularly the shamans,

I think I am approaching that time, though there will be a good few more months of development left (not counting all the final bug-checking and proofreading).

Thanks for the advice.

Hi Eiwyn,

Interesting opinion! Kind of made nonsense of my previous reply:)

However, you would still recommend that part of the beta should still be private, rather than public from start to finish?

1 Like

I would personally think it also depends on how much one gets feedback overall - if there’s lack of testers when the project is fully public, is it really even possible to get enough for a private one? On the other hand, if there’s way too many feedback when it’s public, a private one is probably way more manageable.


You can make a Dashingdon link private and just share it with the tester group if you like, though it’s not fully secure if someone shares it outside the group. Moody has more robust private settings but seems less stable unfortunately; you can also compile a ChoiceScript game and put it on as a private or password-protected game.

My experience is CoG-specific where the way it’s usually done is to have a private beta once the full draft is complete. When putting up my WIPs in public I’ve generally had more detailed feedback at the beginning, and then in the private beta test there is an uptick in that sort of feedback again as people have the bigger picture/perspective having played the whole thing.

I know authors have had good experiences with both fully public and partially-private playtesting. There was some very interesting discussion in this threadv which gave me a lot of things to think about:


There are successful authors that go public from start to finish. @Havenstone 's successful and popular Choice of Rebels is the most known, but @JimD has brought both of his Zombie Exodus stories to the public as well, releasing the parts he writes for them as he writes them.

@Lucid on the other hand has a full private beta with an open invite … and does not open a beta until his game is fully written.

In my case, i started with private testing because of my imposter syndrome and my shyness regarding my writing. I also had testers built up, something you, or others may not have access to.

As my writing improved and I started getting braver and less vulnerable to my imposter feelings, I have opened my game up to more people, arriving to a point where, after this last testing round I will be making a WiP thread in the form that both JimD and Havestone do theirs.

One of the practices I engage in to help overcome my imposter feelings is to share an excerpt of my writing every 15th of the month in the Writer’s Support Thread.

Perhaps that would help if you suffer shyness or imposter feelings as well.


This is just proof of how all over the place that thread ended up getting lol. Reading the description in the referenced part, you’d never know that we discussed pros and cons of public vs private betas. It makes sense once you read through it, obviously, but it looks so out of left field out of context. :rofl:


Oh that’s true! :sweat_smile: I remembered it having a lot of good commentary in it so definitely worth a look though!



Good point. I would say my project seems quite niche and may not have enough testers willing to invest a large amount of time in private testing. What would you say is an optimal amount of private testers- roughly?


Excellent thread! Also, you’ve eased my mind with worrying about privacy, since it is available on dashingdon and From what I have learned, there is no wrong way to do it, in regards to the public-private split. I think I’ll eventually find what works best, once I’ve got the growing pains out of the way.


Thanks for the advice and the excellent examples of other’s work. My project has been fully public since I first uploaded it so I am not shy in that regard. I’ve gone through the typical dozens of rejections for one tiny acceptance letter a good dozen times to wear my imposter suit over my imposter shirt proudly :smiley:

Although I have often browsed those writer’s threads here and the community is fantastic!

Cheers to all of you for your great advice.


I’ll say this: there is no right or wrong way to do it, but their usefulness might vary. You can read for yourself, but in the referenced thread, it seemed to me that many more people were in favor of public testing all the way, or most of the way. The general consensus seemed to be that you got significantly more feedback throughout the entire process, which was something a lot of people valued highly.

Idk. I think most people would agree that a handful of experienced testers would probably be better, but the Avengers aren’t always available. :person_shrugging:

1 Like

No idea, never done either. But from a theoretical perspective - enough that someone is playing through all the major branches (and the more playing through minor ones, the better!) to catch the bugs and continuity issues and such.

…now I got the most hilarious picture in my head. Thanks for that.


Building up a pool of testers is a continuous and taxing endeavor. On average, I lose 10-20% of my testers each round I go through.

Sometimes people do not ever reply back, and other times they only read part of the game and/or give feedback on part of it.

It is one reason I provide feedback guidance with every test and why I ask and canvass for future testers every single day.

It is hard and often discouraging finding the needed testers, but when I do, I treasure them all the more.


I think that if, as Eiwyn said, you have a solid amount of testers built up over time, then a final focused push through a private beta could be very rewarding.

But yes, since public betas do attract a variety of players, some of whom grow to enjoy the work, then it can be inherently more valuable to shape a game and world with their feedback. Also, the exposure to all those ideas can be an amazing thing.

Ha, I thought I decided what I was going to do but am swaying back and forth.

1 Like

It’s entirely up to you. Maybe you could do a middle ground. Keep it public for the first half, then hand pick the most helpful testers and give them the full game privately. :person_shrugging:

1 Like

At least now I am confused but informed! :pray:


It’s an interesting feeling, isn’t it? You feel like you’ve learned so much, but you’re just as confused, if not moreso than you were before. :rofl:

1 Like

Haha! I think it is the default.

Sometimes this feeling settles into a plan of action after a good night’s sleep.

1 Like