Steamworks.NET player kick

C

ckindley

New member
Hey folks,

I had an event this afternoon in which all three players on my server were kicked at the same time. Reviewing logs I see, for instance:

2017-10-25T13:42:13 136787.448 INF [steamworks.NET] Authentication callback. ID: <number>, owner: <number>, result: k_EAuthSessionResponseAuthTicketCanceled

2017-10-25T13:42:13 136787.448 INF [steamworks.NET] Kick player for invalid login: <number> <steamID>

One player mentioned this happened about the time he sent ally requests to the other two, but that may be happenstance. During this time I was shelled in from my work computer and never lost connection to my server. Any ideas?

Thank you!

 
Maybe it's time to revisit this problem? The annoyance level from this elevating. It happens at what seems to be purely random times. When it does, the client often crashes, so the player doesn't really know they were kicked, let alone why. All they know is that the game crashed. But the server log makes it very clear what happened:

2017-12-30T20:10:46 539.221 INF [steamworks.NET] Authentication callback. ID: 76561197960378421, owner: 76561197960378421, result: k_EAuthSessionResponseAuthTicketCanceled

2017-12-30T20:10:46 539.221 INF [steamworks.NET] Kick player for invalid login: 76561197960378421 Ook

2017-12-30T20:10:46 539.223 INF Kicking player (Steam auth failed: k_EAuthSessionResponseAuthTicketCanceled): EntityID=171, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

For some reason, the server thinks the player is not logged into Steam (never mind that they were two minutes ago), and kicks them from the server. I have a rock solid Internet connection, and Steam remains connected to the Steam network.

Is there anything at all that can be done about this? Have TFP any plans to research this and maybe fix it so the players are not so aggressively kicked?

 
Logs?

Also, it's most likely a Steam issue. Or an issue with the network connection between the player and Steam. Logs from both sides when this happens would be more helpful. Read the sticky for details.

 
It may be Steam, but 7D2D is the ONLY game that I have that kicks the player so aggressively. My game count in Steam is 220. Several of them are Unity based games, which 7D2D is. NONE of them kick the player so aggressively.

TFPs can't control the Steam connection, but I believe they do control how a loss of Steam connectivity is handled, and the action taken when the player/server looses the Steam connection for a brief period of time. This game, unlike other Unity based games, appears to be very quick to kick a player that looses connections. Other games either don't check, or wait a long time before they take action.

It's like -> Player looses steam connection, which happens all the time. -> Start 5 second countdown. -> 5..4..3..2..1.. KICK THEM.

Other games-> Player looses steam connection, which happens all the time. -> Start 50000 second countdown. -> Player regains steam connection long before the countdown expires, and player never knows anything was amis.

I firmly believe TFP controls how a temporary loss of Steam connectivity is handled, and how quickly the player is kicked.

 
Last edited by a moderator:
As SylenThunder stated above, sounds like an issue between the clients and Steam.

However, you might be able to work around it by disabling Steamworks.NET as an allowed protocol in the server's "serverconfig.xml" file, by modifying the following line:

<property name="ServerDisabledNetworkProtocols" value="UNET, SteamNetworking"/>

Let me know how this works out for you, as I have not tried it myself. All my clients have had rock solid connections to Steam. On the downside, this may break your ability to ban by SteamID.

 
Last edited by a moderator:
It is an issue between the client and steam, but it's still how 7D2D responds that ultimately causes the problem. TFP can't control a client's steam connection, but they can control how quickly they kick a client that looses the steam connection.

I'll add SteamNetworking to the ServerDisabledNetworkProtocols and see if it makes a difference. Results to follow.

 
alas, no change:

2018-01-01T18:16:13 851.840 INF [NET] PlayerConnected EntityID=-1, PlayerID='', OwnerID='', PlayerName=''

2018-01-01T18:16:14 851.968 INF PlayerLogin: - +Nettle+ -/Alpha 16.4

2018-01-01T18:16:14 851.968 INF Client IP: 10.0.0.4

2018-01-01T18:16:14 851.968 INF [steamworks.NET] Auth.AuthenticateUser()

2018-01-01T18:16:14 851.969 INF [steamworks.NET] Authenticating player: - +Nettle+ - SteamId: 76561197974670426 TicketLen: 1024 Result: k_EBeginAuthSessionResultOK

2018-01-01T18:16:14 852.247 INF [steamworks.NET] Authentication callback. ID: 76561197974670426, owner: 76561197974670426, result: k_EAuthSessionResponseOK

2018-01-01T18:16:14 852.247 INF Steam authentication successful, allowing user: EntityID=-1, PlayerID='76561197974670426', OwnerID='76561197974670426', PlayerName='- +Nettle+ -'

...

2018-01-01T18:22:30 1228.083 INF [steamworks.NET] Authentication callback. ID: 76561197974670426, owner: 76561197974670426, result: k_EAuthSessionResponseAuthTicketCanceled

2018-01-01T18:22:30 1228.083 INF [steamworks.NET] Kick player for invalid login: 76561197974670426 - +Nettle+ -

2018-01-01T18:22:30 1228.084 INF Kicking player (Steam auth failed: k_EAuthSessionResponseAuthTicketCanceled): EntityID=171, PlayerID='76561197974670426', OwnerID='76561197974670426', PlayerName='- +Nettle+ -'

