There should be a zip folder along the lines of "desync-report-2016-09-24_18-42-54.zip" - that's the file that contains everything needed.

The desync report file, is from the server, I just uploaded what the server had saved

The person that desynced should have the full desync report zip file ...

Rseding91 wrote:There should be a zip folder along the lines of "desync-report-2016-09-24_18-42-54.zip" - that's the file that contains everything needed.

The desync report file, is from the server, I just uploaded what the server had saved

That's not the full desync report. It's missing the "other" part of it.

Can you tell me what the other part of the report is? The save file? The log file?

Client side log: https://drive.google.com/open?id=0B0-3oeXJF8g0OU0zRmNTaHVLcnM

Save file from server: https://drive.google.com/open?id=0B0 ...

Playing with this modpack: https://drive.google.com/open?id=0BzbypQp-ydUWT2F6UGR4WWpzUjQ
Throws me into a instant and looping desync. The server is mine, I haven't started to debug why it might cause desync just that it does.
1346.436 Info ServerMultiplayerManager.cpp:733: mapTick(8760422) received ...

A snapshot of the log:

15528.483 Info ServerRouter.cpp:242: Received message type(ClientToServerHeartbeat) heartbeat(sequenceNumber(222695785) ) requestsForHeartbeats() from unknown address(redact), so the peer id can't be deduced.

Issue is that player is dropped, and server is receiving this ...