Their idea of testing it to force it live and experiment what will happen. They really need to throw this on a separate servers like Live Beta or something so they can see the sparks fly before making the actual live servers spark and malfunction.
1 Like
No teh answer is that they were working on Beta and teh PTR , but as usual the transfer to the live realms can cause things not to work . Bugs fixed on the testing realms suddenly reapear on live ones ( usually for different reasons than what was fixed on the test realm . A lot is caused by people on live doing things that nobody did on teh testing realms . You cant plan for that - If no one has done it before how do you know it exists . There is no way that the minimal people on tehtest realm will do everything that happens on live realms
This is why you recreate a big server for beta testing before sending it out to live servers. You stress test it.
2 Likes
Generally not into WoW + external pop culture names but yours is quite good.
Well done.
1 Like
its got nothing to do with stress testing . Some people will do a thing in game that no one else would even think of doing in a million years . This has been my bane at work , we introduce a new piece of software that has been strenuously tested only for an operator to something no one would even dream of doing and crash teh system .
And thats with modern code , not a 20 year old spagetti system that doing something in say STV cause something not to work in valdraken.
This will only get worse as we add more code - its not the timeways we need to worry about , its the codeways
1 Like
2 things I say every time this stuff happens:
-
They could have delayed for 3 months and it would still be a broken buggy mess.
-
Live servers are the real Beta test.
The spaghetti code in this game causes a ton of problems, and even if they made a duplicate of a live server to test the launch on, we’d still get this kind of launch.
Here’s hoping (sniffs packet of copium) week 2 of this patch has things working again. In the meantime I find myself with even more spare time since I’m not about playing the game when it’s busted. 
//“broken”
It seems smart to me. Testing wont find as much as this current method will based on numbers alone. Its either 100 bugs in pre-patch or 75 on launch. No one cares about pre-patch.
I found another solution: You can just pull up the talent window, and manually choose the starter build and that will fix it too.
The game seems fine to me. Enjoying my main and new alt. I’m not sad at all to see whiny over-reactors un subscribe. It makes the game/community better for the rest of us not having that kind of personality around.
eh?
it’s literally always busted.
have you ever seen a day go by where there have been zero bug reports posted?
cracks me up how every major patch is THE WORST EVER
…and even when it’s working as well as it possibly can, people will invent something to complain about.
GD:
if status.game == broken || prepatch == true
{
status = normal
fixYourGame(featuresBroken,extendedMaintenance)
}
else
{
status = wtf
wowIsDead(devs,incompetent)
}
2 Likes
Just out of curiosity here have you grabbed bugsack and checked to see if you’re getting a ton of errors? That seems really odd. I took a hit too but it was a small one, and I was able to isolate why. IF you have anything modifying nameplates at all (even stuff not erroring out) try disabling those. For whatever reason they changed a significant portion of how nameplates are handled and this was a source of a lot of the fps hit for me.
The perfect time would have been their 20th anniversary.
Do you know this for a fact? Because to know this you would have to watch over the shoulder of everyone doing any development.
In big projects software is often given out to people or groups to develop in layers. Think of the user at the top and the hardware at the bottom so the subroutines get called “from above” and call subroutines “below”.
I would always build a test driver for my layer and I would build model support routines that just returned specific replies. I would coordinate the driver and support models so I could run through every path of my code to find bugs. As a result, I hardly ever had bug reports coming back to my code.
But no one ever knew this (no one ever cared) so how would a customer know if I was doing this or not? Unless you actually talk to the developers and unless they actually want to tell you how they work, how would you ever know if they did any testing?
It’s not new but it’s progressively worse over time. Back in Wrath a patch, especially a prepatch, might have a handful of issues and most of the time they were not game-breaking serious. These days the known issues list after a patch are like yards long and the game is broken and janky is so many places.
1 Like
Do you know this for a fact?
I forget whether it was Ion or JAB who said they felt QA was an unnecessary cost and a waste of time. And that QA positions were not careers.
What does that tell you?
They’ve also admitted they’ve been outsourcing for development for awhile now. A good chunk of DF was outsourced, including the UI revamp which was outsourced to a single guy (I’ve seen the interview with him) who apparently had no experience in UI design for anything except mobile games prior.
2 Likes
When I was doing software any test group was always the first to get hit with layoffs. I agree, upper management doesn’t see it as a priority. But if too many bugs come in, oh my gosh how they howl.
So I didn’t wait for someone else to test my code. I tested it myself and made sure it was bullet proof before anyone else could touch it. As a result, I can’t remember a single bug that came back to my code. Maybe it did after I moved to another group, but not while I was there.
As for upper management, who ever listens to them? They get all worked up about some nonsense, call a meeting to tell us about it, demand we fill out forms which half the time you don’t bother to do and soon enough they are off on some other crusade.
Back down in the trenches we just kept designing and coding.
Hilarious how that translates across industries. Sounds incredibly familiar.
1 Like
They really did give us a thousand minor cuts that equate to a bleeding artery with this patch. Just a ton of small things broken.
1 Like