[stupok]

I think we can change the topic of discussion now.

It's clear that the problem is not the steamid replacer plugin.

The problem is that SteamBans relies on a changeable steamid. The plugin exacerbates the problem.

What are the developers of SteamBans going to do about it? Since they're censoring this plugin, they must not be ready to deal with the problem. They could accept reports only from trusted servers. They could maintain a database of who played what, when, and with whom. Contradictions in the database would indicate a changed steamid. They could keep track of the IPs (and countries) that each steamid uses, perhaps even previous names. All of these things would help to increase the likelihood that a steamid report is authentic. It also requires a lot of resources.

So, fine, censor the plugin. Surely it will make the problem smaller right now, but it doesn't save your project from failure in the long term. However, don't censor the knowledge. Users should understand the reliability of your reports.