Reapply #2095 and fix reconnection error cause by it

[NetsuNegi]

No description provided.

[phoboscn-bot]

To Chinese users:
This pull request has been mentioned on Phobos CN. There might be relevant details there:

致中文用户：
此拉取请求已在 Phobos CN 上被提及。那里可能有相关详细信息：

https://www.phoboscn.top/t/topic/238/1

[github-actions]

Nightly build for this pull request:

• compiled-dll-5672a6cf4efd55a4cec73b9c30dbdf344f6fb37d.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

[Coronia]

didn't desync in our test so far, and the previous issues are solved. More testing is appreciated tho

[TaranDahl]

I think we should find out exactly what processing was missing before that caused the desync.
This should be documented in the comments to remind other developers.

[TaranDahl]

The code lgtm. But the issue above should be addressed.

[Coronia]

I think we should find out exactly what processing was missing before that caused the desync. This should be documented in the comments to remind other developers.

We can't even figure out what exactly caused the desync yet, but just take reference of other event codes and add missing checks as much as possible (e.g. planning node, tether etc). So sadly there's no clear document as of now

[NetsuNegi]

I think we should find out exactly what processing was missing before that caused the desync. This should be documented in the comments to remind other developers.

The most important code to resolve this desync seems like pSource->SetTarget(nullptr).
I don't known why, but when I removed it, tester said that desync happend again.