Bronsaw

Would you by chance already have another resource station up and running? Because I successfully made one without issue, before experiencing what you are describing. To be more clear. After creating a ship from the drone, and just leaving it in the default iron block, typing in "/yam <material> "would seem begin the "lost connection" issue . Once the command is entered, the player is unable to do anything that requires the game to do loading, probably because the command has already disconnected the session from the server and is running "client-side" only. Another possibility would be there exists a looping issue in the script that that the engine tries again and again to fire with no success. Eventually ending in the lost connection message. No other input would be possible due to this script taking priority. It takes about 1-2 minutes after entering the /yam command for the lost connection message to show up. Some findings from casual testing: -It's probably nothing to do with the locale of the ship/station. Distance from stations and ships have no impact, including empty sectors. -It seems to have nothing to do with what sort of ship is used for the /yam command. Single block, or otherwise, the same bug initiates the same as the above. -Using a station founding ship purchased from a shipyard , and trying to build a normal station from it causes the exact same bug as above! Even without invoking the /yam commands. For example, using the ship to found a potato farm would pretty much initiate the bug when you hit the "OK" in the confirm transaction warning screen. -Using the default config doesn't seem to stop this from happening. -Not a mod conflict. This was the only mod I'm testing with. -Created a new universe. Successfully created first station with /yam, but second one exhibits the same bug. Deleted the station and then tried the /yam command again, and still got the lost connection bug. -Can't seem to have two of them it seems. - Using the beta and the stable steam release.. Going back to v0.21.4 in Steam resolved this issue for me.