I think you can better add a localhost bypass automaticly.
So after the antiproxy.bypass check add && event.getAddress().getHostAddress() != "127.0.0.1"
If I am not mistaken, it allows people to connect before the proxy check. This enabled joinbots to swarm without being stopped. I switched from another one that DOES stop them, but causes lag.
Many of my players gets "Took to long to login" now when this plugin is installed.
You might wanna change the way this plugin works so players don't have to wait until the website respond/ don't respond.
The plugin should give the option to add your botscout api key, as 20 queries per day is hardly enough. Also, you should write known trusted ips to file and then cache that file so that the plugin doesn't waste time looking up an ip that is known to not be a proxy.
Like I understand "It connects with an online database and checks if the player is using a proxy." it means that each time a user connects the plugin connects to an online database to check. I'm right?
If so I think it can't be much efficient to connect each time to an online database. Wouldn't it better to connect to that online database the first time the plugin is used and download that database data to a local file/mysql db?.
Adding this a feature to check every X time (X = time set by a config file) and sync the local database with online it would be, in my opinion, better than connecting each time online.
The "antiproxy.bypass" permission doesnt seem to be working for me, any chance you could help me? :3
@luca2121998
Since people still comment here I'd guess it still works...
Hi is this plugin still working with 1.7.2 ?
@remcov1
you can enable to see peoples ip in bungee configs
@schtooping
when you will this for your bungee you search a bungee plugin this plugin check players with bukkit and everyone has the same ip in bungee
the ip from your bungee
Does anyone use this with a bungee hub server? any pitfalls?
@wumpyc
It's still working :)
Still working? Source code?
I think you can better add a localhost bypass automaticly. So after the antiproxy.bypass check add && event.getAddress().getHostAddress() != "127.0.0.1"
@carlgo11
That isn't true, check out the comment under this comment
@IndigoParadox
That's true, but that's only when you have a laggy server :(. I did this to prevent lagg.
If I am not mistaken, it allows people to connect before the proxy check. This enabled joinbots to swarm without being stopped. I switched from another one that DOES stop them, but causes lag.
Many of my players gets "Took to long to login" now when this plugin is installed. You might wanna change the way this plugin works so players don't have to wait until the website respond/ don't respond.
could you upload this on github?
The plugin should give the option to add your botscout api key, as 20 queries per day is hardly enough. Also, you should write known trusted ips to file and then cache that file so that the plugin doesn't waste time looking up an ip that is known to not be a proxy.
@NemesisMate
Nope, it doesn't lagg your server ;) Trust me.
@Click_Me
It is done on a separate thread?, does it would make some kind of lag if the site that answer is not fast enough or is not reachable?
@NemesisMate
Oh, the plugin sends the ip to a site and the site answers of the player uses a proxy. :)
Like I understand "It connects with an online database and checks if the player is using a proxy." it means that each time a user connects the plugin connects to an online database to check. I'm right?
If so I think it can't be much efficient to connect each time to an online database. Wouldn't it better to connect to that online database the first time the plugin is used and download that database data to a local file/mysql db?.
Adding this a feature to check every X time (X = time set by a config file) and sync the local database with online it would be, in my opinion, better than connecting each time online.
@keptlv
It doesn't block all the proxies, that's impossible :) So try with a different one, or are there any errors?