• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

Warcraft 3 Legacy 1.29 version now available!

As a drawback, I noticed that the Reforged Classic 1.29 client collides with the game installed from CD-ROM drive. Both executables work, but there's a settings and installation path interference.
Dang, I'd been waiting for someone to report on whether this interfered with other legacy versions...

I don't have the new battle chest, so I haven't been able to install this yet, but when I do (since I want to add the Community Edition to my set of installations) I don't think I'll use the battle.net client; I'll just use 1.29 from here to try to minimize any risk. I'm hesitant to link my legacy installations to updatable clients.
 
Unfortunately, the same problem where you must purge the "Tool Windows" registry stuff for unlocking the legacy 1.29 WE after opening the current version of WE still applies. Also, both legacy 1.29 and the current one still uses the "Documents\Warcraft III" as a location for storing important stuffs (maps, replays, campaigns, etc.) It would be fair for the legacy 1.29 to have those stuffs being stored in game folder, which was the old way (I think this was abandoned after 1.27b).
"Fixed a compatibility issue when trying to launch different versions of the World Editor."
?
 
I'm hesitant to link my legacy installations to updatable clients.
I think I am at a point of being sufficiently cynical that if a bunch of people download 1.29 from BNET and then it later is hit by a patch that automatically replaces it back to Reforged like the last time it was a live version, I would just laugh at all the affected people for ever trusting Activision Microsoft. I guess maybe that's not a good headspace.
 
Do we get the ability to use "Game Cache" for LAN games as well, instead of singleplayer only? Or still will have to use codes that can only be used for hero stats? I want to be able to save base layouts and other stuff for multiplayer games:cry:

TL;DR I JUST WANT TO SAVE AND LOAD PERSISTENT DATA IN MULIPLAYER !!!
 
I think I am at a point of being sufficiently cynical that if a bunch of people download 1.29 from BNET and then it later is hit by a patch that automatically replaces it back to Reforged like the last time it was a live version, I would just laugh at all the affected people for ever trusting Activision Microsoft. I guess maybe that's not a good headspace.
I rather trust bethesda or idsoftware with this issue than Blizzard

at least the former praises their modders at quakecon
 
1.28.5 is only reasonable choice, simply because 1.29 has gamebreaking bugs, like audio not working (only general sound are playing, but any scripts that call for audio on unit or location position won't work), ui and board interfaces broken.
I'm not quite sure 1.29 has a lot of gamebreaking bugs compared to 1.28.5. I heard that according to some reports, some bugs were minimal compared to 1.31.

1775752022713.webp
1775751930774.webp

Btw, 1.26 is the most stable patch AFAIK as it's the last one to be developed by the original Blizzard team from 2002, albeit lacking proper Widescreen and 24 players support.
 
"Fixed a compatibility issue when trying to launch different versions of the World Editor."
?
OMG, I've should know about that before.
 
I'm not quite sure 1.29 has a lot of gamebreaking bugs compared to 1.28.5. I heard that according to some reports, some bugs were minimal compared to 1.31.


Btw, 1.26 is the most stable patch AFAIK as it's the last one to be developed by the original Blizzard team from 2002, albeit lacking proper Widescreen and 24 players support.
Either 1.26 or 1.28.5 are fine, they both rly good legacy patch. 1.28.5 is stable and doesn't have issues outside of security stuffs that all previous versions have and we shouldn't worry about it imo.
1.28.5 is used on eb and by chinese plateforms as base, it's bug free or as close as you can get to bug free anyway, also 1.26 is used on some plateforms like irina.
They both really good, just with 1.28.5 you get some further improvements, as it was exclusively focused on fixing some compatibilities and squeezing last remaining bugs, basically preparing the stable base to start building reforged on top of, so that's why I think it's the better patch. It's virtually very close to 1.26 just with some additional fixes from 1.27 and 1.28.
The serious modernization and introduction of new bugs began with 1.29, this is when they started introducing Reforged natives and working towards Reforged for good and changing stuffs profoundly. It's very different than anything before.

I think 1.29 with fixes from community edition, would be amazing, however without the fixes it's no good. I hope blizzard can work with hive community edition, it's kinda close to done from what I saw, you can basically make the best legacy version out of it with just a bit of help of blizzard, maybe they could reach to them and see to merge their work or something. Would be ideal imo.
 
Last edited:
Quick question: how do you download the legacy version? I've been looking for it on the launcher but I can't find it.
In the Battle.net app, you choose "Warcraft III - Legacy TFT 1.29" from the dropdown of the "Game Version". This only works if you have bought a legit copy of Reforged.

Personally I'm glad it's 1.29.2. That was the last .MPQ patch and the earliest one I know of where campaign cutscenes weren't broken.
I think versions between 1.29 and 1.31 has a problem where some of the unit voices in languages other than English were misplaced and no longer work 100%. Same goes to Reforged.

1.26 and 1.27 have the working original voices for non-English.
 
I'm not quite sure 1.29 has a lot of gamebreaking bugs compared to 1.28.5. I heard that according to some reports, some bugs were minimal compared to 1.31.


Btw, 1.26 is the most stable patch AFAIK as it's the last one to be developed by the original Blizzard team from 2002, albeit lacking proper Widescreen and 24 players support.
Surley if they add 1.31.1. they can fix that as well.
 
Wonder why not 1.26 and 1.31 too)
Wonder why people ask for community splitting when the point was to get it more together with this release update thing.
Besides, it won't really matter if they shan't update/bug fix and/or add B.net capability to it. Might as well stick to Classic 2.00+ instead or to your "unofficial" (but with original CD-Keys) pre-1.35 versions.
 
