11/24/2023 0 Comments Gog galaxy ps2 plugin not workingA lot of the code original code was held together with "duct tape and a prayer" and while we've been slowly improving it ( is basically a co-author at this point), i've also been wielding a sledgehammer and gleefully tearing down basically everything. So these changes need to be security reviewed.Īs for 2.0, we're working on it. Speaking of, the process of getting these releases on to Nebula was nearly complete. This won't be an issue once the release is up on Nebula. I believe 1.0.6 switches to the Nebula address, so it won't work for now. As part of 1.0.5, i fixed the manifest to point to my repo, so any time gog detects there's a new version out it'll try to update it. There is a possibility you will automatically be updated to 1.0.7 or 1.0.6. a single call to strip() saved one of our testers a fair bit of time, so now you all get the benefits. We now remove any leading or trailing whitespace characters from your 2FA code before sending it to steam. This may have given you issues logging in. There's also a quality-of-life fix for those of you who use email for your 2FA: if you copy it directly from your email it often contains an extra space at the end. I'm not sure how, because i tested it myself during development, but i guess not when everything was finally together. This patches a previously unknown issue where if you had SteamGuard (aka Two Factor Authentication or 2FA) disabled, you could not login. As always, found my bugs, but so did and Update:□□ If you have version 1.0.6 beta from before this time, please redownload it. UPDATE: BUGFIX: 21:20:00 UTC Wednesday, JI messed up cleaning up the login logic. initial credit to for mentioning it, for tracking down the old error that dealt with this, and for doing the testing for me.Īs always, the MacOS release will be a little delayed. (You can confirm this yourself if you have a long password by only typing the first 70 or so into steam client, and noticing how it still works) We didn't do that, because that's extremely weird behavior. It also only accepts the first 64 legal characters, all extra ones are thrown away. ![]() Neither of these are our fault, Steam simply deletes extra or 'illegal' characters. Also, if you used certain characters, you'd also have trouble logging in. For some of you who use long passwords (>64 characters), you may have noticed you could not log in. ![]() This is a really minor, yet really important fix. This means i can add type hints, which now that i have better proto, is actually possible. I'm in the process of going through the protobuf code function by function to see what needs updating. naturally these don't act exactly the same because google's code needs to be different (which i guess i can't blame them for, because you can't just overshadow native code. it's definitely better, but the old code used google's nonsense and betterproto uses native types wherever possible. Update: this is fixed, but there are more issues - better proto isn't a straight drop-in like i hoped. The better way would be to monkey patch better proto but that is something python should not allow but it's Python! there are no rules bound to blow up eventually when someone doesn't realize i monkey pattched it and they apply a new version or something. Afaik the names don't matter in protobufs, so this is can be easily fixed with a regex search (which i'm already doing for a different issue). better proto has patched this, but not in the release i'm working with (the newest ones are betas, which have their own issues). Found the issue, Steam uses bytes as a variable name, so python has a bytes : bytes and bytes : int which blows up. ![]() I'll try rolling back to just better proto, which i hope is not broken (but am afraid is) This is what i get for trying 4 different changes at once. I'm way too tired to find that bug, so I'll look tomorrow if i have time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |