World of Warcraft: Current Year
- Thread starter hodj
- Start date
Crone
Bronze Baronet of the Realm
- 9,709
- 3,211
My theory as to why they are so popular with today's teenagers is because of all the ignorant parents out there that restrict their child's video game playing to say, 2 hours a night, or whatever it is. So the kids eat that up quick, so they go from that, to watching it because they can't play. And the parents all the while are like well videos are cool, because at least he's not shooting people in a video game!
It's why I started watching as well, because I can't play at work, so it's a form of entertainment while at work.
Crone
Bronze Baronet of the Realm
- 9,709
- 3,211
Ha, I suppose that could be the first thing that someone thinks of me when I say I couldn't play from work.... Good one!
They were pretty boring to most people to watch though. I was fascinated by the automation and could watch it for hours, but I'm a little weird like that.
@Deathwing As for why use bots... It was mainly a keeping up with the Jones' syndrome. I'm pretty casual in terms of play times, but I wanted to keep up with the AP and gear, etc etc on all my toons. So it was a self-inflicted problem. Use the bot to get 8 level 110's, and now in order to keep up with the gear and AP on them all, the bot was necessary. I could hit 1 button, and it'd clear out all of the WQs on all my toons, for the day, and I could come back and open emissary caches for everyone.
But I've honestly gone Legit, not using a bot for anything, and plan to keep it that way. So the problem should fix itself as I will only have 1 max toon. I'll actually have a "main" , and therefore be much easier to keep up with AP and gear, and not feel the need to use a bot to keep up.
- 5,451
- 12,337
Two-boxed my monk/hunter for WQs yesterday, turned in Wardens on monk, get the bracer for his 2nd legendary (first was WW ring). Awesome.
Immediately turn in hunter's after monk's, and get his 2nd legendary as well. Its the pvp ring, his first was the shield neck.
Today I turn in my DK's Nightfallen WQ and he gets his 2nd legendary, and I had the loot spec set to Blood. He gets the tank belt. His first legendary was the frost spec belt.
lulz
Immediately turn in hunter's after monk's, and get his 2nd legendary as well. Its the pvp ring, his first was the shield neck.
Today I turn in my DK's Nightfallen WQ and he gets his 2nd legendary, and I had the loot spec set to Blood. He gets the tank belt. His first legendary was the frost spec belt.
lulz
Cupcaek
Molten Core Raider
- 742
- 454
Big legendary nerf bat coming
As we mentioned this during the live Q&A last week, we feel the biggest shortcoming of the current Legendary system is that, for some specs, there are some items that are clearly better than others in nearly all situations. As a result, players who have received a different Legendary item feel unlucky, as they didn’t receive the “best” one.
So, we’re making some fairly substantial changes to Legendary items intended to bring them more in line with each other. Items that give a raw throughput increase (without significant situational restrictions or drawbacks) are having their overall power reduced, and we’re taking another pass at several of the more niche items to make sure that, when they’re usable, they feel powerful.
Essentially, we feel that if a Legendary is only usable in certain situations, it should feel extremely valuable in those situations. Conversely, if a Legendary is nearly always going to increase your overall performance, that increase should be relatively smaller. Up until this point, we’ve made the mistake of allowing several items to be both extremely impactful AND always useful, which has made other Legendaries feel “bad” by comparison. It’s also caused some specs to feel as though they need a particular Legendary in order to compete. Those are the issues we’d like to solve.
We’re actively working on these changes right now and expect to have them ready for the next PTR build. We’ll be doing additional class tuning where necessary as a followup, once these changes are in place.
So, we’re making some fairly substantial changes to Legendary items intended to bring them more in line with each other. Items that give a raw throughput increase (without significant situational restrictions or drawbacks) are having their overall power reduced, and we’re taking another pass at several of the more niche items to make sure that, when they’re usable, they feel powerful.
Essentially, we feel that if a Legendary is only usable in certain situations, it should feel extremely valuable in those situations. Conversely, if a Legendary is nearly always going to increase your overall performance, that increase should be relatively smaller. Up until this point, we’ve made the mistake of allowing several items to be both extremely impactful AND always useful, which has made other Legendaries feel “bad” by comparison. It’s also caused some specs to feel as though they need a particular Legendary in order to compete. Those are the issues we’d like to solve.
We’re actively working on these changes right now and expect to have them ready for the next PTR build. We’ll be doing additional class tuning where necessary as a followup, once these changes are in place.
Crone
Bronze Baronet of the Realm
- 9,709
- 3,211
Did they create all the other new legendaries with this idea in mind?
There's been other references to how Diablo has made it's way into WoW, and I can't help but feel a sense that the way they went and started fixing D3 a long while back at this point is a little bit the same as them fixing Legion right now. They seem on the ball with what's not working, even if the original systems put in place are ass backwards.
Brikker
Trump's Staff
- 6,143
- 4,527
Any of you IT guys good with networking? I want to figure out what these retarded Africans did to the internet 5 days ago that makes WoW unplayable (and other sites shitty too). Used the battle.net diagnostic tool and got the following traceroute/ping:
I don't know how to read any of this shit; is anything on there obviously out of the ordinary? Game played fine with a 200-300 average ping for 5.5 months, then they do a "service update" and I can't play. Log in, sometimes it's okay for about 15 minutes, sometimes it is just instant lag (usually shows normal ping but it's actually in the 4000-5000 range) and can't do a thing. Eventually boots me.
Netflix has also gotten much worse; used to stream 720p np but now it struggles even loading and when it does it's very low quality.
TRACEROUTE:
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.726 ms 0.766 ms 0.856 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.710 ms 8.740 ms 8.758 ms
4 37.244.0.34 (37.244.0.34) 2.574 ms 2.618 ms 2.741 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.623 ms 37.643 ms 37.699 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.771 ms 37.570 ms 37.552 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.300 ms 37.443 ms 37.446 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.495 ms 37.309 ms 37.302 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.050 ms 37.175 ms 37.158 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.667 ms 153.071 ms 153.055 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.923 ms 152.936 ms 152.837 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.948 ms 152.844 ms 152.422 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.707 ms 152.723 ms 152.894 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.834 ms 152.705 ms 152.582 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.627 ms 152.666 ms 152.884 ms
14/12/2016 05:52:45 UTC
--------------------
TRACEROUTE:
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.398 ms 0.455 ms 0.495 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.244 ms 8.260 ms 8.302 ms
4 37.244.0.34 (37.244.0.34) 3.072 ms 4.482 ms 4.501 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.384 ms 37.409 ms 38.752 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.698 ms 38.759 ms 38.753 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.166 ms 37.231 ms 37.317 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.596 ms 37.657 ms 37.661 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.084 ms 37.065 ms 37.072 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.881 ms 152.840 ms 152.905 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.756 ms 152.806 ms 152.764 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.706 ms 152.467 ms 152.357 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.516 ms 152.530 ms 152.719 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.806 ms 152.649 ms 152.532 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.470 ms 152.564 ms 152.535 ms
14/12/2016 05:52:45 UTC
--------------------
PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.
--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms
14/12/2016 05:52:45 UTC
--------------------
PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.
--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms
14/12/2016 05:52:50 UTC
--------------------
MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 1.3 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 3.1 4.9 2.9 8.3 1.9
4. 37.244.0.34 0.0% 10 2.8 3.3 2.6 6.3 1.2
5. te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 37.4 37.4 37.2 37.5 0.1
6. be3032.ccr21.lax01.atlas.cogentco.com 0.0% 10 37.8 37.7 37.3 38.3 0.3
7. be2931.ccr21.phx02.atlas.cogentco.com 0.0% 10 37.9 37.5 37.1 37.9 0.2
8. be2929.ccr21.elp01.atlas.cogentco.com 0.0% 10 37.5 37.5 37.2 37.7 0.2
9. be2927.ccr41.iah01.atlas.cogentco.com 0.0% 10 37.2 37.1 36.9 37.3 0.1
10. be2687.ccr41.atl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.6 153.2 0.2
11. be2112.ccr41.dca01.atlas.cogentco.com 0.0% 10 152.8 153.1 152.7 154.3 0.6
12. be2806.ccr41.jfk02.atlas.cogentco.com 0.0% 10 152.6 152.7 152.5 153.0 0.2
13. be2915.ccr21.alb02.atlas.cogentco.com 0.0% 10 152.8 152.9 152.7 153.4 0.2
14. be2088.ccr21.ymq01.atlas.cogentco.com 0.0% 10 152.8 152.8 152.7 152.8 0.0
15. be3042.ccr21.lpl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.7 153.3 0.2
16. be2391.ccr41.lon13.atlas.cogentco.com 0.0% 10 153.0 153.2 153.0 153.3 0.1
17. be12497.ccr41.par01.atlas.cogentco.com 0.0% 10 152.4 152.5 152.3 152.8 0.2
18. be3092.ccr21.mrs01.atlas.cogentco.com 0.0% 10 164.0 163.9 163.8 164.0 0.1
19. be2345.agr21.mrs01.atlas.cogentco.com 0.0% 10 164.3 164.3 164.1 164.5 0.1
20. djibouti-telecom.demarc.cogentco.com 0.0% 10 224.2 226.3 224.2 232.2 2.2
21. 41.189.226.149 0.0% 10 225.8 226.0 225.6 226.5 0.3
22. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
23. 41.189.226.254 0.0% 10 224.9 225.0 224.5 225.5 0.3
24. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
25. 41.189.226.254 10.0% 10 225.7 225.4 224.7 225.9 0.4
26. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27. 41.189.226.254 10.0% 10 226.1 225.5 225.0 226.2 0.5
28. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
29. 41.189.226.254 10.0% 10 226.3 225.9 225.4 226.3 0.3
30. ??? 100.0 9 0.0 0.0 0.0 0.0 0.0
--------------------
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.726 ms 0.766 ms 0.856 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.710 ms 8.740 ms 8.758 ms
4 37.244.0.34 (37.244.0.34) 2.574 ms 2.618 ms 2.741 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.623 ms 37.643 ms 37.699 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.771 ms 37.570 ms 37.552 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.300 ms 37.443 ms 37.446 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.495 ms 37.309 ms 37.302 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.050 ms 37.175 ms 37.158 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.667 ms 153.071 ms 153.055 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.923 ms 152.936 ms 152.837 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.948 ms 152.844 ms 152.422 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.707 ms 152.723 ms 152.894 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.834 ms 152.705 ms 152.582 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.627 ms 152.666 ms 152.884 ms
14/12/2016 05:52:45 UTC
--------------------
TRACEROUTE:
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.398 ms 0.455 ms 0.495 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.244 ms 8.260 ms 8.302 ms
4 37.244.0.34 (37.244.0.34) 3.072 ms 4.482 ms 4.501 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.384 ms 37.409 ms 38.752 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.698 ms 38.759 ms 38.753 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.166 ms 37.231 ms 37.317 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.596 ms 37.657 ms 37.661 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.084 ms 37.065 ms 37.072 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.881 ms 152.840 ms 152.905 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.756 ms 152.806 ms 152.764 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.706 ms 152.467 ms 152.357 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.516 ms 152.530 ms 152.719 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.806 ms 152.649 ms 152.532 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.470 ms 152.564 ms 152.535 ms
14/12/2016 05:52:45 UTC
--------------------
PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.
--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms
14/12/2016 05:52:45 UTC
--------------------
PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.
--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms
14/12/2016 05:52:50 UTC
--------------------
MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 1.3 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 3.1 4.9 2.9 8.3 1.9
4. 37.244.0.34 0.0% 10 2.8 3.3 2.6 6.3 1.2
5. te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 37.4 37.4 37.2 37.5 0.1
6. be3032.ccr21.lax01.atlas.cogentco.com 0.0% 10 37.8 37.7 37.3 38.3 0.3
7. be2931.ccr21.phx02.atlas.cogentco.com 0.0% 10 37.9 37.5 37.1 37.9 0.2
8. be2929.ccr21.elp01.atlas.cogentco.com 0.0% 10 37.5 37.5 37.2 37.7 0.2
9. be2927.ccr41.iah01.atlas.cogentco.com 0.0% 10 37.2 37.1 36.9 37.3 0.1
10. be2687.ccr41.atl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.6 153.2 0.2
11. be2112.ccr41.dca01.atlas.cogentco.com 0.0% 10 152.8 153.1 152.7 154.3 0.6
12. be2806.ccr41.jfk02.atlas.cogentco.com 0.0% 10 152.6 152.7 152.5 153.0 0.2
13. be2915.ccr21.alb02.atlas.cogentco.com 0.0% 10 152.8 152.9 152.7 153.4 0.2
14. be2088.ccr21.ymq01.atlas.cogentco.com 0.0% 10 152.8 152.8 152.7 152.8 0.0
15. be3042.ccr21.lpl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.7 153.3 0.2
16. be2391.ccr41.lon13.atlas.cogentco.com 0.0% 10 153.0 153.2 153.0 153.3 0.1
17. be12497.ccr41.par01.atlas.cogentco.com 0.0% 10 152.4 152.5 152.3 152.8 0.2
18. be3092.ccr21.mrs01.atlas.cogentco.com 0.0% 10 164.0 163.9 163.8 164.0 0.1
19. be2345.agr21.mrs01.atlas.cogentco.com 0.0% 10 164.3 164.3 164.1 164.5 0.1
20. djibouti-telecom.demarc.cogentco.com 0.0% 10 224.2 226.3 224.2 232.2 2.2
21. 41.189.226.149 0.0% 10 225.8 226.0 225.6 226.5 0.3
22. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
23. 41.189.226.254 0.0% 10 224.9 225.0 224.5 225.5 0.3
24. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
25. 41.189.226.254 10.0% 10 225.7 225.4 224.7 225.9 0.4
26. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27. 41.189.226.254 10.0% 10 226.1 225.5 225.0 226.2 0.5
28. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
29. 41.189.226.254 10.0% 10 226.3 225.9 225.4 226.3 0.3
30. ??? 100.0 9 0.0 0.0 0.0 0.0 0.0
--------------------
I don't know how to read any of this shit; is anything on there obviously out of the ordinary? Game played fine with a 200-300 average ping for 5.5 months, then they do a "service update" and I can't play. Log in, sometimes it's okay for about 15 minutes, sometimes it is just instant lag (usually shows normal ping but it's actually in the 4000-5000 range) and can't do a thing. Eventually boots me.
Netflix has also gotten much worse; used to stream 720p np but now it struggles even loading and when it does it's very low quality.
moonarchia
The Scientific Shitlord
- 21,849
- 39,726
Just got 2nd legendary on my hunter. Shitty shield neck! But it's a big mastery item, and it has a gem slot, so I went ahead and got the good enchant and a 200 agi gem. My dps is actually getting decent, so I will roll with this. Hopefully someday I get BM ring, then I can ditch the shitty pants.
Crone
Bronze Baronet of the Realm
- 9,709
- 3,211
Repost over in the routers and other networking stuff thread in technology for more exposure.
Palum
what Suineg set it to
- 23,782
- 34,641
I don't understand blizzard retardation.
I mean their plan is to make situational legendaries powerful and nerf the current bis universally good ones. Great. Except now your bis will be swapping legendaries ever fight. That doesn't help the problem at all, that just makes it so instead of 20% of the population being happy with their good fortune in lego drops, now 100% of the population will be pissed at the drop rates and how specific legos have an even bigger effect in niche fights to help progression.
It's not exactly rocket surgery, you cannot put any powerful ability on anything then restrict reasonable access and not piss off the entire player base.
Not to mention, they've been fucking the game over for years to appease casuals and they introduce some of the least casual friendly grindy RNG mechanics ever to show up in WoW. No casual wants to do minor amounts of content for five months to see Sephuz finally drop. No player wants to see people who put in massively less effort get better shit that you are effectively locked out of getting for at least a few weeks because you just looted a shitter.
God damn they're just stupid to continuously double down on this lunacy.
I mean their plan is to make situational legendaries powerful and nerf the current bis universally good ones. Great. Except now your bis will be swapping legendaries ever fight. That doesn't help the problem at all, that just makes it so instead of 20% of the population being happy with their good fortune in lego drops, now 100% of the population will be pissed at the drop rates and how specific legos have an even bigger effect in niche fights to help progression.
It's not exactly rocket surgery, you cannot put any powerful ability on anything then restrict reasonable access and not piss off the entire player base.
Not to mention, they've been fucking the game over for years to appease casuals and they introduce some of the least casual friendly grindy RNG mechanics ever to show up in WoW. No casual wants to do minor amounts of content for five months to see Sephuz finally drop. No player wants to see people who put in massively less effort get better shit that you are effectively locked out of getting for at least a few weeks because you just looted a shitter.
God damn they're just stupid to continuously double down on this lunacy.
- 1
Fyff
Ahn'Qiraj Raider
- 2,707
- 5,172
Rogerbrown streams daily during the week. My last hour of work I am the only one in the office so I watch streams a lot. I watch him and Azor with the sound turned off. Both interesting to watch because I can see two people succeed with the same class in totally different ways.
Qhue
Tranny Chaser
- 7,495
- 4,446
I'm not at all surprised by the legendary item changes. They are a cool idea to inject some added "oompf" factor and obviously borrowed a lot from both Diablo and Destiny in their implementation. The failure was two-fold:
1) They were too rare and so it was less a matter of choosing which 1 legendary to use and more a matter of using whatever one you happened to get. The limit of only being able to equip 1 means nothing if you don't have to make an actual choice. Similarly getting to equip a second should have been a BIG deal, but not many people even had a second one by the time it was unlocked.
2) The interns they had doing the itemization specifics did not know how to use a calculator. A good number of them are instantly recognizable as great and even more as terrible. Even a cursory review should have uncovered this and be passed back with a note like "please send the use-case calculation to justify X". Obviously players will always come up with niche symmetries that you don't foresee in testing, but that wasn't the case here. Many of the items were awesome or miserable right out of the package.
I just hope they don't end up with them all being absolutely boring. The ones that required a different play style to make maximal use of should provide a nice benefit as reward for making things more interesting.
1) They were too rare and so it was less a matter of choosing which 1 legendary to use and more a matter of using whatever one you happened to get. The limit of only being able to equip 1 means nothing if you don't have to make an actual choice. Similarly getting to equip a second should have been a BIG deal, but not many people even had a second one by the time it was unlocked.
2) The interns they had doing the itemization specifics did not know how to use a calculator. A good number of them are instantly recognizable as great and even more as terrible. Even a cursory review should have uncovered this and be passed back with a note like "please send the use-case calculation to justify X". Obviously players will always come up with niche symmetries that you don't foresee in testing, but that wasn't the case here. Many of the items were awesome or miserable right out of the package.
I just hope they don't end up with them all being absolutely boring. The ones that required a different play style to make maximal use of should provide a nice benefit as reward for making things more interesting.
- 48,509
- 285,370
It just reeks of more "You think you do, but you don't" level arrogance from the Dev team. It feels like all of the talent from Blizzard has either retired of left and now you are stuck with a group who have altered the game so dramatically from it's roots that its no longer even close to the same game.
Noodleface
A Mod Real Quick
- 37,961
- 14,508
I guess what gets me is people gave/give me a lot of shit for my lack of playtime and they're botting under our noses. Crone wasn't the only one, just the only one being transparent about it currently.
- 6,029
- 5,915
Not sure why anyone is giving you shit. You show up to every raid, most of which you're leading as well as MTing, you own up to your mistakes, and you're prepared for fights. We're not a hardcore guild. I feel that that's about as much as you can ask of anyone in this situation.
- 1
Noodleface
A Mod Real Quick
- 37,961
- 14,508