Look at the time between joining server and getting kicked. About six minutes. This a regular player that has logged many hours in the server. Their Steam was not offline, there was nothing wrong with their internet connection, and they were able to immediately rejoin, without restarting Steam.

 
Looks like Gazz of TFP was also having this same issue back in 2015, due to a buggy Steam update. Pretty much grasping at straws now, but here are a couple more things to try.

- IF the server is running rlabrecque's SteamManager Unity script, try editing the server's steammanager.cs file per this post:

https://github.com/rlabrecque/Steamworks.NET/issues/191

- IF the client has the option, try running the 7dtd client executable in compatibility mode for Windows 7, per this post:

https://steamcommunity.com/app/251570/discussions/0/364042063114553939/

 
Last edited by a moderator:
TAADAA!

I have a MAJOR UPDATE about this issue. The thought occurred to me last night that maybe we are looking at the chicken/egg from the wrong angle, and maybe the client is crashing first, causing the server to give us the kicking player message erroneously? To test this, I joined the server, and then forcibly terminated the client. I did this several times, and in every case, immediately AFTER I forcibly terminated the client, the server gave the kicking player message.

At 12:30:24 I joined the server. At 12:31:02 I entered the server. It's about a 30 second process, give or take, to actually spawn once you make the connection attempt.

At 12:31:14 I forcibly terminated the client process.

ONE SECOND LATER You get the messages about kicking player for invalid login steam auth failed blah blah blah.

This is a very misleading message! it leads one to think that the player was kicked because their steam auth failed, when in fact it's the other way around. Their client crashed, and this is how the server removes the player from the server.

First of all my apologies to TFP for going on and on about this issue. Looks like I was wrong (yes, dear, you can write that in your journal - I was wrong :) ).

The problem appears to be that the game just crashes. A lot. And when it does, we get this message in the console that leads us down the wrong rabbit hole.

This is the log from this:

2018-01-02T12:30:24 259.606 INF [NET] PlayerConnected EntityID=-1, PlayerID='', OwnerID='', PlayerName=''

2018-01-02T12:30:24 259.809 INF PlayerLogin: Ook/Alpha 16.4

2018-01-02T12:30:24 259.809 INF Client IP: 10.0.0.2

2018-01-02T12:30:24 259.809 INF [steamworks.NET] Auth.AuthenticateUser()

2018-01-02T12:30:24 259.809 INF [steamworks.NET] Authenticating player: Ook SteamId: 76561197960378421 TicketLen: 1024 Result: k_EBeginAuthSessionResultOK

2018-01-02T12:30:24 260.009 INF [steamworks.NET] Authentication callback. ID: 76561197960378421, owner: 76561197960378421, result: k_EAuthSessionResponseOK

2018-01-02T12:30:24 260.009 INF Steam authentication successful, allowing user: EntityID=-1, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:30:24 260.009 INF Allowing player 12:31:15with id 76561197960378421

2018-01-02T12:30:25 260.762 INF RequestToEnterGame: 76561197960378421/Ook

2018-01-02T12:30:34 269.216 INF RequestToSpawnPlayer: 172, Ook, 12

2018-01-02T12:30:34 269.221 INF Created player with id=172

2018-01-02T12:30:34 269.225 INF Player connected, entityid=172, name=Ook, steamid=76561197960378421, steamOwner=76561197960378421, ip=10.0.0.2

2018-01-02T12:30:34 269.225 INF Player set to online: 76561197960378421

2018-01-02T12:30:50 285.754 INF Time: 4.53m FPS: 21.02 Heap: 549.0MB Max: 549.0MB Chunks: 1109 CGO: 9 Ply: 2 Zom: 0 Ent: 2 (6) Items: 0 CO: 2 RSS: 1309.5MB

2018-01-02T12:31:02 297.731 INF GMSG: Player 'Ook' joined the game

2018-01-02T12:31:02 297.732 INF PlayerSpawnedInWorld (reason: JoinMultiplayer, position: -1306, 51, 200): EntityID=172, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:31:15 310.653 INF [steamworks.NET] Authentication callback. ID: 76561197960378421, owner: 76561197960378421, result: k_EAuthSessionResponseAuthTicketCanceled

2018-01-02T12:31:15 310.653 INF [steamworks.NET] Kick player for invalid login: 76561197960378421 Ook

2018-01-02T12:31:15 310.653 INF Kicking player (Steam auth failed: k_EAuthSessionResponseAuthTicketCanceled): EntityID=172, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:31:16 311.200 INF Player set to offline: 76561197960378421

2018-01-02T12:31:16 311.201 INF Player disconnected: EntityID=172, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:31:16 311.201 INF GMSG: Player 'Ook' left the game

2018-01-02T12:31:20 315.758 INF Time: 5.03m FPS: 36.25 Heap: 524.9MB Max: 549.0MB Chunks: 1109 CGO: 9 Ply: 1 Zom: 0 Ent: 1 (7) Items: 0 CO: 1 RSS: 1309.6MB

2018-01-02T12:31:50 345.774 INF Time: 5.53m FPS: 21.70 Heap: 581.7MB Max: 581.7MB Chunks: 1109 CGO: 9 Ply: 1 Zom: 0 Ent: 1 (7) Items: 0 CO: 1 RSS: 1309.6MB
Click to expand...
 
You must log in or register to reply here.
Back
Top