I'm on my way to investigate. I'm gonna check out your base to see if there is something causing it to crash. -Tipsied [doublepost=1506405202,1506399179][/doublepost]So it seems you do not play on Node 1, but I did find a shared base on Node 2. If this is the node you are talking about, there is nothing in the base that could be causing a crash upon log in. Could you please provide a crash-report for us to better assist you? Just click on crash-report for more information on how to obtain one. -Tipsied
Okay np. I did find a base on Node 2, but did not crash when I looked around; so until we get a crash-report, we won't know for certain what's causing you to crash.
Yes if possible. It doesn't seem the server was crashing. I can double check the logs [doublepost=1506445224,1506430642][/doublepost]Okay, so after PMing back and forth and testing, we have deduced that when you log into SF3 N1, you do crash the server but no crash-report is generated by our bot and it would seem no crash-report is generated client side. I will go ahead and bump to our @Administrator team to further investigate what is causing this. As side note, which may be helpful, it shows you as not having logged into SF3 N1 for 200+ days. I would also suggest trying the MyM launcher in the meantime. EDIT: I forgot to mention that the error received is something along the lines of "the server you were previously on went down" and that we double checked the IP
Hello, I have fixed this crashing issue. There was a bad recipe pattern in your multi-block crafter. Unfortunately I had to nuke the entire multi-block crafter and the RS controllers. I placed a chest for the controllers so you can make the RS operational again. You will have to rebuild the crafting multi-block though. -Aiden
