Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Replays are now saved in Documents/Warcraft III folder instead of the install folder so it cannot find them I am guessing. Additionally it must be modifying Warcraft III virtual memeory to remove limits and perform its other features, something that Windows 10 probably does not like (Virus like behaviour) and will break with patches (different executable structure).
Because WC3 now saves all replays to Documents/Warcraft III folder instead of the ProgramFile install directory. Replay Seeker probably only supports replays in the install directory.just a note that replay seeker is opening but cannot detect any replays
Windows file paths are case insensitive. The NTFS partition format is case sensitive, but Windows OS interfaces with it in a case insensitive way.though i have edited the cfg file several times, by changing war3 to War3
Will not make a difference. Only reasons it shows x86 or 32 next to the process name is to inform the user that it is running using WoW64 (Windows on Windows64) as opposed to using Windows directly.as warcraft 3 runs in 32 bit, and i have a windows 7 64 bit, in process it shows War3.exe *32, so what i need to do is rechange the cfg file to the same and try again
Do not blame them, blame the author for not making an open source tool that someone else could fix after they retire.blizzard dont give a ... about fans and their tools, say hello to new overlords.
Technically the tool is at end of life. Your grievances should be with its author for not having a longer program life cycle. Open sourcing a tool is a great way to extend its program life cycle well beyond what you may be capable of.suuure, like somebody could know back then that blizzard would try to kill wc3 with new patches. blame programmers for not doing everything opersourced, thats how u win..
If you read their terms of use you will notice that they do not support or particularly care about third party software at all. Tool programmers are well aware that this is the case, or at least should be if they are reasonably capable. Especially tools that interface directly with the game are highly prone to breaking between versions and require constant updating. This is largely why JNGP is slowly dying as no one updates how it interfaces with WorldEdit anymore.it's up to company to keep up with key tools provided by community. ignoring those is the yet another reason why blizzard sucks.
No, it should not work on 1.27a. I will implement 1.27a support (along with other known versions) tonight. I am most of time at the work and cannot implement everything i want in one day.So, this one should work on 1.27a right?
