Activision Blizzard describes fan reaction to Diablo Immortal mobile reveal as m | Pocket

Spread the love

Activision Blizzard has labelled the fan reaction to Diablo Immortal’s mobile reveal as muted during an investors call following its Q3 financial reveal.

The Diablo game, made in collaboration with NetEase, was revealed to be coming to mobile at the peak of Blizzcon 2018.

Fans were not happy and have since made their voices heard. In a video that has since gone viral, one fan reflected the mood in the room and asked the developer if it was an out of season April Fools’ joke.

Following the announcement of Diablo Immortal, Blizzard executive producer Allen Adham took part in a press conference and explained that over time the developers had been playing more mobile games, adding that more of Blizzard’s games would be coming to mobile.

That didn’t go down to great either, with a video of the conference sitting at 3.6k dislikes and 132 likes.

On top of this, Activision shares are currently at their lowest since the end of 2017.

Launch confidence

As transcribed by Seeking Alpha, president and COO Collister Johnson first told investors that mobile remained the largest and fastest growing platform for gaming in the world.

He then moved onto the topic of Diablo Immortal, playing down reaction from fans and internet trolls.

“And last week, Blizzard announced Diablo Immortal, which will bring this tenfold franchise to a mobile audience in both the east and the West,” said Johnson.

“While fan reaction was muted to the announcement, players’ hands-on experience this content confirmed what we believe, which is that Diablo mobile will be a very well received game when it releases and players around the world will love it.”

As Activision Blizzard moved to quell some of the fallout following the announcement, we found there to be a touch of déjà vu about the situation, as mobile remains a dirty word in triple-A.

window.fbAsyncInit = function() {

// init the FB JS SDK
appId : 250161755076617, // App ID
//channelUrl : ‘//’+window.location.hostname+’/channel.php’, // Path to your Channel File
status : true, // check login status
cookie : true, // enable cookies to allow the server to access the session
xfbml : true // parse XFBML

FB._PG = {
url: “/useractions/loginfb/”,
response: “allowed”,

// Common handler to fetch FB details and reload the page
process: function(me){
$.post( FB._PG.url, {
username: me.username,
uimg: ‘’ + + ‘/picture?type=large’
if ( $(“status”, xml).text() == FB._PG.response )
alert(‘Error: Something bad just happened. Our tech department has been notified. Please try again later.’);


alert(“Error: something wasn’t right there, please try again.”);


// Used by event subscriptions to handle the response
handleResponse: function(response){
if (response.authResponse) {
FB.api(‘/me’, function(me){
if (

post: function(text, image){
image = image || $(“#fb-image”).attr(“src”);
method: ‘feed’,
display: ‘popup’,
link: ‘’,
description: text,
picture: image

FB.Event.subscribe(‘auth.statusChange’, FB._PG.handleResponse);

FB.Event.subscribe(‘edge.create’, function(response) {
$.post(‘/ajax/social-links/’, { site: ‘facebook’ });

(function(d, s, id){
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) {return;}
js = d.createElement(s); = id;
js.src = “”;
fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, ‘facebook-jssdk’));

Source link