I am also very skeptical of users voting on features since we did multiplayer based on that. The multiplayer feature won all feature votes by a significant margin, we spent months implementing it, and then saw pretty low usage of it after that. It's also stayed pretty flat and has not grown much. Its usage is nowhere near as much as the votes would have suggested.
Ashley without going too much into it, I would like to tell you why it didn't and still doesn't have a lot of people using it.
Based on the feedback of beginners that are using C2, I read that a lot of people didn't expect it to be this difficult.
I know from your perspective and from people like me with 100+hours into C2, the multiplayer plugins usage is as easy as a walk in the park but from a perspective of a beginner with next to no experience with ACE's and the basics of "netcoding" the plugin is very complex and difficult to understand at first.
(Even with the well written tutorials and examples, thanks for that by the way.)
I think that this is due to the high expectations about the plugin, meaning that people expected something like 1 simple action with dropdown options like "Lag Prediction: On | Off ; Priority: Low | Medium | High" instead of the current method, were a set of actions is required to achieve certain functions.
Of course the most of us here don't know the struggle of making a plugin like this and assume that you could just implement something like 1 action for doing multiple processes at once, which I guess would be a pain in the ass to program.
Yeah, that is basically what I and the majority of people think about the multiplayer plugin, it works fine but it is not that beginner friendly.