3/16/2024 0 Comments Burning crusade warcraft 3 mod![]() I remember a few YouTubers even visiting the servers and asking why people were still playing era at the time. There were less than 200 people total on classic era across all servers during TBC. It peaked at just over 7 million WoTLK peaked at just over 15 million. It was not the most played ever as you said. It followed the stories of Illidan and the nagas. It is also not standalone seeing as how you HAD to have the regular World of Warcraft 60 version installed just to install that and most of the lore from it also came from Warcraft 3 as well. Last time around subs kept going up and up right until WoTLK ended. Regular Classic and WoTLK Classic have both been far more popular. Other ratings for the Classic version have it as 4 out of 10 saying the lack of advertising and lack of players caused it to do poorly compared to the original version. Was not talking about regular original TBC. I was talking about Classic TBC which is what people were playing here now. Classic TBC got a 75% rating at max which then dropped even lower after a while. They only rated the original version that high. Making it the 2nd best rated expansion EVER by PCGamer. TBC as a standalone expansion was rated 9.7 by PCGamer when it released WotLK has more for that playerbase than TBC did. TLDR: Due to the way players play the game now, TBC and WotLK are simply worse versions of retail for raidlogging parsers. ![]() If we really compare Vanilla, TBC, WotLK, and Retail, its surprising how active retail is in the world now. This simply made TBC and worse retail, as wotlk has turned out to be. The intent was to have both Azeroth and Outlands populated however, due to min/maxing, speedrunning, and players focused on raiding and parses, at Classic TBC launch, Azeroth was all but abandoned. TBC was built as an actual “expansion” and not designed as a separate game as most expansions are nowadays. So during this time the whole of Azeroth AND Outlands were populated. What made TBC “feel” different back in 2007 was the fact that when TBC released a LARGE portion of the playerbase still hadn’t even reached level 60. WotLK simply added a lot more features to that “playstyle” than TBC did. Vanilla wasn’t solely focused on endgame raiding while TBC and WotLK was the change to focus on endgame raiding. So basically what I did was downloading the client with the sound channel modification and then added the FOV modification into it.Yeah, but this isn’t 2007 anymore it was factually less popular than both vanilla and wotlk this time around. I managed to do it myself by following your last step. The last step is opening WoW.exe in an hex editor and looking for the hex values DB 0F C9 3F E6 F1 47 40 00 00 and replacing them with 66 66 F6 3F E6 F1 47 40 00 00. The last step is opening WoW.exe in an hex editor and looking for the hex values DB 0F C9 3F E6 F1 47 40 00 00 and replacing them with 66 66 F6 3F E6 F1 47 40 00 00.įor anyone who is interested in the explanation on how I did it, here it is: I then changed the value type to array of bytes and the value shown was now DB 0F C9 3F E6 F1 47 40 00 00 (which I assume is the hex representation of 1.57, however it does not seem to be equal to 1.57, maybe only part of it represents the float value? If you know more about this feel free to shed some light).Īfter changing the value type back to float and changing it to the desired value (in my case 1.925) I changed back the value type to array of bytes once more, and it now reported a value of 66 66 F6 3F E6 F1 47 40 00 00. ![]() Then I changed the value type to float, and the address was shown to hold a value of ~1.57, which is the default FoV in Vanilla and TBC. I started WoW.exe normally (there is no need to login), then attached Cheat Engine to it and manually added the address 0x8089B4 for Vanilla or 0x8B5A04 for TBC. I already knew the memory address I wanted to patch so that made things easier. Here are the patched executables: WoW.exe - Vanilla 1.12.1 - FoV WoW.exe - Vanilla 1.12.1 - FoV WoW.exe - Vanilla 1.12.1 - FoV WoW.exe - TBC 2.4.3 - FoV WoW.exe - TBC 2.4.3 - FoV WoW.exe - TBC 2.4.3 - FoV scans: WoW.exe - Vanilla 1.12.1 - FoV WoW.exe - Vanilla 1.12.1 - FoV WoW.exe - Vanilla 1.12.1 - FoV WoW.exe - TBC 2.4.3 - FoV WoW.exe - TBC 2.4.3 - FoV WoW.exe - TBC 2.4.3 - FoV anyone who is interested in the explanation on how I did it, here it is:Īll I used was Cheat Engine and an hex editor (I used HxD). The FoV value is set to 1.925, which should be similar to the one used in WotLK+. As many of you probably already know the field of view in Vanilla and TBC is different than WotLK and all other expansions past WotLK (image representing what I mean here).įirst of all, most of the credit goes to namreeb: thanks to the memory addresses he posted here I managed to patch WoW.exe for both Vanilla and TBC, thus making the FoV change permanent so that it no longer gets reset on /reload and disconnects like it did with memory edits. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |