[QUOTE=;441152]
Yeah I noted before that exposing presence would probably be something I should do at some point, uploading a new build where I expose it (and every other missing setting that I had defaulted to a value), the create advanced sessions node is a monster of booleans now but it has them all on it.
Upload will be live when the build is complete.
Edit Build is uploaded
It’s the classic “It’s better to have it than not need it, than need it and not have it”, after all this is ADVANCED sessions plugin, so it’s better to have all the options exposed. We’re almost there I believe and the session now created on the dedicated server, however I’m running into some issues finding the now created session. I simply cannot see it when i find session :s.
In the dedicated server log I’m getting some warnings which may or may not be preventing the session from being advertised to the master server. These were…
[2015.12.21-22.01.06:765] 39]LogOnline:Warning: STEAM: Server setting ,SESSIONFLAGS:651 overflows Steam SetGameTags call
[2015.12.21-22.01.06:766] 39]LogScript:Warning: StartSessionCallback - Invalid player state
This was with the older plugin where I just changed bUsesPresence from true to false. The newer version with the correct settings checked produces the same following warnings and I am still unable to find the created session. I should note that the SteamNetDriver does initialize and the integration seems to work, the server detects if I close the Steam client, so the connection is there. The session does also create (it doesn’t fail). I am completely at a loss as to why i cannot find the created session :s
edit: I should add that I can ‘create’ a session as the client and am able to find said session over the net. The dedicated server is where the problem seems to be.