Разработчики Overwatch 2 опубликовали новую статью из серии «Еженедельный сбор», в которой регулярно делятся разной информацией о своих подходах к работе над игрой, успехах и неудачах, новинках и прочих волнующих их и игроков моментах. В свежей заметке в честь Хэллоуина авторы поделились страшными историями о своей работе, в основном касающимися странных неполадок и неожиданных проблем с игрой. Weekly Recall: Developer Horror Stories Welcome to a truly terrifying Weekly Recall.
For this Halloween special, we asked Team 4 to regale us with stories that would send shivers down the spine of any reader who dared to dive in, ones that would keep our community tossing and turning in terror at night. And what’s scarier than ghosts, goblins, or ghouls? Derailing an entire live service game with a single line of code or sending Aaron Keller a meme about your dog instead of a pitch deck. These are our Overwatch Developer Horror Stories.
Many brave devs gathered around the campfire, flashlights held beneath their chins, to share tales that will spook anyone that's ever hit “Reply All” on a company-wide email. Enjoy...and keep the lights on. “Back when we were teasing Juno's release, there was a crashed ship on Dorado that had a ‘morse code’ sound playing from it. The way the sound was implemented was a bit different from how we usually implement sounds like that, which resulted in the sound crashing the game on some systems. We unfortunately had to disable Dorado for a while until a hotfix could be made to replace the sound!” – Brian, audio “To optimize how we implemented Zarya’s Energy Lance Perk, which lets her beam pierce enemies, I made it so the tracking tech we use for her beam could return multiple entities rather than the
.