roblox-physics
Design or review Roblox assemblies, constraints, collision, hit detection, and network ownership.
- License 许可
- MIT
- 最近更新
- 2026-09-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- roblox-physics
- description
- Design or review Roblox assemblies, constraints, collision, hit detection, and network ownership.
02 资源文件 1
- 参考文档agents/openai.yaml238 B
03 SKILL.md 正文
Roblox physics
Read ../../references/roblox-engineering.md. Inspect the authored hierarchy, assemblies, roots, anchoring, attachments, constraints, collision groups, and current ownership code before changing behavior.
Treat simulation as distributed and untrusted
- Decide network ownership at the assembly level as both a responsiveness and authority choice. Client ownership reduces input latency and server work, but the client can manipulate its simulation.
- Keep gameplay-critical assemblies server-owned when practical. For responsive player-controlled physics, assign ownership deliberately and validate server-observed position, speed, state transitions, and outcomes within game-specific tolerances.
- Reapply or release explicit ownership when seats, characters, tools, assemblies, or round state change. Anchoring and reconnecting parts can change the ownership model.
- Do not treat
Touchedalone as proof of authoritative damage, collection, or completion. Confirm server-side identity, spatial plausibility, state, cooldown, and duplicate behavior; use an appropriate ray or swept spatial query for fast motion. - Prefer attachments and constraints for simulated mechanisms. Apply forces or impulses to the intended assembly instead of fighting physics with repeated per-frame transforms or velocity assignments.
- Make collision groups and query filters explicit. Exclude the source assembly, validate returned instances and ancestry, and separate physical collision from detection when gameplay requires different rules.
- Bound active simulated assemblies, query frequency, and per-frame work. Measure server physics cost, replication, and mobile client behavior before optimizing.
Deliverable
State the assembly root, owner through each lifecycle state, authority checks, collision and query rules, constraint model, cleanup, and failure behavior. Verify pure hit-validation and state-transition logic locally. Give the user exact Studio checks for ownership visualization, multiple clients, latency, reset, and high-speed contact; never invoke the playtest through MCP.
04 同仓库更多 Skills
why
Recover why a Roblox design or implementation exists from project decisions, source history, current code, and authored context.
unslop
Cut AI tells from any writing. Must always apply.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use for explicit TDD or when Roblox logic has a cheap deterministic Luau regression target that can fail before the fix.
swarm
Coordinate independent routine execution or exploration batches and return one reviewed report. Use for $swarm or large separable work that justifies parallel overhead.