Another bug in the Malak „solution“?

lol Kyno deserves a medal for dealing with all this nonsense. double his paycheck I say!

Sounds like another exploit being taken advantage of..we need reconciliation on this too.

"Nikoms565;c-1993345" wrote:

"Kyno;c-1993304" wrote:

"Nikoms565;c-1993299" wrote:

"Kyno;c-1993154" wrote:

"Nikoms565;c-1993145" wrote:

"Noxfire27;c-1993099" wrote:

"Kyno;c-1993095" wrote:

"Gilgasmash;c-1993056" wrote:
Don't let this thread die, as this is a huge problem in the game now: Players, who shouldn`t be able to equip 6*-mods, have an advantage at the moment (up to +7 speed, higher offense/defense-stats and so on). Also, some players still have g12-gear, whereas their Malak's only a 6*. This has to be fixed immediately.

The mods are stated to be intended, probably the same for the gear.

Just because they say it’s „intended“ doesn’t mean it’s somewhere fair And/or a good solution. its just not right. And leaves a very bad taste after this huge Malak mess.

Let's be honest - in this case, "intended" just means they don't know how to fix it. They certainly didn't say " How about we let bugged Malaks keep 6* mods". "Intended" is just spin to cover ineptitude. It was never intended. As far as I'm concerned, we don't need more communication if it's going to be dishonest drivel like that.

That's not true, but I know I'm not going to convince anyone of that. The reason is far simpler than that.

Kyno
Care to elaborate? If it's simple, then by all means, explain. Or have you also been reduced to vague, non-committal "communication" as well?

They know how to fix it, it is that simple. They didnt due to the work involved and the idea that they wanted to touch our rosters as little as possible.

It would have created way more "work" to get things back to actual square 1 (before the event) and would have created more issues to do this. They knew (I believe they knew from how they talk about it) this would be the final state of things.

The point of me being vague is that I don't expect anyone to care, as apparently any communication on this matter has been reduced to "dishonest drivel".

So, if I am understanding you correctly, the resulted 6* mods staying on Malak was not necessarily the intent, but due to the amount of work it would take (especially given the short amount of time before GAC lock) and the possible issues it would create, was simply a consequence that had to be accepted.

Incidentally, your point and take on it is completely believable - and not at all "intended" as Crumb seemed to indicate.

Nice strawman by you on the "dishonest drivel" comment dig by you by the way. If you're going to quote me, at least keep it in context. You're better than that.

I think the most telling thing about all this is that 6* mods remaining on 5/6* malaks and G12 gear remaining on 5/6* malaks would be an identifiable issue within 10 minutes of any meeting CG would have had about the roll back.

It is something that should have been mentioned in the first or second communication on the matter. It was not and that’s just more evidence of just how inept this shop is.

"AnnerDoon;c-1993363" wrote:
So... they know how to fix it, but chose not to because it was too inconvenient for them.

I must say, the disdain for the players that this describes seems much worse than simple incompetence.

Based on the information available, which admittedly does not paint a complete picture, they chose not because it would be too inconvenient for many players due to the ongoing GAC. Not because it "was too inconvenient for them."

It's fair to say that CG created this situation (6E mods and 7 star gear on 6 star Malaks) because they rushed the rollback. There are many things they could have done to execute this better (including leaving things as they were and not rolling back) but to imply that they chose something out of "disdain for the players" seems like a baseless accusation.

"AnnerDoon;c-1993363" wrote:
So... they know how to fix it, but chose not to because it was too inconvenient for them.

I must say, the disdain for the players that this describes seems much worse than simple incompetence.

If the fix takes a year to develop does it even matter that point? In the end it doesn't matter, they made a decision based on whatever process they have that worked best for them and the community. It will hopefully lead to a review of their processes and communication for future issues to be better prepared, but it is what it is. They probably would have been better off acting immediately and rolling the db back and losing 12 hours of progress for everyone, but they chose to wait to decide on a solution and that was no longer an option.

They should’ve just owned up to the mistake. CG should’ve left the event, left the extra shards and made good with 7* Malak owners prior to the event. That way gear pieces and 6E mods wouldn’t unfairly be left on a G11 character...

Those gear pieces and mods matter in the PvP environment. They could add speed, health, etc., that could prove pivotal in an RNG match. What if those mods add just enough offense for a higher damage hit? What if the health/ defense is higher making the opponent hit for less damage?

