roblox-remote-events — Claude Code skill: Roblox remotes

What roblox-remote-events does

The skill covers picking between RemoteEvent, RemoteFunction and UnreliableRemoteEvent, with a table of direction and whether a value comes back. Its advice: default to RemoteEvent, and skip server-to-client RemoteFunction calls, because a frozen callback on an exploiter's client stalls your server thread.

Then come the patterns. Remotes live in ReplicatedStorage and get created by a server Script before any LocalScript runs. You get templates for FireServer, FireClient, FireAllClients, InvokeServer, plus high-frequency syncing with UnreliableRemoteEvent. A mistakes table catches the usual slips: OnServerEvent inside a LocalScript, remotes parked in ServerStorage, a missing WaitForChild, several OnServerInvoke assignments where only the last one wins.

Security is the part that matters. The client is treated as hostile, so every argument gets checked on the server: per-player cooldown, type checks, a clamp on the value, and target and weapon resolved from server state. The exploit table names argument injection, remote spam, spoofed targets, replayed actions and damage amplification. If odd damage numbers or duplicated items have shown up in your game, start there.