INVALID

We're flexible to changes, and this may only be a temporary measure until we've finalised what we'd like to do for our claim system in general.

We're going to be making a change to PvE claims so that the inactivity timer starts at a base of 2 weeks instead of 3 days. Additionally, if you are a person/group with a larger amount of claims, the amount of inactivity timer you have will scale with that and have a lower limit of 3 days. So large companies with multiple flags have less amount of time where their base can be inactive versus those with just a few flags. We'll think on having a minimum before the number starts shrinking, or perhaps it'll just be 1 flag = 2 weeks. These numbers may not be exact and might change by the time we deploy, but that's the general idea. Hoping to get this out to you guys tomorrow. This may not be the perfect/most optimal solution, but we'll go ahead and make this change until we have thought more on our claim design for the overall game. TLDR: - Inactive claim timer will cap at 2 weeks, and bottom out at 3 days based on the number of claims you have - Sleeping players won't contest claims - NPC Crew can contest claims, but you'll have to feed and pay them otherwise they'll mutiny! This might be a temporary change as we further evaluate how we want the claim system to work, especially with our new philosophy in mind.

We've updated our Linux servers to the latest version on the Steam Depo. Should hopefully resolve the libcurl & save issues. Let me know how that goes and I'll update the engineers

We're currently evaluating our claim system and seeing what changes we can make to improve it across the board, as it definitely needs work. It's arguable that the 3 day timer may need to be increased now that we no longer allow sleeping bodies to contest claims, but due to the limited amount of land available and how PvE servers work we have to put measures in place to make sure that land cannot be sat on indefinitely. Players can still use Crew (which are to be fed and paid) to contest claims. The sleeping measure we put in place was more so to tackle users who hadn't logged on in days and hadn't planned to but were still contesting their inactive claims because their bodies had not died.

Enemy players will no longer be able to climb ladders on anchored ships on PvE servers. This should hopefully prevent boats from being sunk. Going to lock down this thread now, but if there are more ways that people find let us know and we'll investigate. Patched in v16.33

Fixed in v15.21

We're investigating!

We're going to be introducing a natural decay on PvE servers for abandoned boats, as well as on Golden Age Ruin Servers on PvP Realms. If these boats haven't had activity after a certain amount of time (probably a couple weeks) they'll be destroyed. We don't expect it'll be needed as much on Golden Age Ruin servers on PvP, however, we know there's an abundance of Ramshackle Sloops and possibly rafts which players wouldn't want to use materials to sink so we expect it to make a difference :). Definitely not something that's intended, we'll investigate. Claims should only be unclaimable when a player hasn't been active in that claimed area for 3 days, if you've been actively playing in the zone then you'll be safe from having it unclaimed. Only once the 'inactive' timer has gone over 72 days, will a claim on a PvE server be unclaimable by another group. Previously, even if this were the case, sleeping bodies were having an impact on it and that isn't by design. Could you elaborate?

Killing, not deleting

.26 should be available guys, sorry about that folks!

We just ran it once, but now we're just going to keep it running continuously, on all servers. It should be both, but that's assuming no technical hiccups. Best way to know is when the patch is live We'll be looking at doing further work for claim flags and aye it's certainly a point of discussion for our team. Not saying that limiting is what we'll end up doing, but we're exploring options.

Team is looking into this at this very moment

ASAP tbh. Maybe today.... maybe tomorrow. I mean, it'll be a minor version deployment that'll go out as soon as it's been by our QA + Technical folks.

This is a frustrating bug we need to address, it's 72 hours before a claim is considered inactive on PVE, however, the timer is counting beneath 0 because it doesn't start at a high enough value. Going to see if we can get this addressed sooner as that should make it clearer. Which network are you experiencing this on? Will get some eyes on it.

I'll be brushing up on my necromancy, just in case.

Later this year

I'll see if I can chase up the status of getting it set up on Epic, the initial plan was doing it this week and we're probably still on track so you wouldn't have to wait too much longer. We're not really running into any 'issues' with the editor, more so feature requests, heh.

I wouldn't rule it out but it's not really on the horizon right now. Something we'll need to think more on. We just wanted to address the more high-level changes with this Log and over time we'll be able to get into specifics (and you'll see them happening in game too). First thing first is making sure that sap is more widely available on the ATLAS, and then taking a look at how bases are being raided/how players defend them and making adjustments in those areas.

We're working on releasing regular Dev Kit updates to resolve issues, you can keep up to date with those patch notes here: The editor will be making its way onto the Epic Launcher soon, once we're confident that it's had some more time out in the wild and we're sure of its stability. Not sure if it'll be available on Steam, likely it'll just be the manual updates or Epic Launcher in the future.