The legacy version is now available for download and play. It takes around 6.25 GB.
So far, it looks like the Battle.net servers for it are not accessible, it’s probably only available for local and offline play.
5 Likes
Still nice to have it officially supported and not shoved behind a curtain
3 Likes
It was always available through other channels, and otherwise nothing has changed, it still can’t be played online which means if you want to insist on using an old version you’re limited to playing campaigns and offline custom games.
It was never “shoved behind a curtain,” anyone could find and download it for free with a simple google search.
Also… I’m not sure where you’re seeing this. Unless it’s on the battle.net shop, and I can’t find it there, nothing has changed. It can’t be found anywhere in the battle.net app and is only available to download from their file servers or from other sources.
It’s not supported in any way. Being able to download it doesn’t mean its supported. Supported means you can get help for it if it doesn’t work or whatever. And they will not do that.
Go to Warcraft Reforged and above play button you see a menu where you can choose PTR version, Warcraft Reforged and Legacy 1.29.
1 Like
Ya know what…
That is nice of them. Wish we had more versions to choose from but even having this is a nice thing they could have just chosen to not do so kudos to you on that, Blizzard.
EDIT: From the official announcement:
Fair enough.
1 Like
It seems Cinematics aren’t work for whatever reason, if anyone knows a work around please let us know also Kaivax if you could report this back to Warcraft RTS team that would be amazing
1 Like
I would like to add that the client is also, at least on my end, pulling from the Reforged maps directory in the Custom Game menu, leading to no maps being able to be selected besides any downloaded maps.
I wonder if “own warcraft 3” explicitly means owning Reforged.
2 Likes
Why is it so many GBs?
patch 1.27 was less then 2gb, so what made 1.29 to 6.25GBs?
1 Like
Why did they pick 1.29?
1.31 is also pre-reforged, and although it was gearing up for Reforged it wasn’t buggy at all like Reforged was. It was also 64-bit and had some amazing new features like increased player count.
The reason I ask is that 1.29 is 32-bit, which means it doesn’t run on any Mac that can run the battle.net launcher, making this release a complete waste of time over here.
1 Like
OK i see it now
1 Like
just to make people complain about data size. IDK maybe it’s got a bundle of nonstandard maps in it.
Seriously idk why this is such a big deal to people, just delete something and make room.
1 Like
maybe blizzard is concerned about the PCs and laptops that no longer could run the game since behind the scenes it shot up the system requirements to dx11. only something like this would be noticed by someone that barely met the Windows system requirements ¯\_(ツ)_/¯
1 Like
aaaannndddddd the cinematics don’t work :\ and maps won’t show up but overall this is still a cool thing for them to do
2 Likes
you forgot that blizzard is now microsoft right?
1 Like
The maps dont appear, so i can only play the campaigns; and why only english? Where is the rest of the languages??
I hope they fix this soon. They just cant let us install the classic game just to play the campaing and with 1 language only.
1 Like
Another comical decision from the authority department. Now everyone will be incentivized to hack the old game and connect it to unofficial servers. Why is there not an official server for this?
1 Like
That’s great. Thank you.
1 Like
SO WHAT IS THE POINT OF HAVING THIS IF YOU CAN’T PLAY ONLINE WITH IT? HAHA. OMG, BLIZZARD 
https://imgur.com/a/dkmKheZ
Nice full screen
2 Likes
I like this fan-service. Seemingly out of the blue, surprising even those that normally may be informed (but under NDA). I like how it restores the correct colors, very pronounced at the darker blue mana bar for heroes, and creeps now start with correct mana pool (note that the 100% mana pool was an unintended or at least unmentioned surprise change in patch 1.30 which prepped for reforged release).
There are however, quite some problems. Note that many of these need need repeated testing to lock them in as a known issue.
- There is no online (BNet) functionality (seems to be by design, but misses the point of what made legacy so awesome)
- Legacy seems to pick up the reforged folder location for maps. Due to different coding however, these maps don’t show in legacy UI.
- Hitboxes are similar to reforged, see below.
- Pathing is similar to reforged, see below.
- It would be great if it would pick up the customkeys.txt people use in reforged.
Hitboxes and pathing is a known issue, but a very under-represented problem.
The hitboxes is actually well known: items under a creep are very difficult to pick up. Since Reforged the cursor-priority has changed. Making it insanely difficult to click some specific objects. The items under creeps is most evident to the player base. It does happen more often: sometimes specific trees are insanely hard to target with a worker. It is very difficult to target enemy units which are partially hidden behind allied units with share unit control. In addition, many people have noted that in reforged it is much harder to surround enemy units, and enemy units may occasionally ‘pop’ or ‘displace’ themselves out of a surround. This coincides with people stating that units are just harder to select, most noticeable with a group of smaller units (militia, ghouls, footmen) in which its hard to click and correct individual units. E.g. clicking one selects more easily in selecting multiple or an unintended adjacent one. This poses interaction problems, which did not exist in legacy, at least not pre 1.30.
The pathing is less easy to articulate, and frankly we [being veterans with a memory muscle] are surprised that the pro-scene isn’t (or wasn’t) more upset over this. Although at times it operates in conjunction with the aforementioned hitbox issues (e.g. surrounds).
Most notable you see occurring in games somewhat frequently:
- Creeps do not return to original spawning location after agro
- Creeps not returning to sleep at night after agro
- Creeps retaining agro even when the player went well out of leash range for a longer time: prompting creeps to actively re-engage minutes later when the player re-enters leash range. As creeps have visions as-if they are air units, the pro-actively show up out of the fog from the player POV
- Creeps have different interaction and redirection logic. On TM the level 6 troll at the neutral shop will prioritize in range statues over DK and fiends - likely due to the autocast ability. But in 1.27 that wasn’t the case; the troll would only target the statue if it was the player unit in its closest proximity. For those having legacy 1.27 installed, this is very easy to test.
The issue is however more obscure in detail. Even in 2020 I’ve reported a 2on2 AT game with Thaedalius on Synergy. The enemy expanded and builded some defensive structures. We couldn’t target the buildings in front - no matter what. Reported on these forums in March 2020 and Thaedalius confirmed the odd behaviour in the thread. I recently experienced similar again. Hard to replicate though. At times we do see that a large base, walled of at 1 side and open at the far end, seems to ‘trap’ units that spawn inside the base. They simply can’t find their way out. No idea why. This never happened in ‘true’ legacy’.
Pathing summary: something odd has changed. But it is there beyond a doubt. Like a black hole before we discovered them: we can observe objects move oddly, but we can’t pinpoint the exact object prompting these mechanics.
4 Likes