fix: Depend on Screen Capture module for projects that manually disables it

[heshuimu]

fixes #460

Summary by CodeRabbit

• Chores
  • Added screen capture module dependency to project configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A single dependency declaration has been added to MCPForUnity/package.json to declare the package's reliance on Unity's built-in Screen Capture module. This resolves an issue where ScreenshotUtility.cs could not resolve the ScreenCapture class when the module was manually disabled.

Changes

Cohort / File(s)	Change Summary
Dependency Declaration MCPForUnity/package.json	Added com.unity.modules.screencapture version 1.0.0 to the dependencies section to declare reliance on Unity's built-in Screen Capture module

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A capture module, declared with care,
Now ScreenshotUtility can find it there!
One line added, dependency clear,
No more missing classes to fear! 📸

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically describes the main change: adding a dependency on the Screen Capture module to fix projects that manually disable it.
Linked Issues check	✅ Passed	The pull request directly addresses issue #460 by adding the required Screen Capture module dependency to package.json, which prevents unresolved references when the module is manually disabled.
Out of Scope Changes check	✅ Passed	The pull request contains only the necessary dependency addition to package.json with no extraneous changes unrelated to resolving the linked issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8fe73be and 5a12c5d.

📒 Files selected for processing (1)

• MCPForUnity/package.json (2 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: msanatan
Repo: CoplayDev/unity-mcp PR: 316
File: TestProjects/UnityMCPTests/Assets/Tests/EditMode/Resources.meta:1-8
Timestamp: 2025-10-13T13:27:23.040Z
Learning: UnityMcpBridge is a legacy project kept for backwards compatibility; MCPForUnity is the only active Unity plugin project. GUID collisions between UnityMcpBridge and MCPForUnity are acceptable.

Learnt from: JohanHoltby
Repo: CoplayDev/unity-mcp PR: 309
File: MCPForUnity/Editor/Helpers/ServerInstaller.cs:478-508
Timestamp: 2025-10-13T13:41:00.086Z
Learning: In the MCPForUnityTools feature (MCPForUnity/Editor/Helpers/ServerInstaller.cs), the design intentionally forces users to have only one .py file per MCPForUnityTools folder to keep file tracking simple. Package-style tools (subdirectories with __init__.py) are not supported.

Learnt from: dsarno
Repo: CoplayDev/unity-mcp PR: 0
File: :0-0
Timestamp: 2025-09-03T16:00:55.839Z
Learning: ComponentResolver in UnityMcpBridge/Editor/Tools/ManageGameObject.cs is a nested static class within ManageGameObject, not a sibling type. The `using static MCPForUnity.Editor.Tools.ManageGameObject;` import is required to access ComponentResolver methods directly without the outer class qualifier.

Learnt from: msanatan
Repo: CoplayDev/unity-mcp PR: 301
File: docs/CUSTOM_TOOLS.md:54-62
Timestamp: 2025-10-03T22:11:46.002Z
Learning: In Unity MCP, the `description` parameter in the `mcp_for_unity_tool` decorator is technically optional but should always be included as a best practice. Without it, there's a higher chance that MCP clients will not parse the tool correctly. All Unity MCP tools should include the description in the decorator for compatibility.

📚 Learning: 2025-09-04T01:01:11.927Z

Learnt from: dsarno
Repo: CoplayDev/unity-mcp PR: 260
File: UnityMcpBridge/UnityMcpServer~/src/server_version.txt:1-1
Timestamp: 2025-09-04T01:01:11.927Z
Learning: The UnityMcpBridge project is not maintaining changelogs yet, so don't suggest adding changelog entries for version bumps.

Applied to files:

• MCPForUnity/package.json

📚 Learning: 2025-10-13T13:27:23.040Z

Learnt from: msanatan
Repo: CoplayDev/unity-mcp PR: 316
File: TestProjects/UnityMCPTests/Assets/Tests/EditMode/Resources.meta:1-8
Timestamp: 2025-10-13T13:27:23.040Z
Learning: UnityMcpBridge is a legacy project kept for backwards compatibility; MCPForUnity is the only active Unity plugin project. GUID collisions between UnityMcpBridge and MCPForUnity are acceptable.

Applied to files:

• MCPForUnity/package.json

🔇 Additional comments (1)

MCPForUnity/package.json (1)

10-11: Module identifier and version compatibility verified as correct.

The com.unity.modules.screencapture identifier is the official built-in module name per Unity documentation, and the module is available in Unity 2021.3 (the project's minimum version). The dependency addition correctly supports the ScreenCapture.CaptureScreenshot() call in ScreenshotUtility.cs, which is properly guarded by a UNITY_2022_1_OR_NEWER preprocessor directive to fall back to camera rendering in earlier versions.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Scriptwonder]

The manual disable feature may have some problems with dependencies, and thanks for letting me know. I will work on a thoughtful way to resolve the issue.