[0.14.13] AFK countdown is running during "Catching Up" phase.

[danielgweb]

My friend just got kicked for being AFK while he was catching up, on a huge map!

[Loewchen]

Please post the log.

[danielgweb]

Please post the log.

https://1drv.ms/f/s!Aj-x6YxxaqbohfkuGMdBt1o_B2tY3w

[danielgweb]

He was catching up... I just saw that! Also, Desync!

Code: Select all

 956.473 Error ClientMultiplayerManager.cpp:90: MultiplayerManager failed: "You have been disconnected as you have been AFK."

Code: Select all

632.951 Info TransferTarget.cpp:281: TIMEOUT at 0.554563 seconds
 669.902 Info TransferTarget.cpp:281: TIMEOUT at 0.594162 seconds
 671.102 Info TransferTarget.cpp:281: TIMEOUT at 1.188323 seconds
 690.365 Finished download (293 s, 142 MB, 485 kB/s)
 691.105 Info ClientMultiplayerManager.cpp:649: mapTick(-1) map download finished creating scenario
 691.106 Info ClientMultiplayerManager.cpp:538: MapTick(-1) changing state from(DesyncedDownloadingMap) to(DesyncedCreatingReport)
 706.488 Info ParallelDesyncReportCreator.cpp:64: Created desync report
 706.502 Loading map C:\Users\raren\AppData\Roaming\Factorio\temp\mp-download.zip
 706.503 Info ClientMultiplayerManager.cpp:538: MapTick(-1) changing state from(DesyncedCreatingReport) to(ConnectedLoadingMap)
 706.602 Info Scenario.cpp:152: Map version 0.14.13-2
 709.505 Checksum for script C:/Users/raren/AppData/Roaming/Factorio/temp/currently-playing/control.lua: 2823508807
 709.569 Info ClientMultiplayerManager.cpp:538: MapTick(5777772) changing state from(ConnectedLoadingMap) to(TryingToCatchUp)
 956.473 Error ClientMultiplayerManager.cpp:90: MultiplayerManager failed: "You have been disconnected as you have been AFK."
 956.479 Info ClientMultiplayerManager.cpp:538: MapTick(5806392) changing state from(TryingToCatchUp) to(WaitingForUserToSaveOrQuitAfterServerLeft)
 956.480 Info ClientMultiplayerManager.cpp:771: Disconnect notification for peer (3)
1042.583 Info WindowsUDPSocket.cpp:161: Socket closed
1042.583 Joining game 167.114.182.65:34197
1042.583 Info WindowsUDPSocket.cpp:61: Opening socket at port (0)
1042.584 Info ClientMultiplayerManager.cpp:538: MapTick(-1) changing state from(Ready) to(Connecting)
1042.681 Warning ClientRouter.cpp:115: Received NatPunch from 167.114.182.65:34197 as a client
1042.735 Info ClientSynchronizer.cpp:34: Initialized Synchronizer local peer(1) latency(32).
1042.735 Info ClientMultiplayerManager.cpp:538: MapTick(-1) changing state from(Connecting) to(ConnectedWaitingForMap)
1042.735 Info ClientRouter.cpp:219: ConnectionAccepted
1044.218 Info ClientMultiplayerManager.cpp:668: Received mapReadyForDownload
1044.218 Downloading file C:\Users\raren\AppData\Roaming\Factorio\temp\mp-download.zip (22297869 B, 44330 blocks)

[Loewchen]

I would agree that the afk counter should not run when the peer is in the ketchup phase.
Please make a report for the desync as well and include the desync-report, see my signature for details.

[danielgweb]

It is being uploaded on this same link: https://1drv.ms/f/s!Aj-x6YxxaqbohfkuGMdBt1o_B2tY3w

It takes a while, its a 276 MB Desync Report.

Also the map was generated on version 0.14.12. And we were playing on 0.14.13.

EDIT: File upload success!

[Loewchen]

It is being uploaded on this same link: https://1drv.ms/f/s!Aj-x6YxxaqbohfkuGMdBt1o_B2tY3w

It takes a while, its a 276 MB Desync Report.

Also the map was generated on version 0.14.12. And we were playing on 0.14.13.

EDIT: File upload success!

My point is, that you need to make a new report for the desync.

[kovarex]

Hello, teh desync is a script error of your custom server script.

the players is a global variable but not saved in the game state.

You need to use "global.players" instead so it works properly.

[Loewchen]

Well, if there were any doubts that covering two issues in one report is a bad idea...
I'll reopen it, as the original issue of this report is still not addressed.

[kovarex]

It is related as in normal catching up phase the player is not created until he catches up, so he can't be kicked because of AFK.
When he is catching up after desync, the player is there already. I don't want to remove the player after a desync immediately so the desync report is useful, so I will leave it like that.
If the desync report doesn't happen, the problem will not be there.