#1 Hype-Thread Shitposter - Overlord of the Hypethread
They could've still released it on a non reset day, would just make it awkward. (or release on 23rd)
Tho they probably rushed it this week for the call of the scarab event
- - - Updated - - -
If preorders were to start soon, wouldn't the boost already be in the files? Or is that something that is encrypted or could be hotfixed in?
#1 Hype-Thread Shitposter - Overlord of the Hypethread
Nope, sorry. Those kind of communities only work because the general public isn't in there otherwise no work would be done because we'd be explaining things all the time.
I do see what seems to be the source of these rumors linked on Reddit.
It seems to make sense and I wouldn't be surprised if it ends up being accurate. We'll see soon enough.
Also, while they have growing pains right now from bringing 8.0 tech so long before the release of the expansion, it'll be a relief for the devs and the server team when the complexity of the 8.0 prepatch finds itself lessened by that. I don't have data obviously, but i'd also guess there are less active players right now than when 8.0 will launch (or shortly after that) so that also has to be a nice saving on customer support.
All in all I think it has to be a nice benefit for the team. Obvious downside being that, well, chunks of the expansion's changes have to be ready months in advance of the usual calendar.
And I'm sure management doesn't mind that they can get a lot of people back real soon with pre-orders/allied races being in already. Probably the biggest reason why 7.3.5 was rushed is so the Silithus stuff could get going and arrive at the part where allied races become relevant around a planned release of pre-order. I guess they decided they would rather triage the patch than delay anything else.
#1 Hype-Thread Shitposter - Overlord of the Hypethread
So basically, this let's them get all of the difficult backend stuff into play early, allowing them to deal with all of the issues that might arise on live without the extra stress of dealing with an expansion launch and the player rush from that.
Database related stuff, or at least stuff related to BFA would make sense. They basically pushed out a lot of encrypted stuff for BfAinto the latest patch, stuff that I would imagine would only typically come in a pre-patch months from now. I wouldn't be surprised if something that's a work in progress for BfA somehow managed to fuck stuff up on the live servers.
Originally Posted by Bigbazz
some thing that has me puzzled.
why are we getting a battleground that was suppose to be in bfa from what was said at blizzcon.
why put any 8.0 features in 7.3.5
why allow allied races even see able yet and why only 4 not 6
why rush 7.3.5
My theory
i think blizzard plans to put 8.0 ptr up soon unless there is 7.4 but i dont there is
8.0 has stuff that will effect all the game that need in depth testing
i think they plan to let first 4 allied races go up as soon a preorder does live which should be soon
Why do you think it is rushed?
new bg was never meant for bfa, blizzard said that on blizzcon.
I really dont get it, people expect to be all the same "lol, last raid tier, enjoy the lack of content until pre patch"
Now blizz try to break this and people call it's them rushing or something?
On the allied races, i guess its a story thing, so you gotta wait and see why.
All i know is that im having a blast lvling a new toon, especially on dungeons, being able to cast and finally see the bosses mechanics, i almost cried in joyness.
I guess its true, blizzard can never win.
the patch does feel kinda rushed, because it shipped with a fuckload of bugs.
anytime my dh does fighting, her tattoos smudge and go up on her hair. using moroes' polish makes my character's chest look like a flat triangle. old zg and scholo shit was dropping in zf and sfk. fps and lag issues everywhere. antorus lfr was broken, couldn't get to aggramar. wod and mop raid bosses being unsoloable. many many more as well.
it was one of the buggiest patches i've ever experienced, and i've played since mid bc.