PC Gamer first reported the release as the culmination of nearly two years of work. The creator’s Nexus Mods listing and reporting by Inven Global confirm that the September 17 upload is playable from beginning to end, with more than 30 combat encounters, more than 70 items, quests, dungeons, NPCs, cutscenes, puzzles, traders, and a functional camp. The catch is material for anyone considering adding it to an established save: this is an ambitious, third-party addition that deliberately sits at one of Baldur’s Gate 3’s most consequential transition points.
The mod’s scope is substantial by Baldur’s Gate 3 standards. It is not a cosmetic pack, an extra companion, or an encounter arena. Its purpose is to place a full exploration-and-combat region after Act 2’s Shadow-Cursed Lands and before the route to Rivington, extending a stretch of the game where the original campaign otherwise moves quickly toward Baldur’s Gate.
Version 0.8 is a beta release, despite the launch framing
The important qualification absent from the broad “out now” framing is that the available download is labeled version 0.8 and marked as beta by its author. SquallyDaBeanz says the campaign can be completed, but warns that game-breaking issues remain possible and recommends frequent saves.
That distinction should shape expectations. A playable beginning-to-end beta is a meaningful accomplishment for a community campaign built into a game as reactive and script-heavy as Baldur’s Gate 3. It is also different from a release that has accumulated months of compatibility testing across unusual party states, mod stacks, multiplayer configurations, and late-game quest outcomes.
The mod’s public bug tracker already shows reports involving cutscenes failing to play and locking the action bar, along with a separate report that existing saves would not load because of Osiris scripting errors. Those reports are not confirmation that every installation will fail, and no broad failure rate is available. They do, however, reinforce the creator’s own warning that this is a testable beta rather than a drop-in DLC equivalent.
Players should therefore treat a pre-install backup as part of the mod, not optional housekeeping. Back up the save folder before enabling it, especially if the party has a long-running campaign, a large mod list, or unfinished companion and camp events.
The expansion must be installed before leaving Act 2
The standard download is built to insert the Chionthar Wilds into the base campaign between Acts 2 and 3. According to the Nexus listing, it supports existing saves only if installed before the player leaves Act 2. Inven Global’s walkthrough of the release says the route begins by crossing the bridge that would normally advance the campaign toward Act 3.
That installation timing creates the central practical risk. A player who has already crossed the transition point cannot simply load an Act 3 save and expect the new region to appear. The mod is changing the path through a campaign handoff, rather than opening a separate destination available at any time.
Players approaching the end of Act 2 should clear unfinished business before moving forward. Once the mod’s sequence is complete and the party reaches the subsequent point of no return, the creator says neither the original Act 2 areas nor the Chionthar Wilds will remain accessible. Inven Global also reports a specific warning that unresolved camp events may block the eventual move into Act 3.
That makes the expansion better suited to a planned playthrough than an impulsive late-game install. Finish companion conversations, clear desired Act 2 content, make a clean manual save, install and enable the mod, then enter the new region. Anyone trying it on a heavily customized save should preserve a second, untouched save from before the Act 2 exit.
QuickStart is useful for testing, but it has major restrictions
SquallyDaBeanz provides two downloads. The main package integrates the content into a conventional campaign and is the relevant choice for a party nearing the end of Act 2. The alternate QuickStart build launches players into the expansion after beginning a new game, with options for equipment, party experience, and hirelings.
QuickStart is useful for players who want to inspect the campaign without committing a main save. It is also the more constrained package. The creator warns that QuickStart users cannot return to Acts 1 and 2, cannot access Withers for respecs, and cannot use Illithid Powers without cheats.
Those restrictions make QuickStart a demo route rather than the best way to experience the expansion as part of Baldur’s Gate 3’s story. It is a sensible option for evaluating map design, combat difficulty, loot, and stability. It is a poor substitute for a full campaign save if the player wants normal progression systems, party respecs, and the original game’s broader continuity.
The mod is balanced around parties from levels 8 through 10, and its author says experience earned in the new area is artificially reduced to prevent the extra content from flattening Act 3’s challenge. That is a useful design decision, though it will not guarantee balance for every player. Level-cap extensions, stronger enemy overhauls, combat rebalances, and large collections of custom spells can all change the equation.
Larian supports modding, but this package remains third-party
Baldur’s Gate 3 has an official in-game Mod Manager following Larian’s Patch 7 modding rollout, and the Act Two Expansion can be activated there after installation. But it is distributed through Nexus Mods rather than Larian’s moderated mod.io catalog. Larian has said the game recognizes outside mods and labels them as third-party, a distinction that matters when diagnosing instability.
The project does not meet the criteria for Workshop or console distribution, according to the creator’s earlier project FAQ. This is a PC mod release, not a cross-platform Baldur’s Gate 3 addition. Console players should not assume that the official in-game mod browser will make it available.
The Nexus page also flags that some uploaded files have not been scanned. That does not establish that the mod is unsafe, nor does it single out this release from the wider reality of community modding. It does mean Windows users should download only from the verified project listing, scan the archive locally, avoid reposted installers, and be cautious of any executable presented as a required “mod manager” or fix.
For multiplayer, the creator says the expansion works provided every participant has the mod in the load order. As with other scripted Baldur’s Gate 3 mods, identical versions and matching load orders are the minimum baseline, not a promise that every combination of third-party content will behave reliably.
A deliberate limit on story reactivity
The Chionthar Wilds offer new dialogue, NPCs, lore, and cutscenes, but they do not attempt to reproduce the full consequences system of Larian’s original campaign. The creator has said choices in the new region will not carry into Act 3, and NPCs introduced there will not later appear in Baldur’s Gate. The mod also does not support speaking with animals or the dead.
Those omissions are a scope decision, not a minor missing feature. Baldur’s Gate 3’s branching dialogue, companion states, and reactive quest scripting are precisely what make unofficial expansions difficult to ship. By concentrating on combat and exploration while limiting downstream narrative dependencies, the project has a more realistic chance of remaining playable across a broad range of campaign states.
Players should approach Act Two Expansion as a sizeable side journey that preserves the original Act 3 as Larian built it, rather than as a seamless new chapter with equal narrative reactivity. For a beta, that boundary is sensible. The immediate consequence is straightforward: players who want the new region should install version 0.8 before their Act 2 exit, keep a clean save in reserve, and expect patches as its public testing finds the failures private playtesting did not.