test content
Logo
What is the Arc Client?
Install Arc
Options
Cure Found Elite is BROKEN - leaver penalty! *Resolved!*
galaxyrider0
Member Posts: 0 Arc User
Hi!
I was playing earlier today when I joined a Cure Found Elite Space and the mission has already failed, now I know why. It is BROKEN!
The Raptors and Neg'Var are doing insane amounts of damage, seriously, my team was doing everything right, but the second wave melted down two players and damaged the IKS Kang beyond the normal.
Even with three ships healing the Kang, the wave from the second Cube was overwhelming! I never saw that amount of damage in the Kang, even with two ships guarding it. Me with a Scimitar and Elite Drones and a Defiant.
So:
1 - The Bord-Klingon Ships are dealing some bigg above the normal DPS.
2 - They are dealing too much damage to the Kang, one Raptor wiped out 50% of its Hull.
3 - Seems that healing the Kaag had no effect at all. Hazard Emitters, Eng. Team and Tranfer Shield from three ships.
Anyone else saw the same?
EDIT: Please, stop assuming that I'm a Newbie, we are talking about bugs in this mission, not how to play it. I know how to play it, aside of this, feel free to tell us your experience with the mission today, when it seems that the bugs started.
I was playing earlier today when I joined a Cure Found Elite Space and the mission has already failed, now I know why. It is BROKEN!
The Raptors and Neg'Var are doing insane amounts of damage, seriously, my team was doing everything right, but the second wave melted down two players and damaged the IKS Kang beyond the normal.
Even with three ships healing the Kang, the wave from the second Cube was overwhelming! I never saw that amount of damage in the Kang, even with two ships guarding it. Me with a Scimitar and Elite Drones and a Defiant.
So:
1 - The Bord-Klingon Ships are dealing some bigg above the normal DPS.
2 - They are dealing too much damage to the Kang, one Raptor wiped out 50% of its Hull.
3 - Seems that healing the Kaag had no effect at all. Hazard Emitters, Eng. Team and Tranfer Shield from three ships.
Anyone else saw the same?
EDIT: Please, stop assuming that I'm a Newbie, we are talking about bugs in this mission, not how to play it. I know how to play it, aside of this, feel free to tell us your experience with the mission today, when it seems that the bugs started.
--
"If we're going to be damned, let's be damned for what we really are." - Jean-Luc Picard
"If we're going to be damned, let's be damned for what we really are." - Jean-Luc Picard
Post edited by galaxyrider0 on
0
This discussion has been closed.
Comments
It also sounds like you joined a public match. If that's the case then don't be surprised if you lose. You are more than likely going to get ships that are not built for these types of missions. Which means you'll be overrun easily by enemies.
Me and fleetmates completed a Cure Elite run with a group of 5 Galaxies and we had a lot of time left. Contrary to what people say, you do not need super DPS. Just experience. Once you play through a few times you will realize that you do not even need a Kang healer or guard. Stay attentive and be careful when blowing Cubes.
Simple rule: if your group has only so-so DPS, wait before popping the Cubes; if not, it doesn't matter: a high-DPS ground can kill the oncoming Raptors fast enough.
I know everything you said.
The mission was ok yesterday, a challenge, not a buggeg High DPS enemy overkill.
Two time I've played this mission today:
1 - Joined it and BOOM, my ships was cought in the middle of the fray, close to where the Kang should be, but no... the mission was already failed.
2 - Started the mission as normal, first wave was a little more hard to kill than the normal, but when we killed the first cube the trouble began... the second wave... only one Raptor got close to the Kang and more than 50% of it's hull melted down in 5-7 seconds. Then we tried to heal the Kang, as I said, nothing, It was like the heals was not working at all. Second cube, third wave... the Kang exploded with one Raptor again...
Yesterday this mission was ok, but today is insane.
"If we're going to be damned, let's be damned for what we really are." - Jean-Luc Picard
God! I experienced a overkill enemy mission and you could kill the cubes before destroy the Nanites?
"If we're going to be damned, let's be damned for what we really are." - Jean-Luc Picard
Sometimes, you take down enemy ships easily and sometimes they take forever to destroy... in the same run... for the same ships... from the same angle of attack.
But the worst part is when you fail the mission, if you leave, even after destroying all the enemies around, you'll automatically get the 1-hour ban penalty. Yes, that's so cool to be unable to play the rest of the PvE queues because you fail one ESTF and had no choice but to leave or be trapped there forever.
anyways though, people on my team only got KOed a few times. and that was with me playing an experimental torp'Varo build that didn't work as well as I was hoping it would.
My character Tsin'xing
"Last Engage! Magical Girl Origami-san" is in print! Now with three times more rainbows.
Support the "Armored Unicorn" vehicle initiative today!
Thanks for Harajuku. Now let's get a real "Magical Girl" costume!
I ran over 30 CSEs in the past week, about 50% of it being an RML run; only failed once, because someone used fleet support, and the spawned warbird popped the middle cube, while we were working on the right cube.
AGAIN: The mission is bugged! Not me! ok?
I know everything about grouping, how to do the mission, build and etc... the issue was with the mission.
I've played this mission more than 30 times, this is the first time I face such bugs, perhaps the mission went broken after this week update.
"If we're going to be damned, let's be damned for what we really are." - Jean-Luc Picard
SImple...
Yep, seen the strange behaviour of NPC's vs Kang. (Not actually a new issue, happening at random since before rep system)
Yep, Copped the locked in failed mission and subsequent 1hr ban from all other games when forced to leave manually.
- Have even copped 1hr ban when the server booted me as the mission was loading (I didn't even get into a listed game... kicked at loading screen... log straight back in.. no notice, no server ban indicator just no go until I logged out and reclogged back in trying to figure it out then the server ban notice appeared).
Best thing to do. Keep posting and talking bout it peeps.
Keep making NEW posts... (sorry forum admins, I know not your fault BUT its the only way anything ever seems to get fixed).
Don't play missions that CAN fail unless you are 500% sure the team you are with wont fail the mission. -- best of all (which wont happen) - don't play the missions at all...
Finally - Don't count on anyone fixing this anytime soon. Like many other things (CE Encounter) things like this just don't seem to be fixed in any kind of hurry....
Oh the important things like... Tweaking the audio effects on the quad cannons... or look Colony Invasion is bugged allowing players extra marks... Those get fixed really fast. Issues that TRIBBLE players over or make the game pointless... Nahh leave them for a while... Too hard.
Perhaps you had luck, but take a look on the forum or even in this thread, there are some experienced players that experienced the same problems.
"If we're going to be damned, let's be damned for what we really are." - Jean-Luc Picard
Added whilst typing - so response.
Yes it is def mission problem... not you.
I am very experienced with these missions. Currently Tier 5 on two characters and third (romulan) on tier 4. -- This is not to mention the completely specced PRE rep ships I have including most Maco & Omega Gear (multiple times).
Stress less. If people are lucky they wont have a problem. If they are not and start getting screwed... they will come here.
Ok mate.. Mission not bugged eh....
Kewl... I got nothing better to do today. Whats say you and me meet in game. We will create our own mission (instead of pugging it like 99% of people do) and deliberately fail the mission...
THEN you will see it IS bugged... It is bugged (broken) to hell.
No not having a go at you... BUT perhaps.. instead of emphatically making a statement... perhaps re-word it to be a little less hostile. Just an idea.
As Riker once said: "What a perfect vicious little circle"
"If we're going to be damned, let's be damned for what we really are." - Jean-Luc Picard
You must be extremely unlucky in that case I guess.
Unfortunately, the game doesn't remove 'failed' missions from the Queue immediately, so you might have ended up getting into the instance, when the objective was already failed, but the game did not remove it from the queue yet. I think this could be a leftover of an old loophole, when sometimes you could make another run of CSE, right after you finished it, because the game didn't give you a cooldown on it for some reason.
Also, I have to repeat. I did over 30 CSE runs this week and have had absolutely no problems whatsoever.
Not ignoring anything.
Got into a Failed mission only once today; after that, when I got in okay, the missions played out as usual, with no apparent abnormalities (though, I must admit, I did not try to shoot the Cube immediately).
The question is in the statement. The STF mission referred to as Cure, to obtain Omega Marks is Broken.
Specifically, when the mission is failed, you are unable to leave the mission anymore without doing so manually and incurring an automatic 1hr ban from playing any other game, public OR private.
So yes. People have played. People haven't had issue. Good for them. BUT there are probably (from the general sounds of things atm at least 5-1) who HAVE been caught by this new nasty little bug.
In reality, for those who have come here and specified most decisively that this mission
IS NOT BROKEN.... Um well, ahh yeah it has NEVER worked correctly and has had to be fixed on numerous occasions, stemming from its initial launch and appearance as part of the STF end game sequence. Where it was all about finding random drops of Rare Prototype stuff to buy the matching gear.
It has ALWAYS been broken in some way shape or form. Just NOW it is a fresh problem. and is actually having a serious impact on the games playability in general.
SO for the topic at hand. Yes... Yes it is broken. Many have encountered this problem. Many are complaining about it. It does seem to have arisen following the update to tweak the audio on the quad cannons... and add a forgotten about hanger to the new Romluan warbird (must not have been selling enough of em to the kiddies :-s)
Prior to this time, I had not personally encountered a problem with it. Hopefully it will be looked at and fixed soon, so then everyone can go back to accusing each other of not knowing how to play or of stuffing it up, whilst the rest of us real people enjoy playing once again rather than being stuck here talking bout it, because we CANT risk playing these missions ATM in case we get caught out. That happens from time to time, usually no big.. but now. People are getting screwed and punished for actually playing the game.
That is what needs to be fixed. (and yes hopefully they will re-address the one kill super invisi torps and hyper rapters etc etc etc along the way.... BWUH HAHAHAHAHA Yeah right).
Failed Mission? or Failed Optional? Big Difference... If it is a failed optional, the mission can still be completed, and most likely someone warped out... and the queue (as it is intended to do) filled the open spot with another player.
Star Trek Online, Now with out the Trek....
Definitely Failed Mission - NOT failed optional(agreed BIG difference).
Nope. - This is about you not being giving the option to leave the map without incurring a penalty at the completion of the mission.
I specific, when the mission has been failed, and there is nothing more to do... (Kang went kablewy)....
Am unsure if it affects if the mission is completed successfully or not. Have not heard any specific feedback on that point, but from the huffing and puffing of those screaming no its not broken at all, am guessing its fine in that regard.
The being dragged into a game, with a blown optional. Yeah it does happen, sometimes its annoying. But hey, u go public u get what u deserve and suck it up.
Nope this is all about being sucked into a dead game, like the Tholian or Borg Sector Encounters where u hit the red alert button, jump in to find the game is all done and dusted and u get booted out straight away again. Only this case is not booting you out OR letting you leave without punishing you.
Star Trek Online, Now with out the Trek....
I mean I have done this mission countless times over so many months and this has never happened until recently. It is not like there is an embarrassing amount of content for us to do. They delayed their silly little FE ... making it more than 4 months since LoR. Shame is all I have to say. Test your code before you put it on live.
Sorry for the negativity but the "cup runneth over" with Cryptic.
- Judge Aaron Satie
This!!! Before trolls and fanbois come in here telling us things are all okay read this person's post!
This is 2nd ESTF that is now broken. Hive Onslaught is completely foobar even on normal despite the so called hot fix.
- Judge Aaron Satie
- Judge Aaron Satie
I pretty much have not pugged it for days now, since pugging it basically risking a 1hr penalty now if the mission is a fail. It's one thing to fail a mission and not be able to play that mission for an hour.. it's a completely different thing to fail that mission and not be able to join ANY queue for an hour.
I guess lesson learned. If these kinds of bug don't qualify for hot fixes ... I mean real hot fixes that actually resolve the problem I don't know what will. This literally prevents someone from playing the game for 1 hour.
- Judge Aaron Satie
And I don't know if it's intended as I've never noticed this before on Elite, but their Torpedo Spread can OHK you, even if you use "Brace for Impact" or even enough shield or even "Reverse shield polarity" engaged or even all at once.
And I'm not talking about "you took all the spread for yourself so the damage piled up", No, I'm talking about dying after the first or second "pulse" of the attack. 20 000 kinetic damage each seems over the top, even on Elite, especially for an AoE you can't avoid.