Treyarch Address Black Ops 4 20Hz Server Tickrate Controversy

Over the past couple of days, fans began noticing that there’s something different about Black Ops 4’s servers despite its relatively smooth launch. It seems the servers have been downgraded a bit to compensate for the addition of Blackout. After a ton of feedback, Treyarch released the first update for Black Ops 4’s server issues.

However, no official technical specs and changes were reported. Users are reporting that the game’s servers are now running at 30hz instead of the previous 20hz. Treyarch admitted that they had to prioritized game stability over other factors such as network performance. Treyarch recently released a statement addressing the issue:

We’re constantly working to optimize the game, and particularly network performance, to ensure the highest quality online experience for our players. For a game launch with as massive a population as ours hitting so many global servers at once, we configure our infrastructure to ensure game stability as the highest priority over all other factors.

A few days ago, Treyarch released the first major update for the game which added the Black Market to the PS4 version only.

  1. Fixes and improvements to Tier progression earn rate across all modes of Multiplayer and Blackout.
  2. Apart from server issues, Treyarch needs to address many others as well including a serious memory leak problem.

If you don’t know, Black Ops 4 memory leak issue is causing a lot of trouble for players. Players are reporting that the memory leak issue of Black Ops 4 is causing damage to the hard drive and may corrupt windows.

While playing the game, it writes and re-writes thousands of MBs on your hard drive. This gradually shortens the lifespan of your drive and slowly kills your storage device.

If you have a smaller drive then ultimately the game will crash. This is a serious issue which should be reviewed by Treyarch. I am sure the developers already know about this issue and the game will be patched soon.

Contributor at SegmentNext.