This is, unfortunately, going to be a very (very) time consuming fix. What we found was, to fix this will require that we modify every space healing power and many buff powers in the game. This will happen as soon as we can fit it into Geko's schedule, but there's a lot of fierce competition for space on that schedule.
Wierd thing is it affects the klingon carrier but the Kar'fi pets are unaffected they still use their skills I just found that strange. I can't wait to see the update to the Kar'fi once its finished/ready
This is, unfortunately, going to be a very (very) time consuming fix. What we found was, to fix this will require that we modify every space healing power and many buff powers in the game. This will happen as soon as we can fit it into Geko's schedule, but there's a lot of fierce competition for space on that schedule.
When the B'rel first came out, buffs and heals did not decloak it at all - apparently, this was not working as intended, even though I maintain that it would have hurt no-one and it was perfectly fine as it was.*
So it was changed that any such ability triggered by or touching the B'rel automatically decloaks it for a short moment.
Unfortunately, this now includes the possibility of getting decloaked by teammates that think they are doing you a favor by tossing you a heal/buff. Or they do it on purpose (today a carrier healed me whilst I was at 100% ... I could have sworn he wanted to use me as bait).
Anyways ... if the guys at Cryptic want to make the cloak conditional on whether the buff/heal comes from the B'rel or a teammate, or if it affects just the B'rel or is directed at a teammate ... yeah, I can see this meaning to rework a lot of stuff in the code.
*: Basically the fear back then was that a B'rel could fly around perma-cloaked as an invisible healer - but given that this is a set of weapons completely remaining amiss in the battle I am still convinced such gameplay would only end up gimping the own team as it is essentially one player short. A single hull heal every ~30 sec isn't gonna change that.
Personally, I'd already be very content with just distinguishing whether the heal/buff is "leaving" or "approaching" the B'rel or if everything remains within the same hull. In case of the latter, decloak is neither necessary nor canonically viable. In case of the former I can at least understand why some people are concerned (see above) and that, technically, energy spikes travelling between a cloaked ship and another vessel can be tracked down and traced back.
This is, unfortunately, going to be a very (very) time consuming fix. What we found was, to fix this will require that we modify every space healing power and many buff powers in the game. This will happen as soon as we can fit it into Geko's schedule, but there's a lot of fierce competition for space on that schedule.
And come to think of it, last January we were told that this was the problem. In the past 9 months, how much progress has been made on the issue?
And when do you think this will be resolved?
If tbd, why sell it in the c-store?
And come to think of it, last January we were told that this was the problem. In the past 9 months, how much progress has been made on the issue?
And when do you think this will be resolved?
If tbd, why sell it in the c-store?
That is what I don't get. It isn't a new issue. They spent a bunch of time recently on the Rhode Island to insure those that purchased it got their money's worth, but the B'Rel hasn't been made a similar priority.
You're the type of customer that enrages retail employees.
Look. He's explained EXACTLY why this is a problem that won't be fixed easily. In fact, explained that fixing this one "little" thing will force them to fix a myriad of other things.
It's not that he doesn't CARE, it's an issue of manpower. Just like at the local department store that has one register open and you yell at the cashier about how they should open a new register.
Sorry, they can't. They often don't have the manpower to cover the registers. You can't just say "I want this, and if you don't, you obviously don't care".
Employees don't come out of a "Work-O-Tron" in the back, give them a friggin' break.
I quote this because it's absolutely true. I worked retail for nearly 20 years at various locations - all of which were built on the edict "the customer is always right" and I'm happy to be rid of it. Not because the various jobs sucked, but because of the customers with the over-active sense of entitlement.
I was fortunate to work at places that gave their employees the power to help the customer in any way, but one way we could never help them was by doing things "faster". Faster means quality goes out the window and more mistakes get missed.
So folks need to ask themselves:
Do we want it fixed now?
or
Do we want it fixed correctly?
There really is no middle ground on those two questions.
Anyhow...sorry for the rant. That's all just my opinion, and I accept the fact that I could be wrong. Regardless, thanks for reading.
In addition to bugs we get from QA, I will try to collect some of the most egregious ones reported on the forums that seem particularly serious. 95% of the time, bugs are in fact not 100% reproducible, but are only happening for certain players because of conditions they may not even realize aren't universal.
When I get a breather between regularly scheduled work, I will collect all the info that players have provided, which will in turn vastly speed up the time locating what the issue really is and where it is. This is why when I see an issue on the forum I will ask for as much info as possible, so when I do go in to look at it, it will be faster to reproduce the issue.
As it turns out, this case is one of those 5% issues that does in fact happen 100% of the time. We have now located the issue and are planning on pushing out a fix next week.
I just saw the patch notes for this week. I guess this didn't make it in?
Just a head's up, the issue appears to go deeper than we expected, so a fix for the carrier BoPs may not be ready this week. I will let you know as we get more information.
Just a head's up, the issue appears to go deeper than we expected, so a fix for the carrier BoPs may not be ready this week. I will let you know as we get more information.
Many apologies for the delay.
digging through code to fix stuff like this must be a major drag, good luck over there
Just a head's up, the issue appears to go deeper than we expected, so a fix for the carrier BoPs may not be ready this week. I will let you know as we get more information.
Just a head's up, the issue appears to go deeper than we expected, so a fix for the carrier BoPs may not be ready this week. I will let you know as we get more information.
Many apologies for the delay.
. Was really looking forward to hopping back into my carrier this week.
On a related note, how are the upgrades to the Pet Controls you guys have been working on? Throw me a bone as to a ballpark figure when those might be up on tribble?
Just a head's up, the issue appears to go deeper than we expected, so a fix for the carrier BoPs may not be ready this week. I will let you know as we get more information.
Yeah, after all this is the KDF side where things are delayed because of problems on the Fed side... I sure hope that is fixed with having new people come on-board...and soon......
After all I want my fingerless gloves, honor cloak, and hair options...dreads are sooooo not Klingon.....
Is good to have many alts so that when one thing breaks you can go play another ship thats not as broken as the others So right now I can get in the negh'var, vorcha, kar'fi, or my raptor. All the otheres are in the shop with our trusty mechanic working on them
*Sends a barrel of bloodwine to heretic, and sings songs of his glory in the great hall of warriors!*
The carrier groups of the KDF thank you sir.
I actually only deserve the credit for bullying other people. It took two software engineers, two content designers and jheinig to actually figure out and correct the bloody issue.
I actually only deserve the credit for bullying other people. It took two software engineers, two content designers and jheinig to actually figure out and correct the bloody issue.
Such a bizarre bug...
Ah, wow. Great teamwork then. Either way, I appreciate the speed at which is was fixed, having only brought the issue to light a few weeks ago. It'll be fun to hop back in the carrier.
Now I just have to eagerly await the arrival of the pet commands and all the other carrier goodies you've been teasing me with
Ah, wow. Great teamwork then. Either way, I appreciate the speed at which is was fixed, having only brought the issue to light a few weeks ago. It'll be fun to hop back in the carrier.
Now I just have to eagerly await the arrival of the pet commands and all the other carrier goodies you've been teasing me with
Yep. That'll be the true test for the carrier's viability in high-end PvP...
I actually only deserve the credit for bullying other people. It took two software engineers, two content designers and jheinig to actually figure out and correct the bloody issue.
Such a bizarre bug...
Thank you so much and all the people you bullied ROFL
i don't know if it is just me, but my BoP's are only using HYT1 they are still not cloaking or using CRF1, i will buy new ones just to confirm, but all of my tests so far indicate, still an issue, i will get back and edit if selling the old buying the new fixes this issue.
i don't know if it is just me, but my BoP's are only using HYT1 they are still not cloaking or using CRF1, i will buy new ones just to confirm, but all of my tests so far indicate, still an issue, i will get back and edit if selling the old buying the new fixes this issue.
To my knowledge, that fix hasn't made it to live yet.
Comments
Wierd thing is it affects the klingon carrier but the Kar'fi pets are unaffected they still use their skills I just found that strange. I can't wait to see the update to the Kar'fi once its finished/ready
what changed that broke them in the first place?
So it was changed that any such ability triggered by or touching the B'rel automatically decloaks it for a short moment.
Unfortunately, this now includes the possibility of getting decloaked by teammates that think they are doing you a favor by tossing you a heal/buff. Or they do it on purpose (today a carrier healed me whilst I was at 100% ... I could have sworn he wanted to use me as bait).
Anyways ... if the guys at Cryptic want to make the cloak conditional on whether the buff/heal comes from the B'rel or a teammate, or if it affects just the B'rel or is directed at a teammate ... yeah, I can see this meaning to rework a lot of stuff in the code.
*: Basically the fear back then was that a B'rel could fly around perma-cloaked as an invisible healer - but given that this is a set of weapons completely remaining amiss in the battle I am still convinced such gameplay would only end up gimping the own team as it is essentially one player short. A single hull heal every ~30 sec isn't gonna change that.
Personally, I'd already be very content with just distinguishing whether the heal/buff is "leaving" or "approaching" the B'rel or if everything remains within the same hull. In case of the latter, decloak is neither necessary nor canonically viable. In case of the former I can at least understand why some people are concerned (see above) and that, technically, energy spikes travelling between a cloaked ship and another vessel can be tracked down and traced back.
And come to think of it, last January we were told that this was the problem. In the past 9 months, how much progress has been made on the issue?
And when do you think this will be resolved?
If tbd, why sell it in the c-store?
That is what I don't get. It isn't a new issue. They spent a bunch of time recently on the Rhode Island to insure those that purchased it got their money's worth, but the B'Rel hasn't been made a similar priority.
I quote this because it's absolutely true. I worked retail for nearly 20 years at various locations - all of which were built on the edict "the customer is always right" and I'm happy to be rid of it. Not because the various jobs sucked, but because of the customers with the over-active sense of entitlement.
I was fortunate to work at places that gave their employees the power to help the customer in any way, but one way we could never help them was by doing things "faster". Faster means quality goes out the window and more mistakes get missed.
So folks need to ask themselves:
Do we want it fixed now?
or
Do we want it fixed correctly?
There really is no middle ground on those two questions.
Anyhow...sorry for the rant. That's all just my opinion, and I accept the fact that I could be wrong. Regardless, thanks for reading.
I just saw the patch notes for this week. I guess this didn't make it in?
Many apologies for the delay.
digging through code to fix stuff like this must be a major drag, good luck over there
On a related note, how are the upgrades to the Pet Controls you guys have been working on? Throw me a bone as to a ballpark figure when those might be up on tribble?
Its ok. we're pretty much used to delays by now.
Yeah, after all this is the KDF side where things are delayed because of problems on the Fed side... I sure hope that is fixed with having new people come on-board...and soon......
After all I want my fingerless gloves, honor cloak, and hair options...dreads are sooooo not Klingon.....
I for one welcome the change to torpedo spread...once they (well, IF they) fix the problem to the BoP's... it should not be an issue....
Maybe they will get to it after they fix the bugs in the battle cloak that causes it to pop on most dialogues from your own bridge officers.
*docks Carrier into drydock, puts crew on a month long shore leave
Are you SERIOUS? They got WORSE?!?!
What about the BoP's?
havent tried cannons on carrier... as its mostly a beam build with mines.
But i have noticed BOP's not firing!!!!!
and its annoying when the BOP accounts for 33% of your DPS if your a beachfront carrier.
Carrier pets have finally received brain transplants.
W00t! JG man!
*Sends a barrel of bloodwine to heretic, and sings songs of his glory in the great hall of warriors!*
The carrier groups of the KDF thank you sir.
I actually only deserve the credit for bullying other people. It took two software engineers, two content designers and jheinig to actually figure out and correct the bloody issue.
Such a bizarre bug...
Ah, wow. Great teamwork then. Either way, I appreciate the speed at which is was fixed, having only brought the issue to light a few weeks ago. It'll be fun to hop back in the carrier.
Now I just have to eagerly await the arrival of the pet commands and all the other carrier goodies you've been teasing me with
Yep. That'll be the true test for the carrier's viability in high-end PvP...
Thank you so much and all the people you bullied ROFL
To my knowledge, that fix hasn't made it to live yet.