Shell-shocked October veterans get a bomb badge
Accounts made before October 21 now carry a bomb badge and 100 extra XP, enough to reach daemon. Make yours after 14:00 UTC that day and the badge stays locked for good.
Also leadingTook the lead from Replies break formation in your inbox #911. A new bomb badge and 100 bonus XP land on every account created before the October cutoff, waking quiet profiles at level 2 and locking it for later signups. Held off 1 challenger since.

You open your profile and the shelf above your commits now counts 14 badges instead of 13. Hover it and there, beside the terminals and cookies, sits a bomb. That badge is shell shocked, already earned, and your XP total is 100 higher. Nothing to click, nothing to claim.
Credit paulinevos, who tied the October outage to the XP ledger instead of to anything you did. The app stamps the badge on every account created before 14:00 UTC on October 21, 2026, and adds 100 XP once. Since daemon begins at 50 XP, a quiet old account wakes up at level 2 without posting a thing. The badge shows a bomb. Its description reads "survived the php2shell downtime of Oct '26."
The catch is that it checks your signup date, not the outage. It never asks whether you were around in October, so an account made in 2024 and abandoned since gets the 100 XP, while someone who joined at exactly 14:00:00 that afternoon does not, because the cutoff is strictly earlier. Everyone after that moment sees shell shocked locked at 0 of 1, with no way to earn it.
Key files · #926
- app/
Enums/ Achievement.php - app/
Queries/ UserAchievementsQuery.php - resources/
js/ achievements-dialog.tsxcomponents/ - resources/
js/ achievements-shelf.tsxcomponents/ - resources/
js/ achievement.tstypes/ - tests/
Unit/ UserAchievementsQueryTest.phpQueries/ - tests/
Feature/ UserControllerTest.phpControllers/ Api/ - KNOWLEDGE_BASE.md