mcpField
R
roblox-performance-optimization

roblox-performance-optimization

github.com/ashexplainedDevelopment38114 installsUpdated 17w ago
Repository

About roblox-performance-optimization

A workflow skill for diagnosing and reducing Roblox experience performance costs, especially for lower-end phones. It guides Studio inspection, targeted tests, evidence-based prioritization, and follow-up verification.

Key features

  1. 01Inspect scene and instance composition
  2. 02Measure scripts, memory, and properties
  3. 03Review rendering and physics costs
  4. 04Capture and playtest before and after
  5. 05Rank fixes by player impact

Use cases

  1. 01Find costly hierarchies and unanchored parts
  2. 02Reduce effects and rendering load on mobile
  3. 03Check for script loops and stale connections
  4. 04Verify optimization changes after playtesting

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-performance-optimization

After installing, type/roblox-performance-optimizationin Claude Code to confirm it loaded.

Details

From the project README

Roblox Performance Optimization

Goal

Keep the experience smooth on lower-end phones. Favor measurable fixes over visual guesses.

Use The Scene Analysis Skill

When available, invoke rbx-scene-analysis before deep performance work. Use it to inspect rendering, memory, instance composition, unparented instances, and animation or audio asset usage.

MCP Workflow

  1. Confirm Studio state with get_studio_state.
  2. Use search_game_tree and inspect_instance to identify heavy hierarchies.
  3. Use execute_luau for targeted counts, tag scans, memory snapshots, or property audits.
  4. Use screen_capture to preserve before/after visuals.
  5. Playtest with start_stop_play and check get_console_output.

Optimization Targets

  • Instance count and deeply nested hierarchies.
  • Unanchored parts causing physics cost.
  • Excessive constraints, touched events, or per-frame loops.
  • Large textures, too many unique materials, and high-poly meshes.
  • Particle emitters with high rate/lifetime combinations.
  • Dynamic lights, shadows, post-processing, and expensive transparency.
  • Scripts that connect events repeatedly or leave stale connections.
  • Workspace content that should stream or load later.

Mobile Budget Habits

  • Build the first area to be visually strong but technically cheap.
  • Prefer fewer meaningful effects over many constant effects.
  • Use Level of Detail thinking for distant props.
  • Keep UI lightweight and avoid per-frame layout work.
  • Test phones and tablet-like viewport sizes, not only desktop Studio.

Report Format

Return:

  • Biggest performance risks.
  • Evidence from scene analysis, instance inspection, console output, or captures.
  • Fixes ranked by likely player impact.
  • Verification steps and any tradeoffs.

Next

Confirm the gains on-device with roblox-mobile-playtest, and re-run roblox-playtest-qa to make sure nothing regressed.

Comments

Markdown supported