I'm not talking graphical frames, to do hit detection you need to render a "3d map of the world" or, calculate it, so you can know about bullet velocity and impact range and stuff like this.

A good example of this is public/private key cryptography, for you to generate a private key, is easy, but for me to derive the private key you used is difficult, expensive, (in the case of my example it's actually impossible currently). But verifying that you used a private key with a public key is actually incredibly cheap by comparison. (this is probably a bad analogy if you understand the outside information of cryptography but not applied mathematics or algorithms).

Generating a "world" where the server tells your game "the state of the world" and your client cannot "think" for itself would tie the world to being generated by the server, a server frame is generated about once every 100ms, so.. 10FPS, this is because the server has to render the entire universe each frame in order to do the detection of multiple elements.

it's /currently/ 10FPS, even with all the heavy optimisation which is causing development to slow down, now imagine it has to render every single 3d element in the world, manhattan, for 1,000 people, NPCs, objects which are destructed.

You can't say "put it all in the server", because there is a line, the line was drawn in a place where we chose speed of the client over security of the gameserver, which was a mistake for PC players, evidently, but that's how you get sweet 60FPS with little/no server lag.

The initial plan was to have a heavy handed ban policy, but this wasn't communicated with HQ's lawyers who have put a stop to it. We're trying to figure it out, but this was our "political solution to a technical problem"