@weppy/roblox-mcp 2.5.1 → 2.6.1

package/docs/en/installation/ai-apps/gemini-cli.md

@@ -1,120 +0,0 @@
-# Gemini CLI Setup
-
-How to use Roblox MCP with [Google Gemini CLI](https://github.com/google-gemini/gemini-cli).
-
-## Prerequisites
-
-1. **Node.js** (v18.0.0 or higher)
-   ```bash
-   node --version
-   ```
-
-2. **Gemini CLI** installed
-   ```bash
-   npm install -g @google/gemini-cli
-   ```
-
-3. **Roblox Studio Plugin** installed
-
-## Register MCP Server
-
-### Method 1: CLI Command (Recommended)
-
-Register with a single command in your terminal:
-
-```bash
-gemini mcp add weppy-roblox-mcp npx --trust -- -y @weppy/roblox-mcp
-```
-
-> The `--trust` flag skips confirmation prompts for each tool call.
-
-To register globally, add `-s user`:
-
-```bash
-gemini mcp add weppy-roblox-mcp npx -s user --trust -- -y @weppy/roblox-mcp
-```
-
-### Method 2: Edit Configuration File
-
-Add the following content to `.gemini/settings.json`:
-
-```json
-{
-  "mcpServers": {
-    "weppy-roblox-mcp": {
-      "command": "npx",
-      "args": ["-y", "@weppy/roblox-mcp"]
-    }
-  }
-}
-```
-
-**Configuration file locations:**
-| Scope | Path |
-|-------|------|
-| Project | `<project>/.gemini/settings.json` |
-| Global | `~/.gemini/settings.json` |
-
-### Method 3: Using Environment Variables
-
-If specific environment variables are needed:
-
-**CLI:**
-```bash
-gemini mcp add weppy-roblox-mcp npx --trust -e HTTP_PORT=3002 -- -y @weppy/roblox-mcp
-```
-
-**Configuration file:**
-```json
-{
-  "mcpServers": {
-    "weppy-roblox-mcp": {
-      "command": "npx",
-      "args": ["-y", "@weppy/roblox-mcp"],
-      "env": {
-        "HTTP_PORT": "3002"
-      }
-    }
-  }
-}
-```
-
-## Connection Test
-
-1. Open **Roblox Studio** → Plugins tab → **WEPPY** → **Connect**
-2. Run **Gemini CLI** and enter:
-   ```
-   Tell me what's currently selected in Roblox Studio
-   ```
-
-## Check MCP Server Status
-
-You can check connected server status with the `/mcp` command in Gemini CLI:
-
-```
-/mcp
-```
-
-## Troubleshooting
-
-### Server won't start
-
-Run the MCP server directly to check for errors:
-```bash
-npx -y @weppy/roblox-mcp
-```
-
-### Connection failed
-
-- Verify the Roblox Studio plugin is in **Connected** state
-- Check if port 3002 is blocked by a firewall
-- Check server status with `/mcp` command
-
-### Tool conflicts
-
-If multiple MCP servers have tools with the same name, they will be prefixed with `serverAlias__toolName` format.
-
-## Reference
-
-- [Gemini CLI MCP Official Documentation](https://geminicli.com/docs/tools/mcp-server/)
-- [Gemini CLI Configuration Guide](https://geminicli.com/docs/get-started/configuration/)

package/docs/en/installation/roblox-explorer.md

@@ -1,68 +0,0 @@
-# WEPPY Roblox Explorer (VSCode · Antigravity Extension)
-
-> **Optional** — Explorer is not required. All core features work with just MCP and the plugin. Install it when you want to browse the project structure in your editor.
-
-Roblox Studio Explorer-like tree view for your editor. Browse synced instance trees, open scripts directly, and track sync status — all inside your editor.
-This is a companion extension for WEPPY, not a standalone Roblox integration.
-
-![WEPPY Roblox Explorer](../../assets/screenshots/roblox-explorer/roblox-explorer-screen.png)
-
-## Requirements
-
-- VSCode 1.85+ or Antigravity
-- [Roblox MCP](../../../README.md) installed with Sync enabled (Basic or Pro)
-- Sync has already generated `weppy-project-sync/place_*/.sync-meta.json` under your project root
-
-## Installation
-
-### VSCode
-
-Search for **WEPPY Roblox Explorer** in the VSCode Extensions sidebar (`Ctrl+Shift+X` / `Cmd+Shift+X`) and click **Install**.
-
-Or install directly from:
-
-- [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=weppy.weppy-roblox-explorer)
-- [Open VSX](https://open-vsx.org/extension/weppy/weppy-roblox-explorer)
-
-### Antigravity
-
-Antigravity is VSCode-based, so the same extension works. Search for **WEPPY Roblox Explorer** in the Antigravity Extensions tab and click **Install**.
-
----
-
-Core tree browsing works from synced files on disk. Live sync state, direction indicators, and Explorer telemetry forwarding are available when the local MCP server is reachable.
-
-## Features
-
-- **Instance tree**: Service/instance hierarchy matching Roblox Studio
-- **Roblox class icons**: Dark/light theme support with 200+ class icons
-- **Multi-place**: Separate tree roots per synced place
-- **Click-to-open**: Open backing files (`.server.luau`, `.client.luau`, `.module.luau`, `.props.json`)
-- **Instance search**: QuickPick search across all services
-- **Sync status badges**: See `modified`, `studio`, `conflict` states at a glance
-- **Auto-refresh**: Tree updates automatically when sync files change (500ms debounce)
-- **Copy instance path**: Right-click to copy `game.Workspace.Part` style paths
-
-## Settings
-
-| Setting | Default | Description |
-|---------|---------|-------------|
-| `robloxExplorer.syncRoot` | `""` | Absolute path to the `weppy-project-sync` root. If empty, it is auto-discovered. WEPPY uses `{projectRoot}/weppy-project-sync`. |
-| `robloxExplorer.hidePropsFiles` | `false` | Hide sync artifact files (`.props.json`, `_tree.json`, `.value.json`) in the default VSCode explorer. |
-| `robloxExplorer.autoRefresh` | `true` | Auto-refresh tree when sync files change. |
-| `robloxExplorer.showSyncStatus` | `true` | Show sync status decorations on tree items. |
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `WEPPY Explorer: Refresh` | Manually refresh the instance tree |
-| `WEPPY Explorer: Search Instances` | Search instances across all services |
-| `WEPPY Explorer: Open Backing File` | Open the file backing a selected instance |
-| `WEPPY Explorer: Copy Instance Path` | Copy the full instance path (e.g. `game.Workspace.Part`) |
-| `WEPPY Explorer: Reveal in Explorer` | Show the backing file in the default VSCode explorer |
-
-## Related
-
-- [Sync Deep Dive](../sync/overview.md)
-- [Installation Guide](README.md)

package/docs/en/installation/roblox-plugin.md

@@ -1,96 +0,0 @@
-# Roblox Plugin Installation
-
-How to install the plugin to connect AI agents with Roblox Studio.
-
-## Automatic Installation (Recommended)
-
-If the MCP server setup is complete, the plugin is **installed automatically**. No manual download or file copy is needed.
-
-### How it works
-
-1. When the MCP server runs for the first time, it places the plugin file (`WeppyRobloxMCP.rbxm`) into the Roblox Studio Plugins folder automatically.
-2. When you start Roblox Studio, the **WEPPY** button appears in the Plugins tab.
-
-### Connecting
-
-1. Open any project in **Roblox Studio**
-2. Go to **Plugins** tab → **WEPPY**
-
-![WEPPY Button](../../assets/screenshots/plugin/installation/toolbar-button.png)
-
-3. Click the **Connect** button in the plugin window
-4. Once **"Connected"** status is displayed, you're ready
-
-![Plugin Main Screen](../../assets/screenshots/plugin/installation/main-screen.png)
-
-> If automatic installation did not work, follow the manual installation below.
-
----
-
-## Manual Installation
-
-Use this if automatic installation didn't work or you need to install a specific version.
-
-### 1. Download Plugin
-
-1. Open [GitHub Releases](https://github.com/hope1026/weppy-roblox-mcp/releases/latest)
-2. Download `weppy-roblox-mcp-v{version}.zip`
-3. Extract the ZIP file — you will find `roblox-plugin/WeppyRobloxMCP.rbxm`
-
-### 2. Install Plugin
-
-1. Open **Roblox Studio**
-2. Click the **Plugins** tab in the top menu
-3. Click the **Plugins Folder** button
-
-![Open Plugins Folder](../../assets/screenshots/plugin/installation/plugins-menu.png)
-
-4. **Copy** the `WeppyRobloxMCP.rbxm` file from the extracted folder into the opened Plugins folder
-5. **Restart Roblox Studio**
-
-### 3. Verify Installation
-
-After restarting, the **WEPPY** button will appear in the Plugins tab.
-
-![WEPPY Button](../../assets/screenshots/plugin/installation/toolbar-button.png)
-
-### 4. Connect
-
-Follow the same "Connecting" steps above — click Connect in the plugin.
-
----
-
-## Settings (Optional)
-
-Click the settings button in the top right of the plugin to change options.
-
-![Settings Screen](../../assets/screenshots/plugin/installation/settings-screen.png)
-
-- **Auto Connect**: Automatically connect to MCP server when Studio starts
-- **Auto Reconnect**: Automatically attempt to reconnect when connection is lost
-- **Auto Camera Focus**: Automatically move camera to created objects
-- **Language**: Change the plugin UI language
-
-## Tier Information
-
-- Basic users install the same plugin package and use Basic policy (Studio → Local one-way sync).
-- Pro subscribers unlock bidirectional sync and broader advanced tools after license activation.
-
-## Troubleshooting
-
-### Plugin not visible
-
-- Completely close and restart Roblox Studio
-- Check if the file was properly copied to the Plugins Folder
-- Verify the `.rbxm` file is not corrupted
-
-### Cannot connect
-
-- Verify the MCP server is running in your AI app
-- Click the **Connect** button again in the plugin
-- Check if port 3002 is being used by another program
-
-### Connection frequently drops
-
-- Enable the **Auto Reconnect** option in settings
-- Try restarting your AI app

package/docs/en/pro-upgrade.md

@@ -1,96 +0,0 @@
-# Pro Upgrade Guide
-
-## Why Pro?
-
-### Bidirectional Sync built for real development workflows
-
-Pro Sync goes beyond one-way export. Edit scripts locally and push them to Studio. Make changes in Studio and pull them back to disk. Pro keeps both sides in sync.
-
-- **Bidirectional Sync** — Changes flow in both directions between Studio and local files.
-- **Per-type Direction** — Set direction independently for Scripts, Values, Containers, Data, and Services.
-- **Per-type Apply Mode** — Choose Auto or Manual per type to balance speed and control.
-- **Full Sync / Resync** — Rebuild clean project state on demand after large changes or reconnects.
-- **Change History** — Track what changed, when, and in which direction before applying.
-- **Multi-place Sync** — Sync up to 3 Roblox Places simultaneously, each with isolated storage and its own change history.
-
-### Save AI tokens with high-leverage workflows
-
-Bulk and advanced actions reduce repetitive round trips — do more per prompt.
-
-### Let AI run and verify playtests directly
-
-AI can control Roblox Studio playtests directly. It can start and stop Play (F5) or Run (F8), inject test scripts, collect logs, and generate local reports automatically.
-
-- "Start a Run-mode playtest and check whether the NPC reaches the target."
-- "Write a test that verifies the SpawnLocation is above the ground and run it."
-- "Validate that the script I just changed runs without errors in playtest."
-
-### More Pro-only features
-
-Pro unlocks additional features beyond the core workflow.
-
-- **Bulk operations** — Create, modify, or delete multiple instances in a single request
-- **Terrain generation** — Fill with block, ball, cylinder, wedge, and replace materials
-- **Asset search/insert** — Search the Roblox marketplace and insert assets directly
-- **Spatial analysis** — Raycast, find ground, flat area search, collision checks
-- **Environment control** — Lighting, atmosphere, sky, and time-of-day settings
-- **Audio/Animation** — Sound playback and animation load/play
-
-## Buy and Activate
-
-### Step 1: Buy a Pro subscription license on Gumroad
-
-1. Go to [Gumroad - Weppy Roblox Plugin](https://gumroad.com/l/faccjs?utm_source=github&utm_medium=repo&utm_campaign=pro_upgrade_md)
-2. Complete your Pro subscription license purchase
-3. Copy the license key you receive after purchase
-
-You only need to activate the license once, either in the plugin or in the dashboard. Both surfaces share the same MCP local license state, so once you activate in one place, the same status appears in the other.
-
-### Activate in the plugin
-
-1. Open **WEPPY** in Roblox Studio and connect to the MCP server.
-2. Open **Settings > License** in the plugin.
-3. Paste your purchased key into the `License key` field.
-4. Click **Activate** to activate the license.
-5. If the status does not update immediately, click **Refresh**.
-6. When activation succeeds, the status changes from Basic to Pro and Pro features become available.
-
-![WEPPY Plugin license activation screen](../assets/screenshots/plugin/license/plugin-license-screen.png)
-
-### Activate in the dashboard
-
-1. Start the MCP server, then open **Settings > License** in the dashboard.
-2. Confirm that the provider is set to `gumroad`.
-3. Paste your purchased key into the `License Key` field.
-4. Click **Activate License** to activate the license.
-5. If needed, use **Refresh License** to fetch the latest status.
-
-![WEPPY Dashboard license activation screen](../assets/screenshots/plugin/license/dashboard-license-screen.png)
-
-### After activation
-
-- If the license status is shown as `active` or `grace`, Pro features are available.
-- The plugin and dashboard share the same license state, so activating in one place is reflected in the other.
-- Use **Refresh** or **Refresh License** whenever you want to check the latest status again.
-
-## Feature Comparison
-
-| Feature | Basic | Pro |
-|---------|:-----:|:---:|
-| Script create/edit | ✅ | ✅ |
-| Instance create/delete/move | ✅ | ✅ + bulk operations |
-| Property read/write | ✅ | ✅ + bulk changes |
-| Selection, tags, search | ✅ | ✅ |
-| Camera control | ✅ | ✅ |
-| Log monitoring | ✅ | ✅ |
-| Luau code execution | ✅ | ✅ |
-| Project sync | Studio → Local one-way | Bidirectional + per-type direction/mode |
-| Multi-place sync | — | Up to 3 Places simultaneously |
-| Change history | — | Track changes before applying |
-| Playtest control | — | Play / stop / pause / resume + automated tests |
-| Terrain generation/editing | — | Block, ball, cylinder, wedge, material replace |
-| Asset search/insert | — | Search Roblox marketplace and insert directly |
-| Spatial analysis | — | Raycast, find ground, collision checks |
-| Environment control | — | Lighting, atmosphere, sky, time of day |
-| Audio / Animation | — | Sound playback, animation load/play |
-| AI token efficiency | Per-action calls | Fewer calls with bulk actions |

package/docs/en/sync/luau-lsp.md

@@ -1,41 +0,0 @@
-# Use `luau-lsp` with WEPPY Sync
-
-WEPPY Sync can generate the sourcemap files that `luau-lsp` needs, so you can enable Roblox-aware editor features without setting up a separate Rojo project.
-
-## What WEPPY writes
-
-After Full Sync finishes, WEPPY writes:
-
-- Place sourcemap: `weppy-project-sync/place_<id>/sourcemap.json`
-- Root representative file: `weppy-project-sync/sourcemap.json`
-
-For most users, the recommended path is `weppy-project-sync/sourcemap.json`.
-
-## Why this helps
-
-Pointing `luau-lsp` at the WEPPY sourcemap improves:
-
-- `game.*` autocomplete
-- Navigation across synced scripts
-- `require` resolution between synced scripts
-
-## Recommended setup
-
-1. Run Full Sync once so WEPPY creates `weppy-project-sync/sourcemap.json`.
-2. Point your editor's `luau-lsp` sourcemap setting to `weppy-project-sync/sourcemap.json`.
-3. If your client can disable automatic Rojo generation, set `luau-lsp.sourcemap.autogenerate` to `false`.
-
-Example VSCode settings:
-
-```json
-{
-  "luau-lsp.sourcemap.enabled": true,
-  "luau-lsp.sourcemap.autogenerate": false,
-  "luau-lsp.sourcemap.sourcemapFile": "weppy-project-sync/sourcemap.json"
-}
-```
-
-## Multi-place note
-
-`weppy-project-sync/sourcemap.json` follows the current representative place for the project.
-If you need a fixed place instead, point `luau-lsp` directly to that place's `weppy-project-sync/place_<id>/sourcemap.json`.

package/docs/en/sync/overview.md

@@ -1,153 +0,0 @@
-# Roblox MCP Sync Deep Dive
-
-Sync connects Roblox Studio state and local files so AI can read and modify the full project context reliably.
-
-## Why Sync matters
-
-Without Sync, AI only sees snippets pasted into chat. With Sync enabled, AI works from the whole project.
-
-- Apply refactors consistently across multiple scripts
-- Review risky changes quickly using history
-- Keep source-of-truth clear between Studio and local files
-
-## How it works
-
-![Sync workflow — Studio tree mirrored to local files](../../assets/screenshots/plugin/sync/sync-overview.png)
-
-1. Full Sync: initial mirror from Studio tree/instances to local files
-2. Incremental Sync: continuous update of new changes
-3. History/Status tracking: inspect what changed, when, and in which direction
-
-Sync data is stored under `{projectRoot}/weppy-project-sync/place_{placeId}/explorer`.
-WEPPY also writes a place sourcemap to `{projectRoot}/weppy-project-sync/place_{placeId}/sourcemap.json` and keeps the recommended root representative file at `{projectRoot}/weppy-project-sync/sourcemap.json`.
-Use the root path for editor integrations such as `luau-lsp`. Setup steps are covered in [Use `luau-lsp` with WEPPY Sync](./luau-lsp.md).
-
-### Browse sync data in VSCode
-
-Install the [WEPPY Roblox Explorer](../explorer/overview.md) extension to browse the synced instance tree in VSCode, just like in Roblox Studio.
-Explorer reads the sync files generated here, and it can show additional live sync state or direction details when the local MCP server is running.
-
-![WEPPY Roblox Explorer — browse synced instance tree in VSCode](../../assets/screenshots/roblox-explorer/roblox-explorer-screen.png)
-
-- Service/instance tree with Roblox class icons
-- Click a script to open it for editing
-- Sync status badges show modified/conflict state
-
-## Basic vs Pro
-
-| Item | Basic | Pro |
-|------|------|-----|
-| Sync direction | Studio -> Local | Bidirectional |
-| Per-type Direction | Not supported | Supported (Scripts / Values / Containers / Data / Services) |
-| Per-type Apply Mode | Not supported | Supported (Auto / Manual) |
-| Status/history APIs | Not supported | Supported (`status_current_place`, `history`, `progress`) |
-| `manage_sync` tool | Not supported | Supported |
-| Multi-place sync | Not supported | Supported (up to 3 places) |
-
-## Sync targets and default exclusions
-
-Default syncable services:
-
-- `Workspace`
-- `Lighting`
-- `ReplicatedStorage`
-- `ServerStorage`
-- `ServerScriptService`
-- `StarterGui`
-- `StarterPlayer`
-- `StarterPack`
-- `ReplicatedFirst`
-- `SoundService`
-- `Chat`
-- `LocalizationService`
-
-Default exclusions:
-
-- Classes: `Terrain`, `Camera`
-- Security-restricted paths: `CoreGui`, `CorePackages`, `RobloxScript`, `RobloxScriptSecurity`
-
-## Direction and Apply Mode
-
-### Direction (per-type sync direction)
-
-- `forward`: Studio -> Local
-- `reverse`: Local -> Studio
-- `bidirectional`: both directions
-
-Types are managed separately: `scripts`, `values`, `containers`, `data`, `services`.
-
-### Apply Mode (how reverse changes are applied)
-
-- `manual`: user confirms before applying to Studio
-- `auto`: detected changes are auto-applied
-
-In Pro, Direction and Apply Mode can be controlled per type.
-
-## `manage_sync` action guide (Pro)
-
-| Action | Description | Key params |
-|------|------|-----------|
-| `status_current_place` | Check current sync state for the currently connected place | `-` |
-| `history` | Query change history | `placeId`, `query.limit`, `query.offset` |
-| `directions` | Get per-type direction settings | `placeId` |
-| `read_file` | Read a synced file | `placeId`, `instancePath` |
-| `write_file` | Write a synced file | `placeId`, `instancePath`, `content` |
-| `progress` | Get realtime sync progress/throughput | `placeId` |
-
-## Recommended workflow
-
-### 1) Start safely
-
-- Complete Full Sync first to establish a stable baseline
-- Start with `manual` apply mode to reduce risk
-
-### 2) Work with AI
-
-- "Check sync status, then summarize only risky changes from recent history"
-- "Refactor scripts in `ServerScriptService` first and include history output"
-
-### 3) Resolve conflicts
-
-When changes are detected on both Studio and local sides during bidirectional sync, a conflict resolution dialog appears.
-
-![Local Changes Detected — conflict resolution options (Studio Priority / Local Priority / Per-File)](../../assets/screenshots/plugin/sync/sync-conflict.png)
-
-- **Studio Priority**: overwrite with Studio state as the source of truth
-- **Local Priority**: apply local files to Studio
-- **Per-File**: choose which side takes priority for each file individually
-
-### 4) Recover when needed
-
-- Track recent entries with `history`
-- Inspect target file with `read_file`
-- Restore content with `write_file`, then verify Studio state
-
-## File format (v2 nested directory)
-
-Each Roblox instance is stored as its own directory containing meta files:
-
-```
-explorer/
-├── Workspace/
-│   ├── _tree.json
-│   ├── Part/
-│   │   └── Part.props.json
-│   ├── MyScript/
-│   │   └── MyScript.server.luau
-│   └── Coins/
-│       └── Coins.value.json
-```
-
-Naming conventions:
-- Props: `{Name}/{Name}.props.json`
-- Scripts: `{Name}/{Name}.server.luau` / `.client.luau` / `.module.luau`
-- Values: `{Name}/{Name}.value.json`
-
-Duplicate instance names use `~N` suffix on the directory (e.g. `Part~2/Part.props.json`).
-Names containing `~` are escaped to `~~` (e.g. `Part~2` becomes `Part~~2/`). The Odd-Count Tilde Rule applies: a trailing `~+N` is a collision suffix only when the tilde count is odd.
-
-## Related docs
-
-- [Use `luau-lsp` with WEPPY Sync](./luau-lsp.md)
-- [Tools Overview](../tools/overview.md)
-- [Pro Upgrade Guide](https://weppyai.com/en/plans)

package/docs/en/tools/assets-and-effects.md

@@ -1,104 +0,0 @@
-# Assets & Effects
-
-> Insert assets and control tweening, audio, particles, animation, and collision groups.
-
-## Included Tools
-
-| Tool | Tier | Description |
-|------|:----:|-------------|
-| `manage_assets` | Pro | Search Creator Store, insert models and packages, inspect asset info |
-| `manage_tween` | Pro | Create, play, pause, and cancel tweens |
-| `manage_animation` | Pro | Load, play, stop, and inspect animation tracks |
-| `manage_audio` | Pro | Play, stop, pause, and resume sounds; set the audio listener |
-| `manage_effects` | Pro | Emit particles, clear effects, and toggle effect state |
-| `manage_physics` | Pro | Register collision groups and configure collisions |
-
-## Key Workflows
-
-### Build a scene with assets
-
-```
-"Search Creator Store for a tree model and place three of them in Workspace."
-```
-
-Use `manage_assets.search_insert` to search and insert in a single step.
-
-### Create interactive set pieces
-
-```
-"Make the door open with a 3-second tween when clicked."
-```
-
-Use `manage_tween.create` to define the motion, then `manage_tween.play` to trigger it. Pair it with `manage_audio.play` for a matching sound effect.
-
-### Combine particles and audio
-
-```
-"Play an explosion sound and emit burst particles when the boss appears."
-```
-
-Use `manage_effects.emit` for the particles and `manage_audio.play` for the sound in the same workflow.
-
-## Action Reference
-
-### Manage Assets (Pro)
-
-| Action | Description | Tier |
-|--------|-------------|------|
-| `insert` | Insert a model by asset ID | Pro |
-| `info` | Get asset metadata | Pro |
-| `search` | Search Creator Store | Pro |
-| `search_insert` | Search and insert the first match | Pro |
-| `insert_free` | Insert a free model | Pro |
-| `insert_package` | Insert a package | Pro |
-| `export` | Export the current selection | Pro |
-
-### Manage Tween (Pro)
-
-| Action | Description | Tier |
-|--------|-------------|------|
-| `create` | Create a tween with target properties | Pro |
-| `play` | Play a created tween | Pro |
-| `pause` | Pause a running tween | Pro |
-| `cancel` | Cancel a tween | Pro |
-
-### Manage Animation (Pro)
-
-| Action | Description | Tier |
-|--------|-------------|------|
-| `load` | Load animation on a Humanoid or AnimationController | Pro |
-| `play` | Play a loaded animation track | Pro |
-| `stop` | Stop a playing animation | Pro |
-| `get_tracks` | List all loaded animation tracks | Pro |
-
-### Manage Audio (Pro)
-
-| Action | Description | Tier |
-|--------|-------------|------|
-| `play` | Play a sound and create `Sound` if needed | Pro |
-| `stop` | Stop a playing sound | Pro |
-| `pause` | Pause a playing sound | Pro |
-| `resume` | Resume a paused sound | Pro |
-| `set_listener` | Set the audio listener type or target | Pro |
-
-### Manage Effects (Pro)
-
-| Action | Description | Tier |
-|--------|-------------|------|
-| `emit` | Emit particles from a `ParticleEmitter` | Pro |
-| `clear` | Clear all particles | Pro |
-| `toggle` | Enable or disable an effect | Pro |
-
-### Manage Physics (Pro)
-
-| Action | Description | Tier |
-|--------|-------------|------|
-| `register_group` | Register a collision group | Pro |
-| `set_collidable` | Set whether two groups can collide | Pro |
-| `get_groups` | List all registered collision groups | Pro |
-
-## Related Docs
-
-- [Instances & Properties](instances-and-properties.md) - create and place objects
-- [World & Environment](world-and-environment.md) - lighting, terrain, and camera
-- [Tools Reference](overview.md)