Add Warcraft III 3.0 support news

Author: Frotty

README.md

@@ -70,7 +70,7 @@ Adding a standard library doc page works almost the same as tutorials.
 
 The site uses [`pagefind`](https://pagefind.app/) for fully local static search. No external API key is required.
 
-**The index is generated automatically by CI on every deploy** — see
+**The index is generated automatically by CI on every deploy.** See
 [`.github/workflows/pages.yml`](.github/workflows/pages.yml). It builds the
 site, runs Pagefind against the *built* `_site`, and deploys the result to
 GitHub Pages. Because the index is rebuilt from the actual content on every
@@ -94,7 +94,7 @@ In repo **Settings → Pages → Build and deployment**, set **Source** to
 2. Generate the index into `_site/pagefind`: `npx -y pagefind@1.5.2 --site _site`
 3. Serve `_site` (e.g. `npx -y serve _site`). Search loads from `/pagefind/pagefind.js`.
 
-Repeat steps 1–2 after content changes you want reflected in local search.
+Repeat steps 1-2 after content changes you want reflected in local search.
 Prerequisite: Node.js (for `npx pagefind`).
 
 ### Jenkins

_config.yml

@@ -44,6 +44,9 @@ kramdown:
   entity_output: as_char
   toc_levels: 1..6
   smart_quotes: lsquo,rsquo,ldquo,rdquo
+  typographic_symbols:
+    mdash: "---"
+    ndash: "--"
   input: GFM
   hard_wrap: false
   footnote_nr: 1

_doc/features/agents.md

@@ -54,4 +54,4 @@ Without the flag, `grill` simply asks during setup.
 
 ## Keeping It Up to Date
 
-The template is versioned. `grill install` detects when a project's `AGENTS.md` was generated from an older template and suggests refreshing it. Commit the file to version control so the whole team — and their agents — benefit.
+The template is versioned. `grill install` detects when a project's `AGENTS.md` was generated from an older template and suggests refreshing it. Commit the file to version control so the whole team, including their agents, benefits.

_doc/features/backends.md

@@ -12,7 +12,7 @@ redirect_from:
   - /tutorials/lua-jass-shim.html
 ---
 
-WurstScript compiles to either **Jass** or **Lua**. The goal is to write code once and have it behave identically on both backends — no conditional code paths, no per-backend workarounds in user space.
+WurstScript compiles to either **Jass** or **Lua**. The goal is to write code once and have it behave identically on both backends, with no conditional code paths or per-backend workarounds in user space.
 
 ## Choosing a Backend
 
@@ -28,15 +28,15 @@ Jass is the default and works well for classic and pre-Reforged patches. Lua tar
 
 Jass and Lua have different runtime semantics in several areas. The most common differences that affect real maps:
 
-**Null handles.** In Jass, calling a native with a `null` argument is valid — the function returns a type-appropriate zero value. In plain Lua, the same call raises a nil error and crashes.
+**Null handles.** In Jass, calling a native with a `null` argument is valid: the function returns a type-appropriate zero value. In plain Lua, the same call raises a nil error and crashes.
 
 **Handle IDs.** `GetHandleId` in Jass returns stable integers across a session, commonly used as table keys or for comparisons. In Lua, the equivalent is not stable across sessions and is a known cause of desyncs.
 
 **Uninitialized variables.** Jass initializes all variables to zero values (`0`, `0.0`, `false`, `""`, `null`). Lua leaves uninitialized variables as `nil`, causing type errors when first used.
 
 ## The Jass Shim Pass
 
-To close these gaps, the compiler applies a dedicated **Jass shim pass** to all generated Lua code. This pass inserts targeted emulation so that Lua behaves like Jass for the cases above — without any changes needed in user code.
+To close these gaps, the compiler applies a dedicated **Jass shim pass** to all generated Lua code. This pass inserts targeted emulation so that Lua behaves like Jass for the cases above, without any changes needed in user code.
 
 ### Null-safe natives
 
@@ -50,11 +50,11 @@ Null handle arguments return the same defaults as Jass instead of erroring:
 | `GetUnitName(null)` | `""` | nil error | `""` |
 | `GetHandleId(null)` | `0` | nil error | `0` |
 
-This applies across the native surface — integer, real, boolean, and string return types all fall back to their Jass defaults when called with null handles.
+This applies across the native surface. Integer, real, boolean, and string return types all fall back to their Jass defaults when called with null handles.
 
 ### Handle ID replacement
 
-All `GetHandleId` usage is replaced by the compiler with a safe alternative that produces consistent, desync-free identifiers. This is transparent — the replacement behaves the same way as the Jass `GetHandleId` for the purposes code actually relies on.
+All `GetHandleId` usage is replaced by the compiler with a safe alternative that produces consistent, desync-free identifiers. This is transparent; the replacement behaves the same way as the Jass `GetHandleId` for the purposes code actually relies on.
 
 ### Uninitialized variable defaults
 

_doc/features/map-formats.md

@@ -14,19 +14,19 @@ WurstScript supports both of Warcraft III's map storage formats: the classic MPQ
 
 ## MPQ Archives
 
-`.w3x` and `.w3m` files are MPQ archives — binary containers that pack all map assets and data into a single file. This is the traditional format and remains the default output of the World Editor.
+`.w3x` and `.w3m` files are MPQ archives, binary containers that pack all map assets and data into a single file. This is the traditional format and remains the default output of the World Editor.
 
 Wurst reads MPQ archives natively for building and running. No unpacking step is needed.
 
 ## Map Folders
 
 The Reforged World Editor can also load and save maps as plain folders, as long as the folder name ends in `.w3x` or `.w3m`. All the files that would normally be packed into the MPQ archive are stored directly on disk instead.
 
-Wurst supports map folders as a first-class input. A map stored as a folder behaves identically to a packed archive from Wurst's perspective — open, build, and run work the same way.
+Wurst supports map folders as a first-class input. A map stored as a folder behaves identically to a packed archive from Wurst's perspective: open, build, and run work the same way.
 
 **Why use folders:**
 
-- Full version control over map data — every file is a plain file, so diffs and history work naturally
+- Full version control over map data because every file is a plain file, so diffs and history work naturally
 - No binary merge conflicts
 - Works well with the Export to Folder workflow described below
 
@@ -38,7 +38,7 @@ The VS Code extension can convert an existing MPQ map to folder format directly:
 2. Use **Export to Folder** from the context menu or command palette.
 3. The extension unpacks the entire archive into a new folder with the same `.w3x`/`.w3m` name.
 
-From that point, the folder can be opened in the World Editor and used with Wurst exactly like the original archive — but now all files are accessible individually for editing, scripting, and version control.
+From that point, the folder can be opened in the World Editor and used with Wurst exactly like the original archive, but now all files are accessible individually for editing, scripting, and version control.
 
 ## Which Format to Use
 

_doc/features/vscode.md

@@ -10,17 +10,17 @@ author: Frotty
 layout: doc
 ---
 
-The [Wurst VS Code extension](https://marketplace.visualstudio.com/items?itemName=peterzeller.wurst) turns VS Code into a full Warcraft III development environment. Installing it is all that is needed to get started — the extension manages the compiler and CLI automatically.
+The [Wurst VS Code extension](https://marketplace.visualstudio.com/items?itemName=peterzeller.wurst) turns VS Code into a full Warcraft III development environment. Installing it is all that is needed to get started because the extension manages the compiler and CLI automatically.
 
 ## Language Support
 
 The extension provides first-class editing support for `.wurst` files:
 
 - **Syntax highlighting** and semantic tokens
-- **Hover documentation** for functions, types, and variables — including native documentation pulled from [JassDoc](https://github.com/lep/jassdoc) where available
+- **Hover documentation** for functions, types, and variables, including native documentation pulled from [JassDoc](https://github.com/lep/jassdoc) where available
 - **Inlay hints** for type information and code flow
 - **Go-to-definition** and **find references** across the full project
-- **Inline diagnostics** from the compiler — errors and warnings appear in the editor as you type
+- **Inline diagnostics** from the compiler; errors and warnings appear in the editor as you type
 - **Code completion** for identifiers, packages, and native functions
 
 ## Build and Run
@@ -50,7 +50,7 @@ Wurst supports both MPQ-era classic installations and CASC-backed clients such a
 
 The extension is the editor-facing part of Wurst’s broader patch-aware workflow. It detects the available Warcraft III client when possible and uses the selected game data for previews and map tooling, whether the project targets classic Jass or modern Reforged Lua.
 
-Wurst can also read assets directly from the Warcraft III installation — not only from files inside your project. This works with both Reforged CASC storage and classic Warcraft III MPQ installations.
+Wurst can also read assets directly from the Warcraft III installation, not only from files inside your project. This works with both Reforged CASC storage and classic Warcraft III MPQ installations.
 
 For MPQ-era classic installations, Wurst follows the game’s layered archive model, resolving files through the base game, expansion, locale, and patch archives so patched assets override their older versions:
 
@@ -64,13 +64,13 @@ That means the asset browser, object metadata, icons, model viewer, textures, an
 
 - **Browse** the archive file tree without unpacking
 - **Extract** individual files from the archive
-- **Export to Folder** — unpacks the entire archive into a `.w3x` or `.w3m` folder for use with version control or the map folder workflow (see [Map Formats](/features/map-formats.html))
+- **Export to Folder**: unpacks the entire archive into a `.w3x` or `.w3m` folder for use with version control or the map folder workflow (see [Map Formats](/features/map-formats.html))
 
 ## Command Palette
 
 Common Wurst actions are available via `F1`:
 
-- `Wurst: Run` — build and launch the map
-- `Wurst: Build` — compile without running
-- `Wurst: Install` — install/update the toolchain
-- `Wurst: New Wurst Project` — project scaffolding
+- `Wurst: Run`: build and launch the map
+- `Wurst: Build`: compile without running
+- `Wurst: Install`: install/update the toolchain
+- `Wurst: New Wurst Project`: project scaffolding

_doc/manual.md

@@ -281,7 +281,7 @@ temp.addAction(function action)
 ### Null-safe operator
 
 The null-safe operator `?.` accesses a member only when the receiver is not `null`.
-The receiver is evaluated exactly once; if it is `null`, the access is skipped entirely — for a method call this means the arguments are not evaluated either — and the result of the whole expression is `null`.
+The receiver is evaluated exactly once. If it is `null`, the access is skipped entirely. For a method call, this means the arguments are not evaluated either, and the result of the whole expression is `null`.
 
 ```wurst
 u?.kill()                    // only kills the unit if u is not null

_layouts/compress.html

@@ -2,7 +2,7 @@
 # Jekyll layout that compresses HTML
 # v3.0.4
 # http://jch.penibelst.de/
-# © 2014–2015 Anatol Broder
+# © 2014-2015 Anatol Broder
 # MIT License
 ---
 

_news/map-folders-mpq-lua-guardrails.md

@@ -18,15 +18,15 @@ This means you can open, build, and run a map that lives as an unpacked director
 
 The VSCode extension gained an MPQ inspector that lets you browse the contents of a `.w3x`/`.w3m` file directly in the editor without needing the World Editor.
 
-From there you can extract individual files or use the new **Export to Folder** action, which unpacks the entire map archive into a folder — matching the `.w3x`/`.w3m` folder format described above. This pairs well with the map folder support: open a legacy map, export it to a folder, and from that point on work with it as a plain directory.
+From there you can extract individual files or use the new **Export to Folder** action, which unpacks the entire map archive into a folder matching the `.w3x`/`.w3m` folder format described above. This pairs well with the map folder support: open a legacy map, export it to a folder, and from that point on work with it as a plain directory.
 
 The inspector also has better asset integration now. Icons can be previewed directly, and Ctrl-clicking asset paths opens a preview for the referenced model or texture, making it much faster to check whether an imported path resolves to the file you expected.
 
 Under the hood, there is now rudimentary read support for most Warcraft III binary formats. That gives the tooling a broader view into map data and lays the groundwork for richer inspection and editor features in future updates.
 
 ## Lua Jass Shimming
 
-The Lua backend now applies a dedicated **Jass shim pass** to the generated Lua code. The goal is to emulate Jass runtime behavior in places where plain Lua would act differently — so that code written for the Jass backend keeps working on Lua without any user-side changes.
+The Lua backend now applies a dedicated **Jass shim pass** to the generated Lua code. The goal is to emulate Jass runtime behavior in places where plain Lua would act differently, so that code written for the Jass backend keeps working on Lua without any user-side changes.
 
 The most common case is natives called with `null`. In Jass, this is well-defined: most natives simply return a default value. In plain Lua the same call raises a nil error and crashes. With the shim pass, the behavior matches Jass:
 
@@ -36,7 +36,7 @@ GetUnitX(null)  -- Jass: returns 0.0
                 -- shimmed Lua: returns 0.0
 ```
 
-The same principle applies across the native surface — integer, real, boolean, and string returns all fall back to their Jass defaults when called with null handles, rather than erroring.
+The same principle applies across the native surface: integer, real, boolean, and string returns all fall back to their Jass defaults when called with null handles, rather than erroring.
 
 **Handle ID safety.** `GetHandleId` in Jass returns stable integers that code commonly stores and compares. In Lua the equivalent is fragile and a known source of desyncs. The compiler replaces `GetHandleId` usage with a safe alternative that avoids this class of problem entirely.
 

_news/warcraft-3-reforged-3-support.md

@@ -0,0 +1,38 @@
+---
+title: Support for Warcraft III 3.0
+excerpt: Reforged 3.0 joins WurstScript's supported patch targets, with updated tools, standard library support, and new native APIs.
+date: 2026-09-13
+image: /assets/images/news/wurst-perfect.png
+layout: newsarticle
+author: Frotty
+---
+
+Warcraft III: Reforged 3.0.0 has arrived alongside **Forsaken Kingdom**, the first new official Warcraft III campaign in more than two decades. The paid campaign follows the last days of Lordaeron and the rise of the Forsaken, while the free 3.0 update brings substantial changes for players and mapmakers alike.
+
+## Patch 3.0 Joins the Supported Targets
+
+WurstScript supports building maps for different Warcraft III patches rather than tying every project to one game version. Projects can target older patches or current Reforged releases and compile to either Jass or Lua, with the appropriate core definitions and standard library for the selected target.
+
+Support for Reforged 3.0 has now been added to the tools and standard library, including the patch's new flows and native API additions. You can select the version and backend that fit your map while still taking advantage of the latest functionality when targeting 3.0.
+
+## Updating an Existing Project
+
+Grill keeps an existing project's patch target unchanged, so `grill install` will not automatically move a project from 2.0 to 3.0. To opt in, update the target in `wurst.build`:
+
+```yaml
+wc3Patch: v3.0
+```
+
+Make sure the Wurst VS Code extension is up to date, then refresh the project dependencies:
+
+```bash
+grill install
+```
+
+The command updates dependencies such as the standard library and prepares the core JASS definitions for the selected patch. Your existing Jass or Lua backend choice remains unchanged. New projects, and older projects without a recorded `wc3Patch`, are offered the patch selector by Grill with 3.0 as the default.
+
+The new scripting surface includes natives for resetting a unit's attack cooldown, changing the remaining cooldown of a unit ability, enabling or disabling a unit's aura abilities, and more. The update also adds a broad set of World Editor features, including expanded lighting, fog and water controls, a free camera, per-player HUD selection, and new doodad and minimap options.
+
+Whether you are maintaining an older Jass map, building a modern project with Lua, or moving between supported patch targets, Wurst lets you keep the workflow that fits your project. Update your Wurst installation and project dependencies through the usual workflow to build for 3.0.
+
+Read the full [Warcraft III: Reforged: Forsaken Kingdom patch notes](https://us.forums.blizzard.com/en/warcraft3/t/warcraft-iii-reforged-forsaken-kingdom-patch-notes/38400).