Wonder why people ask for community splitting when the point was to get it more together with this release update thing.
Besides, it won't really matter if they shan't update/bug fix and/or add B.net capability to it. Might as well stick to Classic 2.00+ instead or to your "unofficial" (but with original CD-Keys) pre-1.35 versions.
As far as I know 1.29 was unofficial until now. so....
 
community splitting
Not really much of a concern when this version doesn't even have native online support. The only way to play it is to use the fan mods that already existed for years before this. It's pretty close to what people already had, except Blizz just made it way easier and more intuitive.

The community is only "split" in the way it already was, and the majority of the American playerbase will pretty much still play Reforged because its the path of least resistance and has the most mod support. As long as Blizzard doesn't give the legacy client its own online service, that's not likely to change. It's also probably not getting any updates either, since its a legacy client.

Personally, I don't think it should have online support or get new patches. I think it should remain what it is: just an official archival of the previous version that people can use and mod as they wish. Companies don't have to support old games forever, they just have to let people keep them if they want.

In fact, I think this might actually unite the community, since now people who like older patches now actually have incentive to buy the official version again instead of just using their old files. Hell, I'll take it one step further: I can't believe I'm saying this, but because of the Legacy client, I think Reforged is actually worth paying for now. That's me saying this. 🤯

...well, maybe, anyway. $30 is still a really steep asking price for a 25+ year old game, and its not like Reforged has much in the way of "new" content to actually justify that higher price.
 
Last edited:
In fact, I think this might actually unite the community, since now people who like older patches now actually have incentive to buy the official version again instead of just using their old files. Hell, I'll take it one step further: I can't believe I'm saying this, but because of the Legacy client, I think Reforged is actually worth paying for now. That's me saying this. 🤯
That makes a lot of nonsense. If the official 1.29 is the same as the unofficial, why buy without any updates and/or B.net support? Wow. Don't tell me, it's because of fear of viruses and such OCD impediments?
Total bull. For archiving purposes, they could have just free released it as some of their other older games.
As far as community splitting goes, it's not solved since as you can see there's people asking for 1.26 etc. and if those on 2.0+ will have trouble playing 1.29 maps due to incompatibility issues, they will still need two separate installs; and of course vice versa.
Also, this separation thing is quite subjective. What does it mean then if it's not supposed to be the unavailability of an all encompassing B.net and/or inter-game versions compatibility?
 
