Testing before pushing updates

[finite field]

Here's a suggestion.

How about you TEST an update before pushing it?
Every other app company does it. It's standard part of the procedure. You know - so you don't break half the stuff in an already buggy game.

[muted quail]

Theirs testing but a test server and a live server are two diffrent types of things.

both have diffrent factors.

[stark stag]

They have a QA team that tests it and a KCP team (content creators) that test it again on a beta. This bug did not happen on the beta.

[upbeat pagoda]

We always have bug after an update, why not do a kind of "live beta" server ? (with more beta tester) . It can avoid this kind of problem.

[crude owl]

Because they don't want the content revealed early

Like we have to sign a NDA to get access to the kcp beta

Maybe they could invite people who are willing to sign it though in? expand the pool

[muted quail]

Where do i sign XD

[upbeat pagoda]

I don't know how to explain that in english, but Shakes and Fidget have done the same kind of thing, but they have a limited number of place on their server to test new updates(with registration). They can do the same. (with NDA of course), they can avoid some of annoying bugs like that ^^

[stark stag]

Yea but even then it can still break when the patch goes live

So yes, we would find maybe more bugs on the beta server if we had more people but the bug that don't exist on beta might still happen on live

[upbeat pagoda]

If beta server acting like live server ? Should it resolve some issues?

[stark stag]

It might, we have had that one time iirc

[crude owl]

They did that once
I ended up locked out of my account for a weekend 😛

[stark stag]

Oh yea that also happend, forgot about that haha

[crude owl]

Their system did not like it