Quote from: NewK on Feb 19, 2019, 01:00 PMQuote from: dracc on Feb 19, 2019, 06:36 AMI doubt it could be worse if it's already an ongoing issue even when the source code is NOT freely available?Regardless of being an ongoing issue or not, it would still make it worse as cheaters would take of advantage of vcmp internals to make better cheats. Also I think you're overestimating the amount of willing and knowledgeable people available that could contribute in a positive manner. Something stormeus also mentioned:
Also, more eyes on the code means more brains to find fixes for exploits.Quote from: Stormeus on Jun 02, 2018, 06:11 AMthe few community members I figured were knowledgeable enough in C++ and good ambassadors of the community don't seem to be active anymore eitherThis was proven when VCMP devs made the code for VCMP 0.1 available. It's been public for years now, and all that's happened in the meantime was that 1 or 2 people made clones of it to create their own version of VCMP but then quickly abandoned it once they faced issues.
Okay, I think we understand the staff's position about this issue, but the still don't give a reasonable solution to the problem. We have been stuck for years without doing anything.
The viable solution is to recruitment people as a developer, but it isn't done either. Then... Is developing for a half-dead project the best solution?