Fix capabilities for equipping and unequipping tools

[ryanlua]

Disables sandboxing by default and adds missing capabilities.

Instead of using sandboxing always to sandbox everything, including tools, it should be disabled for backwards compatibility.

[Copilot]

Pull request overview

Adjusts Purse’s default sandboxing configuration and documented capabilities to restore backwards compatibility while enabling tool equip/unequip behavior when sandboxing is opted into.

Changes:

• Disable Sandboxed by default for the Purse model, while updating the capabilities bitmask.
• Update documentation to include the additional capabilities needed for equipping/unequipping tools.
• Update MkDocs navigation to link to the sandboxing documentation page.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
models/Purse/init.meta.json	Changes default sandboxing to off and updates the SecurityCapabilities bitmask.
mkdocs.yml	Updates docs nav entry from “Capabilities” to “Sandboxing”.
docs/sandboxing.md	Rewords sandboxing guidance and adds Avatar-related capabilities to the documented list.

Comments suppressed due to low confidence (1)

docs/sandboxing.md:7

• The opening paragraph and warning are misleading about how Roblox sandboxed containers/capabilities apply to tools. Purse is a ModuleScript typically placed in ReplicatedStorage, so enabling Sandboxed on Purse won’t automatically sandbox tools in Backpack/Character (only scripts/instances that are descendants of the sandboxed container are affected), and capabilities are set on scripts/containers—not on Tool instances themselves. Please reword to clarify when tools/scripts are actually sandboxed and where capabilities must be configured. (Also: “Script capabilities are used…”, not “is used”.)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.