You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
As sniping is really dependent on friends and neighbors lists, would it be possible to add a scan method that would check for players in the guilds ranking menu ?
The idea behind that would be to identify which players could become good sources of profit to later add them in our friendlist. The bot would :
Pick a guild
For each player : scan GBs and if profits (thresholds - % or x FPs - already existing could be used) are possible, makes a sum of the different possible investments
Return in the Snipe Log : players name, guild name (not necessarily though) and the calculated sum
The guilds 'to be checked' could use a parameter like a whitelist as it already exists for players and GBs or even better, a parameter that would allow a scan for guilds ranked between x and y. The second method could send a lot of requests but the good thing with guild scanning is that it could be made with any account that is on the same server, highly reducing the risk of getting banned on the main account.
The text was updated successfully, but these errors were encountered:
Hi,
As sniping is really dependent on friends and neighbors lists, would it be possible to add a scan method that would check for players in the guilds ranking menu ?
The idea behind that would be to identify which players could become good sources of profit to later add them in our friendlist. The bot would :
The guilds 'to be checked' could use a parameter like a whitelist as it already exists for players and GBs or even better, a parameter that would allow a scan for guilds ranked between x and y. The second method could send a lot of requests but the good thing with guild scanning is that it could be made with any account that is on the same server, highly reducing the risk of getting banned on the main account.
The text was updated successfully, but these errors were encountered: