[Bridger]

[Jestersmith]

[Remsus]

Reminds me about this old joke:

A helicopter was flying around above Seattle yesterday
when an electrical malfunction disabled all of the
aircraft`s electronic navigation and communications
equipment. Due to the clouds and haze, the pilot could
not determine the helicopter`s position and course to
steer to the airport.
The pilot saw a tall building, flew toward it, circled,
drew a handwritten sign, and held it in the
helicopter`s window. The pilot`s sign said
"WHERE AM I?" in large letters.
People in the tall building quickly responded to the
aircraft, drew a large sign, and held it in a
building window.
Their sign said "YOU ARE IN A HELICOPTER."
The pilot smiled, waved, looked at his map, determined
the course to steer to SEATAC airport, and landed safely.
After they were on the ground, the co-pilot asked the
pilot how the "YOU ARE IN A HELICOPTER"
sign helped determine their position.
The pilot responded "I knew that had to be the MICROSOFT
building because, similar to their help-lines, they gave
me a technically correct but completely useless answer."

[Sorotia]

Just the status quo for them...I'm sure sometime down the line they will just nerf the console to oblivion like they typically do

[darthnovawave]

While I don't disagree with Spencer that stuff like this is frustrating, I think he's potentially calling out the wrong team here. QA teams are generally responsible for identifying and flagging any bugs or other problems with gameplay. They are not however the ones that typically fix said problems, and may not even have coding skills depending on how Cryptic hires for that team. We on the outside of Cryptic don't really know what may be on the "to-do" list for those fixes, but I'd suspect that with a team as small as the STO team is and based on what we see in patch notes and comments the team public makes on Ten Forward streams and whatnot, the top priority for the devs limited bandwidth outside of making new content is probably system and game-breaking bugs like stuff that cause the game to crash entirely, players to get stuck, or subsystems like BOFFs, traits, and the like to stop working or severely malfunction.

Stuff like the Agony Redistributor console issue Spencer is calling out fits none of these and instead is a gameplay balancing change, which in general seems to be a low priority for the STO team. Under certain circumstances (e.g., TFOs where more than one player has and triggers the console at the same time), it can create a really powerful effect, but otherwise the console seems to be performing as the devs seemed to have intended, and while really powerful, there are other ways to create insanely high DPS numbers too so it could be debated what constitutes "broken" (which the DPS community usually sees as "get good for cheap" things like this) vs. "meta" (e.g., get good by investing epic amounts of time and/or money to procure a bunch of rare stuff to min/max the game mechanics to their extremes). Unless triggering the console starts crashing the game client or something, it isn't going to be touched until one of the dev team has "rainy day project" time or is tapped or chooses to take on a broader rebalancing project like we've seen with the reworking of the Command and Intel specializations. Those kinds of changes are pretty rare in STO, and given that supposedly the devs have been doing that kind of stuff on their own time, I don't really see this kind of thing being touched any time soon.

[Mack]

Hmm, Craptic, posts of new ships and legendary bundles.

So business has been as usual eh?

[Moose]

.