Respawn announce Apex Legends PC update for June 20 – Patch notes
Respawn Entertainment has announced that an Apex Legends client patch will be dropping on June 20, exclusively for PC players.
[ad name=”article1″]
Just a day after Respawn teased a possible Flyer event headed to Apex Legends, the company announced that a PC-only client patch is headed to the PC version of the game very soon.
The update is just some behind-the-scenes server stuff, focusing on data centers and server-based errors, so if you’re hoping it’ll be some exclusive dragon content for PC, you’ll be sorely disappointed.
New Flyer updates won’t be in this patch – sorry!Though this patch isn’t the most interesting, it will deliver some improvements PC players have been asking for for a while.
The data center list is being revamped to make it easier for people to navigate through when selecting a server, and will be sorted by ping by default. Game clients will also now be sending user inputs to the server at a higher rate.
Some players have encountered an error where they’ve been booted back to the main lobby for no reason, under the error code ‘leaf.’ The patch won’t outright fix this issue, though measures to find out what’s causing the bug will be added.
The patch is only coming to PC for now as a test to see how it runs, but will hopefully be released for all systems in the near future.
The ‘leaf’ error code won’t be fixed in this patch – but measures to find out what’s causing it are being added.Full June 20 patch notes
You can read the complete patch notes for June 20 below.
- Datacenter improvements to make the list easier to understand and use:
- List will be sorted by ping by default.
- The selected data center will be highlighted in orange.
- Focused/hovered data centers will still be highlighted in grey.
- Right clicking a data center will no longer make it look selected
- Right click wouldn’t actually select the data center but would still highlight the selection which could be confusing.
- Clients will now send user input to the server at a higher rate.
- Code: Leaf error
- There is still some work to do on our end to nail down what is causing this error. In this patch we’re adding more telemetry to help us identify specifically how this error is being caused. You may start to get a code:net error instead of code:leaf. That is intended and part of the telemetry we added. We’ll be continuing to investigate this issue and it remains a priority.
