I had a problem that prevented me from logging in to a server. I was restarting my game several times while testing something on the server Light vs Dark. I was using scripting to import and export sectors. One time I restarted the game and tried to log in, I was having my script import a sector. I had accidentally logged in without meaning to, so I closed the game immediately after clicking the button to log in. Then I started it again and tried to log into the server. However, my game kept popping up a strange error, "ZipException: Not in GZIP format." There was a "continue" and "exit" option. Clicking continue seemed to do nothing except pop up another exact same error message. So I closed the game completely and tried again. I tried restarting the game several times and using different usernames to log into the server, but nothing worked. The same error happening. So I hit exit, then I used steam to verify my game files. It found 4 files to replace and then it redownloaded them. I was then able to log in again. However, when I spawned in a new ship core and tried to enter it, a new error popped up giving me an error message about a texture not being loaded. I clicked the "send report" button to send in a report about this, however the "Report Bug of Crash" tool does not appear to be working correctly. When I filled everything out and clicked the "Send Report and Logs" button, nothing happened. So I am here now reporting it.
So, after the crash. I restarted my game again completely, and this time I was able to enter the build core successfully.
Here is a screenshot of the "ZipException" error: http://prnt.sc/cvs9yn
Here is a screenshot of the steam verification results: http://prnt.sc/cvsd9a
I did not catch a screenshot of the last error, because I was expecting the bug report tool to send that information.
10-19-16 Update: I am continuing to have the bug where it states a texture is not loaded. If I click "continue," it allows me to keep playing but then gives other bugs, so eventually I have to restart the game since this is very disruptive. I forgot to document the bugs when they were occurring, but I'll do so next time it happens.