We are thinking of having an "early access" build that is publicly updated once a week (once we get something worth playing). And then tweaking / adding to / removing what the community thinks is fun.

Or would you guys rather wait for more finalized builds to go into the wild?

How about public sign up for early access. If you rather wait, wait. If you complain about bugs instead of being productive, your off the list, or on the list of not beta approved. So it will be semi private as in you will control who you agree to have it, but limited control since it could be redistributed potentially.

How about public sign up for early access. If you rather wait, wait. If you complain about bugs instead of being productive, your off the list, or on the list of not beta approved. So it will be semi private as in you will control who you agree to have it, but limited control since it could be redistributed potentially.

sounds good to me, incentive to behave

How about public sign up for early access. If you rather wait, wait. If you complain about bugs instead of being productive, your off the list, or on the list of not beta approved. So it will be semi private as in you will control who you agree to have it, but limited control since it could be redistributed potentially.

So your saying they should do something other than report bugs? Isn't that kind of the point of beta testing, to complain about bugs/issues that you find? Would you rather they lie and tell you that the map is perfect and has nothing wrong with it, only for non beta testers to complain on release?

So your saying they should do something other than report bugs? Isn't that kind of the point of beta testing, to complain about bugs/issues that you find? Would you rather they lie and tell you that the map is perfect and has nothing wrong with it, only for non beta testers to complain on release?

Complaining about bugs is not just the point of beta testing, it's the point of life am I right Deadra?

So your saying they should do something other than report bugs? Isn't that kind of the point of beta testing, to complain about bugs/issues that you find? Would you rather they lie and tell you that the map is perfect and has nothing wrong with it, only for non beta testers to complain on release?

I guess you misunderstood what I meant by "complain about bugs instead of being productive". Being productive would include bug reporting, and giving your opinion. Complaining would include making negative comments that added nothing constructive, or to just start drama for no reason. Kind of like your comment, pointless.

Kind of like your comment, pointless.

*Sniff* You smell that? I smell burned DD

*Sniff* You smell that? I smell burned DD

Really? I smell wiffy banta...

So your saying they should do something other than report bugs? Isn't that kind of the point of beta testing, to complain about bugs/issues that you find? Would you rather they lie and tell you that the map is perfect and has nothing wrong with it, only for non beta testers to complain on release?

difference between being constructive, finding, identifying and checking bugs, reporting them properly

To the majority of people, they just complain and whine, giving no specific explination as to what happened or even remotely aware of what was happening at the time - Just look at leviathan, 100 odd people going G SPAWN FIX THE MAP!!! - Nearly none explained ANY further than that

Next look at requiem, do you know just how many people complained over that? And for the most part its infact, VERY good? AND IT WAS A "BETA" - something people struggle with the concept of

Project viking, people were reporting bugs that were frickin features

Other people just wanna complain about gun stats, DESPITE the fact we LITERALLY copied the BO2 files in most of these cases, therefore are identical

Stuff like that is just annoying and makes us not even wanna look at fixing these bugs, as we might as well just test, make, play everything ourselves in that case

difference between being constructive, finding, identifying and checking bugs, reporting them properly

To the majority of people, they just complain and whine, giving no specific explination as to what happened or even remotely aware of what was happening at the time - Just look at leviathan, 100 odd people going G SPAWN FIX THE MAP!!! - Nearly none explained ANY further than that

Next look at requiem, do you know just how many people complained over that? And for the most part its infact, VERY good? AND IT WAS A "BETA" - something people struggle with the concept of

Project viking, people were reporting bugs that were frickin features

Other people just wanna complain about gun stats, DESPITE the fact we LITERALLY copied the BO2 files in most of these cases, therefore are identical

Stuff like that is just annoying and makes us not even wanna look at fixing these bugs, as we might as well just test, make, play everything ourselves in that case

Which is why you probably shouldn't give betas to people who know little about how the game works, or split the beta between the first 'closed' and the second 'open' phases to iron out the worst issues like G Spawn errors beforehand.

In the case of leviathan though, i feel like the amount of people complaining is completely justified since I personally suggested that they get better testers in their WIP topic to begin with - which they ignored - and probably wouldn't have as many people complaining about bugs in the first place. Not saying it'd be perfect, just a little better. 

yea right... coz everyone just telepathically "knows" if someone is gonna be good at it or not...

yea right... coz everyone just telepathically "knows" if someone is gonna be good at it or not...

Deductive reasoning.

Has person X participated in any betas recently?
Has person X reported any bugs while participating in a beta?
Has person X created a custom map before?
Has person X created a custom map that works?

etc.

Before we get anymore hostile let's just press the restart button

Deductive reasoning.

Has person X participated in any betas recently?
Has person X reported any bugs while participating in a beta?
Has person X created a custom map before?
Has person X created a custom map that works?

etc.

So after maybe 2 years, I still don't know what makes a map good? Nice to know.

Before we get anymore hostile let's just press the restart button

Agreed.

Anyway, whatever you and that sexy beast known as SparkyMcSparks plan on doing for the beta, i definitely want in. 

Before we get anymore hostile let's just press the restart button

was never hostile, just pointing out the silly side of that argument

Has person X participated in any betas recently? - people can easily lie, or would you expect em to reel off a list of proof with time stamps, or mayhaps a list of references we could contact via the post? Maybe we should also contact the mapper in question and do a personality check on the individual, and check he didnt leave part way or waste anyones time eh

Has person X reported any bugs while participating in a beta? - people can easily lie - or again shall we have them show us somebody elses private beta info to prove it?

Has person X created a custom map before? - you dont NEED to be a mapper to test a map

Has person X created a custom map that works? - again - not interviewing, not applying to help create it in anyway, they are supposed to be regular players out to see what bugs they encounter, not diagnose all the causes and bug fix it themselves

...

By those standards, the only people who qualify, are the best of the best who are "already" busy with their own works that need beta testing...

Agree to disagree i think