WurstScript for Visual Studio CodeModern Wurst and Jass development for Warcraft III. Write typed WurstScript, compile to Jass or Lua, and build, test, inspect, and run maps without leaving VS Code.
One extension, complete setupThe extension installs and updates the Wurst compiler, bundled Java runtime, and Grill CLI automatically. No separate Java or compiler setup is needed.
Choose WurstScript compiler version in the Command Palette or the WurstScript status menu lets you install a specific stable release, including an older version. Selecting a specific version pins it across VS Code windows until you choose Follow latest stable in the picker. Install/Update honors the pin, and automatic update prompts stay quiet while pinned. The status item shows the installed compiler version. Update prompts follow stable semantic versions; development builds and prereleases are excluded. Installation and updates are managed under Supported on Windows, macOS, and Linux, with x64 and Arm64 builds where available. NixOS and custom environments can provide Java through Language intelligence
WurstScript itself provides packages, classes, closures, extension methods, compile-time code, unit testing, dependency management, and a large WC3-focused standard library. The same source can target Jass or Lua. Warcraft III inside VS CodeOpening a supported Warcraft III file selects a dedicated viewer or editor:
Packed
Object-data editors resolve rawcodes, game metadata, icons, base values, and trigger strings while keeping custom overrides editable.
The experimental Wurst: Open Map Terrain & Placement Editor command renders terrain, cliffs, water, doodads, units, items, and start locations from an exploded map, and lets you select, move, place, and delete units and items. Edits use VS Code undo/redo and save back to Installed-game assetsThe extension reads stock Warcraft III data directly from either Reforged CASC storage or legacy MPQ archives. Asset browsers and previews can resolve:
This powers searchable object catalogs, inline command-button icons, texture hovers, and models with their dependent textures. Run Wurst: Browse Warcraft III Assets from the Command Palette to inspect models, images and sounds, including without an open file or workspace. Model previews also provide a Browse assets toolbar button. Clicking an asset opens its preview and keeps the browser available; the existing code and object-editor pickers still select replacement values.
Build, test, and runSearch for Wurst in the Command Palette to:
ConfigurationMost projects need no custom settings. Common overrides are For projects edited primarily by agents, enable Asset CodeLens commands resolve on demand, and asset links defer filesystem lookups until resolution. Large scans yield to edits and cancellation. The language client delays opening hidden documents on the server until they become visible or an edit or request needs them; briefly opened, unedited files can avoid an open/close cycle entirely. Compilers supporting build-status notifications preserve this deferral during startup and automatic restarts too. Older compilers retain the initial-build readiness probe, which synchronizes pending documents. Wurst: Prepare AGENTS.md Update downloads the current WurstSetup template on demand and opens a diff against the project's guide. Copy Agent Prompt provides instructions for reconciling changes with local compiler documentation and project-specific rules. Guides created by the extension retain their original template as a comparison baseline; customized guides without a baseline get a conservative reconciliation prompt. Reviewing an update never overwrites Wurst: Copy Diagnostics produces a bounded report with repeated-error summaries. Routine inline-preview tracing is available at Debug level in the Wurst Inline Icons log channel. Learn WurstScript
Report extension problems in the wurst4vscode issue tracker. Extension developmentInstall a current Node.js LTS release and clone this repository alongside the
Before submitting a change, follow the validation checklist in AGENTS.md. For release packaging, also run For compiler/client startup changes, build the compiler with Place generated objects in World EditorRun wurst: Export object data (.w3o) for World Editor from the Command Palette and select your input map. It runs compiletime generation and saves the combined map and generated object data to You can save that edited map and use it as the Wurst input map again. Keep generated custom-object rawcodes stable so placements remain valid. Wurst removes and regenerates custom objects marked This command requires a compiler with |




