i mean k, i get it, and i also think they should remove the fist weapon only restriction.
but comparing this to the dh's warglaives is pretty dumb.
Formerly known as Arafal
I mean, we only have 145 different FW models (most of them being recolors), but people compare it to Warglaives cause the excuse used to say "They have a different model and animation than other weapons that it makes it hard to allow transmog without it being somehow broken, and are not that "alike" as Staves, polearm or not as simple as Swords, axes, etc..." but now we got another new weapon, with many new animations and it doesn't have that restriction
The animation argument is 100% invalid anyway. Tons of classes can alternate between animations already by simply switching weapons. I get that you can't transmog a wand into a 2H sword but they could at least give some options to remove the very restricted visuals for an entire expansion.
I hope we get a cosmetic helm or toy that looks like the masks we wear in Suramar
The fist weapon thing isnt really bothering me. I will be having those totems from the highmountain on my back for compensation (on my orc, I am not a taurennoob)
I don't have the link to it, but I remember a blue post in the past stating that it's a major coding issue regarding the animation of fist weapons that they haven't been able to figure out. Yes, I"m sure you could argue that they could throw countless man hours into fixing it but I would assume it's a really difficult one to fix if they haven't been able to at this point.
Need a build tonight to fix the enormous phasing issues
#nophaseclub
All weekend /2 has looked like this:
"pls inv for working Dal phase."
Repeat 20 fucking million times.
The Beta forum post on the subject was growing by like 5 pages per hour with an unending stream of people coming in and reporting the same problem ad nauseum.
Look on the bright side.. there is absolutely no way Blizzard will allow that situation to happen at launch. And if it does.. they deserve to be savaged for it. It's the Legion version of the Warlords Garrison bottleneck. I hope for their sake they've already fixed it. Having all players in the same local zone at the launch of an expansion always seems to end in tears.
Im fairly certain that this is what they were trying to avoid with the auto-phasing tech that was supposed to split large concentrations of people up into separate temporary instances. Unfortunately the phasing tech seems to have gone self-aware - Skynet style - and is putting almost every player AND the npcs into separate instances, so nobody can see or interact with anyone else. And as of Saturday evening, Blizzard doesnt know why it was happening.
It doesnt seem to happen until after you finish the Broken Isle pre-quest (which is mandatory now, unlike Alpha), then get to Dalaran for the first time to start your Artifact quest.
They are working on it. So I doubt it last more than a couple more days.
@Zorbrix
Work continues on Beta stability; the phasing/NPCs vanishing issue is our #1 issue.
Thanks for being patient while we work through it.
It wouldn't entirely surprise me if they intentionally scaled back their beta infrastructure so that they could get a good stress-testing analysis of where their weak points are, to simulate the deluge of players they might have at launch. That could be one cause of the phasing/lag issues everybody has been experiencing. Not to say that they intentionally forced the phasing bug on players, but rather that they may have created circumstances where the servers would be overloaded so that they could expose problems like the phasing bug.
I wouldn't blame them for doing this, but I imagine that a lot of beta testers would launch into tears about how their fun was impacted just for the sake of minor things like "testing", so if they did take this course of action I probably wouldn't expect them to admit to it.