Platform Update – February 21, 2026
Community

Platform Update – February 21, 2026

ExiliM
Feb 21, 2026 2 min read

We've rolled out a bunch of improvements and bug fixes over the past day. Here's what's new:

  ---
  What's New

  Site-wide announcement banners
  We can now display important messages as a banner at the very top of the page, above the navigation bar. You may be
  seeing one right now — perfect for maintenance notices, important news, or reminders.

  Live Activity feed improvements
  The activity feed now correctly shows team kills, base captures with faction info, player connections/disconnections,
  and working profile links.

  ---
Bug Fixes

  Weapons page – Longest Kill now filters correctly
  The Avg Distance and Longest Kill columns were previously including AI kills, which inflated the numbers
  significantly. Both columns now only show PvP kills (player vs player).

  Achievements – Progress could exceed 100%
  In some cases achievement progress could display over 100%, or the system would crash during calculation. Both issues
  are now resolved.

  Player search crashed on certain names
  Searching on /players would crash if a player name contained special characters like <, > or &. Fixed.

  Push notifications broken on Android/Chrome
  Browser notifications were crashing on modern versions of Chrome (Android) due to a Service Worker API requirement.
  The notification system now handles this correctly.

  Notification polling didn't stop on logout
  Background polling for notifications kept running after your session expired. It now stops correctly.

  Admin – Moderation queue showed wrong count
  The queue badge in the admin panel was counting all chat messages with a flag column, not just the actually flagged
  ones. The number is now accurate.

  Mobile navbar was broken
  The logo collapsed incorrectly, icons were cramped, and the layout broke on smaller screens. Fixed.

  Achievement checker crashed during scheduled run
  The hourly job that awards achievements could crash if a player had missing or invalid data, stopping the entire run.
  It now skips problematic players gracefully and continues.

Comments (0)

Log in to leave a comment.

No comments yet. Be the first to comment!