BanAsync is no longer banning alt accounts

As here the user is alt banned:
image

Reproduction step:
Use your main on normal roblox application
Get roblox from microsoft app

System Information:
Windows 11 pro 24H2

1 Like

It worked before?

1 Like

yes it did, its the reason there are many video on youtube of mac spoofer to try to bypass the system.

Did a similar test just a few days ago with a friend. Only 9% of his alts were detected. Reproduction was simply to log out and log into an alt and join the game. Feels like it has been broken forever.

1 Like

Alt accounts are not identified based on IP address, it is not a IP ban at all.

After careful examination, we confirmed that the reported behavior is by design. We’re closing this report, but please reach out if you have any additional questions.

Well you just can’t ban yourself from your own game with HD admin.

Same thing happened with a attempt directly from a script. Which caused me to confirm the alt detection isn’t really working with microsoft roblox app anymore.

1 Like

Can you explain in more detail how the alt-detection failing to detect and ban alts is ‘by design’? This system has been poorly functioning for a while. Was there something wrong with OP’s report?

2 Likes

Yeah, this is confusing this system was made but why was it designed it not to work like what :skull:

Hm, I think I misunderstood the original report. Is the report that bans aren’t respected in windows app (e.g., the ListRestrictions shows the user as banned, but said user is still able to join the experience)? Or is the report that alts aren’t being detected?

I originally interpreted the report as the latter, and closed this since I was able to confirm that alt detections and propagations are indeed still happening.

It barely ever worked, and this is great that it doesn’t work.

The issue is that the “New real-time alternate account detection” system, as presented in the Ban API’s announcement topic, does not work. As demonstrated in OP’s video, he is logged into his alt and said alt is not banned in “real-time” even though it’s playing at the same time on the same PC that his other account is banned on. I have tested this system extensively and, at best, it detects only 9% of even the most blatant alt accounts. My test method is simply logging out and logging into an alt and attempting to rejoin the experience. The system does not prevent the alt account from doing so. I can repeat this for 12 alt accounts and only 1 gets detected. I can provide a document of our testing if that would help the teams determine why the system isn’t really working.

If the system is intentionally designed to have an overwhelming amount of false-negatives and this is expected behavior, then that is unfortunate. While this might not technically be a ‘bug’ as the system does not error, it would be nice if the shortcomings of the system were acknowledged and put on track for improvement before the issue is closed.

1 Like

Not a bug, his alt just isn’t being picked up as an alt because the methods of finding alts are so incredibly miniscule that most of the time “bypassing” the alt detection just involves not having the accounts immediately linked through the account switcher.

Ah thanks for the clarification. The team’s aware of this and has ongoing work to improve alt detection without increasing incorrect alt bans. I can leave this report open in the meantime.

1 Like