C-3PO Nerf

here you go again.. smh..
Just out of curiosity. what is the difference between "what's" and "what is"?

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What do you mean? " the clear implication was that they rushed that out the first time and it didnt workout..."

Are you referring to the nightsister fix?

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What is my conclusion? What doesn't make sense? The fact that I'm trying to get more info?

My guild has a specific order to follow on the P3:

1 - People without C3PO, anyone.
2 - People with C3PO that cannot SOLO.
3 - People with C3PO that can SOLO.

When the C3PO came up, they made the P3 basically solo.
But right after this the guys just asked to go first with other teams, not for rewards, but they would like to be prepared to the NERF (not fix). And everybody agreed with this.

To us was amazing the possibility to start farm Traya and keep working in many other teams to make it faster.
I hope they never apply this NERF (not fix), it's just a thing that each guild can handle under their own rules.

"Ninjah9;c-1769776" wrote:

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What do you mean? " the clear implication was that they rushed that out the first time and it didnt workout..."

Are you referring to the nightsister fix?

Yes. They rushed out the first NS fix. They are trying to avoid making the same mistake.

"Ninjah9;c-1769782" wrote:

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What is my conclusion? What doesn't make sense? The fact that I'm trying to get more info?

The conclusion that because the NS fix was rolled out faster, that must mean there is cause for concern about whether they intend to fix this issue at all.

You trying to get more info is not a conclusion. But I seriously don’t understand what more you want here. Kyno told you they are still working on it. There was a dev post on reddit saying they are still working on it. I think you can reasonably conclude that yes, in fact, they are still working on it.

I

"Liath;c-1769792" wrote:

"Ninjah9;c-1769776" wrote:

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What do you mean? " the clear implication was that they rushed that out the first time and it didnt workout..."

Are you referring to the nightsister fix?

Yes. They rushed out the first NS fix. They are trying to avoid making the same mistake.

"Ninjah9;c-1769782" wrote:

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What is my conclusion? What doesn't make sense? The fact that I'm trying to get more info?

The conclusion that because the NS fix was rolled out faster, that must mean there is cause for concern about whether they intend to fix this issue at all.

You trying to get more info is not a conclusion. But I seriously don’t understand what more you want here. Kyno told you they are still working on it. There was a dev post on reddit saying they are still working on it. I think you can reasonably conclude that yes, in fact, they are still working on it.

I dont remember the ns fix being botched? I remember everything being resolved pretty quickly. @Kyno said he hadn't heard anything since the first attempt to fix it, that was about a month ago. And I dont follow reddit, when was that post made? There's nothing wrong with trying to get more info as soon as possible, since this change greatly impacts my farming strategy. Plus this seems like a very simple fix, all you have to do is make it so traya stacks tenacity while toppled, boom problem solved. Since it's been so long, it's a legitimate concern that they might just leave it the way it is. There are players on this board who believe that's what's going to happen. And if that's the case I would have to make it a priority to farm the ewoks (which I hate) if I ever want to place high in the hstr again. So there is a legitimate concern. So if you think that they are guranteed going to fix it, then that's great for you. But the fact of the matter is no one as of right now knows for sure. So I dont get why it seems to be so offensive to some of you that I try to find answers???

It's not offensive, it's just because you look like a whining child when answering others.

See your last leef reply and then read your last post btw.

"Ninjah9;c-1769444" wrote:

"Firebrigade;c-1769001" wrote:

"Ninjah9;c-1768923" wrote:


Kyno: If there is anyway you could get more info on this, please feel free to share before this discussion is completey overrun by troll nation. Thank you ?

You’ve asked him specifically multiple times now and he keeps giving you the same answer. Take the hint. We all know everything there is to know right now. When the devs have a workable solution they will share it.

In the meantime, it’s not a glitch, it’s a mechanic the devs aren’t happy with. It is WAI, just used better than they thought it would be, hence the proposed solution is a “nerf” and not a “bug fix”.

Also, calling it an infinite loop is not completely accurate. It is near-infinite, but there are still opportunities for it to fail based on probability. This is different than the critolyte mechanic because there was no opportunity for that to fail once it started.

And the people in this topic are not trolling. Just because they disagree with you doesn’t make them a troll.

@Firebrigade: I was asking if he finds anything MORE to please share. In the past he has been able to communicate directly with people at CG to clarify things.

And for trolling I'm not talking about those that disagree with me. I'm referring to those who are attacking me personally, rather than discussing the topic. Saying that I'm "whining", or I'm lying, or the problem is not the infinite loop; it's that I cant communicate with my guild properly??? That's trolling. And whether it's a bug, nerf, broken mechanic, or whatever is irrelevant; and just you knit picking about minor details. If a player can rack up the highest score in the hardest raid, literally with his/her eyes closed; then something is broken, and needs to be fixed.

