agentleFS
szlayszlay/roblox-base/.claude/skills/roblox-networking/SKILL.md

roblox-networking

Skill1 starsChanged 4 months agoMITView on GitHub

Use when validating RemoteEvent or RemoteFunction arguments, adding rate limits, designing server-authoritative systems, or preventing exploits.

6 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat every client argument as attacker-controlled input.

    line 25
  2. Distinctive:

    Look up prices, damage, rewards, and permissions from server-owned definitions.

    line 27
  3. Very specific:

    Use events for most gameplay requests.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

roblox networking

When to Load

Load when adding a remote, handling untrusted client input, implementing cooldowns, or deciding which side owns a gameplay result.

Quick Reference

  • Treat every client argument as attacker-controlled input.
  • Validate type, size, ownership, state, distance, and cooldown on the server.
  • Look up prices, damage, rewards, and permissions from server-owned definitions.
  • Choose the authority model before designing movement or continuous simulation. Server Authority uses client input prediction and server rollback; it is not the same thing as handing a part to a client with SetNetworkOwner.
  • For simulation-affecting input in Server Authority, use InputAction/InputContext and RunService:BindToSimulation() rather than feeding continuous input through a RemoteEvent.
  • Use events for most gameplay requests. Keep RemoteFunction calls short and bounded.
  • Use RemoteEvent for reliable state changes within its event channel. Do not assume a RemoteEvent is ordered with property or attribute replication; use one explicit state channel or version the state when ordering matters. Use UnreliableRemoteEvent only for replaceable or ephemeral data such as VFX and continuous snapshots.
  • Unreliable does not mean automatically faster: delivery is unordered, packets may be dropped, and payloads should stay at or below the documented 900-byte limit.
  • Measure payload size and fire rate under load. Do not treat a community packet-size estimator as an official wire-format specification.
  • Validate numeric inputs for NaN and infinity before applying range checks. NaN makes ordinary < and > checks return false.
  • Rate limits protect the server, but validation must still reject invalid requests.
  • Record suspicious behavior and use thresholds. Do not punish a player for one malformed packet.

Need the details? Load references/full.md for reusable validation and throttling patterns.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.