Last edited:
That makes a lot of nonsense. If the official 1.29 is the same as the unofficial, why buy without any updates and/or B.net support? Wow. Don't tell me, it's because of fear of viruses and such OCD impediments?
Total bull. For archiving purposes, they could have just free released it as some of their other older games.
I highly agree with deepstrasz's sentiment here, other than that I think the possibility of viruses isn't total bull. Somebody hacked Hive in 2016. If that were my server, I'd be paranoid forever after that. Usually the best way to know you're not hacked is to never be hacked in the first place. Once you know you are hacked, how do you ever come back from that? How do you prove a negative, that the hacker is gone? "I asked Norton AntiVirus" to me isn't as convincing as it was when I was a 15 year old.

So if we know that downloading 1.29.2 from Hive:
  • Is a properly functioning secure HTTPS connection between your computer and Hive
  • Has been shown to download a ZIP file containing the exact md5 / sha checksums as my backup of 1.29.2 from when it was live (which I got from Activision)
This still doesn't change the fact that an evil attacker who had been secretly lurking inside of Hive's servers since 2016 could log back in, swap out the 1.29.2 download for 10 minutes prior to you downloading it, let you download the virus copy, and then swap it back. This is a totally real thing that could happen and the cryptography wouldn't save you unless you re-verify the checksums after the download, which 99.999% of players won't do. (Of course, yes, Activision is total susceptible to the same issue but we don't have prior knowledge of them literally being hacked. Or maybe someone does, and I didn't hear about it.)

But I met Ralle in person and he was friendly and cool and I think if I ever downloaded 1.29.2 and the hashes were wrong and it was a virus, we could as a community ping him and he would probably fix it. For better or worse. I don't think Microsoft Activision will be so friendly.

All of that aside, I pretty much totally agree with deepstrasz otherwise.
  • Official 1.29 is the same as the unofficial means we didn't gain anything. No technology was fixed -- it's just Microsoft trying to pander socially.
  • If you believe official is much more "accessible" than unofficial, then surely you also believe that it makes a big difference for "official" 1.29 to have no multiplayer server. With no server, it's essentially "not fixed" as players still can't go play it together without a slew of (often hacky) workarounds or third party tools. You might say, "ah but those are easily downloadable on Hive" but so was 1.29 unofficial so then we're back to the point of: why are we even talking about this or praising Microsoft for it if it achieves nothing?
  • You say "people who like older patches now actually have incentive to buy the official version again instead of just using their old files" but do they, though? It cannot play online...
I actually might go further in saying that in the already muddied waters of "what is Warcraft III" and "what is legacy," this official dump of 1.29 makes the problem even worse because
This was the last version before Warcraft III: Reforged development began.
... now we have dubious claims like Archian's text here in the OP. I'm not going to expressly say it's false because there's some matter of subjectivity here, but for reference:
  • I am quite confident based on the leaked information available at the time that 1.29 was created by "The Reforged Team" even if it does not say Reforged on the menu
  • The patch notes for 1.31 say that it is "the last version before Warcraft III: Reforged" released, seeming to conflict with Archian's claim
  • There is actually code in 1.29 for loading the Reforged assets into the game disabled with #ifdef's and stuff in the C++ so it won't run, but if you put an MPQ into the same folder as the game where the name of the MPQ matches the archive used to store HD assets during Reforged development then 1.29 will load it as if it were the HD assets bundle. Telling ourselves that 1.29 is not a half-finished Reforged prepatch but rather is "the last version before Reforged development began" to me is wishful thinking to praise Microsoft's subpar behavior (probably based on the premise it's better than nothing) and also is probably an attempt to pave the way for W3CE to succeed. But still, why should we say borderline false things to get the outcome we want instead of just saying the truth? The truth is that 1.26 was the last patch before Reforged development began, and 1.27 is the near-identical version of 1.26 that was compiled by the Reforged team to get their feet wet. This is my truth; is that somehow subjective?
EDIT: Muddying the waters further of what actual legacy Warcraft III is by publishing a buggy, unfinished Reforged prepatch and calling it Legacy Warcraft III does further harm to the actual "LEGACY" of a game that this company seems hellbent on destroying. I can release a video tutorial of how to trigger the subroutines in 1.29 that load the Reforged assets bundle that were used inside the office if you do not believe me.
 
