Spring RTS Engine

AFAIK, nobody can rely on those things. well, my thoughts here are multiple-layers of security, as with any system, only one method cannot be trusted, but a series of methods are always better than just one, as if we just check files, packets can still be modified, etc. as for the PGP-encoded netco...

Here's my thoughts on this issue, since spring IS an open source game, a client-server-master model won't work, however a client server model would work great. maybe have an ability to import an XML blacklist of cheaters or someting for a "master" but no official master because this IS ope...