Okay, calm down. Phew. You got this.
Alright, so after going through the many troubleshooting steps only to find this nearly 24 hours later and then being forced to wait another 15 mins for the game to let me unstuck my character has driven me over the edge, so. I’m more than a wee bit pissed off.
This is an issue with 8.3 (and possibly earlier) that I have seen on the eu. and us. forums now that I’ve found keywords to lookup. Apparently when flying into silithus or leaving the portal to the heart chamber your character can get into some sort of “stuck” state where you can’t move or you instantly Crash-To-Desktop or it kicks you to the login screen. After deleting all of blizzard’s software off my computer, flushing my dns, resetting my router, wiping my port forwarding and server port stuff out, and causing me another 20+hours of work, I have just now found this article that showed me there is a character unstuck feature on the web (since I can’t hearth while flying or do anything without being D/C instantly and logging back in where I was.) that appears to fix this issue with your game.
The problem is; that char stuck thing isn’t listed on the help article related to our error message ANYWHERE. So, go fix your error message help. I know that it’s probably automatically generated and that the error is probably a generic one but you should still at least put it under the advanced tab when explaining other things to try. Or maybe, try that first since you know most people don’t even know what a cmd prompt is.
First.
That in and of itself shows how completely inept and moronic your team is that designed the help articles. You should do something about that. Seriously. I know people probably tell you guys to fire people and get all mad, but seriously just fix the issue and put the char stuck thing in there so people know about it.
Second.
Why is this still happening to players 10/2/2020 when this issue has been popping up since (the earliest I’ve seen, but not intentionally looked for) is january 2020. How in the world could it take nearly 10 months and you guys have no fixed this GAME BREAKING BUG. I deleted literally everything and had to reinstall around 70GB of game, and then get the shadowlands prepatch which is around another 20GB of data. Plus, I got so mad because the game was crashing to desktop (not even showing me the error at login screen.)
Third.
I have more details to report. Not that you will even send this to a programmer who will investigate further, or attempt to fix this issue because of your ineptness and inability to actually get anything done as customer support other than relay crap they feed to you.
3.A. - When I first encountered this issue I had just ding’d 110, grabbed the quest for allied races, interacted with the flags at the embassy thing in stormwind, went to the docks, skipped the cutscene, went straight to uldum portal, took it, fly towards the sword in silithus. As soon as I crossed the border and got about 15 seconds in I began CTD’ing. Let me explain. I CTD’d. Then I logged in, and attempted to keep going and CTD’d again. Then I logged in and stayed put for a few minutes thinking maybe something wasn’t loaded, then I CTD’d again after moving forward.
Here’s where it get’s interesting.
3.b
I began looking into the problem so I checked for logs, deleted my cache/wtf/addons, logged back in, same thing. No logs. Except I got the intro cutscene when playing wow for the first time. this is the clue.
3.c
Then I deleted wow’s executable (not the launcher but the one inside /retail_ or whatever) and scan and repaired and tried again. No dice.
I deleted the game, I pulled up the game after redownloading it, reset ALL settings, and then logged in to my character - this time instead of crashing to desktop when attempting to move or do anything, it kicked me to the screen with the error WOW51900319 and it began playing the cutscene from the previous attempt again behind the error message. (strange?) So, I have no idea why this time it didn’t CTD but instead played the intro cinematic. But that’s the only clue I had which was this generic error message. That eventually lead me down a rabbit hole nearly 35 hours later that lead me to the european forums which then lead me back to here and I discovered there’s a web based unstuck feature that resolves the problem because as soon as you leave silithus and come back you no longer have the issue. It’s the only clue I got for any developer that actually knows how to code to debug and try to figure out. But, it may not even be related so I thought I’d share just incase it is a settings issue that is causing the 8.3 silithus character stuck/ctd/wow51900319 error.
Finally,
People have been having this issue since 8.3 as far as other’s have stated on EU forums. I’m insanely impressed you guys have not fixed it yet. I imagined a multi-billion dollar company could squash a tiny, insignificant, puny, game breaking bug such as this, in a fraction of that time. But hey, it’s my $15 I gave to you for “service”. It’s cool. **** us, right? Customer’s don’t matter, just MAU. (which is why you delayed shadowlands right before pre-patch was supposed to happen; to get that extra MAU count up, right? Right? (looking at you SOO/WOD prepatch (3monthslongugh))
Oh and if you write my last comment off as a baseless accusation I wonder what the data shows, and how long does it take to balance a class with like 4 buttons and a few passives? Adjust the numbers during beta more. Where is your teamwork at? It can’t be that hard to get all the dps classes within 5% performance of each other during beta. Wow has the most sophisticated dps simiulators I’ve seen in a while. Not to mention I’m sure there’s people that have had damage meters going during beta. All of it screams incompetence from my eyes as a customer/game player. So, write it off if you think I’m being too harsh in my criticisms, it doesn’t change my mind that someone somewhere within blizzard is being like this because “I’m too busy” or “I’ve got other stuff to do first” or whatever reasoning you like, you’re still inept and poor at programming your own game when you let CTD bugs exist post-launch and post-multiple patches extending well over a year’s period.
