FFlag prevent certain touch events from firing

Recently, I found out that there’s a fast-flag named DFIntTouchSenderMaxBandwidthBps which when set to "-1" will prevents certain touch events from firing. This may grant player an unfair advantage in games that heavily rely on touch events, such as obby games or games with NPCs that can attack you.

Expected behavior

This FFlag should not be existed at all.

4 Likes

Touch Events should not be used for crucial gameplay parts such as damage dealing scripts.
Touch Events are client side, handled by client and sent to server when client touches something, it’s an unreliable and bad practice to use Touches for important gameplay aspects.
As this flag name states, it is used for performance optimizations, to throttle touch event bandwidth in order to keep other essential network functions working stable when player have slow internet connection.

1 Like

what-the-point-went-over-your-head
Hes talking about exploiters using it to gain unfair advantages like not touching killbricks. Also, if you shouldnt use it for killbricks, how come rob!ox themselves and basically every game ever does killbricks on the server

https://create.roblox.com/docs/reference/engine/classes/WorldRoot#Blockcast

Hi guys - this particular exploit of setting that DFInt should be solved by the changes described in this post: Allowlist for local client configuration via Fast Flags

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.