I agree that they should be removed/blacklisted for not using proper map/arch/codebase fields.
I haven't looked into their code, but if in fact they are using a different/incompatible protocol (different format for commands, or different commands), they should also be removed - in that case, they should set up and run their own metaserver. My point is more that if a server states it is running some specific version of the protocol, and is in fact compatible with that version of the protocol, it shouldn't be blacklisted just because of that (otherwise as mentioned, we'd get cases of slightly out of date servers getting blacklisted) OTOH, protocol compatibility is a bit of mess simply because so much stuff is negotiated with the 'setup' commands, so lots of commands were even added to the base crossfire server without the protocol ever changing. So I suppose the real test then is if the official client of the corresponding protocol version can play on the server, it is OK to be listed, if it can't (because of removal of common communication or need for client to support commands it doesn't), then it should not be on the metaserver. _______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
