Closed gitandrew07 closed 1 year ago
Can I get a screenshot of the error screen?
So, what can i do?
So when I looked up the error code, it says it might be an SSL thing. If you have the means, try testing out the patcher on a different network.
Looking into it further, I might be able to bypass the issue in the next update, so stay tuned.
Pretty cool, Thank you!👍 Im gonna wait for the next update
I pushed a nightly build, if you check out the nightly branch, see if that fixes your issue.
It appears i got another error, with the nightly build
Just curious, what is your locale set to? It seems like Batch is really picky and the script doesn't work right if the locale isn't "English (United States)"
Okay I pushed another build where I changed around the formatting of some commands to hopefully make it not error out like that. It seemed to work on my end fine, but as I've learned lately, it might not be the case for everyone else, so please do report back if this fixed it.
I already had my language set to English (United States), however with this new push, i get this giant lump of errors.
Also when i press any key to exit, like the patcher asks to, it gives more errors and then goes to the "What are we doing today?" screen.
Oh my.. yeah I didn't expect that at all. I didn't think Batch would be this unpredictable when it comes to how Windows is set up in other regions. Honestly, it makes me want to remake this whole thing in a proper programming language so it'll at least work the same for everyone.
So... what can i do in conclusion?
For now, I would say for now nothing much until I can port it to a proper programming language. Or you could try out the Unix Patcher on a Linux or macOS machine (or virtual machine for Linux), that one seems a lot more stable.
If you're interested in trying a new (potential) replacement for the Batch script, check this branch out. https://github.com/WiiLink24/WiiLink24-Patcher/tree/csharp-ver
oh my god i think its working.
im running the C Sharp patcher now
LETS GO IT WORKED!
Thank you Pablo!
I'm glad to hear that! In that case, I'll consider this issue resolved.
When i start the patching process, it will instantly crash giving error code 60. (and no im not using powershell this time.)