Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/rest-api/class-wp-rest-request.php on line 952

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/rest-api/class-wp-rest-request.php on line 972

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/rest-api/class-wp-rest-request.php on line 984

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/rest-api/class-wp-rest-request.php on line 995

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/class-wp-block-list.php on line 199

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Model::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Model.php on line 240

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Model::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Model.php on line 244

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Model::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Model.php on line 248

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Model::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Model.php on line 257

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Collection::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Collection.php on line 19

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Collection::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Collection.php on line 32

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Collection::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Collection.php on line 26

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Collection::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Collection.php on line 36

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Collection::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Collection.php on line 13

Deprecated: Return type of Google\Site_Kit_Dependencies\Google\Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Collection.php on line 41

Deprecated: Return type of Google\Site_Kit\Core\Util\JSON_File::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/JSON_File.php on line 87

Deprecated: Return type of Google\Site_Kit\Core\Util\JSON_File::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/JSON_File.php on line 101

Deprecated: Return type of Google\Site_Kit\Core\Util\JSON_File::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/JSON_File.php on line 113

Deprecated: Return type of Google\Site_Kit\Core\Util\JSON_File::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/JSON_File.php on line 124

Deprecated: Return type of Google\Site_Kit\Core\Util\JSON_File::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/JSON_File.php on line 148

Deprecated: Return type of Google\Site_Kit\Core\Util\JSON_File::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/JSON_File.php on line 135

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-includes/wp-db.php on line 3031

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Main Sidebar" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /homepages/11/d418110977/htdocs/wp-includes/functions.php on line 5313

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer 1" sidebar. Defaulting to "sidebar-2". Manually set the id to "sidebar-2" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /homepages/11/d418110977/htdocs/wp-includes/functions.php on line 5313

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer 2" sidebar. Defaulting to "sidebar-3". Manually set the id to "sidebar-3" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /homepages/11/d418110977/htdocs/wp-includes/functions.php on line 5313

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer 3" sidebar. Defaulting to "sidebar-4". Manually set the id to "sidebar-4" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /homepages/11/d418110977/htdocs/wp-includes/functions.php on line 5313

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer 4" sidebar. Defaulting to "sidebar-5". Manually set the id to "sidebar-5" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /homepages/11/d418110977/htdocs/wp-includes/functions.php on line 5313

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Admin/Standalone.php on line 95

Deprecated: filter_input(): Passing null to parameter #4 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 64

Deprecated: filter_input(): Passing null to parameter #4 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 64

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-includes/script-loader.php on line 331

Deprecated: Return type of ActionScheduler_DateTime::setTimezone($timezone) should either be compatible with DateTime::setTimezone(DateTimeZone $timezone): DateTime, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/ActionScheduler_DateTime.php on line 60

