Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Witcher 3 hits its highest-ever Steam concurrent player count following Remastered launch

The Witcher 3: Wild Hunt has hit its highest concurrent player count on Steam since launch following the launch of CD Projekt Red's free Remastered edition. Read more

The Witcher 3 hits its highest-ever Steam concurrent player count following Remastered launch

Following the launch of the Remastered edition, The Witcher 3: Wild Hunt achieved its highest concurrent player count on Steam since its debut. At the time of reporting, over 120,000 gamers were simultaneously immersed in the 2015 RPG on the platform. This surpasses the game's previous peak of 92,000 players in 2015 during its original launch, a 103,000 player peak in January 2020 when Netflix's Witcher series was at its most popular, and an 89,000 player peak in December 2022 following a next-gen update.

However, this figure does not include players on other platforms such as GOG, the Epic Games Store, PlayStation, Xbox, or Switch 2. The Remastered update, which is free for owners of any existing version and includes the Hearts of Stone and Blood of Wine expansions, introduces visual and gameplay enhancements. Earlier this year, Netflix announced that the fifth season of The Witcher will be its final season.

Written by urgent.news from GamesIndustry's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at gamesindustry.biz →

More in Tech

3 Redis Design Failures You Should Avoid Before They Become Production Incidents

Caching is usually introduced for one simple reason: Take pressure off the database and make reads faster. The architecture often looks straightforward: Client | v Application | +----> Redis | +---->…

  • Stale data occurs when cached copy becomes outdated, serving incorrect information to users.
  • TTL balances performance and consistency, but doesn't guarantee immediate freshness.
  • Cache invalidation upon database updates prevents staleness but adds complexity.

Why Your Date Shows 1970: Unix Timestamps in Seconds vs Milliseconds

Why Your Date Shows 1970: Unix Timestamps in Seconds vs Milliseconds You fetch a timestamp from an API, pass it to new Date(), and the screen says January 20, 1970.

  • Unix timestamps count seconds or milliseconds since Jan 1, 1970
  • Mistakes from treating seconds as milliseconds or vice versa
  • Use appropriate unit in code to avoid incorrect dates

A small business VPS in 2026: what it really costs after year one

Shared hosting is a bargain right up to the moment it stops being one. The symptoms are always the same: the site crawls at lunchtime, PHP workers get throttled, the extension your developer needs…

  • Small business VPS costs vary based on workload needs
  • First-term pricing often misleading, renewal prices skyrocket
  • Contabo offers cheapest RAM, DigitalOcean provides transparent pricing

A stored procedure can compile and still change its meaning

The syntax errors are the visible part of moving a stored procedure between databases. The quieter problem is a query that compiles in both places but answers a different question.

  • Stored procedures can compile but change behavior across databases.
  • PostgreSQL's SELECT ... INTO with STRICT checks for single row, raises error on multiple or none.
  • Adding LIMIT 1 hides rejection condition, may mask original procedure's intent.

Passwords security and storage:

It is very important to keep your networks, systems, accounts as well as your passwords safe. As we are all living in digital era and we all want our systems and accounts safe.

  • 80% of developers still use passwords as primary security
  • Passwords can be stored in browsers, session storage, cache, local storage
  • Remove passwords from all storage methods after logging out of other devices

More from Wednesday 30 September →