Last edited:
I was told it was the last version before Reforged.
It's subjective based on whether people define Reforged as being:
  1. The web page menu
  2. The change from MPQ to CASC
  3. The Classic Games team touching the game in 2017+ after Bob Bridenbecker announced 1.27 and they began the multi-year cycle of updates that culminated in Reforged
  4. Pete Stilwell getting on a stage and saying the word "Reforged" in front of the world and telling them that was the upcoming plan
I'm pretty sure 1.29 hits bullet point #2 above, and possibly bullet point #4. So somebody could say "ehhh that's a lot of bullet points" but from my perspective Bob Bridenbecker's announcement in 2016-2017 of the patch 1.27 was the start of the obviously different team changing things (often breaking things) who ultimately created Reforged. So I would define this by #3 above and then say the last patch before Reforged technologically in terms of who touched the code was 1.26.

I'm pretty sure 1.30 was the last patch before #4 above though, and obviously 1.31 was the last patch before #1 above.


Edit:

I know of numerous bugs in 1.29 that I reported to Kam at the time, which they subsequently fixed in 1.30, and it is sad to think those would be forever encoded as the Legacy Warcraft III, since they are not, and were introduced by the people he was working with.
 
  • 1.26 is by all means the last legacy patch.
  • 1.28.5 is close to 1.26 but has some compatibilities fixes for modern OS and stuff that still make it worthwhile (it's basically legacy wc3 with a bunch of small changes that don't break things but are just positive in general).
  • 1.29 is when they are starting to mess up with things, and has some of the new reforged native in the world editor along with many bugs.

=> 1.29 with community edition patch is solid, but without it it's poop and shouldn't made available.
 
I need a cool conspiracy theory to latch onto.
W3CE devs told them to do it to grow their power. Community Edition to take the world by storm!

If only it was open source...
 
I highly agree with deepstrasz's sentiment here, other than that I think the possibility of viruses isn't total bull.
My point was, the only real "advantage" I see is that their official upload has a lower chance of being hacked/infected. The bull wasn't related to the viruses specifically.
1.26 is by all means the last legacy patch.
How does one define or pinpoint legacy?
Retera kind of showed in a recent post that 'tis subjective.
 
I need a cool conspiracy theory to latch onto.
I'm afraid that if I say my conspiracy theory, lurking Microsoft employees will decide it's a good idea and do it. So I won't say what I'm thinking, and I honestly don't want anyone else to post conspiracies either, for the same reason lol. 😬

So, instead, I'll just say: I hope to see lots of activity on the CE servers!
 
My point was, the only real "advantage" I see is that their official upload has a lower chance of being hacked/infected. The bull wasn't related to the viruses specifically.

How does one define or pinpoint legacy?
Retera kind of showed in a recent post that 'tis subjective.


You look at the date, as you can see there is a massive gap of 5 years between 1.26 and 1.27. Before 1.26, there was constant development since 2003, 1.27 released just as Reforged started its development. I think it speaks in favor of 1.26 being considered the most legacy version.
However, personally I still consider 1.28.5 for example to be legacy, since it's 1.26 just with some fixes for modern plateform, the game remains largely unchanged.
1.29 however though can't be legacy, you have 24 player support added, actual balance changes to melee, new blz natives in the world editor,, you can even run maps that are saved on Reforged in it, which isn't the case before. I don't think it's really a problem if they merge with community edition though.
 
Last edited:
You look at the date, as you can see there is a massive gap of 5 years between 1.26 and 1.27. Before 1.26, there was constant development since 2003, 1.27 released just as Reforged started its development. I think it speaks in favor of 1.26 being considered the most legacy version.
However, personally I still consider 1.28.5 for example to be legacy, since it's 1.26 just with some fixes for modern plateform, the game remains largely unchanged.
1.29 however though can't be legacy, you have new blz natives in the world editor, you can even run maps that are saved on Reforged in it, which isn't the case before. I don't think it's really a problem if they merge with community edition though.
IMO, legacy would still be the first iterations of RoC and TfT but I digress.
Older patches 1.26 included have some hacking exploit security issue.
^says it's the patch when the games and their editors were merged.
 
