# \[Known Issue\] Bans for Everyone? **URL:** \ **Category:** Bug Reports\ **Created:** [December 23, 2022, 10:27pm UTC](https://community.gemsofwar.com/t/known-issue-bans-for-everyone/78221 "2022-12-23T22:27:38Z")\ **Posts on this page:** 1\ **Showing post:** 172
**Author:** ![Stratelier](https://avatars.discourse-cdn.com/v4/letter/s/977dab/32.png) [@Stratelier](https://community.gemsofwar.com/u/Stratelier)\ **Post date:** [December 26, 2022, 6:42pm UTC](https://community.gemsofwar.com/t/known-issue-bans-for-everyone/78221/172 "2022-12-26T18:42:04Z")
I am still curious for the technical explanation of what happened … or rather how a problem [this obvious and this severe](https://www.youtube.com/watch?v=GzhKG23pl-0) made it through alpha/beta. I can think of only a few plausibilities: - Clientside vs. server updates are likely distinct development branches, and not all dependencies were properly tested during alpha? (which still sucks, but let’s keep the speculation simple) - Maybe the beta servers (if they are distinct from the live/release servers) didn’t have automatic hack-detecting bans enabled (because beta is limited to a smaller pool of to-certain-degree “trusted” users), thus making it legitimately impossible to discover during beta? This would still be poor design because the whole point of beta is to mirror the release environment in _every_ detail possible (other than sheer scale). - Since there seems to be a latency between the suspected cause (using Kris Krinkle in battle) and the actual bans, depending on the length of the beta period maybe the bans did occur but _not_ in enough time to get reported before release? --- _[View the full topic](https://community.gemsofwar.com/t/known-issue-bans-for-everyone/78221)._