There’s no more US East region. It all falls under USW now, this change happened silently about a year ago. You can check by looking at regions in the custom games list.
Okay thanks.
I’m gathering info about this to pass a report along to Bliz. I can’t promise anything, but at least someone there will know.
I also forwarded that year-long thread about this that’s in the Bug Report forum, so we’ll see what comes of it.
1 Like
I appreciate that! The latency has always been bad on Warcraft 3 Reforged, but it definitely got worse some time in October/November of 2023.
There’s another thread someone started about a year ago:
Yep! That’s the one I forwarded to Bliz.
It’s got a good representation of the issue’s history.
1 Like
The sad part is that they could have kept the old game client and just update is slightly, while hooking it to the new Battle.net. That would have been VASTLY cheaper and faster. Instead, they wasted millions on this “deforged” turd, and called it a day.
2 Likes
You clearly have no interest in having a civilized conversation with others. if you can’t write to anyone else without being inflammatory, just don’t write anything at all. This is the final time I will tell you. Beyond this point, I (and probably most of us) will just flag your posts and block you (which I can’t truly do permanently, but ignoring someone “Forever” will remove them from the ignore list after 1,000 years).
You can disagree or dispute opinions without looking like a child.
1 Like
Misinformation. It is in fact, still largely the same game client. The only thing that’s changed (besides adding new art, adding new bugs, and some other things) is the main menu interface.
This is why “deforged” was implemented as patch to the game rather than a stand alone product. Because it basically was exactly that. Just an update.
And as I’ve explained many times on this forum, it didn’t have to turn out this way- It’s not the fault of the people who worked on the game, who did so in good faith. The fault laid with Activision, who for whatever reason decided the project wasn’t really worth it but also didn’t want to upset people by cancelling it (at least, thats my best guess on the reason), and pulled funding and staff from the project. Thus, what we got was such a failiure because the dev team wasn’t given the resources they needed to actually complete the project.
And now, nobody that is involved with the project now was part of the original team, so there are some things they’re simply not going to be able to do, as it would require months of analyzing the existing design and code base to truly address the current issues. In short; If you feel the need to keep beating this horse, remember that it’s not the dev’s fault, it’s the publisher’s fault
1 Like
I doubt that you are right, because Reforged also seems to have a new renderer, and many OLD features are broken.
1 Like
I am right. Don’t take it from me, take it from Architct, a poster here who worked on the game and also the retrospective video posted a long time ago by another dev which illustrates the issue.
It’s obvious that you say this because it’s me, and not because of any rational or logical reason. Stop projecting your personal dislikes and accept the actual truth.
It was not developer incompetence, it was publisher ghosting, defunding and staff reallocation that caused Reforged’s failed launch. Blizzard had hired people who worked on the original game to handle the remaster. But by the end, they had only one level designer to re-make all the campaign maps for Reforged, which originally took a whole team of level designers multiple years to complete.
Yes, they did add modern DirectX support, but that’s about it. The engine HAD to remain largely the same in order to keep compatibility with any existing custom games.
1 Like