Compare Revisions

11 Windrose does not currently have a date-by-date public roadmap. What Kraken Express has published instead is a broad Early Access direction: the game is expected to stay in Early Access for about 1.5 to 2.5 years and grow by roughly 50 percent before the 1.0 release. The studio has also said it wants to turn launch feedback into a more detailed roadmap later, rather than locking one in before enough players have touched the live build.
22  
33 That distinction is the whole point of this page. Several Windrose pages and third-party articles blurred together three different things: current launch-state facts, pre-launch work-in-progress intentions, and genuine future roadmap promises.
44  
55 What Is Actually Confirmed Right Now
66  
7-TopicBest Current Public AnswerEarly Access lengthRoughly 1.5 to 2.5 yearsTotal growth target before 1.0About 50 percent more content than the Early Access launch buildDetailed date-by-date roadmapNot published yetFuture biome directionAt least one future biome is part of the plan; Ashlands is the clearest named exampleConsole version timingNo concrete console schedule or platforms announcedOfficial mod supportStill future-facing; the studio talks about making modding technically feasible
7+TopicBest Current Public AnswerEarly Access lengthRoughly 1.5 to 2.5 yearsTotal growth target before 1.0About 50 percent more content than the Early Access launch buildDetailed date-by-date roadmapNot published yetFuture biome directionAt least one future biome is part of the plan; Ashlands is the clearest named exampleConsole version timingNo concrete console schedule or platforms announcedOfficial mod supportStill planned for later; the studio talks about making modding technically feasible
88 How To Read the March 23 Steam Post
99  
1010 The March 23, 2026 Steam news post is one of the most cited Windrose sources, but it is often misread. Kraken Express explicitly called that list work in progress and said some of the mentioned features could change or never make it into the game. In other words, it was a pre-launch status update, not a final contractual launch checklist.
1111  
1212 That is especially important for multiplayer interpretation. The March 23 post discussed ideas like more players in co-op and co-op on one ship through battery manning, but the safer current official baseline after launch still comes from the FAQ and launch-facing messaging: up to 8 players total, one player commanding one ship, and broader shared-ship roles still being explored.
1313  
1414 What the March 23 Post Actually Listed
1515  
1616 The March 23 update is still useful because it showed the studio's immediate pre-launch priorities in unusually concrete language. Kraken Express highlighted more players in co-op, co-op battery manning on one ship, randomized loot, hold-to-gather, an FOV slider, rougher backing vocals for shanties, a dedicated Signal Fire building piece, DLSS and FSR support, controller improvements, a dismantling workbench, and target-lock switching. But the studio paired that list with a direct warning that the items were still work in progress and some might change or never make it into the game.
1717  
1818 That means the list is best used as roadmap context, not as a launch checklist. It tells you what the team believed players cared about most after the demo, and it gives useful insight into design priorities, but it does not override cleaner launch-facing sources when there is a conflict.
1919  
2020 Why the Multiplayer Items Need Extra Caution
2121  
2222 The multiplayer bullets from March 23 are where most downstream confusion came from. The post said the team was introducing battery manning and testing a higher co-op limit, while also warning that real performance would depend on player connections and server hardware and that the best gameplay experience still seemed to sit in the 1-to-4-player range. After launch, the official FAQ and launch messaging settled on a clearer public baseline: up to 8 players total, dedicated servers supported, one player commanding one ship, and broader multi-crew features still in the exploration stage.
2323  
2424 In practical wiki terms, that means you should not read the March 23 post as proof that Windrose launched with a fully realized Sea of Thieves-style shared-ship role system. It is better evidence of what Kraken Express wanted to test and pursue than of what it had definitively locked in.
2525  
2626 Launch-State Items Versus Future Items
2727  
2828 BucketHow To Treat ItLaunch-state factsUse official FAQ, launch post, Steam news, and dedicated-server guide. These describe what players can rely on now.March 23 pre-launch improvements postUse as context for what the team was trying to ship or improve, but not as a guarantee that every bullet landed exactly as previewed.Future roadmap promisesUse only where Kraken Express clearly frames something as later Early Access or post-launch work.
2929 Current Future-Content Direction
3030  
3131 More biomes beyond the launch three, with Ashlands remaining the most clearly documented planned biomeMore ships, ship equipment, and broader naval progression beyond the current launch lineupMore enemies, bosses, and points of interest across the Caribbean archipelagoMore weapons, armor, and general build diversityAdditional story content beyond the Chapter 1 launch campaignContinued quality-of-life work, onboarding cleanup, optimization, and multiplayer polish
3232  
3333 None of those categories currently have public dates attached to them. That is the central roadmap fact as of April 16, 2026: the direction is clear, but the sequencing is still intentionally open. Players should expect the studio to respond first to live friction and only later publish a more formal long-horizon schedule.
3434  
3535 Ashlands Status
3636  
3737 Ashlands is not live. It was revealed during the Crosswind-era August 2025 pivot messaging and remains one of the clearest future-biome ideas in public developer communication. But as of April 16, 2026, it is still planned content rather than current content.
3838  
3939 Multiplayer Features Still Best Treated as Future-Facing
4040  
4141 Deep multi-crew role play on a single ship as a settled, official launch featureAny player-cap expansion beyond the current official 8-player messagingStronger permissions, storage security, and broader social-governance tools for larger communities
4242  
4343 This does not mean the team is against those ideas. It means Kraken Express has not yet published the kind of hard confirmation that should let the wiki describe them as current features.
4444  
4545 Operational Priorities Launch Week Already Exposed
4646  
4747 Launch week also showed which roadmap items may get pulled forward by reality. Server-link issues, discovery friction, onboarding confusion, combat complaints, and social-trust complaints around chest security all surfaced immediately. Even without a formal roadmap, that response pattern gives strong evidence that early patches are likely to keep leaning toward stability, onboarding, and friction reduction before the biggest content expansions arrive.
4848  
4949 That reading is reinforced by the launch-day hotfix itself. Hotfix 0.10.0.1.6 dealt with localization, Nitrado link correction, and safer server-info visibility rather than new content. It was an operations-first update, which is exactly what you would expect from a team still stabilizing a popular Early Access release.
5050  
5151 Non-Negotiable Design Direction
5252  
5353 Windrose remains a PvE-first game. PvP is not part of the current core roadmap.The business model remains buy-to-play, not microtransaction-driven or live-service-driven.The team is prioritizing the PC build first, with console work only discussed as a later ambition.
5454  
5555 What a Detailed Roadmap Still Needs To Answer
5656  
5757 Which quality-of-life fixes come before the first major biome-sized content updateWhether deeper multi-crew ship play becomes a near-term or late-term Early Access goalHow much of the next content wave will focus on story progression versus systems expansionWhen, if ever, official mod support graduates from technical possibility to documented featureWhether console work remains post-1.0 only or starts overlapping with the later PC Early Access phase
5858  
5959 Those unanswered questions are not surprising when the live build is only days old. Kraken Express is still choosing not to over-promise. Until the studio publishes a more explicit roadmap, that restraint is part of the roadmap story.
6060  
6161 What Launch Week Suggests the Roadmap Needs First
6262  
6363 If you read the launch-week response closely, the first roadmap pressure points are obvious: onboarding clarity, combat feel, hosting ergonomics, and trust tools for multiplayer worlds. That is an inference from player and press reaction, not a quoted roadmap promise. But it is the clearest way to understand what kind of updates the community is likely to prioritize before bigger biome-sized expansions arrive.
6464  
6565 The launch-day hotfix already supports that reading. Kraken Express used its first post-release update on operational issues such as localization, Nitrado link correction, and safer server-info visibility rather than flashy new content. That is exactly how a team behaves when it is still stabilizing the live foundation.
6666  
6767 Where To Watch for Real Roadmap Changes
6868  
6969 The official Steam news feed for launch posts, hotfixes, and future roadmap messagingplaywindrose.com for long-form announcementsThe official Discord for fast-moving clarifications and community pain points
7070  
7171 See Also
7272  
73-Early Access - the live-launch state and current pricing/build factsLaunch Reception - what launch week revealed about player prioritiesMultiplayer - current co-op reality versus future-facing expectationsAshlands - the best-documented future biome so far
73+Early Access - the live-launch state and current pricing/build factsLaunch Reception - what launch week revealed about player prioritiesMultiplayer - current co-op reality versus later co-op ambitionsAshlands - the best-documented future biome so far