Star Trek Online

Star Trek Online (
-   Gameplay Bug Reports (
-   -   Repeatedly Kicked from Fleet Actions (

theeishtmo 11-18-2012 10:15 PM

Repeatedly Kicked from Fleet Actions
Half the time I try to join a fleet action, be it Starbase 24, The Big Dig, Klingon Scout Force, or whatever, I get kicked from it IMMEDIATELY after entering. It doesn't matter what character, which faction, it just happens, over and over again. I am very, VERY tired of this. Please make it stop so I can enjoy this game with my friends when we queue together.

Also, could you set it up so players don't get joined into a Fleet Action that's almost over and thus get nothing but a cooldown timer for their trouble. REALLY annoying when it happens after being kicked from one that just started.

wolfpacknz 11-18-2012 11:23 PM

Yeah this is turning into a joke. It's the same with Red alerts. This is what happens when you don't fix the bugs before you release a season. Thought we were past this PWE.. Seriously GET THIS SORTED OUT FAST!!!

somrik 11-19-2012 12:58 AM

I think they screwed with the cooldown.

It claims to be 30minutes but I think in the back end somewhere its still 60 mins.

So the game will let you queue after 30 mins. it'll even put you into the game but once you're in the map the game checks again, sees you're sitll on the 60 min cooldowna and boots you.

I think someone else was having the same problem and stated after 38-40 minutes of trying to get back in after the cooldown ended he was able to play another match which supports my "30 minutes on the front end, yet someone didnt change the 60 min on the back"

winstonandar 11-19-2012 01:42 AM

My two cents
I have been attempting to play the Dilithium events - The Big Dig, Starbase 24, Klingon Scout Force - for the last two days.

Each time that I enter the map, I get to look around for 5 seconds and then get booted out, with a warm message that makes me tingle, "You will be removed from the map in 10 seconds".

I have no cooldowns on any of these maps, since I haven't played in them for two days. I would appreciate it if the developers could look into this as soon as possible.

With regards,

ebemnared 11-19-2012 03:52 AM

I don't think it had to do with the cooldowns since I've been kicked out even before playing for the first time - I think it has to do with too many players assigned to the same game - I think server detects 11 players in a 10 man game and kicks out the last to join.

6 days after patch this is still going on. I know it's a free to play game now but this is ridiculous.

a30t 11-20-2012 08:39 AM

Same here. Sometimes kicked out even before playing for the first time.

malkarris 11-20-2012 09:02 AM

Same here, sometimes I get in, usually on SB 24, sometimes I don't, usually on Gorn Minefield or Klingon Scout force. Can't remember having an issue KDF side, but I don't play those much. Either way, if I get kicked, it will usually let me in for a little while, then pop up the you will leave in 10 seconds message. It almost like the srver lets me in and then realizes that it shouldn't have like there are too many people and its cutting the extra out. Then when I get kicked out, I can que right back up again, no cooldown, but it usually just does the same thing, and kicks me out again.

absolutbritish 11-20-2012 09:31 AM

Same for Mirror event. Me and two of my friends either get kicked right after entereing or no maps are found. Really really really takes the fun out of everything!

Please include these fixed in your next patch!

fiskee 11-20-2012 09:59 AM

I'm having the same problems. I started queuing for Mirror event games on the hour, finally started playing my first mirror event game 25 minutes in, after experiencing many insta-kicks or simply getting the "could not get maps from map manager" message.
Relogging doesn't help, switching characters doesn't help... this is getting tedious.

rextorvan36 11-20-2012 11:37 AM

This is actually beyond tedious.

I've tried going into 2 different ques not 5 minutes ago, and got the same error (cant get names from map manager) this bug was a bad bug from season 6. It shouldn't have reappeared on season 7!!!

All times are GMT -7. The time now is 06:51 AM.