Skip to content

Commit 07ea6de

Browse files
committed
Tighten Warcraft III 3.0 news post
1 parent 7e4228b commit 07ea6de

1 file changed

Lines changed: 9 additions & 17 deletions

File tree

Lines changed: 9 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,50 +1,42 @@
11
---
22
title: Support for Warcraft III 3.0
3-
excerpt: Reforged 3.0 joins WurstScript's patch targets with matching core definitions, native wrappers, and Grill-assisted alignment for Jass and Lua projects.
3+
excerpt: Warcraft III 3.0 is now supported by the Wurst tools and standard library.
44
date: 2026-09-13 00:00:00 +0200
55
image: /assets/images/news/reforged-3.0.png
66
layout: newsarticle
77
author: Frotty
88
---
99

10-
Warcraft III 3.0 is now a supported WurstScript target. The compiler tooling, core definitions, Grill workflow, and standard library have been updated so projects can opt into the new patch without giving up Wurst's support for older Warcraft III versions.
10+
WurstScript now supports Warcraft III 3.0. The tools include matching core JASS definitions, and the standard library provides Wurst wrappers for the new natives. Projects targeting 3.0 can compile to either Jass or Lua.
1111

12-
## Patch 3.0 Joins the Supported Targets
12+
## Update with Grill
1313

14-
WurstScript keeps the Warcraft III patch target separate from the script backend. A project can target an older patch or Reforged 3.0 and independently compile to Jass or Lua. The selected patch controls the matching native definitions and standard library, while the backend remains the project's choice.
15-
16-
For 3.0 projects, Wurst now provides the matching core JASS files and standard library. The standard library also wraps the new native APIs with Wurst-friendly functions for cameras, doodads and destructables, effects, frames, equipment and items, input, units, cinematics, terrain fog, and HD water.
17-
18-
## Aligning a Project with Grill
19-
20-
Make sure the Wurst VS Code extension is up to date so the current compiler and Grill CLI are installed. You can then compare the project's target with the installed Warcraft III client:
14+
Update the Wurst VS Code extension, then check the project against the installed Warcraft III client:
2115

2216
```bash
2317
grill patch
2418
```
2519

26-
This check is read-only. If Grill reports a mismatch, align the project explicitly:
20+
If Grill reports a mismatch, align the project:
2721

2822
```bash
2923
grill patch align
3024
```
3125

32-
Grill detects the exact client patch from the Warcraft III path configured in VS Code, or through automatic installation detection. Alignment updates `wc3Patch`, the official standard library branch, and Grill-managed core JASS together. It creates a `wurst.build.bak` backup and preserves custom standard library forks.
33-
34-
`grill install` does not silently change an existing project's patch target. It keeps the official standard library on the branch required by the current `wc3Patch` and suggests alignment when the installed client targets a different supported patch.
26+
This updates `wc3Patch`, the official standard library branch, and managed core JASS. Grill creates `wurst.build.bak` before changing the project and leaves custom standard library forks unchanged.
3527

3628
## Manual Update
3729

38-
You can still select 3.0 manually by changing `wurst.build`:
30+
To select 3.0 manually, change `wurst.build`:
3931

4032
```yaml
4133
wc3Patch: v3.0
4234
```
4335
44-
Then refresh the project dependencies and managed core definitions:
36+
Then run:
4537
4638
```bash
4739
grill install
4840
```
4941

50-
This changes only the Warcraft III target. Existing Jass or Lua backend settings remain unchanged, so projects can adopt the 3.0 APIs without changing how their map script is emitted.
42+
`grill install` does not change an existing patch target automatically. The project's Jass or Lua backend setting is unaffected by either update method.

0 commit comments

Comments
 (0)