A unique ID feature has been in a long standing debate amongst the team for a while now. We still haven't decided on which way to implement it.
Our biggest concern is the how the serial is generated, and the possibility of it being breached.

A few options we've considered:

1. Authentication server that provides a token when connecting. Works like this: client provides a public key to game server. Game server contacts the authentication server. Authentication server validates the key and provides a unique token back to the game server to identify the client.

2. Kernel driver to enforce memory protection like MTA SA uses. This is probably the most secure. However, antiviruses don't usually take kindly to this approach. It also requires a code signing cert, which is expensive.

3. Simple UID generated from PC hardware info. Since the generation of this UID is done client-side, a hacker could reverse-engineer it and find how it's generated. This is how LU's (LUID) was breached. We could update how it's done but every time we do, all previous UID's that a server stored for bans are invalid.

4. Master account system. Sort of like Minecraft. Optional for servers in config. Not very effective since GTAC isn't a paid service so making more free accounts is an easy bypass.