Going Rouge got up and WENT

So, I am playing this morning. All is well.

I logout to go get lunch.

When I come back, I no longer can access my Goldside characters.
Instead I am greeted with a messege saying "This option is only available for people that have Going Rouge. Would you like to buy it?"

Now, that's what I THOUGHT I did WEEKS ago, when I bought the Going Rouge Box set! ;-)


Clearly a glitch of some kind, but annoying, as I just recently got my new video card, and that is the zone with "all the new pretty" that I bought the GPU for in the first place!


Help!?! Please? help...

I'm going to be mature in saying, that the expansion is called Going Rogue, before anyone makes fun of you for talking about a color going up and running away.

This is something that ties into your account. I believe it is just coincidence that when you switch your card, this problem happened. Unlikely, yes. But graphics card's would not give off this sort of problem. Talk to support, and they will have this fixed in a jiffy.

Thanks for not ripping on my dyslexia too bad :-) (darn google spell check for not knowing what I MEANT to type :-)


Not a fault of switching cards though.

I suppose I should have been more clear...
there were NO hardware changes made from over a month ago. And my lost access occurred today.

Literally, I logged in this morning.(I WAS able to access them then)
Played a while.
Logged out.
Went for Lunch.
Logged in.
Could no longer access gold-side characters.

Ok... now THIS is just getting odd.

I logged out of my villain using the "Quit to character select" button.

And what do you know... I have access to all my characters again, without the offer to buy Going Rogue. Unless Support wants to investigate further, I'm going to chalk this one up to either nasty login-server lag, or gremlins. Probably gremlins.

I read your post this morning and thought it was strange. Then when I logged on two friends of mine reported the same thing, and it just happened to me a minute ago.

I plan on sending a bug report in game as well.

This sounds like the same problem where some people's accounts were reported as trial when they were not.

Database hiccup.

Had the same issue Last night while running Kahn TF. Got the sound loop bug, it crashed my game eventually. So, I go to log back in and access the toon I was playing (Level 50+1 Kin/Elec Tank) and It says I cannot access These features without having the Going Rogue Expansion. Then it asks me if i would like to purchase it or later. So I hit later, I exit out of the login screen then logged back in and everything was back to normal.

Freaked me out at first but knew it was some kind of weird server bug/lag/failed check or something. Would have been really concerned if it kept me out completely every time I tried logging back in lol.

Still, this is a recent bug that seems to have been introduced with the Weekly Strike Target feature. It is possible that all the activity and red servers are causing a strain on their systems. *shrug*

Can't access my Gold characters. Can't access nearly any of my Blue side toons. My Red side toons seem mostly accessible. Toons that are rogue/vigilantes are inaccessible. Toons that started Gold and are now Blue are also inaccessible. Lastly, I think toons that have the new auras aren't playable.

I see a nice little Upgrade to Going Rogue icon in the lower right. But I've already done that. Been a player for 2 1/2 years. Have every booster but the Party pack (although after seeing the Michael Jackson dance emote I am considering it).

Maybe I'll log out and in again. Just wanted to drop a quick note that this may still be occurring.

Happening to me as well. Wouldn't let me log in with anything except red-side (villain or rogue), but let me log in blue-side once I logged in then back out.

Happened to a friend of mine last night when he was switching characters. Logging out of the game entirely seemed to fix it, at least at the time. No idea if he's had the issue today.

Might be a database error. Might also be a locally stored account flag being improperly read, which might be the case if the problem isn't universal. Even if you DO eventually get access to the "locked" characters, I'd advise submitting a /bug report so they can accurately track the issue.