Patch 1.29 BUGGED

General Discussion
1

When the Reforged guys were making Patch 1.29 at the office, some snarky guy was given the title of Data Guy whose job it was to “maintain the data” and he moved many files to Deprecated.mpq. For other files, he moved the file location as if to better organize them.

One of his snark changes on Patch 1.29 that makes it different from Warcraft Legacy (real version by Vivendi’s Blizzard, not yours) and also different from Reforged (where Reforged guy fixed it because he reached out to me for help and I explained it) is the snark renaming of files to make them more ideologically organized.

EXAMPLE:

Patch 1.00 - Patch 1.28 has this file:

Buildings\Naga\AltarOfDepths\NagaBirth.MDX

Patch 1.29 has this file:

SharedModels\NagaBirth.MDX

Patch 1.30 and beyond ( The Reforged ) have filealiases.json as a redirect to fix this bug, which maps references to Buildings\Naga\AltarOfDepths\NagaBirth.MDX back to SharedModels\NagaBirth.MDX.

Now you have published the one specific version where Mr Snarky Data Guy changed the location of the file as if it were the definitively legacy edition of the game. But actually, 18 years of legacy maps that might refer to the Altar of Depths specific file path are broken on this version. (Example custom graphic that is broken can be found at https://www.hiveworkshop.com/threads/turtle-hatchery.302771/)

This is not an isolated case, every Naga building had a copy of this file that got lost. Similarly there were probably other files that moved. I don’t remember all of them off the top of my head.

For people who want to have a working Legacy client, that usually means entirely working – no missing assets moved by Mr Snarky Data Guy while he was building Reforged. Do you think you could put the assets back to their legacy locations – or even better introduce the filealiases JSON file to be supported on 1.29?

This is the kind of problem you introduce when you publish a version and call it legacy, unless you have the gumption to publish a version from before the Activision merger so that the program has no missing files and works in its entirety.

4 Likes
Legacy 1.29 - I can help you fix your bug again
2

Who is this guy?

3

I do not know the name of Mr Snarky Data Guy. I do not particularly care. I just want my old video game to work!

1 Like
4

@Retera - would be good to move to Technical Support or Bug Report sections.
A lot of issues are with Legacy, someone should have a look, and also consider increased resolution beyond Full hd.

5

It works no better or worse than it did when it came out, it is the same version now as it was then. The only thing that’s changed is your hardware and software.

1.29 has been released as-is, it will not be updated or supported beyond technical issues caused by their deployment of it. About the best you can do is try to convince them to release some other old version of the game, or just find it yourself because there are installers all over the internet.

6

Right, even though it might work worse than The Frozen Throne by Vivendi Blizzard as mentioned above in this thread.

This would be nice but the older versions of the game are vulnerable to security issues.
So then what?

7

Every old version of software is vulnerable to security issues. But let’s be real here, most people are not playing an old offline version of the game so who is going to attack it?

And really it doesn’t matter. This version was released as a courtesy so people could play some old maps that don’t work in Reforged. Aside from playing it on the oldest possible machine that will open the battle.net app there’s not a lot of other reason to go back consdiering that, while it took 5+ years, the game is playable just fine now (aside from matchmaking related problems)

1 Like
8

We are talking about some poorly placed files and folders here, possibly also some incorrect references. This could probably be fixed quite easily by the dev or installer who handled the build.

9

You’re wasting your words here, Retera. They won’t do anything about it. Imagine they did the fix, then what? Repack the game? What would be the version number? 1.29-rev1? And what signal will this effort send? Like they will overturn the whole WC3 Reforged thing? Not to mention that the bug is already fixed in Reforged.

I would rather say that 1.31 is much better than 1.29, as 1.31 is the last Reforged-free version. But they still choose 1.29, because of what? Perhaps because they know after 1.29 they break a lot of internal workings, and 1.29 is the first version with dx11 and widescreen. They didn’t know 1.29 is also buggy. Even if they knew that, what would they do? Pick 1.28 = no widescreen. Pick 1.31 = admit the Reforged disaster.

11

1.29 is MPQ , 1.30+ not

1.00~1.29 is MPQ

1 Like
12

Can be 1.29.1 / 1.29.2 if they support 3-number patching, or 1.29b / 1.29c like the old Blizzard style – whatever fits their versioning system.

It’s not about admitting anything – it’s about stability and compatibility. 1.29 just sits in the best middle ground between too old (1.28) and too “Reforged-era” (1.31).