- Joined
- Aug 18, 2009
- Messages
- 4,097
Stumbled on another weird bug/limit. I have reason to believe that the Preloader native not only loads the target file but also accesses the buffer created by Preload.
If you call Preloader on any valid file and the path given specifies a drive/folder, and if you put a string with more than 233 (Windows 7) characters into the buffer beforehand, wc3 crashes in a fatal error. The length of the path passed to Preloader does not seem to matter, does not influence the 233, there only has to be a directory.
edit: It probably depends on wc3's install path because that's where it primarily looks up files. The Preload line can be longer if you start from drive root. This makes it kind of problematic though if players have a deeper install path.
If you call Preloader on any valid file and the path given specifies a drive/folder, and if you put a string with more than 233 (Windows 7) characters into the buffer beforehand, wc3 crashes in a fatal error. The length of the path passed to Preloader does not seem to matter, does not influence the 233, there only has to be a directory.
edit: It probably depends on wc3's install path because that's where it primarily looks up files. The Preload line can be longer if you start from drive root. This makes it kind of problematic though if players have a deeper install path.
