{"id":38787,"date":"2026-04-17T18:14:04","date_gmt":"2026-04-17T22:14:04","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=38787"},"modified":"2026-04-17T18:20:27","modified_gmt":"2026-04-17T22:20:27","slug":"windrose-v0-10-0-2-patch-notes","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/windrose-v0-10-0-2-patch-notes\/","title":{"rendered":"Windrose v0.10.0.2 Patch Notes: Connectivity, Boss Scaling & Invite Codes"},"content":{"rendered":"\n

The first major hotfix for Windrose<\/em> has arrived, and it brings more than just routine bug squashes. On Friday, April 17, the development team will roll out version 0.10.0.2.54-451ec92d<\/strong>, a patch designed to address critical community pain points\u2014starting with online stability<\/a>. While offline mode remains fully playable, online modes will experience scheduled downtime for approximately one<\/a> hour (from 12 AM PDT \/ 3 AM EDT \/ 7 AM GMT \/ 9 AM CEST). The headline fix? Disabling the access token generation cooldown for dedicated servers, a change expected to significantly reduce connectivity issues for host players. Beyond that, the update introduces smarter version-checking to prevent mismatched server connections, a streamlined 1\u201332 character invite code system (replacing the old 8-character minimum), and critical corrections to boss scaling for parties larger than three. Even the main menu gets a humble tweak\u2014the \u201cWishlist Now\u201d link has been removed, with the developers openly admitting, \u201cThat was actually stupid.\u201d Whether you’re a dedicated host or a solo sailor, this patch lays essential groundwork for smoother seas.<\/p>\n\n\n\n

Connectivity Fixes: A Stronger Foundation for Online Play<\/h2>\n\n\n\n

The most significant technical improvement in this patch targets dedicated servers directly. Previously, a cooldown on access token generation could prevent dedicated hosts from establishing stable connections, leading to frustrating dropouts and failed join attempts. By disabling that cooldown entirely, the development team has removed a major bottleneck. While the patch notes<\/a> acknowledge that “more connectivity fixes are underway and are currently being tested,” this initial step should provide immediate relief for server operators and their crews.<\/p>\n\n\n\n

Additionally, the update introduces a long-overdue version-checking mechanism. Before this fix, clients would attempt to connect to a server without verifying whether that server was running a compatible game version. The result was often a crash or an unresponsive black screen. Now, if a server is outdated, players will see a clear UI error message explaining the problem\u2014saving time, confusion, and unnecessary troubleshooting.<\/p>\n\n\n\n

Invite Codes: Simpler, Shorter, Smarter<\/h2>\n\n\n\n

Small quality-of-life changes often make the biggest daily difference. The removal of the 8-character minimum limit for invite codes falls squarely into that category. Players can now generate or enter codes ranging from just 1 character up to 32 characters. This change makes manual code sharing faster, reduces typos, and eliminates the awkward padding that longer codes sometimes required. For streamers, content creators, and community event organizers, this is a subtle but welcome improvement.<\/p>\n\n\n\n

Boss Scaling Fixed for Large Parties<\/h2>\n\n\n\n

One of the more frustrating PvE bugs involved boss encounters with more than three players. The scaling system would fail to adjust enemy health and damage properly, making fights either impossibly difficult or disappointingly trivial depending on the exact party composition. With this patch, boss scaling now functions correctly when four or more players initiate a fight. This fix encourages larger co-op groups without breaking encounter balance\u2014essential for a game that thrives on shared adventures.<\/p>\n\n\n\n

Combat and AI: Thomas Richards, Grenadiers, and the Plague Crusher<\/h2>\n\n\n\n

Several enemy behavior fixes stand out in this update. Thomas Richards<\/strong>, a boss known for his aggressive Grab attack, previously suffered from two distinct bugs: he would occasionally switch targets mid-sprint, and he would sometimes chain his Grab attack immediately after throwing bombs\u2014creating nearly unavoidable damage sequences. Both issues are now resolved, making his fight more predictable and fair.<\/p>\n\n\n\n

Grenadiers<\/strong> also received behavioral corrections. Their grenades now pass through players and other NPCs as originally intended, preventing accidental friendly fire and weird collision blocks. More importantly, their aggro logic has been tightened: they no longer lose targets as quickly, and they will correctly close the distance if a player moves too far away. This makes Grenadiers more threatening but also more consistent to outplay.<\/p>\n\n\n\n

The Plague Crusher<\/strong>, a larger enemy type, suffered from an embarrassing but impactful bug: it would get stuck in trees. The fix allows it to correctly destroy trees while moving, restoring both its intended pathfinding and the environmental destruction that makes encounters feel dynamic.<\/p>\n\n\n\n

Weapons, Abilities, and Visual Effects<\/h2>\n\n\n\n

The Plague Halberd<\/strong> special attack previously displayed its VFX floating above the deck during boarding actions\u2014a disorienting visual glitch that broke immersion. That effect now correctly anchors to the weapon and environment. The Dragonbreath Blunderbuss<\/strong> also sees a correction: fire damage numbers now display properly alongside the correct VFX, giving players accurate combat feedback.<\/p>\n\n\n\n

The Overpenetration talent<\/strong>, which likely affects projectile behavior, now functions as described in its tooltip\u2014though the patch notes<\/a> do not specify the exact nature of the previous failure. Musket movement while aiming has been smoothed out, addressing a common complaint about jerky or unresponsive aiming controls.<\/p>\n\n\n\n

Healing and Consumables: No More Interruptions<\/h2>\n\n\n\n

A subtle but impactful fix addresses healing potion effects. Previously, using another consumable or performing a dash could prematurely cancel an active healing potion’s effect, leaving players with less health than expected and wasting valuable resources. This interruption no longer occurs, making healing more reliable during intense combat sequences.<\/p>\n\n\n\n

The Boar Whistle and Inventory Edge Cases<\/h2>\n\n\n\n

One of the more creative bug fixes involves the Boar Whistle<\/strong>, an item that could become permanently unobtainable if it fell into the Altar’s bowl at the exact moment a player’s inventory was full. The game now handles this edge case properly, ensuring that the whistle is either granted or recoverable rather than lost to an unintended black hole.<\/p>\n\n\n\n

Carrying Animations and Crash Fixes<\/h2>\n\n\n\n

The animation for carrying objects has been fixed\u2014though the patch notes do not elaborate on what was broken, carrying objects is a core interaction in many adventure and survival games, so this fix likely improves both visual polish and functional clarity. Additionally, a crash caused by ship spawns in Tortuga has been resolved, removing a stability<\/a> risk in that specific location.<\/p>\n\n\n\n

Extended Server Timeout and Dedicated Server Documentation<\/h2>\n\n\n\n

For dedicated server operators, two important changes arrive. First, the host server start timeout has been extended to 5 minutes<\/strong> (up from a presumably shorter limit). This allows more time for world version updates, particularly useful for larger save files or modded setups. Second, the DedicatedServer.md<\/code> documentation file now contains concrete examples for WorldPresetType<\/code> using the values \"Easy\"<\/code>, \"Medium\"<\/code>, and \"Hard\"<\/code>. This small documentation improvement reduces guesswork for new server administrators.<\/p>\n\n\n\n

Localization Fixes and the “Stupid” Menu Link<\/h2>\n\n\n\n

Numerous localization errors have been corrected across multiple languages, improving accessibility for non-English players. And in a moment of refreshing developer honesty, the “Wishlist Now” link has been removed from the main menu with the note: “That was actually stupid.” For a game that has already launched into early access or full release, leaving a wishlist call-to-action on the main menu was indeed confusing\u2014and its removal signals that the team is paying attention to player feedback and common sense.<\/p>\n\n\n\n

Practical Recommendations for Players<\/h2>\n\n\n\n

If you are hosting a dedicated server, apply this update as soon as possible. The access token change alone should improve stability, and the extended timeout gives you breathing room during updates. For regular players, downloading the patch before your next online session will prevent the new version-checking UI from blocking you from your favorite servers. Offline mode remains unaffected, so solo players can continue without interruption, but the combat and AI fixes are substantial enough to recommend updating regardless of playstyle.<\/p>\n\n\n\n

The patch notes explicitly state that more connectivity fixes are being tested and will arrive later. This suggests that while the current improvements are meaningful, the development team has identified additional underlying issues that require more time. Players should expect another connectivity-focused patch in the near future. For now, version 0.10.0.2.54-451ec92d delivers a cleaner, more stable, and less frustrating Windrose<\/em> experience\u2014especially for those sailing in crews of four or more.<\/p>\n\n\n\n

Windrose First Full Update Patch Notes<\/h2>\n\n\n\n

Connectivity Fixes:<\/strong><\/p>\n\n\n\n