Firstly, when I stumbled upon the plugin, the lack of information provided in the description was disconcerting. The plugin was initially posted with no details whatsoever and explicitly mentioned that it wasn't ready for use on production servers. This begs the question: Why was the plugin made public in the first place? It seems counterintuitive to release a plugin without sufficient information or a clear indication of its usability.

Adding to the disappointment, the plugin description includes a rather off-putting statement: "No, I don't need your ideas." This outright refusal to accept feedback from the community raises concerns about the author's receptiveness to improvement and collaboration. A successful plugin is often the result of a cooperative effort with the user base, and an author's unwillingness to consider suggestions can hinder the overall development and usefulness of the plugin.

Moreover, delving into the plugin's code by decompiling it revealed some troubling coding practices. While it's acknowledged that the author may be a beginner, the quality of the code is crucial for the stability and security of any plugin. The evident lack of sound coding practices makes Vital Control a risky choice for running on your server. It's essential to prioritize plugins that are well-crafted and follow industry standards to avoid potential issues and conflicts with other server functionalities.

In conclusion, my experience with the Vital Control plugin has been less than satisfactory. From the lack of information and the author's dismissive attitude towards feedback to the subpar coding practices, it's evident that this plugin may not be suitable for use on a production server. I strongly recommend exercising caution and considering alternative options that prioritize transparency, user collaboration, and high-quality coding standards.

No description, no images, no link for github. Release it first and then post it. Wierd modern developers.