I don't understand what you are trying to say, it also says you can switch between them. This is just 1.26 with lot of QoL.
Balance changes to melee happened for the first time with 1.29 after many years, and bugs, and problems.
And yeah any older patches have some security issues, but this is not something you should worry about imo, specially if it's lan only. And even then, this has never impacted anyone in the history of wc3 and now that the game is dead without b.net, I doubt it happens lol.
I bet many older games you play have such exploits as well. Anyway I think all has been discussed imo.
They need to contact community edition and merge all their fixes that took years to be made for 1.29. Keeping 1.29 in this state is ridiculous, you can already see many bugs being reported right now on b.net wc3 official forum, this thing is just dead in the water without the fixes.
 
IMO, legacy would still be the first iterations of RoC and TfT but I digress.
Actually, what I might say is that 1.22ish is legacy.

From what I can tell/remember, the 1.23-1.26 patch cycle in 2009-2011 was created to start trying to fix the virus exploit. That was the only reason. The hashtable natives were added with guidance from Vexorian and maybe a few other community members to resolve what would otherwise have been a glaring flaw / glaring loss in the map script APIs. Because otherwise fixing the virus exploit made return bug not work, which made cheesing Gamecache to be away to have a hashtable structure not work, and so the hashtable natives were necessary to keep the system running despite the effort involved. There were like 2 other natives added as a friendly nod to Vexorian that weren't strictly necessary like GetSpellTargetX and GetSpellTargetY but essentially they were just trying to "save" the mapmaking in what was otherwise quite literally the custom games apocalypse that made the most customized and most interesting custom maps die -- in what was otherwise a backwards compatible system.

But if we look at the date of Activision buying Blizzard, I think it was slightly before that patch cycle. And if we look at the hashtable natives in the TriggerStrings.txt and TriggerData.txt files in the game, they are thrown in haphazardly to what was otherwise a harmonious and well organized system.

In other words, if we ignore community and think more about the technology history, I would almost sooner say that the true legacy version of Warcraft III would/should be the game as it was circa patch 1.22 in 2008. It was at this time that Activision bought out Blizzard and someone, some sneaky person inside of Blizzard, changed the code of Warcraft III so that it no longer looked for a physical CD rom drive in the computer and would instead be launchable as a standalone Windows application after it was installed. It enabled the future of digital downloads for the game but it was essentially also I think the cutoff point where some very bright person made the true legacy CD game of Warcraft III be only slightly modified in this way so that it was playable without a physical CD drive, while their company was getting bought out probably. I have a copy of that version on my computer which seems to be a 1.22 game install but maybe where as a user I dumped the 1.23 world editor EXE into the install because it likewise can launch without a physical disk in the computer. So then it operates as my oldest possible playable backup which requires no physical CD media.

On my computer I would think of that version as the true legacy and I am frequently playing Warsmash emulator using that version as the asset source. The Warsmash emulator provides the implementation for hashtable natives and other code changes, so in all reality there's like nothing lost and it's literally the classic legacy game with support for all sorts of maps from future versions. It's well within the realm of possibility to think of this as being a defining legacy version, even if it's not the pop culture world view of looking at 1.26 as being that thing because it was live for 5 good years without changes.
 
Last edited:
Also, this separation thing is quite subjective. What does it mean then if it's not supposed to be the unavailability of an all encompassing B.net and/or inter-game versions compatibility?
I don't think its really all that subjective or ambiguous or anything. "Splitting the playerbase" is a pretty nebulous and ill-defined term, but my impression of it is that it means people can't play together or enjoy the same experience. But that fear is totally unfounded because if you want to play with the most amount of people and the most amount of mods, your best option is still to play Reforged. Or play Community Edition, which is compatible with Reforged content. There are also ways to download both versions.

The only "separation" comes from people playing the game they want to play, the way they want to play it, and there's absolutely zero way to stop that and never has been. If anything, fan mods have made it easier than ever for people playing on different versions to still be able to connect.

You never hear people bring this up about any other game sequels, ports or remasters. I think this is just a line of thinking that took root in a small part of the WC3 community to help people feel better about the state of Reforged. A sort of "we're all in this together" mindset.

But whether you like Reforged, 1.21, 1.26, 1.29, 1.31 or even exclusively play DOTA, we're all Warcraft 3 fans and we all love the game, and that's all that matters.

Plus, again, the lack of official online play for the Legacy Client, and the existence of Community Edition makes it all kind of a moot point. Especially since RF and CE have crossplay.
 
