An Update on Automated Action Against Modified Clients

The lack of directly addressing popular third-party solutions such as Bloxstrap is confusing, but I also recognise it’s a possibility that you are still internally evaluating things for what is considered safe for the user to change and what not to change.

While this does put you in a rock and a hard place for wanting to communicate progress when dealing with account farming and exploits, not being given the green light to tell us about the status of the most popular third-party tool for Roblox leaves many of us with more questions than answers.

Hopefully as decisions are more-firmly made internally there will be the possibility to clarify on this thread; Bloxstrap serves as an amazing tool in my use-case by allowing me to use all of my CPU cores in Parallel Luau workloads. Restricting this specific FFlag would kill any viability my custom rendering solution has, so I hope you are working internally to better define these types of restrictions you are placing in mind of security.

2 Likes