文档

​
​

Development

User Acquisition

Monetization

工业

Unity Version Control

DevOps

On-prem

Gluon

Editor plug-in

Open Unity Dashboard

Unity Version Control

此页面不支持所选语言。
​
​
Unity Version Control
  • Overview
  • Cloud Repositories organization update
  • Installation
  • Use UVCS with the Unity Editor
  • Unity Version Control plugins
  • Concepts
  • Tutorials
    • Migrate from Git
    • Migrate from Perforce
    • Version Control settings
    • Configure the client
      • Client configuration files
      • Use filter pattern files
      • Use value matching pattern files
      • Globally configure the branch explorer
      • Configure EOL conversion
      • Configure external tools
      • Configure syntax language
      • Configure the Open with menu
    • Version Control workflow
    • Version Control tools
  • On-Prem
  • Gluon
  • CLI and shortcut references
  • Release Notes
  1. Unity Version Control (previously Plastic SCM)

Configure external tools

Configure external tools in Unity Version Control configuration files.
阅读时间2 分钟
最后更新于 10 个月前
Use the 
externaltools.conf
file to run actions from external tools on selected objects.
If you configure actions, these actions appear in the submenu when you right-click and select Open in the following locations:
  • Controlled and private items in the Workspace Explorer tab.
  • The Pending Changes tab
  • The History view (Windows only)
The actions also appear as a new context menu item, External tools, in the following locations:
  • The Branches tab
  • The Changesets tab
  • The Labels tab
  • The History side panel (only GTK and macOS)

Create the 
externaltools.conf
file

Create the 
externaltools.conf
file in one of the following locations:
注意
The following locations are listed in order of precedence. For example, a configuration file in 
plastic-global-config
overrides a configuration file in the 
plastic4
directory.
  • In the 
    plastic-global-config
    repository under 
    /externaltools/externaltools.conf
    so that all clients have the same settings by default.
  • In your client installation directory.
  • In the 
    plastic4
    directory:
    • Windows: under 
      C:\Users\<em>user</em>\AppData\Local\plastic4
    • Linux or macOS: under 
      $HOME/.plastic4

Syntax

Use the following syntax for the 
externaltools.conf
file:
<objectType>[:<objectType>[...]] | <toolName> | <actionToRun> | <args>

Parameters

Parameter

Description

objectType
The name of the target object. The object can be an item, label, changeset, or branch. To combine objects, use 
:
to separate them,
toolName
The name of the tool you want the context menu to display.
actionToRun
The path or environment variable:
  • pathToExecutable
    : the absolute path to the target application.
  • %PATH_TO_TOOL_EXE%
    : the name of the environment variable that contains the path to the target application.
    You don’t need to escape or protect spaces.
args
The arguments line to pass to the target application. There are three supported placeholders:
  • @object
    : replaces with the object name.
  • @repository
    : replaces with the repository of the object.
  • @wkpath
    : replaces with the current workspace path.
    If the replaced values contain blank spaces, you need to surround them with quotes.

externaltools.conf
file example

Refer to the following example of a valid 
externaltools.conf
file:
item | Open with sublime | C:\Program Files\Sublime Text 3\subl.exe | "@object"label:changeset:branch | Create new code review... | /usr/bin/createcodereview | "@object@@repository" @wkpathitem | Preview with PhotoScape | %PHOTOSCAPE_PATH% | "@object"
Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择（Cookie 设置）

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标（此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见，一些页面是机器翻译的，可能包含不准确的内容。如有信息不一致的情况，以英文版本为准。

  • 在本页上

    • Create the externaltools.conf file

      • Syntax

      • Parameters

    • externaltools.conf file example

报告此页面的问题