Every bug is reproducible. There are no magic things happening. It is acceptible as a bug report when you can say what changes a working case into a case that bans. If there are specific actions that lead to a ban on an install which does not otherwise give a ban, then those steps are the first thing needed. Again, the same steps work to ban always or it is not those steps that is the cause. In another case, if you can find a pk3 file that makes you get banned. There are some cheats that proxy system dll files and can be inside a pk3 file in the working directory. Server specific proxy dlls (private anti-cheat programs (or other)) are not known to cause bans when connecting to a server without them. That is because the mod is reloaded every time server or map changes. The binary that is referenced by the server is used as long as the server has the sv_pure 1 setting enabled. I'm intentionally using term "not known to". So far it has not happened on testing and such a thing has not been reported. But I can't give guarantee as I have not investigated the mod loading techniques in the engine to that level. Also, self made ET client could behave differently. In any case, it would still be reproducible. Everything works in a rational way and all bugs are reproducible. It is just a matter to analyze what is different and isolate the thing that is causing the ban. We can't do it on behalf of anyone. It is always good to remember that blaming a bug without actually providing any evidence for that is just an attempt to socially engineer the ban. You can compare such case to a rage botter calling admins noob when they ban him.