Is a system like this allowed? and If so, is it even feasible?

Help and Feedback Scripting Support
1

I made a Ban system and thought of an idea for detecting if a player is utilizing an alt account, the tldr of how it works is the following:

local scorevalues={
    ScreenSize = 25, --resolution
    Sensitivity = 25, --mouse sensitivity level
    Volume = 25, --volume level
    Quality = 10, --graphics quality level
    FullScreen = 5, --boolean
    LocaleId = 5, --what language they set roblox to, ex:[en-us]
    Region = 5 --player region, ex:['CA']
}

  1. The player joins the game and their user settings is logged to a datastore (each of the keys above)

  2. If the players roblox account is unverified, or the account age is less than 6 months old, the players settings gets compared to those of banned players that were previously logged.

  3. For each setting that matches, it add up to their suspicious-level score that is taken from the table above^.

  4. If this score is > 85, post a warning to a discord webhook (and maybe kick the player)

is such a system allowed in roblox? also how much variety do you think there could possibly be in these settings? enough to uniquely identify someone or is it too extreme?

Any insight is appreciated

2

I don’t think it’s strictly against ToS but factoring in a players’ national origin in calculating their “suspicious-level score” may fall under discrimination per community standards.

4 Likes
3

LOL, true i had not thought of that. Xenophobic code

4

I don’t know if @MP3Face 's comment would be against TOS.
You aren’t using their nationality as a reason to kick them, you are just comparing it as one of a multiple factors in trying to recognize if an alt is similar kicked player’s stats.

The issue I’d see with it is if you have a kicked player who used factory preset mouse settings, an average volume level, fullscreen resolution, are from the US, speak English, and run their quality settings at 10 then you are going to have a lot of players who match that kicked player using the same average settings.

1 Like
5

Yeah… very true, Which is why i considered only using it for unverified and low age accounts… Although sensivity and volume values are actually pretty precise, down to the .00001th. I guess i should try running this on a game and banning a a test account with all the settings on default and see what happens :thinking:.

But so far I think Im just keeping this as a post-to-webhook type warning and not taking any drastic measures like kicking players.

Edit: another potential solution could be ignoring all of these parameters if the settings are on default

1 Like
6

Ik this is a bit of a large bump, but i feel that a good addition to this system is getting the average FPS of both players, and make that a huge factor in the score. There are a lot of different computers on the market, each preforming differently.

Sensitivity and volume would have to be rounded in order for it to work. But the more data you can compare, the lower the chance for false positives. Unfortunately that also has the downside of lower catch chance for the ban-evaders due to them only having to change a few minor values, and go right on through.

8

The only issue with this idea is that FPS is variable even for the same player. The same machine can generate different FPS depending on a number of factors. To give a few: Uptime, background apps, hardware changes, minimizing the Roblox app.

Roblox also caps FPS at 60 which further bars the ability to apply a unique identifier to that variable.

I think it’s an interesting thought experiment, though.

1 Like