And if you actually read the previous comments instead of knit picking mine, you'd see that there is a debate to be had about whether or not CG will actually fix this.

He gave you everything he had and said there was nothing more. He’d already asked. You wanted him to ask again because you didn’t like the answer. This smacks of sense of entitlement.

You’re perceiving people who disagree with you as attacking you. Nobody here is trying to troll you. People are raising valid points about things like communication within your guild, and because they’re not the answer you want to hear you’re calling them trolls.

And whether it's a bug, nerf, broken mechanic, or whatever is irrelevant; and just you knit picking about minor details.

Simply not true. Bugs and broken mechanics are very different than something working as designed with unintended consequences, particularly in terms of the expectation for time to resolution. In IT parlance, one is a breakfix while the other is an enhancement.

If a player can rack up the highest score in the hardest raid, literally with his/her eyes closed; then something is broken, and needs to be fixed.

Also not true. Being able to solo on auto has become true for both other raids at some point in time. The only question here, in this case, is whether now is an acceptable time. Whether it’s allowable isn’t really part of the discussion as there is precedent.

Beyond that, we’re not even talking about a full raid solo, we’re talking about a single phase. This would be like getting upset that Thrawn allowed you to solo the p1 pigs in Rancor. It seems to come down to you being upset because someone has a better roster than you for this particular phase of the raid.

And if you actually read the previous comments instead of knit picking mine, you'd see that there is a debate to be had about whether or not CG will actually fix this.

Once again, just because you don’t like the points I’m raising, it doesn’t invalidate them or make them knit picking.

Ultimately it’s up to CG whether they think it’s the right time to be able to solo a single phase of the Sith Raid. Personally, I’m fine with it as is, but would also understand if this mechanic were changed. Something has to give eventually to make the raid less time consuming so we can enjoy other content.

"Ninjah9;c-1769806" wrote:
I

"Liath;c-1769792" wrote:

"Ninjah9;c-1769776" wrote:

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What do you mean? " the clear implication was that they rushed that out the first time and it didnt workout..."

Are you referring to the nightsister fix?

Yes. They rushed out the first NS fix. They are trying to avoid making the same mistake.

"Ninjah9;c-1769782" wrote:

"Liath;c-1769760" wrote:

"Ninjah9;c-1769446" wrote:

"InRevanWeTrust;c-1768993" wrote:
I doubt it will get fixed

They fixed the NS acolyte loop with traya like that SAME week. I assume there's a raid around the corner and the suckers that didn't pay2win for c3p0 are being punished for not buying in.

This is exactly why im concerned. That fix was way more complicated, and was rolled out way faster. I really have no idea at this point if they even are going to fix this, hence why I'm trying to get more info.

They specifically said they didn’t want to rush this one. The clear implication was that they rushed that out the first time and it didn’t work out well and they are trying to avoid that situation here by taking their time and fully testing things. So your conclusion makes no sense.

What is my conclusion? What doesn't make sense? The fact that I'm trying to get more info?

The conclusion that because the NS fix was rolled out faster, that must mean there is cause for concern about whether they intend to fix this issue at all.

You trying to get more info is not a conclusion. But I seriously don’t understand what more you want here. Kyno told you they are still working on it. There was a dev post on reddit saying they are still working on it. I think you can reasonably conclude that yes, in fact, they are still working on it.

I dont remember the ns fix being botched? I remember everything being resolved pretty quickly.

The first NS fix was definitely botched. They broke BOW (could no longer fully heal after hitting 20 stacks, even once they were cleared), and did it on a Friday afternoon on their way out of the office so we had to sit with it all weekend.

They then came back with the change to Acolyte and “promised” that the change would have no impact to other game modes, when in fact it reduced her arena viability considerably.

That’s the reason they’re taking their time on this (that they’ve stated at least).

"Ninjah9;c-1769701" wrote:
Cool with me. I'm trying to have a real discussion here, but @leef seems pretty intent on bickering. @EA_Rtas : I'm sorry it took this to get the attention of a dev. I would really appreciate it if you could possibly help to clarify what the situation is with c3po, and the hstr? It hasn't been mentioned for a while. Some believe it will not getting fixed ever , while others say the devs are waiting until the next 3po event date to make any changes...

I'm not actually a Dev unfortunately so I don't have any answers for you, I'm a moderator so I'm here to make sure the forums are a safe and constructive place. I just popped in to make sure the conversation stayed constructive and polite.

On that point I do wish to re-iterate we keep this discussion polite, theres a lot of posts in here which are bordering on hostile. Tone these down please or I might have to lock the thread if we can't be civil.