Monarchs,

This patch contains several bug fixes, improvements to memory performance and to networking including:

• Fixed the issue that would cause Hephaestus' hammer quest item to disappear from the level in multiplayer, blocking your progress. If your save file was affected, loading the save on the new patch will automatically complete the quest and grant you the reward.
  
• Fixed the issue that prevented the achievement Mediterranean Vacation from unlocking at the right time. Unfortunately, the achievement can not be unlocked retroactively on save files that were encountering this issue. To get it, the requirements must be met again in a fresh campaign.
  
• Optimized networking and reduced traffic to improve online co-op experience.
  
• Fixed several issues that could cause crashes to occur in specific gameplay scenarios.
  
• Fixed the issue that would sometimes cause ruler animations to break when starting a co-op session.
  
• Fixed the issue that would cause the client player’s movement to break while riding the Hippocampus.
  
• Fixed the issue where the boar re-spawning in wintertime would have the game consider the island as incomplete. If you give any lingering threats a good whack in this patch, it should do the trick and the island status will stay as "completed".
  
• Shield Walls in Norse Lands should now block Crushers correctly.
  
• Archers following a Squire or Knight should no longer be left outside the safety of the Kingdom walls at night.
  
• Archers on the Fleet boats should now attack Serpent weak points correctly.
  
• Farmers who have boarded a boat will no longer occupy farmlands.
  
• Fixed minor visual and audio issues.
  
• The zoom levels have been temporarily capped to prevent issues with environment graphics, while we are working on a bigger fix to preserve graphic integrity at more zoomed out levels for a future patch.

We'd like to take a moment and thank those of you who have tested the multiplayer public beta and confirmed the networking performance has improved. We will now end the public beta, so everyone in it will be automatically reverted back to the default branch which now, after this patch, has the same fixes.

We will continue to patch the game with more bugfixes as soon as possible.

As before, we always communicate updates on our X, Facebook and Discord, so please make sure you follow them to stay on track with the latest news. If you encounter any further issues, please report them at https://rawfury.atlassian.net/servicedesk/customer/portal/1 as this is the quickest way for us to investigate and get back to you.

Thank you for your continuous support.

/The Kingdom Team

Monarchs,

The team is now back from the holidays and our annual internal conference where we spent a lot of time planning. We will share more on that later, but for now we would like to focus on fixing and addressing some of the multiplayer issues identified in the game. We have implemented and tested a series of these fixes and would like to invite the community to participate in a public beta test for additional feedback. We deeply appreciate everyone's patience as we keep developing and implementing fixes to issues in the game.

Please note that this solution is still in testing - however, if it helps you, please do let us know in the comments. Some questions that could help would be - is it stable? Are there any unexpected disconnects? Is the connection reliable? Is there a lag? If it plays well for you, we'll be working on patching the game as soon as possible, so that you could start enjoying the multiplayer fully.

To access the beta, please follow these steps:

1. Go to your Steam Library
2. Right click on Kingdom Two Crowns -> Properties -> Betas
3. In the list of betas, please select "public-test - Multiplayer fixes to version 2.1.0 (Feb 25)"
4. Enjoy!

Important - please make sure that your play partner is also playing the beta, and that you've made a backup of your saves before installing the update.

With the goal of eliminating multiplayer issues and disconnects that players have reported, we have taken a good hard look at our networking code and found ways to reduce the overall network overhead. Our networking now uses less additional data to identify messages and state their purpose. We have also increased the timeout duration for connections meaning it will stick in there longer when you experience lag spikes or connectivity issues. We deployed some advanced optimization heuristics on our most common message types to also reduce the actual amount of data being sent. Along with the already optimized overhead, these two put together result in up to 40% less traffic. Finally we implemented some Steam specific optimizations to better utilize the Steam P2P networking API, minimizing external overhead and fixing a potential bottleneck.

/The Kingdom Team

Come join our virtual fire and take refuge from what grows in the darkness 🔥 Share your stories, participate in giveaways and find fellow Monarchs who share your passion for adventure:

👑X👑[twitter.com] 👑Facebook👑[www.facebook.com] 👑Instagram👑[www.instagram.com] 👑TikTok👑[www.tiktok.com] 👑Discord👑[discord.gg]