Kay

There is a service issue in US East that is impacting some of our worlds. Unfortunately there are global services that route through this region, so the impact is not limited to US East.

We have been informed that the recovery is in progress, and worlds should be normalizing soon.

EDIT: there is impact on expeditions and outpost rush while this issue is still active. Please refrain from attempting to enter either until the issue is fully resolved. We will update this post when that happens.

Thank you for your patience.

EDIT: the service issue is resolved. It is now okay to enter instances such as expeditions and outpost rush.

You should be able to take all/drop all now - is that not the case? I just tested on a few of my characters and I was able to.

Downtime is complete and all regions are out of maintenance. Thanks all

We ran it with standard PTR gear, and I think it’s getting released this week?

As far as recorded v live content, we likely won’t ever do a live run because stream sniping and all. But we also won’t cut anything to make it seem like we are more amazing than we already are

Spoiler alert…we also find that the corrupted portal is, uh, difficult

I hear that Scorpius is another one y’all want us to run? And we are looking into the charity aspect. Maybe next time

I’m not sure where you heard that. Only thing I can think of is that we had a bug back in Beta where persistence was borked after the merge and influence wasn’t saving, but that has been fixed.

After the merge, you are be able to push influence against opposing faction control, capture forts in the open world, etc. Does that address your question?

EDIT: I will ask on Monday though, just in case.

Yes, what we are discussing applies to everyone.

Hello everyone,

We announced some world merges this week and didn’t do a great job explaining the reasoning, specifically for the merges that seem less than ideal.

When planning for world merges, our team typically looks for close to equal faction representation and a peak population above 1000, among other indicators of world health post-merge. That’s not entirely the case with some of the upcoming merges due to an issue I will explain below. I want to be clear that for these worlds, this is the first step in a multi-merge process. The working plan is to reassess and address all struggling servers in early 2022.

Unfortunately, we cannot merge every world as we would like in the near team due to a housing persistence concern that would be tripped if we moved forward with the all-to-one plan right now in some sets. We have discovered that when multiple housing plots are stacked from merging or transfers, we reach an unsafe level of persistent data which can cause...

really, problem mitigated - but we definitely see the value, and are discussing it as well as potential timing. If it does happen, it will be soon after the merge.

good call out! Not Valhalla, that one is not getting merged.

Hi Morrow, Locuta and Xibalba folks,

I understand the concern here - we typically look for close to equal faction represetation post-merge as part of our process. That’s not the case with the upcoming merge due to an issue I will explain below, and also this merge is not the last that we are planning for the Arkadia Eta world set. This is the first step in a multi-merge process.

The working plan is to merge all struggling servers in the Arkadia Eta set into Morrow in early 2022. Unfortunately, we cannot do this in the super near team due to a persistence bug that would be tripped if we moved forward with the all-to-one plan right now. The merge we are moving forward with is the safest option for your worlds right now.

I hear you on the faction reset, and that is something being considered for sure. Stay tuned. If it’s possible, more info will be ready next week, likely soon after the merge.

Kay

EDIT: Valhalla will not be merged into Morrow, other w...

We are aware of this issue and are working on this.

This is a known issue - if it wasn’t on the known issues list that was posted with this release, sorry! The team is working on the fix, hoping to have it in with the next big update in January.

We are looking into a solution. Unfortunately, this isn’t as simple as we thought it would be and will require some… interesting maneuvers on our end.

The resolution won’t be today, but it will be Soon - on the horizon if you will.

Yeah, that’s not supposed to happen. I’ll reach out to the team working on it.

Though inaccurate, that wheel is very creative. Kudos @Dioxin.

The services team that is working on the contracts state plans to run a revised script tomorrow after the December update goes live. I’m not sure of the specific edge case you fall into @Butskittles but I hope it’s resolved as part of these most recent edits to the script.

I can’t make any promises, but we are indeed working on it.

Hey all, thanks for tagging me in.

This is a known issue that we have been looking into. The mob isn’t spawning as intended, and unfortunately it won’t be fixed as part of the December update. The team handling this is aiming to have the fix tested and ready to go by the time we release the next big update.

Hey all,

The region has not completely recovered. You may encounter stability issues as a result. AWS engineers are on the case, and we will keep you updated as the situation resolves.

The service region is recovering.

You should be good to play now.

Hello Adventurers,

We are experiencing an issue with services routed through US West. Though the root issue is localized to one region, there is likely impact across all regions in New World.

AWS engineers are working on it and we expect to have this resolved for you soon.

Either myself or our Community Managers will provide an update once we have more information.

Thank you for your patience and understanding.

We are investigating what is going on. It doesn’t look like the errors this morning are caused by the game, and are likely a result of an outage with AWS.

We will check back when we have more info.