This doesn’t do the same thing as the Ban API - this is a list. They are meant to be used in tandem, not in place of the other
All games rely on human moderation - either as the first line of defense or as the quality assurance/support side. There will never be a 100% accurate automatic solution. I think you’re misunderstanding the fact that this resource isn’t an automatic solution nor are the status quo tools provided by Roblox. Yes, it’s a list provided to you, but that doesn’t mean this isn’t just one layer abstracted from human moderation.
That’s not how the Ban API works. Anything automatically handled by the Ban API (syncing bans within the same experience, banning alternate accounts, automatic unbanning, etc.) has nothing to do with what this resource is about. Players | Documentation - Roblox Creator Hub
Ban API is designed to prevent usage of the alt accounts (or at least make it more difficult) also most of the experiences do not rely on human moderation and try to automate everything as much as possible because automating is better and more reliable than the humans the humans can be biased towards certain situations and scripts can’t because they have no feelings making it far more reliable
Also the bigger the experience gets, the harder it becomes for humans to moderate it (which also proves that automating the moderation is not only more reliable its also more productive regardless of the size)
There legit no reason to why this should be used when ban API exists because ban API already automatically blocks alt accounts sure it can be bypassed but it’s more reliable than banning people based on random list created by bunch of humans
with all this being said i wish good luck and i appreciate the contribution
The ban api does not work against alt accounts. numerous complaints in the thread and I have sent well over 50 examples to the security team. That part of it is completely broken unfortunately. It has, at best, a 15% detection rate from my testing with a friend who wasn’t even trying to bypass it. Simply logging out and logging in to another account is enough to get around it.
like all previous attempts to make a “ban list”, all of them fails. no one with significance backs these projects or even has the resources to attempt such thing on a platform with 88.9 daily active users
// Example data table (array of objects)
const dataTable = ["2690751130", ""];
also, please use an actual database like SQL if you’re going to make projects involving databases, using plain jsons will absolutely not scale and will cause performance issues, i’ve made that same mistake before, i regret it.
yeah, this is risky. I dont think i can trust some random dude to send be a list of exploiters to ban, esspecially since it could be compromised and ban a ton of innocent people.
can i see the devforum post?
Also im the only one managing this, so the chance of the token getting leaked is only slighly less that if i worked in an group
Banlist has 1 person, maybe at least build a database of exploiters before releasing. 1 person feels more like witch-hunting/a personal vendetta over anything else
