[boskid][2.0.26] desync right after doing some modded platform building

[Quezler]

I was alone on the server when it happened, i moved the collector setup up by two so i could fit more laser turrets.

The screenshot is from during the desync, the video file (which you'll have to rename) shows me trying to replicate what i did sometime after the latest autosave.

I tried to replicate it twice on the server by loading the save but i had no luck there.

As per the desync post guideline thing it should be made in viewforum.php?f=209, but i saw no create button there so i'm mentioning modding in the title, though i do not believe any of the mods were actively involved in me just moving that setup around a bit.

[Quezler]

the autosave and desync report didn't seem to have been attached to the main post, let me try reuploading them:

[Quezler]

hmm desync report didn't want to get posted again, retrying

[Quezler]

desync report:

[Quezler]

failed to attach the desync report as a file, just grab it here: https://proxmox.nydus.app/desync-report ... -34-42.zip

Code: Select all

<b>[phpBB Debug] PHP Warning</b>: in file <b>[ROOT]/phpbb/plupload/plupload.php</b> on line <b>347</b>: <b>move_uploaded_file(./files//plupload/cfd5f8e59121bb005a34a00a22e0e3b4_50c4fad191ee48d7e20eb6af26569399): failed to open stream: Permission denied</b><br />
<b>[phpBB Debug] PHP Warning</b>: in file <b>[ROOT]/phpbb/plupload/plupload.php</b> on line <b>347</b>: <b>move_uploaded_file(): Unable to move '/tmp/phpPmfyYb' to './files//plupload/cfd5f8e59121bb005a34a00a22e0e3b4_50c4fad191ee48d7e20eb6af26569399'</b><br />
{"jsonrpc":"2.0","id":"id","error":{"code":103,"message":"Failed to move uploaded file."}}

[Quezler]

Got another one right as i was about to copy paste two turrets to force build over the inserter gap due to moving the railguns left a bit:
https://proxmox.nydus.app/desync-report ... -54-14.zip

[Quezler]

shower thought: ammo removed from mined railguns ends up in the hub, i have not opened the hub but it could be a vector

[boskid]

Thanks for the report. This desync is now fixed for 2.0.27. It was introduced in 2.0.26 as part of the asteroid collector's chunk tracking optimization.