• 1

    posted a message on Well, Blizzcon has let me down

    Don't get me wrong. Necro class in D3. Okay, that's pretty cool. Diablo 1 built into D3? Sure, that's...neat. But in my eyes, this is Diablo's 20th anniversary. I was expecting something JAW DROPPING! And while these additions will no doubt be fun, I don't feel they live up to what could have been and should have been incredible Diablo news.


    I, like many, had my hopes set for a few things. A Diablo 4 announcement would have been worthy of the 20th Anniversary. I personally would have been happy with a Diablo 2 HD remake. Whether they decided to make an exact clone or whether they wanted to add or improve certain aspects of the game, a D2 HD remake would have been most welcome. I also wouldn't have been opposed to an entirely new game based in the Diablo Universe yet separate from the core Diablo games. Any of those announcements would have been welcome for Diablo's 20th anniversary.


    Now while this is only my personal opinion, and I may be in the minority here, but to me these announcements are lacking. They would have been acceptable for just about any other Blizzcon in my eyes, but this year is special and I feel the announcements don't reflect that. Now I acknowledge that Blizzcon isn't over yet and there's still a chance for something else to be announced, but as it stands right now, I feel the Diablo news from Blizzcon is once again somewhat lackluster and it's just a bit heartbreaking.

    Posted in: Diablo III General Discussion
  • 1

    posted a message on Please nerf healing monk

    When you're trying to be competitive, there's always going to be a 'best' build, 'best' group composition, 'best' class etc. Unfortunately that's true in this instance (it would seem). If you want diversity, then you'll have to sacrifice optimization. In other words, you can make runs without a healing monk right now and have fun with it, and even do well. Just don't expect to get #1 on the leaderboards.

    Posted in: Diablo III General Discussion
  • 1

    posted a message on Patch 2.3: Botter's Heaven?
    Quote from Bagstone»

    See, that's exactly what I don't get. This attitude is the same as in D3V - "you don't like the AH? Don't use it". If the cube goes live as is, Blizzard will need to fix it so that high-end players have to do something, because with bot-supported cache supplied they'll be done gearing after a week. And I mean pitch perfect gear with everything 650 main stat ancient rolls and so on. It DOES affect you, because after a while drop rates will be lowered, material cost for re-rolling will be increased, and so on; just like the AH, where drop rates became ridiculously low in the end such that casual players found about one item per week.


    This is not the time to look the other way and say "I don't care". There's a harmful thread to the entire community.

    Basically this. Let's say 2 months after the patch goes live Blizzard says, "We underestimated how effective it was for players to roll perfect quality gear with the Kanai Cube, so to address this, we've adjusted the recipe requirements appropriately. Kanai Cube recipe requirements have been increased."


    This could easily be a real possibility and the reality being it's only really the botters that have said perfect gear and the reguluar Joe players are still stuck with their moderate gear except now for them to reroll an item, instead 50 Forgotten Souls they need 250 with a bunch of other inflated craftings materials. (numbers are just placeholder examples but it gets the point across).


    People that say, "Botting doesn't affect me so I don't care" are just fooling themselves. Botting very much affects everyone that plays the game and the player base shouldn't passively stand by and allow it to further ruin an otherwise good game.

    Posted in: Diablo III General Discussion
  • 1

    posted a message on Not allowed blood shards

    Glad you got that worked out. Good luck in game!

    Posted in: Technical Support
  • 1

    posted a message on Not allowed blood shards
    Quote from Wazza180»

    Quote from Kallizk»

    blood shards are a currency next to your gold btw, mouse over it to see how many can u carry.



    I did and I cant pick them up even with an empty inventory

    Blood shards do not go into your traditional inventory like a sword or ring would. Blood shards are just a currency number, like your gold number, and you can view how many blood shards you have in your inventory screen at the bottom next to your gold number. Unlike your gold however, there is a limit as to how many you can carry at once. A new player just hitting level 70 would not be able to carry any more than 500 blood shards. If you try to run over blood shards on the ground and it's telling you your inventory is full, it means you're at your current maximum capacity of blood shards and you need to spend them at Kadala in town.


    If however on the extremely rare chance you check your blood shards and are not at maximum capacity and you still are receiving this message, then it's clearly a bug and you'll need to contact Blizzard. However, I've never heard of this being an actual bug. Odds are, you just hit your cap and didn't quite understand why you were receiving an 'Inventory Full' message without a full inventory, which is understandable for new players.

    Posted in: Technical Support
  • 1

    posted a message on Crushing Everything in T1 then Malthael Says: Nooooooope.
    I consider Malthael to be equivalent of at least the next difficulty up of any other boss, if not 2 difficulties up. IE: T1 Malth is about on par with T2 Adria, maybe even T3.

    The difficulty ramps up dramatically for that fight and that fight alone. Release night, my friend and I managed to get to 70 and beat everything up to Malth on Torment I (I was carrying him fairly hard). The second we hit Malth, we were getting wrecked. I ended up dropping the game and defeating him on T1 solo, which took some spec tweaking including redoing how I spent Paragon points, but my friend had to drop the game down to hard difficulty to finally beat him. I just couldn't make up the damage my friend was lacking to carry us through the fight. He's a monster and a very difficult yet extremely fun fight.

    My advice to you is Health regen is your friend. One thing that really helped me was I changed my Paragon points in Defense from max All Res to max Life Regen. That 8000+ health per second was a godsend. Beyond that, adjust your spec for more survival. When I solo'd him on my barb, Warcry and Threatening Shout were a must. Then it's just practice, learn his routine and beat his ass. Good Luck
    Posted in: Diablo III General Discussion
  • 1

    posted a message on TryHard: Demonic Essence Farming Route, Blue Posts, Fan Creation of the Week: /r/Diablo's Short Story Winners, Weavesilk Tyrael
    I think it's cool that people are going out of their way to find the fastest farming route for Demonic Essences, but me personally, I just don't see a need to have to farm them efficiently. By that I mean, I just do my xp grinding route and I seem to find plenty just doing that. I don't feel like I need to go out of my way to make sure I get the most DE drops per hour. Could just be me and of course, for people already Paragon lvl.100, this could be very helpful.
    Posted in: News & Announcements
  • 1

    posted a message on Diablo 3 Announced for PlayStation
    D3 on consoles will be mediocre at best. There are just some ports that shouldn't happen and D3 to consoles is one of them, at least in my opinion.

    The original Diablo on the PS1 was a total flop. It felt unnatural and forced. In short, it sucked.

    The only way for D3 to truly be a success on consoles is to go far beyond that of a traditional port. They need to make D3 feel natural on the console. As if the game was designed; built from the ground up with the sole intention of being played on a console with a gamepad. To be frank, I don't see this happening. I believe Blizzard will develop a system that will be passable at best and, while technically will be D3 on a console, will still likely feel awkward.

    I predict D3 sales on the PS3 and 4 will also tank. Even if Blizzard pulls off the perfect port, the game has a fairly bad rep and until that gets turned around, I don't see it hitting big on consoles anytime soon.
    Posted in: News & Announcements
  • 1

    posted a message on Upcoming Change to Trail of Cinders and Patch 1.0.5, +x% Elemental Damage Mechanic, Diablo III Web APIs, Inferno Booster Pack C
    Quote from Emmerald

    It was a bug (miscommunication often causes bugs - did you hear about the Mars lander that crashed and burned because the development teams in US and Europe had confused feet and meters - the lander entered the atmosphere at three times the intended speed), and it was their mistake to not catch it in testing. They said that in their comments. So to me it looks like they _are_ owning to their mistakes.

    Then basically they're just incompetent. If the person behind the changes didn't notice that the ability was doing 1500% instead of the intended 300%, and as a result call it a 'bug', then yeah, there's no other logical explanation.

    I'd have more respect for a developer that simply states, "Oops, we made it way too powerful. Our bad, we'll fix it" over one that sayd, "The ability that says it does 1500% damage is actually doing 1500% damage and that's a bug that needs to be fixed."

    IMO, if an ability states it does 1500% damage and it actually does 1500% damage, that is not a bug. Overtuned? sure. Overpowered? Definitely. But, it's doing what it says it's supposed to be doing and just needs to be toned down and brought in line. However, if it said it was supposed to do 300% damage and was instead doing 1500%, then that would be a bug and I would understand it being called as such.

    As it stands, I don't appreciate Blizzard calling this a bug. They're adjusting a (very) overpowered ability, not fixing an unintentional bug. It may have been unintentional for the ability to be as powerful as it is, but this was not the result of a bug but rather an oversight.

    I read how they "explained" it's a bug. To me, that's just more insulting to people. I simply don't understand why they couldn't have come out and said, "We made ToC way too powerful. Our bad, we'll be reducing it's power to be more in line with where we originally intended it come next patch" That I would have been fine with.

    Let me also just say, I don't even play a DH. I have a 60 DH, but I sold all her gear so she's pretty much naked. This change means nothing to me. But saying that when the patch notes and tooltip of the ability state it does 1500% damage and it in fact does 1500% damage and then try to call that a bug a week and a half after the patch goes live? I call BS on that. Again, whoever was adjusting the numbers should have instantly realized 1500 is not 300, or they're incredibly incompetent and needs to find new employment. Even if by some chance they legitimately didn't notice at first, they should have immediately noticed it after the patch went live and a hotfix within 24 hours would have been okay. No, they waited nearly 2 weeks, then come to everyone and say, "ToC is way too powerful, but not because we made it like that but rather due to an unforeseeable bug. We're fixing this with the next patch". Yup, *cough* BS.
    Posted in: News & Announcements
  • 1

    posted a message on Upcoming Change to Trail of Cinders and Patch 1.0.5, +x% Elemental Damage Mechanic, Diablo III Web APIs, Inferno Booster Pack C
    Yeah, I don't buy the fact that it's an 'unintended bug' either. I believe they very much intended it to do 1500% damage, it's just they found out that 1500% damage over that short a period ended up being way too powerful. Instead of admitting that they overtuned the ability intentionally and are now bringing it in line, they're calling it a bug that they somehow missed.

    If it was always supposed to do 300% damage and not 1500%, and the tooltip accurately reflects what the ability actually does, it would have been noticed immediately when they originally changed it and would have been fixed immediately. The difference is too blatant to not notice, it stands out like a soar thumb. What actually happened is it was changed to 1500%, they tested it a little and thought, 'yeah, this seems good' and rolled with it. After the fact when every DH started using is when they realized, 'holy crap, we really overcompensated with this ability. However, instead of turning around a week and a half later and calling it a 'nerf' lets just claim it was an unintentional bug to save face.

    I agree with other people's statements. Just own up to it. Everyone makes mistakes. So an ability was overtuned and needs to be fixed. It happens all the time in League of Legends and they freely admit to it. ToC is too powerful and needs to be toned down. I get it. But don't play it off as some kind of unexpected 'bug'. That's just insulting to many people's intelligence that know better.
    Posted in: News & Announcements
  • To post a comment, please or register a new account.