Monster Hunter Wilds is set to receive a significant expansion later this year, as revealed in a video celebrating the open-world game's first anniversary. Series producer Ryozo Tsujimoto hinted that this add-on will be on a similar scale to Monster Hunter World's Iceborne expansion, though he kept specifics under wraps. He emphasized that this will be the final major update for the game.
Tsujimoto stated, "We are currently developing a large-scale expansion for Monster Hunter: Wilds, comparable to Monster Hunter World: Iceborne and Monster Hunter Rise: Sunbreak. More details will be shared this summer."
In addition to the expansion news, an update scheduled for February 18 was detailed. It will introduce Arch-Tempered Arkveld, 10-star Arc-Tempered monsters, and a special collaboration with Monster Hunter Stories 3, a spin-off launching next month. An anniversary event will make all previous awards and quests available again. Players logging in during this event will receive a free item pack, and past seasonal events will return on a weekly rotation. Starting February 18, nearly all previously released event quests will become permanent.
Tsujimoto also mentioned ongoing improvements to game stability and performance since Title Update 4, with further enhancements planned in the upcoming update. Capcom advises fans to follow its social media for more information as the date approaches.
The development team confirmed, "While this concludes major content updates, we are actively working on a large-scale expansion for Monster Hunter Wilds and look forward to revealing it this summer."
Monster Hunter Wilds has faced some challenges recently. Title Update 4, released late last year, brought numerous gameplay and balance adjustments, along with CPU/GPU optimizations, reduced loading times, and PC-specific improvements. A roadmap from December outlined plans to address issues affecting the PC version. Last month, a player discovered that PC performance was influenced by the number of DLCs owned, which Capcom acknowledged as an unintended bug. It will be fixed in Patch 1.040.03.01.