This shows me that they were only worried about how player obtain Malaks shards. Behind a currency that requires tedious TBs to complete and through many Sith Raids and TW’s (which now guilds with Gear11 6E mods will go up against guilds without those...)

They aren’t worried about the integrity of the game. They messed up big time and simultaneously screwed over players that didn’t take part in the bug, and didn’t slap on Mods or extra gear. They created a bigger mess by trying to undo THEIR mess up. It’s like they spilled milk, then mopped up with a dirty mop.

"Myriddan;c-1993359" wrote:

"Eweff;c-1993343" wrote:

"Myriddan;c-1993321" wrote:

"Eweff;c-1993316" wrote:

"Kyno;c-1993304" wrote:

"Nikoms565;c-1993299" wrote:

"Kyno;c-1993154" wrote:

"Nikoms565;c-1993145" wrote:

"Noxfire27;c-1993099" wrote:

"Kyno;c-1993095" wrote:

"Gilgasmash;c-1993056" wrote:
Don't let this thread die, as this is a huge problem in the game now: Players, who shouldn`t be able to equip 6*-mods, have an advantage at the moment (up to +7 speed, higher offense/defense-stats and so on). Also, some players still have g12-gear, whereas their Malak's only a 6*. This has to be fixed immediately.

The mods are stated to be intended, probably the same for the gear.

Just because they say it’s „intended“ doesn’t mean it’s somewhere fair And/or a good solution. its just not right. And leaves a very bad taste after this huge Malak mess.

Let's be honest - in this case, "intended" just means they don't know how to fix it. They certainly didn't say " How about we let bugged Malaks keep 6* mods". "Intended" is just spin to cover ineptitude. It was never intended. As far as I'm concerned, we don't need more communication if it's going to be dishonest drivel like that.

That's not true, but I know I'm not going to convince anyone of that. The reason is far simpler than that.

Kyno
Care to elaborate? If it's simple, then by all means, explain. Or have you also been reduced to vague, non-committal "communication" as well?

They know how to fix it, it is that simple. They didnt due to the work involved and the idea that they wanted to touch our rosters as little as possible.

It would have created way more "work" to get things back to actual square 1 (before the event) and would have created more issues to do this. They knew (I believe they knew from how they talk about it) this would be the final state of things.

The point of me being vague is that I don't expect anyone to care, as apparently any communication on this matter has been reduced to "dishonest drivel".

The other poster said “they don’t know how to fix it” not “they don’t know how to remove the mods”. You just stated that they don’t know how to fix it without causing more issues. If your “fix” creates more issues regarding the subject you are trying to “fix” then you aren’t “fixing” anything. So no, they don’t know “how to fix it”

Or likely the fix is to roll the entire db back to the day before the event and destroy all progress from then until now. Sometimes the real fix is not worth pursuing. Just because they can fix it doesn't mean they should from a time or cost perspective

I guess we just have a different understanding of what “knowing how to fix it” means

That would be the easiest fix and not possible. The true "fix" to get everyone to the right gear and mods etc, probably is not possible in an automated way unless they build something new, and the time/ cost of doing so for a one off issue is not worth it.

One off issue? You're optimistic.

"AnnerDoon;c-1993404" wrote:

"jhbuchholz;c-1993376" wrote:

"AnnerDoon;c-1993363" wrote:
So... they know how to fix it, but chose not to because it was too inconvenient for them.

I must say, the disdain for the players that this describes seems much worse than simple incompetence.

Based on the information available, which admittedly does not paint a complete picture, they chose not because it would be too inconvenient for many players due to the ongoing GAC. Not because it "was too inconvenient for them."

According to CG's mouthpiece on the forum, that's simply not true.

"Kyno;c-1993304" wrote:
They know how to fix it, it is that simple. They didnt due to the work involved and the idea that they wanted to touch our rosters as little as possible.

You put the emphasis on the wrong part of the quote:

"Kyno;c-1993304" wrote:
They know how to fix it, it is that simple. They didnt due to the work involved and the idea that they wanted to touch our rosters as little as possible.

That supports the idea that a long complicated rollback could be a major inconvenience to players involved.

But now we're parsing words from a guy who heard from a guy who heard from a guy... pretty pointless.

This is like saying that I know how to fix a flat tire on my car but I won’t since it would result in the car catching on fire.

"Gifafi;c-1993364" wrote:
lol Kyno deserves a medal for dealing with all this nonsense. double his paycheck I say!

2 x 0 is still 0.... lol