I'm getting randomly disconnected, I'm not doing much more than being in VAB or launching/flying a rocket.

This is from the server console:

I've tried having 2 different clients on my own comp when playing with friends and it's only the one I'm actually plaing in that disconnects (I have the other one idle in tracking station)

Something I'd like to take a look at.

EDIT: seems like an issue with the client not sending the correct message.

I've seen other players complain about this same problem on servers.

We just got the same error, for us it happened in Career mode, when one player clicked the Revert to Launch button.

At the time I was actually about to launch my own craft, in the safety bubble.

[19:37:14][DEBUG] : Kicked for trying to create an existing subspace
[19:37:14][INFO] : Disconnecting client xxxx, sent CONNECTION_END (Kicked for trying to create an existing subspace) to endpoint xxxx
[19:37:14][DEBUG] : Online players is now: 1, connected: 1

RockyTV: This one is actually an easy one, here's the cause:
https://github.com/godarklight/DarkMultiPlayer/blob/master/Server/Messages/WarpControl.cs#L52-L57

This is a direct result of the warp system being far too peer-to-peer than it should be, The fix would be to rip out the created subspace ID out of the message, and build a new subspace from the new details, and then sending the client coming out of warp into that subspace via WARP_CONTROL/SET_SUBSPACE.

This is pre v0.1.0.0 lazyness :P

EDIT: This is a protocol break as well btw, so we'll have to include it in 0.2.1.0

@godarklight Maybe call SendSetSubspace()?

This issue is addressed in the warp-rework branch - I'll close this when it hits dev.