More Warnings Needed for client side RemoteFunctions

There is a great warning on the Remote Functions and Events article. Thiere is also warning on the InvokeClient method docs but it is less pronounced.

However, many other pages documenting RemoteFunctions offer no such warnings. (e.g. RemoteFunction | Documentation - Roblox Creator Hub and RemoteFunction | Documentation - Roblox Creator Hub )

While I understand that it may be repetitive information, information around possible security issues with non-deprecated Roblox APIs should be more pronounced in the documentation. There are serious considerations that should be taken when invoking RemoteFunctions on the client and the docs should be more indicative of that.

5 Likes

Something like this?

To be fair, the Roblox Developer wiki can be hard to navigate sometimes, and information can be hidden in some articles and much more easily seen in others. It’s still definitely a good resource, but it can be cleaned up more.

(Source: Remote Functions and Events)

3 Likes

Hey,

Thanks for reporting this. Just so we can be 100% clear, what warning are you specifically referring to?

1 Like

I am referring to the warning that @NINJAMASTR999 included in his post from the Remote Functions and Events page. While just checking the documentation for using a RemoteFunction that is invoked by the server, there are not clear enough warnings about how it can be problematic.

Awesome ok, I’m on the same page now. I’ve added it to our backlog, and we’ll get to it as soon as we can. Thanks for highlighting it!

3 Likes

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