Longi94
[Bug]: SteamUser.kickPlayingSession onlyStopGame param does not work
Describe the bug
When I call kickPlayingSession(onlyStopGame=true), it disconnects the other Steam session the same way as if onlyStopGame=false.
I expect it to just close the game and not disconnect the entire session.
To Reproduce
- Log in to Steam and start a game on one device
- Call
kickPlayingSession(true)in JavaSteam - The session from 1 will fully disconnect and require you to log in to Steam again
Expected behavior
The session should stay active, and only the running game should stop
JavaSteam Version
1.6.1-snapshot
Platform Version
Android
JVM Version
17
Additional Information
It's been merged in to GameNative now. You can pull master, run the app while having a Steam game running elsewhere. If you then launch a game via GameNative, it prompts you to close the other game, and if you click continue, it calls kickPlayingSession(onlyStopGame=true)
So I played around with steam on my PC and through a VM. I am unable to find a scenario where steam officially sets onlyStopGame to true.
I have a theory setting this value to true doesn't do anything since most games wouldn't know how to handle steam telling it to close. It seems Steam just tells the other client to disconnect with LoggedInElsewhere leaving the game to run and allow the "newer" session to take priority for cloud saves.
If I can get a scenario where onlyStopGame is true, I'd like to know what happens before and after it's called through NetHook
