** this was a stopic started on NDA forum, but well its not really an NDA thing as it still applies now **
As most of you know, right now if you log off, your construct will freeze wherever it was. This is due to the fact that the game client is the one computing / handling construct movement and a limitation were unlikely to ever see completely vanish.
So heres my suggestion to counter the abuse it bring (free instant brake)
Save the velocity in the construct, so that a frozen construct, will resume its previous course once "activated" again by a player sitting in it. There would still be some potential slight abuse from it. but it would be much less impactfull.
it can also be improved to consider the mass of the construct when applying velocity back (if its heavier, apply less off it, following a simple implementation of f = ma. just dont allow the other way around or bad surprise could happen i guess (as in light ship starting faster than they were xD).
it would not be a perfect fix by any mean, there are still ways to use such system to your advantage, but at least it would be an improvement over the current status, and would not require any major rewriting of mechanics for it to be applied.
Ideally later on we could have construct wake up on a new client computer whenever a player enter an area around it or something, but at least, this suggestion would improve the situation / reduce abuse with minimal actual core mechanic changes.
An interesting and also simple fix to cargo related abuse with this change (where you could unload cargo while frozen etc), would simply to lock container whenever the construct is frozen and has a velocity magnitude of something higher than like 50m/s. this wouldnt affect messing with cargo of a normally parked construct even if the owner crashed or server crashed or what not, but would prevent high speed abuses.