SkillAgentSearch skills...

scenario-roblox-networking

Use when securing a Roblox experience against exploiters or designing its networking: RemoteEvent, RemoteFunction or UnreliableRemoteEvent design, validating remote arguments on the server, remote spam and rate limits, speed hacks, teleport or fly hacks, kill aura or hitbox abuse, hit validation und…

Install / Use

npx skills add scenario-labs/skills --skill scenario-roblox-networking

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Security

Supported Platforms

Universal

Our assessment of scenario-roblox-networking

scenario-roblox-networking scores 86/100 on our quality scale, 754th of 1,098 Security skills we index.

Its SKILL.md is 18 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 35 days ago, so scenario-roblox-networking is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-roblox-networking compared with similar skills

All 4 of these similar skills score higher than scenario-roblox-networking; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-roblox-networking (this skill)by scenario-labs861.0k35d agoSKILL.md
taste-skillby Leonxlnx100120.0ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.6k12d agoCLAUDE.md
algorithmic-artby anthropics100177.9k2mo agoSKILL.md
pptxby anthropics100177.9k2mo agoSKILL.md

Frequently asked questions

How do I install scenario-roblox-networking?
Run npx skills add scenario-labs/skills --skill scenario-roblox-networking. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-roblox-networking work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scenario-roblox-networking safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scenario-roblox-networking still maintained?
The repository was last updated 35 days ago, so scenario-roblox-networking is actively maintained.

name: scenario-roblox-networking description: "Use when securing a Roblox experience against exploiters or designing its networking: RemoteEvent, RemoteFunction or UnreliableRemoteEvent design, validating remote arguments on the server, remote spam and rate limits, speed hacks, teleport or fly hacks, kill aura or hitbox abuse, hit validation under lag, network ownership and fling exploits, ProximityPrompt or ClickDetector abuse, honeypots, kick and ban policy, Server Authority (AuthorityMode) setup, bandwidth or payload size problems, or after an exploit (free items, infinite money, duplicated items)." license: MIT

Roblox Networking and Security

Target: Roblox Studio (October 2026 build) on macOS, driven through the scenario-roblox-expert toolkit.

Expert level here means every client-triggerable action is attacker input: the server owns state, checks each call in a fixed order, and proves it by firing hostile arguments from a playtest client. Detection supplements validation, and visible consequences come late, from varied signals.

If a sibling skill named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag the gap.

REQUIRED BACKGROUND: scenario-roblox-expert (channels, review loop, toolkit, current-Roblox traps).

Stance (the expert delta)

  1. Remotes carry intent, never results. The client names an item, and the server prices it. A weapon reports origin and hit point, never the victim or the damage (Creator Docs, client-server boundary; GnomeCode).
  2. Check in a fixed order: rate, then arguments, then context. The docs list context, type, value and rate; running the rate limit first is cheapest [added]. NaN passes typeof(v) == "number" and fails every comparison, so use math.isfinite (Creator Docs; Suphi Kaner). Live, NaN and infinity payloads through a handler that only range-checked set an IntValue balance to -9223372036854775808.
  3. An Instance argument is a claim. Check typeof and IsDescendantOf(expectedFolder): a table can mimic an Instance, and a client can replay a destroyed pickup it still references (Creator Docs; Suphi Kaner).
  4. Every client-triggerable surface is a remote. ProximityPrompt checks distance on Triggered only and ignores Enabled. ClickDetector has no server checks. Touched reports the client's physics (Creator Docs; Suphi Kaner).
  5. Movement: Server Authority for new competitive games, a server MoveGuard for existing casual places. The deciding condition is genre plus whether you can adopt fixed simulation, InputActions and streaming (Creator Docs; Jason Knight, Roblox). Server Authority does not stop ESP, aimbots or camera abuse (ev1).
  6. Validate hits against what the attacker saw. Roblox has no built-in lag compensation (ev1). Rewind server-recorded positions over [now - min(ping + 0.1, 0.4), now] [added], or use a cone of about 10 degrees (ev1). Obstruction uses static geometry only (Creator Docs).
  7. Consequences climb a ladder and arrive late. Keep a decaying suspicion score, require two distinct reasons before enforcement, and delay visible action randomly by 20 to 90 s [added numbers]. Honeypot remotes and direction honeypots are high-confidence signals (Creator Docs, server-side detection). For movement, rubber-band instead of kicking, because lag causes false positives (GnomeCode).
  8. UnreliableRemoteEvent only for frequent cosmetic data under 1,000 bytes. The cap is 1,000 bytes (Creator Docs); the 900 figure in a 2025 Roblox Learn video is outdated, and live a 980-byte random buffer arrived while 1,000 was dropped. Both remote types need identical validation.

Establish first

  • Workspace.AuthorityMode: Automatic means client-owned characters (MoveGuard applies); Server means the engine simulates them. rbx_net.audit_place(place) reads all six settings offline.
  • Stakes: competitive or casual, live or prototype. A prototype can defer honeypots and the ladder, never validation.
  • Remote inventory: name, direction, frequency, payload size, and what server value each handler writes.
  • Interactive surface: prompts, ClickDetectors, DragDetectors, Touched pickups, and whether their parents are unanchored.
  • Enforcement policy: kick, Players:BanAsync, or mitigation only; who handles appeals (Net.reset).
  • Defaults when unanswered: every remote through Net.bind, one honeypot, Net.serverOnly on server-to-client remotes, enforcement as a dry run during tests.

Procedure

