That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.
So we get a fix for the half dozen people who fly a D'Kyr still but we get to wait atleast another week for the FAW crippling bug to be fixed. We are now over 2 months with you people being unable to fix FAW. :mad:
So we get a fix for the half dozen people who fly a D'Kyr still but we get to wait atleast another week for the FAW crippling bug to be fixed. We are now over 2 months with you people being unable to fix FAW. :mad:
Graphics bug seems to creep up after you have left the game running for a couple days, not closing it every day just logging off, at least that's when I get it.
I haven't seen one of these ships in-game for months now, close to a YEAR. In fact I discarded mine because of continual graphical glitches.
We have far more game breaking bugs... Memory leaks at ESD causing graphical issues. We have the uniform slot issue. Should I mention FAW? Yep still broken. There are glitches throughout the original progression missions. Problems with STFs, grind-maps and chat is still broken.
Yet... somehow this gets pushed to the top of the pile and is worthy of a solo-issue patch?
The mind boggles. It simply boggles. WHO if anyone sets bug-priority over there? I'd like them to step forward and explain this. Why does my tool-tray reset itself at random (still, four seasons now)? And why is a glitch on a ship that is no longer relevant to the game considered a priority?
So we get a fix for the half dozen people who fly a D'Kyr still but we get to wait atleast another week for the FAW crippling bug to be fixed. We are now over 2 months with you people being unable to fix FAW. :mad:
Could be worse. It could be a bug that's just about as old but presumably much easier to fix, (likely just the restoration of a trigger at a certain set of coordinates for a menu for an area transition to pop up) but which affects every single player in an entire faction regardless of their weapon/skill loadout.
It's pretty bad when you que up and enter an STF, only to have your BOFF's get unassigned as you load in and get started. Not much time there to reassign them again.
-AoP- Warrior's Blood (KDF Armada) / -AoP- Qu' raD qulbo'Degh / -AoP- ProjectPhoenix Join Date: Tuesday, February 2, 2010
So we get a fix for the half dozen people who fly a D'Kyr still but we get to wait atleast another week for the FAW crippling bug to be fixed. We are now over 2 months with you people being unable to fix FAW. :mad:
I use FAW all the time, so I feel your frustration, but they're aware of the problem. It's just not so easy, given the layered architecture of the antiquated game engine, for the new people to clean up old mistakes from past Cryptic staff brought on by Atari's horrid mismanagement of the game in the beginning.
Work towards a resolution continues, but there will not be one available in tomorrow's patch. As many of you know, there is an interesting history with FaW in STO, and we plan on continuing to investigate the reason why bugs with it occur. We are not currently planning to push a resolution for any issues related to FaW until we're confident that we've tracked down the underlying issue and have a permanent solution in place. I don't have a current ETA for this. We will continue to keep you in the loop as we have more information related to FaW to share, but know it's not forgotten.
Thanks for your patience, and we apologize for the inconvenience experienced by our players who use this power.
Cheers,
Brandon =/\=
As ya'all can see, it's rather complicated and they are working hard to figure out the problems to fix it. So just relax and be patient.
Funny thing is, BfAW with an A2B setup is kinda mildly OP s it is...so just letting them Crit IMHO will break the game, really as NOTHING will be able to compare to a fully functional A2B FAW build that can uber-crit.
Do you mind linking where that comment from branflakes was originally posted.
I want to send it to my fleet, and no offense I want send them a link to a post from branflakes not someone with the trollface as a profile pic
Tip: In the quote you will see a little red dot next to the name of the person quoted. Clicking that dot will take you directly to the post that was quoted in the thread it came from. So in my post you are responding to, click the little red dot next to pwebranflake's name in my quote.
Edit: How I quoted someone from another thread: I clicked the quote button on the post I wanted to quote. In the message window I copied (CTRL+C) the whole text. Then for my post here I pasted (CTRL+V) the whole text first then put my comment under it.
Comments
I call it, the Stoutes paradox.
Absolutely mental isn't it. Mental.
Valdus | Charn | Costello | Typhus | Thyran
Cant reproduce you say, but look at the forums once, hundreds of people have the issue. Probably more like thousands.
Fleet Admiral Rylana - Fed Tac - U.S.S Wild Card - Tactical Miracle Worker Cruiser
Lifetime Subscriber since 2012 == 17,200 Accolades = RIP PvP and Vice Squad
Chief of Starfleet Intelligence Service == Praise Cheesus
Indeed, this and the FAW bug are around for too long in my opinion.
We have far more game breaking bugs... Memory leaks at ESD causing graphical issues. We have the uniform slot issue. Should I mention FAW? Yep still broken. There are glitches throughout the original progression missions. Problems with STFs, grind-maps and chat is still broken.
Yet... somehow this gets pushed to the top of the pile and is worthy of a solo-issue patch?
The mind boggles. It simply boggles. WHO if anyone sets bug-priority over there? I'd like them to step forward and explain this. Why does my tool-tray reset itself at random (still, four seasons now)? And why is a glitch on a ship that is no longer relevant to the game considered a priority?
http://imageshack.com/a/img34/9245/wa7z.jpg
DELTA PRICE RISING
Could be worse. It could be a bug that's just about as old but presumably much easier to fix, (likely just the restoration of a trigger at a certain set of coordinates for a menu for an area transition to pop up) but which affects every single player in an entire faction regardless of their weapon/skill loadout.
"Resolved an issue which was making the Tal'Kyr invisible with the support vessel and shuttle versions."
Join Date: Tuesday, February 2, 2010
I use FAW all the time, so I feel your frustration, but they're aware of the problem. It's just not so easy, given the layered architecture of the antiquated game engine, for the new people to clean up old mistakes from past Cryptic staff brought on by Atari's horrid mismanagement of the game in the beginning.
"Back on topic. Destinii is correct."
(Formerly Destinii until the 'Great PWE Forum Shakeup of 2012')
As ya'all can see, it's rather complicated and they are working hard to figure out the problems to fix it. So just relax and be patient.
NOTHING.
...[Server Not Responding...]
:mad:
Do you mind linking where that comment from branflakes was originally posted.
I want to send it to my fleet, and no offense I want send them a link to a post from branflakes not someone with the trollface as a profile pic
Tip: In the quote you will see a little red dot next to the name of the person quoted. Clicking that dot will take you directly to the post that was quoted in the thread it came from. So in my post you are responding to, click the little red dot next to pwebranflake's name in my quote.
But here is the link to the post of pwebranflakes that I quoted in the original thread it came from http://sto-forum.perfectworld.com/showthread.php?p=14406091#post14406091 Thread title: Fire at Will (Faw) not critting *Team is investigating - latest update: pg. 20, #200*
Edit: How I quoted someone from another thread: I clicked the quote button on the post I wanted to quote. In the message window I copied (CTRL+C) the whole text. Then for my post here I pasted (CTRL+V) the whole text first then put my comment under it.