Respawn give another update on broken Apex Legends hit reg - Dexerto
Apex Legends

Respawn give another update on broken Apex Legends hit reg

Published: 19/May/2020 11:11

by Jacob Hale

Share


Apex Legends developer Respawn Entertainment has provided another update on broken hit reg issues in their battle royale title, after numerous complaints from players after the Season 5 update.

Although the Season 5 update was one of the most exciting ever, with new character Loba joining the Apex Games, hit reg issues have plagued the game since, with players baffled as their shots don’t connect despite being on target.

Shortly after the new season launched, players immediately noticed the problem, and devs were quick to announce that they were aware of the issue.

While a new season is supposed to be one of the most exciting times in the game’s life-cycle, bringing new content, fixes and updates to the game, the moment has been a little stifled by the hit reg problems.

Most players at this point have found themselves having some kind of issue, but if you’re lucky enough to have not, this clip from pro player Diego ‘Diegosaurs’ Navarrette will give you an idea of what exactly players are dealing with.

Although this isn’t the worst of it, you can both see and hear the shots connecting on Diegosaurs’ side, though no damage is actually dealt.

During the days since the update went live, Respawn have clearly been hard at work trying to figure out what the issue is so that they can come up with a solution, and have provided players yet another update to put their minds at ease.

They say that they’re aware of issues persisting but are still working on a fix, and will provide an update “as soon as there is more information.”

This isn’t the ideal response in the eyes of Apex Legends players, who would likely have been hoping for a fix by now, but given the ongoing global crisis, these issues must be slightly harder to resolve.

The developers did previously roll out a hotfix on May 14 to fix the issues, but they have persisted since, so clearly that wasn’t the fix needed.

Hopefully, though, they will have an update soon enough and put an end to these hit reg issues, or risk losing players to the likes of competitors such as Warzone or Fortnite. TSM have already had to delay their invitational tournament for Apex due to the problems, at Respawn’s recommendation.

Apex Legends

How to fix Apex Legends code 100 error on Xbox, PlayStation and PC

Published: 18/Jan/2021 1:20 Updated: 18/Jan/2021 1:30

by Connor Bennett

Share


Despite being around for a while now, the infamous code 100 error continues to cause problems in Apex Legends and we’ve got all the info you need to address it.

What is the code 100 error in Apex Legends?

The Code 100 Error has been annoying Apex Legends players since early 2020; the error relates to players being unable to ‘complete their EA Account sign in,’ which is particularly annoying for players as EA have not yet noted the issues, much less acknowledged that they have their own fix coming.

Players have come up with a temporary fix of their own, with the remedy being pretty much the same regardless of whether you play the popular title on PC, Xbox, or PlayStation. You can find the fix for each respective platform below.

Respawn Entertainment / EA GamesThe Code 100 error is stopping Apex Legends players from helping teammates as Lifeline.

How to fix Apex Legends code 100 Error on Xbox One & Series X/S

The temporary fix, which has been a success for most players, revolves around being able to change your DNS [Domain Name System] server to a public DNS service, which has its own numbered code.

To make the fix work on Xbox, go into your network settings and tweak a few things:

  1. Go to Settings – Network, Advanced Settings, DNS Settings
  2. Change DNS settings to the following:
  3. Primary DNS: 8.8.8.8
  4. Secondary DNS: 8.8.4.4
  5. Save settings and return to Apex Legends

You may have to restart the game for the updated settings to make a change.

Windows CentralThe network settings for Xbox One are slightly tucked away – but you’ll be back playing Apex in no time.

How to fix Apex Legends code 100 Error on PS4 & PS5

Again, fixing the error on either PlayStation console is pretty similar to Xbox but there are a couple more steps to follow:

  1. Go to Settings » Network » Set Up Internet Connection.
  2. Select which connection you use – be it WiFi or LAN Cable
  3. Select ‘custom’ and enter the following settings:
    • IP Address Settings: Automatic
    • DHCP Host Name: Do Not Specify
    • DNS Settings: Manual
    • Primary DNS: 8.8.8.8
    • Secondary DNS: 8.8.4.4
    • MTU Settings: Automatic
    • Proxy Server: Do Not Use

Save these settings and then return to your home screen.  Like on Xbox, you may have to close the Apex Legends application and start it up again for the changes to take effect.

Respawn EntertainmentThe code 100 error has been affecting Apex Legends players for a few days

How to fix Apex Legends code 100 Error on PC

The good news is that there is a fix for code 100 on PC, the bad news is that it takes a bit longer to do that on console. That said, if you follow these steps, you should be able to bypass the error.

  1. On PC, hit the Win + R keys together, opening the command box
  2. There, type in ncpa.cpl and wait for ‘Network Connections’ to appear
  3. On Network Connections, head to the internet connection you operate on and right-click it
  4. Once that right-click menu open, select properties
  5. After the properties menu opens, find Internet Protocol version 4 (TCP/IPv4) and select properties – which is towards the bottom right-hand side of the box
  6. There, select ‘Use the following DNS server addresses’ and type in:
  7.  Preferred DNS server: 8.8.8.8
  8. Alternate DNS server: 8.8.4.4
  9. Once done, select OK in the bottom right-hand corner. Once the box disappears, restart your PC and allow the changes to take place.

So, there you have it, that’s how you fix the Code 100 Error on old-gen and next-gen consoles, as well as PC.

Last updated January 17, 2021, at 5:30 PM EST.