Deprecated: Return type of ActionScheduler_DateTime::getOffset() should either be compatible with DateTime::getOffset(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/ActionScheduler_DateTime.php on line 48

Deprecated: Return type of ActionScheduler_DateTime::getTimestamp() should either be compatible with DateTime::getTimestamp(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/ActionScheduler_DateTime.php on line 27

Deprecated: Return type of AIOSEO\Plugin\Common\Models\Model::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Models/Model.php on line 378

Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Utils/Database.php on line 428

Deprecated: json_decode(): Passing null to parameter #1 ($json) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Models/Model.php on line 159

Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Utils/Database.php on line 428

Deprecated: json_decode(): Passing null to parameter #1 ($json) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Models/Model.php on line 159

Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Utils/Database.php on line 428

Deprecated: json_decode(): Passing null to parameter #1 ($json) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Models/Model.php on line 159

Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Utils/Database.php on line 428

Deprecated: json_decode(): Passing null to parameter #1 ($json) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Models/Model.php on line 159

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/11/d418110977/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: get_theme_data is deprecated since version 3.4.0! Use wp_get_theme() instead. in /homepages/11/d418110977/htdocs/wp-includes/functions.php on line 4861

Deprecated: filter_input(): Passing null to parameter #4 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 64

Deprecated: filter_input(): Passing null to parameter #4 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 64

Deprecated: filter_var(): Passing null to parameter #3 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 75

Deprecated: filter_input(): Passing null to parameter #4 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 64

Deprecated: filter_var(): Passing null to parameter #3 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 75

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-includes/wp-db.php on line 3031

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-includes/class-wp.php on line 173

Deprecated: filter_input(): Passing null to parameter #4 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 64

Deprecated: filter_input(): Passing null to parameter #4 ($options) of type array|int is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/google-site-kit/includes/Core/Util/Input.php on line 64
Diablo III – Jay Wilson Apologizes To Brevik And Fans | GamingRendo - News, Reviews, and Videos of all your favourite games
Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-includes/formatting.php on line 4974

Diablo III – Jay Wilson Apologizes To Brevik And Fans


Warning: Undefined array key "publisher_id" in /homepages/11/d418110977/htdocs/wp-content/plugins/adsense-plugin/adsense-plugin.php on line 338

Jay Wilson posted a public apology to not only David Brevik, but to all Diablo fans for his comments made on Facebook a few days ago and for the poor community interaction from the developers.  I was wondering when this apology would occur, and I assumed Jay may have been waiting to apologize to David privately before he made a public one.  I hope Jay is being honest with this apology.  Actions speak louder than words, so let’s see that better community interaction and progress towards fixing all the flaws of Diablo 3.

As many of you probably know, I recently made a comment on Facebook about Dave Brevik. I want to make it clear that I am very sorry for what I said. I have higher expectations for myself than to express my feelings in such a rash way and disrespect a fellow developer like Dave, someone who deserves to be treated with greater respect.

What I said was expressed out of anger, and in defense of my team and the game. People can say what they want about me, but I don’t take lightly when they disparage the commitment and passion of the Diablo III team. Dave is awesome. In Diablo and Diablo II, he made two of the games that have most affected me as a developer. I respect his vision for Diablo, but just like he said in his interview, the Diablo III team must drive a vision for the game that is true to us. We believe in Diablo and have stuck by it through years of hard development to make it a reality.

The foundation of the Diablo team was built from the remnants of Blizzard North: Our lead programmer, who built the basis of the Diablo III engine while at Blizzard North; our lead tech artist, who drove much of the combat visuals, FX, and skill direction of our classes and is one of the most avid Diablo II players you can find; our lead concept artist, who helped establish the core look of the game; Wyatt Cheng, our senior technical game designer, who writes many of our blogs and works tirelessly on the live game. All these people and many others made the commitment to Diablo even after Blizzard North shut down. It was hard for me to see their contributions be diminished by someone they worked alongside, and even harder for me not to try to jump to their defense. I only wish I’d done so in a more professional manner.

Joining the Diablo team was a dream come true for me. In my house, the name Diablo was always spoken in hushed tones. It meant late nights that turned into early mornings, moments of pure adrenaline and pure joy. It meant countless conversations, debates, scouring websites for good builds, and more than one or two sick days. 🙂 When Diablo II was released, I took a week off work and sent my wife out of state… and she was pregnant at the time! I played Diablo II with my dad during one of the most difficult times of his life, and the experience brought me closer to him, and I hope helped him through it. I joined the Diablo team because the idea of a world without more Diablo seemed like a pretty crappy world to me. I wasn’t sure if I’d be good enough. I’m still not sure. But I felt I had to try.

Regardless of how I’ve done, my team has been more than good enough, and I’m proud of the game we made together. We believe it’s a great game. But Diablo III has flaws. It is not perfect. Sales mean nothing if the game doesn’t live on in all of our hearts, and standing by our games is what Blizzard does. Patch 1.0.4 is a step in the right direction, but we have no illusions that our work is done.

Playing Diablo III needs to be a rewarding experience. The new legendaries are a big step in the right direction, as are tweaks to item drop rates. But I’m not convinced that we’ve gone far enough. If you don’t have that great feeling of a good drop being right around the corner — and the burst of excitement when it finally arrives — then we haven’t done our jobs right. Out of our concern to make sure that Diablo III would have longevity, we were overly cautious about how we handled item drops and affixes. If 1.0.4 hasn’t fixed that, you can be sure we’ll continue to address it.

Part of the problem, however, is not just item drops, but the variety of things to do within the game. Many of you have stated that there needs to be more to the game than just the item hunt, and we agree completely. The Paragon system is a step in the right direction, giving meta-progress for your time in the game, but it does little to address the variety of activities you can do while playing. I don’t think there’s a silver-bullet solution to this problem, but I do think we can make this aspect of the game better, and as such we’re planning more than just PvP for the next major patch. Not trying to be coy, but we’re still firming things up and will talk about this as soon as we can.

Difficulty has been a constant source of division when discussing the game. Some players believe Diablo has never been about crushing challenges, but more about efficiency and farming. Some players want a game that tests them to their limits. Neither player is wrong. As it stands, Diablo III simply does not provide the tools to allow players to scale the game challenge to something appropriate for them. We set Inferno as the high watermark and took a one-size-fits-all approach to game challenge. Later in the development of Diablo II, the ‘players 8’ command — which let people set monster difficulty — was added to address this issue, and we’re considering something similar for the next major Diablo III patch to allow players to make up their own minds about how hard or how easy is right for them.

The Auction House has also proven to be a big challenge. It adds a lot of power for players to trade and acquire items. Getting a great Monk drop that you can trade for better gear for your Wizard is obviously a great benefit, but it does come with a downside. The Auction House can short circuit the natural pace of item drops, making the game feel less rewarding for some players. This is a problem we recognize. At this point we’re not sure of the exact way to fix it, but we’re discussing it constantly, and we believe it’s a problem we can overcome.

While these are some of the major issues with Diablo III, they aren’t the only things we’re looking at. On a daily basis we ask ourselves if the classes are satisfying to play, if rares and champions are fun to fight, if they’re tuned well relative to normal monsters. Can we make further improvements to social elements of the game? How can items be even better?

We made Diablo III because we believe in the Diablo games. We think the gameplay is awesome, the world is compelling, and it’s the game we all wanted to play. Because we believe in it, we’ll continue to stand by it and make it better. We are committed to making Diablo III the best Diablo game to date, and we hope you’ll continue to help us do just that.

Saying that, I’d like to apologize to all of you, the players in our community. You deserve better than my reaction to Dave’s comments. You deserve more honest communication about the game and what we’re doing to make it a more awesome experience for us all. We care about Diablo very much, and appreciate your passion for it. Without you, we wouldn’t be able to do this, and for that I can’t thank you enough.

 

SHARE THIS POST

  • Facebook
  • Twitter
  • Reddit
  • Stumnleupon
  • Digg

Deprecated: get_the_author_email is deprecated since version 2.8.0! Use get_the_author_meta('email') instead. in /homepages/11/d418110977/htdocs/wp-includes/functions.php on line 4861
Author: GamingRendo View all posts by
MJ Goulah, creator of GamingRendo.com, lifelong gamer, avid hockey fan, and the most random, insane character you'll ever meet.

Leave A Response


Warning: Undefined array key "publisher_id" in /homepages/11/d418110977/htdocs/wp-content/plugins/adsense-plugin/adsense-plugin.php on line 392

*


Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Utils/Database.php on line 428

Deprecated: json_decode(): Passing null to parameter #1 ($json) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Models/Model.php on line 159

Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Utils/Database.php on line 428

Deprecated: json_decode(): Passing null to parameter #1 ($json) of type string is deprecated in /homepages/11/d418110977/htdocs/wp-content/plugins/all-in-one-seo-pack/app/Common/Models/Model.php on line 159