I don't think there's anything new in the log either: plugin-steam.log It's still behaving as before in the client - connection status doesn't change when I revoke the connection, nor when I force Galaxy to run a sync. I figured since you borrowed some code from SteamKit, maybe it's because they're assuming the reason the connection would terminate like this is that the user is switching between devices where they can only be signed into one at the same time?Īnyway I've loaded up the new branch (still installing from zip for now, since I'm new to Github and just flying by the seat of my pants), and the bad news is whatever you've changed isn't clueing Galaxy in that the plugin has disconnected as you hoped. We're going to revert the start page to be username and password, which should indirectly fix this by forcing us to update the RSA key.īeta Was this translation helpful? Give feedback. Regardless, the instructions are on the readme. Or, we may have told you the wrong thing to do, lol. You may have set up the virtual environment wrong, etc. We've simplified this process as much as possible, but we're not providing a one-click solution because there isn't a good one-click solution - you may have multiple instances of python (or not), and frankly checking that is beyond our scope here. If you are on MacOS, you are doubly valuable because most of us are on Windows and we need it to work everywhere One of our devs who does use it had managed to trigger an unexpected error and we could use help replicating it. The mobile steamguard page is probably the thing that needs the most testing, because i don't have steam guard and haven't checked it. Wait an hour on the steam guard code so it expires. Use illegal or nonstandard characters (diacritics, emojis, etc). There are things that need fixing, most notably when you do something wrong. It is now public.Īt this point, the code works, but it doesn't work well.

I'm not announcing it, but i'm also not making it private.

Virtual sailor 7 gog galaxy