Run each stage through the toolkit; full code and test results are in procedures.md. Status: 24 live tests pass in Studio 0.743 (arena rerun and Server Authority place on 2026-10-19). Keep NetKit (Guard, RateLimit, Suspicion, Net, HitCheck, MoveGuard) as ModuleScripts under one server folder. rbx_net.kit_tree(project_dir) gives the Rojo fragment for a test place; in a user's repository, rbx_net.vendor_kit(repo, dest) copies the modules in and returns paths inside it.

  1. Audit. Goal: a list of every remote, handler and interactive instance with findings. How: rbx_net.audit_place(place) offline (Lune), then rbx_net.run(studio, "return NetAudit.run(game, Audit)", kit=["NetAudit"], lead_kit=["Audit"]) in Edit. GATE: zero errors; every warning fixed or justified; live tally equals offline tally.
  2. Validate and limit. Goal: no handler runs on bad arguments or at flood rates. How: Net.bind(remote, {args = {Guard...}, limit = {capacity, perSecond}, handler = fn}) for every client-to-server remote; idempotent handlers on the server clock. GATE: the audit shows no handler-unvalidated, nan-unsafe, trusted-value or no-rate-limit finding.
  3. Hits. Goal: claims checked against history. How: a 1 s HitCheck.History per target pushed every Heartbeat, HitCheck.melee and HitCheck.ranged with ExcludeInstances or IncludeInstances for static walls. GATE: out-of-reach, fake-origin, through-wall and offset shots rejected; valid shots hit.
  4. Movement. Goal: speed and teleport hacks neutralized without false positives. How: Server Authority (Rojo writes the settings, stage P11), or MoveGuard.start with MoveGuard.grace(player, s) before every server teleport; enforce = false only logs, then measures from where the character stands. GATE: honest walk 0 flags; client teleport and local WalkSpeed changes rubber-banded (live: WalkSpeed 80 for 2.5 s netted 12.6 studs on the server). Under Server Authority, live: W held 2 s moved the server character 32.4 studs, a client teleport 0, local WalkSpeed 80 then W 32.0.
  5. Ownership and surfaces. Goal: no client-owned part decides an outcome. How: SetNetworkOwner(nil) on unanchored pickups, NPC roots and prompt parents; Net.prompt re-checks distance, state and rate; a distance check in MouseClick; Net.touch for Touched pickups (toucher, CanTouch, distance, MoveGuard reach, shared limiter). GATE: a client CFrame write moves nothing on the server.
  6. Exploit tests from the Client. Goal: proof, not intent. How: in a Playtest, rbx_net.fuzz(pt, path, gap=...), a same-frame spam, a honeypot fire, then rbx_net.net_log(pt) in the Server data model. Include a deliberately vulnerable remote as a negative control. GATE: balances and health unchanged, ok_<Remote> equals the valid-case count, no server script error, the negative control pays out. A Touched pickup has no remote: use exploit_case with a client teleport onto the part, then a Net.touch part and a bare Touched part side by side (P6).
  7. Detection and consequences. Goal: high-confidence signals, delayed action. How: Net.init({enforce = ..., enforceDelay = {20, 90}}), Net.honeypot, Net.serverOnly. GATE: one honeypot fire reaches enforce with a scheduled delay; a flood alone stays below restrict.
  8. Latency. Goal: valid play survives real ping. How: rbx_net.set_latency(studio, 100, 100) in Edit before Play, last-moment swings at a moving target. GATE: rewind hit rate at least 0.8. Live at 202 ms ping: rewind 13 of 13, no rewind 0 of 13 (three runs). Trigger the swings close to reach plus slack: with 0.2 s of margin left, the no-rewind rate swung from 31 to 92 percent between runs.
  9. Bandwidth. Goal: small, on-change traffic. How: rbx_net.payload_probe before choosing unreliable delivery; pack with buffer; sequence numbers on streams. GATE: payloads measured under the cap; stream accepted count equals sent.

Numbers

| Value | Relative to | Source | | ----------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | 1,000 bytes | UnreliableRemoteEvent payload after compression; a lone buffer fits 996 | Docs; live: random 980 arrived, 1,000 "went over by: 4 bytes" | | About 500 per second | Client-to-server requests per client, per remote type | RemoteEvent reference; not observed in a Studio playtest (live: 1,000 arrived within 0.5 s) | | Burst 5, 1 per 2 s | Docs token bucket sample TokenBucket.new(5, 10) | Docs | | 50 dropped calls in 1 s | Flood flag threshold, once per window | [added] | | WalkSpeed + 5 studs/s | MoveGuard allowed XZ speed, dt clamp 0.01 s | Suphi Kaner | | 6 studs, leak 0.5/s | MoveGuard burst bucket | [added] | | 0.1 s interp, 0.4 s cap | Rewind window [now - min(ping + 0.1, 0.4), now] | [added] | | About 10 degrees | Hit plausibility cone | ev1 | | 1, 3, 6, 10 | Suspicion levels log, mitigate, restrict, enforce; half-life 120 s | [added] | | 20 to 90 s | Random delay before visible enforcement | [added] | | 64, 50 chars | Replicated attributes per predicted instance; name and string length | Docs | | 0.5 percent | Highest scripted packet loss (5 reads back 0.5) | live | | 50 KB/s | Roblox's send and receive target per client (Stewiepfing aims for 25) | Stewiepfing |

Quality gates

Measurable:

  • Audit: zero errors; every warning resolved or written down with a reason.
  • Fuzz: every hostile case lands in args_<Remote> or rate_<Remote>; balances, health and pickups unchanged.
  • Spam: 1,000 same-frame re

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.0k
CategorySecurity
Updated1mo ago
Forks129

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions