Twitch viewers can screw with you in #killallzombies
To be clear: that's the name of the game
Dumb name aside, I quite like the premise of #killallzombies. It's a top-down shooter for PlayStation 4 in which zombie survival has become a televised sport, and there will be real, human spectators watching you play (if you want). There's optional Twitch functionality built in.
Viewers will be able to affect the game through votes and chat commands, much like the way folks (and fish!) have been able to "play" games through the streaming site. They can change things like the player character's speed or health, the arena configuration, and even the camera angle. Sit through the video above to see some of these elements in action.
As a shooter, this looks pretty standard, and I'm not so sure the spectator interaction will be all that enjoyable for anyone but the spectators. Interesting, though.
Setup email comments
Straight from Beatshapers, here are the ways viewers can affect the broadcaster:
- Every ~80 seconds, we have a choice of two encounters options available to vote via interactions including: encounter spawns and various arena events.
- The perk selection screen has its own voting mechanic in which if the player decides to wait and select the spectator’s most voted perk, the player will be offered extra XP and Health.
- The chat commands are available throughout the broadcast as we are executing chat commands in real time; allowing the spectators to affect on a variety of imperative decisions that can significantly increase or decrease your chance of survival: affecting character’s speed or health, changing arena configuration, spawning more zombies and obstacles; and for the most evil of spectators is the opportunity to deliberately change the camera angle to a less effective perspective and reverse the entire control scheme and much more!
Please report harassment, spam, and hate speech to our moderators
, and flag the user (we will ban users dishing bad karma
). Can't see comments?
Apps like Avast
or browser extensions
can cause it. You can fix it by adding *.disqus.com to your whitelists.