PartWelsh

We announced the exact timing of it 3 hours before (not 10 minutes), having also cited it as happening today in 'This Week in Battlefield' earlier this week, and possibly last Fridays Weekly Roundup post.

Apologies for not being able to be more precise upfront - the team are all working on finalising our upcoming update so our schedule needed to be a bit more fluid in order to make sure that you get to hear from folks like Ryan, David, and Florian. Getting folks time away from doing their job, at the same time is like her...

Correct. The feature is still coming with 5.2.

We can't publish the information about what Community Games is until it's cleared through our approvals process and Thanksgiving natrually creates a small backlog. Hope is still that we get what we need to publish it tommorrow but there's every chance we end up missing this because of the Holidays and getting the full detail next week.

Just to re-state though, this feature launches with Update 5.2

Correct - we can't adjust this screen until the patch goes live so apologies that it's not coming (check my post history for the 5.2 Update Preview that talks about why).

This will be replaced with an alternative reward.

Lunge Mine will not be available in the game before the end of the year and I'll have updates on this in January. We still intend for this to feature in the Chapter, though there's presently the possibility that it may not feature until the final couple of days. I will have a new update in January.

Sorry about that one. This was accidentally caused by what we believed was a minor backend update (which we have since rolled back).

Fun Fact: This is what we use throughout all our internal testings for new content whilst it's still being developed. We only really replace this with 'Final Level Art' as we get much much closer to shipping it. It's strange seeing it out in the open!

This will slowly disappear over the course of the evening as the servers change back.

Sorry about that (and also for the weird 'PLACEHOLDER IMAGE' bug that popped up this afternoon).

I can't go into any details about what this map is, or if it's going to be releasing in the game in the future. That type of information can only be shared when it can be.

What I can say is that you've seen something that we're not ready to show, or talk about. This goof is on us.

If you as a community feel that's valuable to have, I'll support it. I'm a guest on the sub as much as you all are, this is your home so don't be shy discuss it with the mods.

More Specific and Less Vague is an important standard we aim for. That often results in us being able to comment on things that will, or need to happen in the future.

Timelines are only ever going to be shown when it's clear that it's set to appear in an upcoming update. If its actually happening, and it's not at risk of me having to return and come back to you to say 'Sorry, but we need more time' then it gets discussed publicly.

Doesn't solve the problem, but that's transparency about how we'll behave.

'Nobody' is a pretty unfair term to apply here. To say that you're frustrated that the thing that people are discussing hasn't been fixed/changed/implemented is fair - but when we see broken things in our game that we want to address, sometimes discovered (or even caused) by ourselves, often sent to us privately or just on platforms or via channels that don't trend in a manner where they're so actively surfaced like on reddit, then we actively work to do that.

What trends here is still important, but often trends because it represents a bigger problem to solve that requires more people to do more work. Irrespective of how much resource is allocated to development - there's still a finite amount of time that can be dedicated to developing fixes and improvements before an update needs to be tested and shipped.

We'll take every opportunity we can to do as much as we can to improve the game, with each person across the team spending as much time as possible utilizing th...

Correct. The other aspect is that we often see multiple posts on the same topic and to add the same comment in different places splits the attention. It feels doubly rude of us to show up on a thread and state 'I've answered this here'.

If this would be an alternative preference of folks, I'm happy to do that.

Genuinely interested in better understanding this belief that a post like this (or anything else here on the Sub, or posted elsewhere on the internet) is actively ignored by myself and the team. It's presently the second most upvoted post on the sub, and it's directly tagged into my mentions.

Everything that OP has volunteered is fair and constructive feedback. There's no response I can give to it other than to credit the way that they've volunteered their feelings and perspective. That's not a limitation imposed on me in my role, that's just the reality of game development and being responsible about how we respond.

When folks are making these posts it's because they want to see improvements added to the game that directly respond to the criticism outlined. We respond to that in the form of action than promise. You've had enough promises.

There's not a single day that goes by where your concerns and your feedback isn't shared with the teams and used to inf...

Weapon Balancing requires manipulating existing systems and values, the other requires changing game code and creating new logics, and then testing those systems under all circumstances. Further consider that a 'developer' isn't generically skilled across all disciplines, so the team who will have worked on this aren't necessarily the same as the folks who could do more advanced changes.

As I said above, certainly an area that we need to show you some improvements on. I will be talking to you all about any changes we can make closer to a time where it's evident from our internal testing that they're set to get made.

I dont have specific answers to any of the questions you've put forward but they'll certainly be discussed. If in the future we can then attach those discussions to an actual change that's set to arrive in the imminent future then we'll share that back with everyone else.

All of those things are important, and no doubt contribute towards the same issue.

All of those things are important, and warrant further attention.

In this update, we're making some adjustments here. In future updates we're making adjustments and changes elsewhere.

Zero desire to take away from your point or frustration - just want to make it clear to you that what we're doing isn't a single answer to a wider problem.

Well Summarized!

The TL;DR is at the top of the post.

Hey folks,

In our last Community Broadcast, I provided you with an early insight on the changes that are coming with Update 5.2 (Missed the post? Check it here). This is an important reset on the level of transparency that we want to provide to you, and I’m really grateful for the amount of engagement that you provided throughout the last week.

You fairly raised some concerns around the changes that we’re making. Today I want to help to address those concerns, and I’ve spent the past week sharing your feedback with the team in as direct a m...

It's been moved to a new binding. Double check it in Options (unless you're on console and using 'Alternate' preset. In which case you can either switch back to standard or sit tight till the next update when we can fix it)

An odd one. Thanks for letting me know!

One of the big things that helped me to change my experience with the system is to go into the menu and switch the behaviour of 'Press to Skip/Hold On' to 'Toggle to Skip/Hold On'.

As soon as I die, I can tap Hold on and check messages on my phone/take a drink of water and 9 times out 10, I actually do get a clutch revive. If I've been on some daft flank out to the middle of nowhere is pretty much the only time I skip.

Either way, Toggle is a lot kinder on the fingers!