Valve's highly anticipated MOBA shooter, Deadlock, finally emerges from the shadows with its official Steam page debut. This article delves into the details surrounding Deadlock's unveiling, including its impressive closed beta statistics, unique gameplay mechanics, and the controversy surrounding Valve's deviation from its own Steam Store guidelines.
Deadlock Officially Launches on Steam
After a period of intense secrecy, fueled by leaks and speculation, Valve has confirmed Deadlock's existence and launched its official Steam store page. The closed beta recently reached a staggering 89,203 concurrent players, more than doubling its previous peak. Valve has also lifted restrictions on public discussion, allowing streaming and community engagement to flourish. However, it's important to note that the game remains invite-only and is still in early access, featuring placeholder art and experimental gameplay elements.
A Unique Blend of MOBA and Shooter Mechanics
Deadlock seamlessly blends MOBA and shooter genres, resulting in fast-paced 6v6 combat similar to Overwatch. Teams battle for control, pushing opponents back while managing waves of AI-controlled units across multiple lanes. This dynamic gameplay emphasizes strategic coordination, combining direct hero combat with the management of AI troops. Frequent respawns, wave-based attacks, and powerful abilities contribute to the intense and ever-changing battlefield. With 20 unique heroes, each possessing distinct abilities and playstyles, Deadlock promises a diverse and engaging experience.
Valve's Controversial Steam Store Approach
Interestingly, Valve appears to be disregarding its own Steam Store guidelines for Deadlock. While the platform typically requires at least five screenshots for a game page, Deadlock currently features only a single teaser video. This inconsistency has drawn criticism, with some arguing that Valve should uphold the same standards it sets for other developers. This echoes a previous controversy surrounding promotional materials for The Orange Box. This situation highlights the complexities of a company acting as both developer and platform owner, raising questions about the enforcement of its own rules. The future implications of this approach remain to be seen.