>>But on the other end, it removed alot of the risk/reward. … iirc they can’t have too many players and bots at the same time on the same sector. <<
Remove risk? I hate it, to fly 5mins+(with 700m/s!) to some sectors to farm there and then need to go back/self destroy to play in another mode. Where is the ‘risk removed’ by such a logout? That you can be destroyed the way back? The anti-aggro rescue(another player attacking - which a shame is totally removed by BS station protection in whole OS)/npcs? Sorry, it could take time to safe logout and if you had this time, you have no risk at all having at that time.
>>Also, missions are just a few jumps aways. And travel time is part of any open space game. And 90% of them have a much much much slower pace.<<
First, not all missions are just a few jumps away. Second, such safe logouts are more in the sense of farming in a distant sector for a bit of time(half an hour up to several).
>>What would have happened if, the guy is in shard 2 of the Russian server and in Iridium Strand. When he want to “log back” in his OS ship, but the shard on which he was is now full.<<
Yeah because this would happen so often. Either the ship remain unavailable or he would be transfered to another shard(and according to the logdata of the sectors, they are generated on distinct servers, not shards).
>>Or if you’re spot get “reserved”/saved for you. That mean someone who does not play, lock a spot for someone else that could come there and actually play.<<
How can a place be ‘locked’ by somebody? You can have multiple instances of ‘player’ on the same spot, that’s not a problem. The only problem would be if players simultaneous would login having their ships on the same spot, and then they would just have to wait that the other guy move away with his ship. Just a loading into OS - ‘issue’, nothing more and not a problem itself.
The only real problem would be changes in ship/layout/map etc. ‘corrupting’ data in the player’s database. Else no problem.