The ship combat damage bug in Windrose is a known issue that surfaced after a recent hotfix patch. Players report that cannon fire against enemy ships sometimes deals zero damage, even when shots visually connect with the hull. The root cause has been traced to a damage threshold check that was introduced to prevent exploit strategies involving rapid-fire micro-damage on specific ship components.
Specifically, the bug triggers when the calculated damage per shot falls below a certain threshold relative to the target ship's armor rating. In these cases, the game incorrectly applies a full nullification instead of a reduced damage value. This means that smaller caliber cannons -- such as 12lb guns -- are disproportionately affected when firing at heavily armored targets like Galleons or military frigates.
The issue is further compounded by desync problems in multiplayer sessions. When the host and client have slightly different positional data for the enemy ship, the server-side damage validation may reject hits that appear accurate on the client side. This creates a frustrating experience where players see their cannonballs impact the enemy hull with splash effects, but the enemy health bar does not move.
Additionally, certain ship upgrade modules -- particularly reinforced hull plating and damage redistribution modules -- have been found to interact incorrectly with the new threshold system, amplifying the bug's effects. Players who have invested in defensive upgrades on their own ships may also notice reduced incoming damage from AI enemies due to the same underlying calculation error.
What Causes the Ship Combat Damage Bug
The ship combat damage bug in Windrose is a known issue that surfaced after a recent hotfix patch. Players report that cannon fire against enemy ships sometimes deals zero damage, even when shots visually connect with the hull. The root cause has been traced to a damage threshold check that was introduced to prevent exploit strategies involving rapid-fire micro-damage on specific ship components.
Specifically, the bug triggers when the calculated damage per shot falls below a certain threshold relative to the target ship's armor rating. In these cases, the game incorrectly applies a full nullification instead of a reduced damage value. This means that smaller caliber cannons -- such as 12lb guns -- are disproportionately affected when firing at heavily armored targets like Galleons or military frigates.
The issue is further compounded by desync problems in multiplayer sessions. When the host and client have slightly different positional data for the enemy ship, the server-side damage validation may reject hits that appear accurate on the client side. This creates a frustrating experience where players see their cannonballs impact the enemy hull with splash effects, but the enemy health bar does not move.
Additionally, certain ship upgrade modules -- particularly reinforced hull plating and damage redistribution modules -- have been found to interact incorrectly with the new threshold system, amplifying the bug's effects. Players who have invested in defensive upgrades on their own ships may also notice reduced incoming damage from AI enemies due to the same underlying calculation error.
How to Verify If You Are Affected
To confirm whether you are experiencing this specific bug rather than a gameplay mechanic, follow a structured testing process. First, engage a low-level AI merchant ship in solo mode using your standard cannon loadout. Monitor the enemy health bar closely over 10-15 solid hits.
If the health bar does not move at all despite visible impacts, you are likely affected. To rule out armor-related damage reduction, check the enemy ship type in your combat log. A low-level merchant vessel should have minimal armor and take noticeable damage from any cannon type. You can also switch to a higher caliber cannon temporarily and test whether damage registers normally.
The following table summarizes common symptoms and their likely causes:
| Symptom | Likely Cause | Bug Confirmed? |
|---|---|---|
| Zero damage on all hits | Damage threshold bug | Yes |
| Reduced damage on armored targets | Normal armor mechanic | No |
| Intermittent damage in co-op | Desync issue | Partial |
| Damage works in solo but not co-op | Network validation error | Yes |
| Specific cannon type deals no damage | Cannon-armor threshold mismatch | Yes |
If your testing confirms zero damage across multiple engagements, document the enemy ship type, your cannon loadout, and your game version. This information is valuable for submitting a bug report through the official Windrose Discord or the Steam community forums, where developers actively track known issues.
Step-by-Step Fix Guide
Follow these steps in order to resolve or mitigate the ship combat damage bug. Each step addresses a different potential cause of the issue.
Step 1: Verify game files. Open Steam, right-click Windrose in your library, select Properties, go to Installed Files, and click Verify Integrity of Game Files. This process checks for corrupted or missing files that may have resulted from a partially applied patch. Wait for the verification to complete -- it typically takes 2-5 minutes depending on your drive speed. If any files are flagged as corrupted, Steam will automatically redownload them.
Step 2: Check cannon type vs enemy armor. Review the armor rating of the enemy ships you are engaging. If you are using 12lb cannons against a Galleon or military frigate, the damage threshold bug is likely the cause. Switch to 24lb or 36lb cannons if available, or target weaker ship classes until the bug is patched. You can check enemy armor ratings by using the spyglass tool, which displays detailed ship information including armor class.
Step 3: Update to the latest patch. Ensure your game is fully updated. Steam usually auto-updates, but you can force an update by right-clicking the game, selecting Properties, and checking the Updates tab. Set the game to Always Keep This Game Updated. If a hotfix has been released, the patch notes will typically mention ship combat fixes.
Step 4: Clear configuration cache. Navigate to your Windrose install directory and look for a folder called ConfigCache or LocalData. Delete the contents of this folder (but not the folder itself). This forces the game to rebuild its configuration files, which can resolve lingering issues from previous patches. Launch the game and test combat again.
Workarounds If the Fix Does Not Work
If the official fixes above do not resolve the issue, several community-discovered workarounds can help you continue playing while waiting for a developer patch. These workarounds do not fix the underlying bug but provide ways to work around it.
Workaround 1: Disengage and re-engage. If you notice that an enemy ship has stopped taking damage, sail away until the enemy ship despawns or resets its aggro. When you re-engage, the damage calculation resets and typically works correctly for the first few salvos. This is the most reliable workaround for single-player sessions.
Workaround 2: Switch cannon ammunition types. Some players report that switching from standard round shot to chain shot or grape shot bypasses the damage threshold check. While these ammunition types serve different purposes -- chain shot targets sails, grape shot targets crew -- they may register damage when standard shot does not. Experiment with different ammunition to find one that works against your current target.
Workaround 3: Target specific ship components. Instead of aiming at the main hull, try targeting the sails, masts, or rudder. Component damage uses a separate calculation from hull damage and is less likely to be affected by the threshold bug. Disabling the enemy ship's sails first also prevents them from fleeing, giving you more time to work around the damage issue.
Workaround 4: Use ramming and boarding. If cannon damage is completely non-functional, ramming damage and boarding combat bypass the cannon damage system entirely. Ram the enemy ship to deal impact damage, then initiate boarding to resolve the engagement through melee combat. This approach is slower but guarantees a resolution to the encounter.
Report persistent issues to the developers through the official bug tracker, including your game version, ship type, cannon loadout, and whether you are playing solo or in co-op. Community reports help prioritize fixes in upcoming patches.