Highlight multi-patch support - #69
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1472b4dc3f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| | Target | Typical output | Installed game data | | ||
| | --- | --- | --- | | ||
| | Classic / pre-Reforged patch | Jass | Layered MPQ archives | |
There was a problem hiding this comment.
For projects targeting Warcraft III 1.30/1.31, the target is still pre-Reforged/classic, but those installed clients use CASC-backed game data rather than the layered MPQ files listed here. As written, the table sends those users down the wrong game-data workflow; please narrow the MPQ row to older MPQ-era patches or add a separate pre-Reforged CASC row for 1.30/1.31.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 400182c01f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| 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 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: |
There was a problem hiding this comment.
For projects targeting classic CASC clients such as Warcraft III 1.30/1.31, this sentence still describes “classic installations” as following the layered MPQ archive model, even though the section now defines those clients as classic and CASC-backed. Those users will not have the listed war3.mpq/war3patch.mpq game-data archives, so this should be scoped to older MPQ-era installations instead of all classic installations.
Useful? React with 👍 / 👎.
|
@codex review Addressed the remaining P2 in 69fa382 by scoping the layered MPQ archive description to MPQ-era classic installations. Also included the website component polish pass: scoped navigation styling, improved card focus/hover behavior, responsive spacing, image alt text, navigation labeling, and safe external-link attributes. |
|
Codex Review: Didn't find any major issues. 🚀 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
What changed
Why
Wurst supports multiple Warcraft III generations across the toolchain, not only inside VS Code. The site should make that patch-aware workflow visible to users targeting older clients as well as Reforged.
Validation
npm testgit diff --check