Thank You

Solved now

Just i went to the warcraft TFT legacy installed folder and i opened the file “enUS-Maps”

I copied all files folder and files and paste it in C:\User\Documents\Warcraft III\Maps

now they are all here

thanks
You don't need to move those contents from the "Maps" folder. Simply remove the "enUS" prefixes for the "Maps" folder, and it will work.

The "Documents\Warcraft III\Maps" is only intended for your own custom maps (not the Blizzard-made maps).

Additionally, you can do the same thing for the "Movies" folder by removing that "enUS" prefixes, and you will be able to watch FMVs.
 
Cheers for releasing this as an alternate version of the game rather than re-releasing it and selling it separately. Will be downloading it.

Edit #1: They removed the ability to skip the first chapter of the Founding of Durotar, where you start with Rokhan.
Edit #2: You can't play any map from Reforged and the Legacy Edition share the same Documents folder, so no map is loaded in at all.
Do I need to uninstall Reforged first for this, or...?
 
Last edited:
Or play Community Edition, which is compatible with Reforged content.
What does that even mean? You can play Reforged maps on 1.29? How does that make any sense? Doesn't that mean you're actually playing Classic Reforged (like you still have both games into one but allegedly playing 1.29)? Would still be a better option to just play 2.00+ instead as it's official, updated and has B.net.
 
Hear me
1.29.2 with community fixes and the HDpack with proper texture shading and saturation
Btw, I've been using 1.29 as a base for War3HD all this time. So for me, it feels somewhat inspiring that they picked that version for the launcher. Of course, it's near useless until they add multiplayer (and make it available for people with CD keys only)
 
You can't play any map from Reforged and the Legacy Edition share the same Documents folder, so no map is loaded in at all.
Do I need to uninstall Reforged first for this, or...?
1.Reforged maps can't be playable on 1.29 (or older patches), but any maps that were made with older patches will work on Reforged.
2.The maps stored in Documents is only for custom contents (not the ones by Blizzard). You were referring to the Blizzard-made maps.
 
1.Reforged maps can't be playable on 1.29 (or older patches), but any maps that were made with older patches will work on Reforged.
2.The maps stored in Documents is only for custom contents (not the ones by Blizzard). You were referring to the Blizzard-made maps.
Is there an official download for the older versions of the map? The Blizzard-made ones? Though I assume they're from MPQs, no?
 
They made CD keys "expire" last year so you can buy the game you already own again and it doesn't even have online, why are people excited for this?
You don't need to buy the game again. This is just for the people who don't already have it. It's good to have for the sake of preservation. But you can still just stick with the old files you already have if you have them.

What does that even mean? You can play Reforged maps on 1.29? How does that make any sense? Doesn't that mean you're actually playing Classic Reforged (like you still have both games into one but allegedly playing 1.29)? Would still be a better option to just play 2.00+ instead as it's official, updated and has B.net.
IIRC Community Edition lets you load Reforged maps. If they use Reforged-only assets they'll appear as error blocks, but the map will still function. An imperfect solution but it means if you wanna play with friends and have different versions of the game, you have the option. I could have it completely wrong, I'm not the expert. But IIRC the mod allows for crossplay between two versions unless I'm mistaken.
 
Last edited:
IIRC Community Edition lets you load Reforged maps. If they use Reforged-only assets they'll appear as error blocks, but the map will still function. An imperfect solution but it means if you wanna play with friends and have different versions of the game, you have the option.
While that may sound nice, it's useless if you can't really play Reforged maps because of those errors. They mean improper functionality. It's a flawed option. Playing with map affecting errors together is not fun.
You don't need to buy the game again. This is just for the people who don't already have it. It's good to have for the sake of preservation. But you can still just stick with the old files you already have if you have them.
If they didn't want it freeware, they could have at least put it on their official site/server for everyone to use their CD-Keys on instead of privileging those who already have Reforged which gives little to no incentive to them to even try 1.29. But I guess there were some shady methods to get CD-Keys from the net or via some hacking programs which might be the case they made it only be accessible with the current B.net app which probably is much more secure in what CD-Key legality is concerned.
 
Last edited:
Back
Top