god ur bad
@Ravid why do you keep feeding the trolls?
The thread has just become a cesspool of idiots who contribute nothing but flaming and toxicity instead of actually listing issues in the game or backing up the OP.
Ignore them.
Why would we back up the OP when he’s being an idiot?
Never seen a AAA mmo release with this many bugs. Maybe Swtor and look how their launch went. So which private server are we all re-rolling?
Yeah, but nah.
Probably the mindset that has caused their subscriber count to tank over the last couple of years.
i feel most people are mad not because it has bugs but because Blizzard has been so silent about the bugs and some of these bugs legitimately break some classes and have been broken since the beginning of beta.
Blizz also let layering exploits in Beta to continue into launch. Blizz knowing that exploits would ruin player experiences in classic in the hopes people would go back to micro transaction BFA. Classic would be the funnel to BFA. So don’t expect Blizz to fix things in a hurry.
MMO that released a month ago missed bugs in testing and aren’t fixed immediately. News at 11.
The fact that you’re not only quitting over this but making a forum post about it tells me you’re not that interested in the game in the first place, so no great loss to the playerbase.
A lot of these bugs have less to do with the initial programming and more to do with a shoddy port where much of the codebase wasn’t refactored and just “made to understand” the old data and, as a result, many things aren’t working as intended.
Additionally, we’ve seen items in their post-vanilla states and recently there was an improper order of execution for Hunter feign death which leads me to believe it’s a mix of the modern client and how it executes abilities which may work with a faster batch but have unintended consequences when parsed slower.
As someone who has ported games between engines and game consoles, it’s Blizz’s job to make sure things are executing properly by making sure they are in their 1.12 states. Just because you can hit a button and have it work doesn’t mean it is working correctly.
Even a simple damage calculation, if the modern client has changed any order of how it calculates based on any number of modifiers that can have an improper outcome if you don’t ensure the order of execution is correct.
TLDR; Most of the bugs are due to this being a shoddy port. Due to the game’s scale, I wouldn’t doubt Blizz didn’t put enough hands on the project.
I see daily updates on my feed about the retail game, but we don’t get any reply to our concerns in the bug report forum, or for classic in general unless there is an actual game destroying bug.
There are plenty of game breaking bugs live right now, some have been known since beta, and at best we have gotten summary replies with no deadline for being addressed or any further specifics.
My understanding is that classic doubled the number of subs for WoW, so why are we continuing to be treated as an afterthought and as second class citizens?
This game has bugs? Say it ain’t so!
Appreciate the bump feel free to read the OP when you get a chance
You’d think after 15 years of existing and Blizzard having billions of dollars, they can iron out some in Wow and not leave a bajillion in.
Can we at least stop getting nodes such as herbs and veins to stop clipping into the enviroment, please?
imagine having a game double your sub count, and putting absolutely none of that new revenue into that product
I did. You realize half the things you mentioned have been addressed by the devs, and those things can sometimes take months to be fixed?
No, they haven’t
You mean, like a beta?
Seriously, go look through the threads you just linked. There are blue posts and links to blue posts addressing them.
I’m the author of the first two threads. Each describe at least 10 major bugs with different mechanics.
None of those have ever been addressed.
In fact, of those posts, only 2 have blue responses
Hunter feign death, which has not been fixed. And the hit bug, which is game breaking and has also not been fixed.
The point you’re trying to make is irrelevant. Acknowledging something that has been known since beta means nothing until it’s addressed
Just be mad dude. We all want you to be mad.