Reforger Script Tools

Reforger Script Tools brings Enfusion Script language support and Arma Reforger Workbench compiler feedback to Visual Studio Code. Everything needed by the extension is included; no additional tools or runtimes are required.

Unofficial Project and Product Terms

Reforger Script Tools is an independent, unofficial project. It is not affiliated with, authorized by, endorsed by, or supported by Bohemia Interactive a.s.

Use of this extension with Bohemia Interactive games, tools, services, or content remains subject to all applicable end-user license agreements, terms of use, and content licenses, including but not limited to the Arma Reforger EULA and Arma Reforger Workshop Terms of Use. This extension is not designed or intended to circumvent those agreements, violate license restrictions, or enable others to do so. Content created or generated with this extension must be made and used only for Arma purposes, in accordance with the Arma Public License (APL) and its ArmaOnly condition where applicable. A mod that incorporates, adapts, or is distributed with another mod's content must preserve and comply with that content's applicable license terms, including any requirements for derivative works. Users are responsible for ensuring that their use and all resulting content comply with the agreements and licenses applicable to the Bohemia Interactive products and content they use.

Bohemia Interactive, Arma, Arma Reforger, and associated logos and designs are trademarks or registered trademarks of Bohemia Interactive a.s.

Features

• Enfusion Script syntax highlighting and semantic coloring without replacing your selected VS Code theme.
• Context-aware completion, snippets, signature help, hover information, and go to definition.
• Document symbols and indexing of Reforger base-game data.
• Editor errors and authoritative Workbench compiler results shown separately.
• Range formatting plus experimental automatic formatting while typing, including indentation, comment pairs, and preprocessor separators.
• Semantic, punctuation-colored, or native VS Code bracket presentation.
• Automatic installed add-on discovery and PAC-backed base-game indexing.
• Automatic and manual script validation through the Workbench NET API.
• Script and resource search with Ctrl+Alt+F.
• Bundled MCP server for script, resource, add-on, and official documentation search, plus Workbench inspection and editing.

The extension recognizes .c files under Scripts or scripts directories as Enfusion Script.

Workbench Integration

Workbench integration is disabled by default. On the first Enforce activation or explicit Workbench action, the extension asks whether it may enable the integration and install its managed bridge. Approval enables Workbench's local NET API, registers the per-user enfusion:// handler, installs the bridge, and changes reforgerScriptTools.workbench.enabled to true. That setting is also the durable approval for future bridge updates; no separate approval state is stored. If Workbench is open, restart it when prompted. If it is closed, setup completes without launching it. Declining records the setting as false while the other language and indexing features continue normally.

The extension reconnects automatically. The Workbench status item shows availability; selecting it while disabled opens the enablement prompt, while selecting it after enablement runs validation. Reforger Script Tools: Validate Scripts in Workbench also runs validation manually. Workbench validation is requested at session start and after an eligible save. By default, it also saves the active dirty script and validates after three seconds without typing; disable Workbench NET API: Save and Validate On Idle to use only explicit saves and manual validation.

These steps follow Bohemia Interactive's official Resource Manager options documentation.

MCP Server

Installing the extension also installs its local MCP Runtime. VS Code discovers Reforger Script Tools automatically in Chat and manages the bundled stdio process; no .vscode/mcp.json, separate runtime, Rust toolchain, or open Enforce document is required. Official Wiki and workspace evidence remain available when Workbench integration is disabled or Workbench is closed.

Native MCP discovery does not enable Workbench integration, contact the Workbench NET API, or install the managed bridge. Its compact authoring profile provides one cross-authority search plus exact evidence handoffs and common Workbench lifecycle tools. The native VS Code definition selects that profile when it starts the MCP process; profiles do not change within a running session. External clients can select specialized inspection, editing, administration, or complete compatibility profiles at process start. Enable Workbench integration separately when live editor capabilities are wanted.

The same one-time extension install contributes three Agent Skills to VS Code Chat:

• reforger for evidence-led research, implementation, compiler validation, reload, and live verification;
• reforger-deep-dive for comprehensive read-only diagnosis and evidence dossiers;
• reforger-workbench-edit for explicitly requested live editor mutations with inspection, confirmation, persistence, and readback.

The skills are plain, client-neutral Open Agent Skills files packaged with the extension. Discovering or invoking them does not enable Workbench. With Workbench disabled, they use offline Wiki, Game Data, and workspace evidence and report live gates as unavailable without contacting or changing Workbench.

For Codex or another MCP client outside VS Code, run Reforger Script Tools: Copy MCP Configuration and choose Codex TOML or generic MCP JSON. The copied entry launches the same bundled runtime with the current workspace and External Indexes scope. Copy it again after changing that scope or upgrading the extension because external clients do not receive VS Code's native definition updates. Clients that support Agent Skills can also consume the packaged skills/ library; the MCP configuration command configures the server only and does not modify another client's skill installation.

Settings

Open Preferences: Open Settings (UI) and search for Reforger Script Tools, or add the keys to settings.json.

For the default "semantic" bracket mode, the extension contributes and maintains these language-specific user settings when Enforce support activates:

"[enforce]": {
  "editor.bracketPairColorization.enabled": false,
  "editor.matchBrackets": "never"
}

The "punctuation" mode uses the same editor settings. The "vscode" mode sets them to true and "always" so native bracket coloring and matching take over.

Customize Semantic Colors

The previous custom color theme has been removed. The extension now supplies default Enfusion Script colors through VS Code's native semantic-token settings without replacing your selected theme. VS Code applies these defaults automatically, so they do not appear in User Settings (JSON) until you add your own overrides.

To change a color:

1. Open the Command Palette with Ctrl+Shift+P.
2. Run Preferences: Open User Settings (JSON).
3. Add the selectors you want to override under editor.semanticTokenColorCustomizations.rules.

For example:

{
  "editor.semanticTokenColorCustomizations": {
    "rules": {
      "class:enforce": "#4EC9B0",
      "function:enforce": "#DCDCAA",
      "reforgerField:enforce": "#9CDCFE",
      "keyword:enforce": "#569CD6",
      "comment:enforce": "#6A9955",
      "string:enforce": "#CE9178",
      "reforgerPunctuation:enforce": "#D4D4D4"
    }
  }
}

Only the selectors included in the user's settings are changed; all others keep the extension defaults. The :enforce suffix limits each rule to Enfusion Script. Available selectors are:

class:enforce, enum:enforce, type:enforce, typeParameter:enforce, function:enforce, reforgerField:enforce, variable:enforce, parameter:enforce, enumMember:enforce, number:enforce, operator:enforce, reforgerPunctuation:enforce, keyword:enforce, comment:enforce, string:enforce, and reforgerPreprocessor:enforce.