about 1 month ago - EricMusco - Direct link

Hey folks,

I wanted to give you a quick heads up on our plans for the next little bit as we have 3 patches coming to you in pretty short order.

7.4.1a will be coming ASAP, likely tomorrow. This is to address an issue that the Join the Fight mount is not currently working at level 1 as intended. Jackie will be posting details once we have locked down maintenance timing.

7.4.1b is right on the horizon, targeting early/mid next week followed by 7.4.1c in the next 2-3 weeks. We are tracking a variety of emerging issues for these patches such as Ancient Armaments and Conquest/Rep change. I’ll be back later today or early tomorrow with a follow-up post about our internal conversations following your feedback on the Conquest/Rep changes.

I’m gonna lock this thread for now and will respond here later. I will reopen the thread when I do!

Thanks all, talk soon.

-eric
 

about 1 month ago - JackieKo - Direct link

Hi everyone,

Chiming in to give you all an idea of what to expect for tomorrow. We do intend on taking down the servers to roll out 7.4.1a which would fix the K-NorCo B5C Mount from the Join the Fight bundle. However, we do not have an exact time scheduled just yet as there are levels of verification and testing that needs to be happen. Once I have this information, I will update this thread. What I can say at this time that estimated downtime is approximately two (2) hours.

Thanks all.

about 1 month ago - JackieKo - Direct link

Good morning everyone, 

We're getting ready to deploy Game Update 7.4.1a:

  • Time: 9:30am CT / 2:30pm UTC
  • Estimated downtime: 2 hours

I'll update this thread when the servers are back up. 

about 1 month ago - JackieKo - Direct link

Servers are now back up! 

The following patch notes will be added shortly. 

  • Fixed an issue with the exclusive Join the Fight bundle K-NorCo B5C Mount not being able to be rideable at level 1.
  • Galactic Seasons 6 Blueprint Fragments are now Bind on Pickup.

Thanks all

about 1 month ago - EricMusco - Direct link

Hey folks,

Coming off of 7.4.1, there were obviously some changes we made that received some feedback and I wanted to talk through them with you! I think we can put them in three buckets and in each there are some problems from our side that I want to address. Those buckets in order are:

  • Removing Reputation tracks from GS / Blueprint Fragment confusion
  • Changes to Reputation Conquest Objectives
  • Missing patch notes

Where is the Rep Track?!

Simply put, the intended functionality of a Rep track does not pair well with the functionality of Galactic Seasons. For us, we want a rep track to be something that a player can engage with over a long period of time, to work through, earn rewards and titles, etc. Since a GS is only available for a limited time we didn’t want to push into a FOMO feeling or anything like that. We want Rep tracks to be tied to things like Daily Areas.

However, there was a similar expectation of those items being on the track, of those Achievements being earned during the season, etc. And so as a middle ground we replaced the rep items with the Blueprint Fragments which could serve a similar purpose. The problem here is that our messaging and overall user experience for these could use some work. We didn’t communicate this change clearly up front and more importantly, Blueprint Fragments themselves don’t do a great job of communicating what they or what their purpose is.

Going forward, it is our intention to stop doing rep tracks for Galactic Seasons and reserve them for content where it makes more sense (like Daily Areas).

The Conquest Change

This is surely the place we saw the most feedback here in the forums following the patch yesterday. First off, why did we even make this change? Well, this Objective is quite a bit outsized in just how many points you get relative to its effort. Not that we don’t want a range of Objectives, some of which can be completed very easily/quickly. But this Objective was a very large amount of points for what was required of you, and that’s why we ultimately nerfed it.

In connection to the first section is that although we lowered the points from this Conquest, our goal was to add in new objectives so that players who were jumping in for quick sessions and progression through Galactic Seasons, could then also be gaining Conquest points (the new Objectives focus on gaining GS levels).

Now, all of that being said, we definitely hear your feedback. We know that we hit this Objective pretty hard. And although it may have been needed to pull it into balance, we are actively discussing what adjustments we can make and I will let you know once I have those details.

But, Where was the Patch Note

Ok so before I peel back the curtain a little I want to get something out of the way, we didn’t try to hide any of this, it was just missed (I’ll tell you how in a minute). We know that a nerf like this is never fun and you having to discover it on your own adds so much more friction to the situation. But to be clear, any change that is player facing should be communicated to you, whether that is through patch notes, social media, forums, or some combination of all of the above. A change that affects you that is missed is never intentional. 

I know ya’ll appreciate some behind the scenes when we can and so this is a good opportunity, so here goes. Let me walk you through how our patch notes are built to illustrate how this was missed. And amusingly a little bit of how Musco of the past and Musco of the present combined for this one. Also usual reminder I am going to be doing a bit of oversimplifying here so don’t take all of this as 100% 1 to 1, but to be illustrative!

Ok so when we pull patch notes we do so mostly in two ways:

  • Highlights - These are the big features we know and track across a whole lot of teams, usually have marketing blurbs written, blogs, etc. 
  • Bugs - The important one for this section, we pull our bug fixes internally based on a query that Musco, Community Manager of the past, helped write. This pulls from our internal tracking of all of the bug fixes we made for a particular release so that Jackie and the Live team can convert those into patch notes!

Now fast forward. As of late we’ve really been trying to squeeze in more stuff when we can and often this stuff is small. So not a whole big feature, but also not us fixing a bug. From a project management standpoint, those things are tasks. This is something Musco, Producer of the Present has been helping to drive internally. You can see this in things like Ancient Armaments or the new Legacy Perk. 

Well, when we are building our patch notes as I already described, we are typically looking at our highlight features and bugs (thanks Musco of the past) and in that query we now realize we were missing some tasks. In fact, both of my examples of tasks from above, Ancient Armaments and the new Legacy Perk, were missed on our first internal draft of the patch notes until we caught them on review.

You can probably see where this is going. The changes I’ve been talking about in this thread were all captured in tasks and so when we were writing the patch notes they were just missed and then weren’t caught on internal review. As you already can guess we are updating our process to make sure we are throwing a better net on catching those tasks in the future.

Anyways, this is a long post and I have thrown quite a lot of information at you. Thank you all for the continued feedback and I will pass on any more information as I have it.

-eric