Fortnite: Battle Royale Dev Tracker

Not in this version. I'm curious, what's the use case for this type of functionality?

This will be coming very soon.

Look at the 3rd image in the post. In the Actions list there is an Edit and Repair. Those are not hold actions. You can put them where you want.

Heya,

Aaron from Epic here to talk to you folks about controllers and our plans for enabling you to play how you want. Just on the horizon are Custom Controls landing in the v6.0 update, which will let you modify your setup as you wish!

Custom Control Flow

The way you’ll be selecting the configuration has changed to a selector on the left side of the menu. After selecting Custom, the right side of the menu becomes buttons that are selectable. When a button is clicked, it opens a list of actions that can be assigned to that button.

Mode selection (Combat, Build) has changed to selectable by triggers. When you’re in a mode, the actions for that mode and actions that span between modes will show in the actions list to select from.

The idea here is to make a system that is easy to use and can be built upon with more functionality in later releases, if needed.

...

We totally understand and it wasn't meant to give an advantage over another, just trying things out. We plan on making this an adjustable value in a coming update. Then everyone will be able to make it the value they want for the configuration they use.

Will add a bug to investigate, thanks for the video.

Thanks for adding me to this.

The sensitivity change is indeed intentional. We are planning on going back to the smaller increments though very soon.

On the subject of the aim assist, I was directly involved in that and we could not reproduce it. So what we ended up doing was talking with those users offline and eventually had to hard reset their settings. If this is still an issue please report it to our customer service and we may be able to fix it for you. We honestly didn't think this was wide spread and that we had dealt with the handful that had the issue.

After the hurricane I'll have a discussion with really smart people on what we can do here to get everyone back to a reset aim assist setting.

We totally agree. We're going to change this to switch to the intended piece but also try to place it at the same time. If there is outcry from other users then we'll have to temporarily turn it off and create an option for it but we're hoping that won't be necessary.

This change will be in a patch after 5.41.

We've been hard at work trying to finalize custom...

https://www.reddit.com/r/FortNiteBR/comments/9dg6qt/v540_patch_notes/e5hv7wz?utm_source=reddit-android

Let me apologize for the misunderstanding then. We work on a slightly different release schedule than what is seen as the next patch to the public. I should have been more specific in my wording since the patch you received today was already in the process of being certified, which means no new changes were being made at that time. The change will be in the patch after this one that you just received.

We haven't patched since I mentioned the change.

Hi! Do you mind answering a few follow up questions for us?

Were you kicked back to the lobby at any point after you lost control? Is this persisting for every 50v50 match you enter?

Thanks!

It’s a mix of both.

This is a display bug when the challenges haven't unlocked yet. It will be fixed in a future build. Once they have unlocked, you can see that some challenges are now multi-part, granting some Battle Stars for each step, but the total number of Battle Stars remains the same for each week.

Cheers, Michael Noland

Thanks for the suggestion. I'll chat with the audio dudes about this.

Mia nonna usa due quando lei è molta arrabbiata!

Keywords. Sound, audio, music, etc.

We've fixed this for the next patch. Sorry everyone!

Thanks for pointing this out again - this is something we would like to see improved as well.

TLDR - There are a few things we can try to make this better, making sure this gets tracked for us to look at again internally.

As for the more detailed how and why - technically there is no structural support for the building grid in that spot because it is made up of static geometry that was built with specific dimensions to fit behind building pieces (I.e. you still need to be able to build walls flat against this piece without clipping), not support it, and therefore doesn't extend far enough to register a connection based on collision overlapping into the neighboring grid tile.

The railing is a decorative prop and does not count as a wall piece.

For optimization reasons we avoid filling spaces like this with additional wall pieces that could otherwise count as supports.

We deployed a new build of the backend which should have fixed up the counts for everyone today.

Cheers, Michael Noland