WEPPY Roblox AI Toolkit - Roblox Studio MCP with Sync, Playtest, and UI Studio

Resources Community Resources
, ,
61

Recent updates improve both the Project Sync file format and Terrain generation quality.

Project Sync file format

New Sync projects now use the v3 file format. It separates game data managed by Sync from runtime information such as timestamps and session data. Unchanged files are no longer rewritten when the same Studio state is synced again.

This reduces unnecessary Git diffs and makes actual script and instance changes easier to review.

Existing v2 projects are not migrated automatically and will continue to work as before. When you are ready to update, open the Sync page in the WEPPY Dashboard to review every file that will be added, modified, or removed, along with anything blocking the migration.

The migration only reorganizes Sync-managed files and does not modify Luau source files. WEPPY creates a backup before applying the update and restores the existing v2 state if the migration cannot complete successfully. Before updating, make sure your latest work is saved in the Roblox Studio place file.

Once a project has been migrated to v3, its Sync data must be used with the latest MCP server. Opening it again with an older MCP server is not supported.

Terrain generation improvements

Terrain generation now combines large landforms with smaller surface variations instead of relying on a single layer of noise. Materials change between ground and cliffs based on slope, while water and shorelines follow the generated terrain more naturally.

Six biome presets are available: mountains, hills, plains, dunes, islands, and canyon. You can refine the result by adjusting height, detail, water level, materials, and seed. Reusing the same seed reproduces the same terrain, making it easier to keep a result while changing individual settings.

These changes help AI agents create more natural environments in fewer steps, with less manual smoothing and material cleanup afterward. Each Terrain generation operation is also recorded as a single Studio Undo step.

1 Like
62

Hello! I’d like to share the main improvements included in the recent WEPPY v2.11.0–v2.11.1 updates.

Read only the script lines you need

AI agents can now request a specific range of lines from a large script instead of loading the entire source every time.

This feature is available on Basic and helps the AI focus on the code around the area being changed. If the requested range extends past the end of the script, WEPPY also reports the actual range that was returned.

Warnings for unused options

WEPPY now displays a warning when an AI agent includes options that are not used by the selected operation.

The operation will still run when possible, and the warning helps the AI identify which options were ignored and correct them in its next request.

Studio readiness checks before AI work

Before starting a task, AI agents can now perform read-only checks for:

  • Roblox Studio connection status
  • The currently selected place
  • Edit or Play state
  • Publish status
  • Screen capture readiness
  • Image and mesh feature readiness

These checks do not modify Studio settings or game data. If something needs attention, WEPPY explains what should be checked before the agent continues.

Open Cloud preflight checks

Pro users can verify their saved API key authentication, Assets Read and Write permissions, Creator target, file format, and file size before uploading an asset.

This is a read-only check. It does not upload a new asset or modify an existing one.

Improved Playtest reports

We also fixed an issue that caused duplicate logs and signals to appear in completed Playtest reports. No additional setup or migration is required.

I originally created WEPPY to solve the problems I experienced while developing Roblox games with AI agents. I still actively develop Roblox games myself, and I continue updating WEPPY whenever I encounter something that makes the development process unnecessarily difficult.

Today, many improvements also come directly from feedback shared by WEPPY users. The new line-range script reading feature in this update is one example—it was implemented based on a user’s suggestion.

For urgent bugs and critical issues, I try to release a fix within 24 hours whenever possible. For feature improvements, I usually aim to review, implement, and release feasible requests within two or three days.

If you encounter anything inconvenient or notice something that could be improved while using WEPPY, please feel free to share your feedback. I’m always grateful for it, and I’ll continue reviewing and applying it to make WEPPY better.

Thank you for using WEPPY.

1 Like
63

What’s the difference between this MCP and Chrrxs roblox MCP?

64

Great question! The main difference from other MCPs is that WEPPY not only controls Studio, but also lets you monitor what is happening and manage multiple work environments together.

With WEPPY, AI agents can create and modify scripts, instances, terrain, lighting, assets, and UI, as well as run Sync and Playtest workflows. The Dashboard shows which AI agents and Studio sessions are connected, which tools were executed, whether they succeeded or failed, Sync status, Playtest reports, project change history, and UI Studio analysis and before-and-after records.

You can also connect multiple AI agents and up to five Roblox Studio windows to a single MCP server. For example, you can keep Lobby, Game, and Shop open in separate Studio windows, target the correct Place using its Studio ID, and monitor the connection and routing status directly from the Dashboard.

So the main difference from other MCPs is that WEPPY goes beyond sending instructions to Studio—you can see what actually changed while managing multiple agents and Studio sessions together.

65

Hi! Here’s what was added in v2.12.0.

This update introduces Luau Syntax Validation, allowing you to catch Luau syntax errors without starting Playtest. It is available on both Basic and Pro and can be enabled under Dashboard > Controls > Luau Syntax Validation.

When enabled, WEPPY validates the source that was actually saved after supported script-writing operations. If it finds a syntax error, it provides details the AI agent can use to correct the script. This feature is Off by default, and script changes remain saved even if validation finds an error or is unavailable.

We also improved stability on Windows:

  • MCP and Studio Sync now continue running when a history file is temporarily locked.
  • Dashboard settings can be saved through temporary file locks.
  • Local files, the Explorer tree, and the Sync index now stay consistent when sibling objects have duplicate names.
  • Project Change Summary save failures are now included in the Dashboard bug-report ZIP for easier diagnosis.

These changes are available in v2.12.0 or later. If you encounter an issue, please share your current version and reproduction steps, and we’ll look into it.

66

WEPPY Roblox AI Toolkit v2.12.2 is now available.

The main change is support for referencing an Instance directly from an attribute, which Roblox introduced on July 23 ([Studio Beta] Reference Instances Directly with Attributes). Until now, those attributes came through Sync as empty values on the file side, and applying that file back to Studio could turn the reference into plain text or remove it. Starting with v2.12.2, WEPPY records the location of the referenced object, including which one you meant when several objects along the path share the same name. The reference survives the round trip in both directions, Studio to file and file to Studio.

Other fixes in this release:

  • If an attribute referenced one object and you repointed it at a different object with the same name, the change could go undetected and never reach your files. These changes are now picked up.
  • When an attribute uses a type WEPPY does not recognize yet, the value is kept as a placeholder that records the type instead of being dropped during Sync. Applying that file back to Studio skips the attribute, so your Studio value stays as it is.
  • If a reference in a file cannot be matched to an object in Studio, the attribute is left untouched rather than cleared or replaced with text, and the reason is written to the plugin log.

Update to the latest version, then fully restart Roblox Studio and your AI agent.

Related announcement: [Studio Beta] Reference Instances Directly with Attributes

67

We’ve updated the Asset Library in the dashboard!

Assets can now be browsed by folder, making it much easier to find what you need as your library grows.

You can also switch between thumbnail and list views, and adjust the thumbnail size to match your workflow. Use smaller thumbnails to scan more assets at once, or enlarge them when you need to compare visual details.

These options should reduce the time spent searching through files and help you stay focused on building.

image
image1328×776 98.1 KB

image
image1413×903 236 KB