You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So when awaiting @ 7:45 AM Sunday.. (today), I was talking with Raven1 about his character. He logged off yesterday while his character was on Desolation. Turns out someone hacked it to make it all non-blue (NC). Since then he cannot log onto his main account because it's in limbo as he reports granted there are now no NC spawn points. (apparently). He made an alt, Raven1, to make up for that.
Not sure if this makes much practical sense. He thinks locking it into being all NC will help. We're awaiting the results. I'll make another message when he's done and trying to get back on his main.
//xEquinaux
The text was updated successfully, but these errors were encountered:
Status update: it worked for him to hack all the bases to NC from VS/TR. I guess 'Your position has been compromised--you were spawned in nearest friendly location' or whatever prompt wasn't working when nothing was NC on that battle island.
Seems we are having a particular problem logging in. Some of us can get on. But most of us are running into a crash upon login. We're listed on the PSForever Portal, then get a crash. As of this Sunday.
Lazer in particular was crashing. I think others as well. I'd see them listed, and then unlisted.
I'd get one crash upon logging in. Then I was successful about 5 minutes later.
Hi there FateJH,
So when awaiting @ 7:45 AM Sunday.. (today), I was talking with Raven1 about his character. He logged off yesterday while his character was on Desolation. Turns out someone hacked it to make it all non-blue (NC). Since then he cannot log onto his main account because it's in limbo as he reports granted there are now no NC spawn points. (apparently). He made an alt, Raven1, to make up for that.
Not sure if this makes much practical sense. He thinks locking it into being all NC will help. We're awaiting the results. I'll make another message when he's done and trying to get back on his main.
//xEquinaux
The text was updated successfully, but these errors were encountered: