Solve our load problem
silasary opened this issue · comments
Apparently this bot got really popular over the weekend. Not sure why.
But it's being used in what appears to be farming servers (autocatchers + spambots), and the load of 10+ spawns per second is not good.
We need to think about scaling, I guess.
- Make image recognition non-blocking
- Leave servers that are explicitly for cheating (how?)
- Think about upgrading the hardware
- Rate Limiting
according to me solution would be:-
-
make the guessed pokemon name in image format (may apply some cosmetics like different backgrounds)
[leading it to be used fairly and making it hard to code cheats like :- p!catch oakreply] -
make a requirement for the bot for example atleast 100members required.
[i think not that helpful because people will create a private channel in their public servers] -
make a ban system in oak bot that are being used for cheating to trace we can have a threshold amount and a logging temp txt file. (whichever guild is banned,there oak wont work or it will auto-leave.)
[poketwo used this method to stop cheating by p!hint ] -
leave servers that are exploiting, hmm:-
i got a idea for this but it can be adjusted what you feel :-
(this is a theory actually.)
you may check the interval of the msg of the alts (might be wrong if applied everytime ; apply on special conditions)
⭐ let the bot check for small servers or a private channel (who have access to it) and check their account creation date.
it would not only decrease a huge amount of new alts being created daily but also stop new autos
create a temp data of how many pokes are being caught by a person daily and make some algorithms based on common ways to exploit. (this will reduce the time the auto is being used by exploiters)
🌟 a improvement to the above idea:- we can't let everyone's caught data be stored and it will create a bunch of bundle.
poketwo has messages like:-
@user! You caught a level 7 Rattata! This is your 100th Rattata! You received 3,500 Pokécoins.
we can deploy something based on this msg and much better idea than mentioned above.
you may pick any that is comfortable for you.
i gave my suggestions and my ways, if you find any methods helpful ; let me know i would be glad that i was able to help you!
i am on discord, feel free to drop a dm on HOPE_NEXUS #4668
To solve your load issue you might consider imposing a rate limit (guild ID or user ID)
To solve your load issue you might consider imposing a rate limit (guild ID or user ID)
People Associated with Autocatchers/cheating are pretty sick,
they will create like 5accounts for a server and find quick solutions for things that are easy to exploit (example:- couldn't make a.i , so made hint catcher).
RateLimits will also affect Big guilds , in which Oak bot is present (ruining the fun of honest ppl.).
Upto the developers ^_^ how they decide to structure the bot. (ik they will look into it.)