DS Geo TB Phase 2 Bug Fix is Too Late

"DarjeloSalas;c-2291028" wrote:

"nottenst;d-248516" wrote:
With barely 4 hours left in Phase 2 of the DS Geo TB, I can confidently say that any bug fix for this fleet requirement problem is going to be too late to do any good for many, if not most, guilds.

They should have immediately rolled back the changes that produced the bug once they heard of it. If they had incorporated that rollback in yesterday's update then there would have been time to recover from the mistake. Then they could work on making the changes correctly for next month's DS Geo TB.

As it is we only heard "We will investigate a fix as soon as possible" and nothing further. The poor communication continues.

I am beyond certain that “the changes that produced the bug” was the addition of Executor to the game.

How well do you think a rollback would have been received if it removed that ship in the process?

What baffles me is how they are continue to be so inept. It's not even the first time adding a new capital ship caused issues with mission requirements in TB, so you'd think it would be on a checklist. It is super hilarious how they can mess up the simplest of things though.

Bottom line: this bug reinforced the fact that CG is terrible at coding and doesn’t care about their customers or how they feel about anything.

https://forums.galaxy-of-heroes.starwars.ea.com/discussion/248671/geonosis-territory-battle-phase-2-fleet-issue-update#latest

I'll give back a star for 500 crystals.

Yeah, from the start I was extremely doubtful that any fix was going to happen "in time". It's definitely going to cost us a star. Hardly a tragedy, I know, but annoying nevertheless. I just wonder if there's going to be any sort of compensation. Time to happily anticipate 3 more CWC shards?

"DarjeloSalas;c-2291028" wrote:

I am beyond certain that “the changes that produced the bug” was the addition of Executor to the game.

How well do you think a rollback would have been received if it removed that ship in the process?

I think it would have been well received by the vast majority of players. It is only the few players that rushed out to get the Executor to 6* or 7* that would be upset. They are vocal, but I think they should have understood the situation.

Really annoyed by this. We are currently on 20, about to close off 21. But we should be about to close off 22.

Luckily my guild is not losing crystals because of it, many will.

But that better gear box at 22 means a lot to us. We push and push to get it.

"DarjeloSalas;c-2291028" wrote:

"nottenst;d-248516" wrote:
With barely 4 hours left in Phase 2 of the DS Geo TB, I can confidently say that any bug fix for this fleet requirement problem is going to be too late to do any good for many, if not most, guilds.

They should have immediately rolled back the changes that produced the bug once they heard of it. If they had incorporated that rollback in yesterday's update then there would have been time to recover from the mistake. Then they could work on making the changes correctly for next month's DS Geo TB.

As it is we only heard "We will investigate a fix as soon as possible" and nothing further. The poor communication continues.

I am beyond certain that “the changes that produced the bug” was the addition of Executor to the game.

How well do you think a rollback would have been received if it removed that ship in the process?

Key word: "if"
I'm sure there are ways to fix the bug that don't involve removing Executor. However, I doubt CG would touch/fix an ongoing TB.

"nottenst;c-2291041" wrote:

"DarjeloSalas;c-2291028" wrote:

I am beyond certain that “the changes that produced the bug” was the addition of Executor to the game.

How well do you think a rollback would have been received if it removed that ship in the process?

I think it would have been well received by the vast majority of players. It is only the few players that rushed out to get the Executor to 6* or 7* that would be upset. They are vocal, but I think they should have understood the situation.

You think those that got Executor would have understood? How many guilds did this actually affect stars for? You can 3* that territory with only doing the Executrix battle, which is worth more points anyway. Then there are those that didn't have the ship gp to get the 3rd star even if they could do both. So there is this sweet spot of guilds where there are enough people to do both missions to barely make up for people who can't do either given how low overall ship gp is. I think more people would be upset over Executor getting kicked out than missed a star in that zone.

I misspoke, it was the Chimaera battle that was hit. Same principle, though.

Our guild missed that star because we couldn't do a second battle. @Crayons appears to have missed out as well. I think the number of guilds that had enough members with the Executor to do both battles is much less than the number who could have got 3 stars by doing both battles and couldn't because of the bug. Those guilds who had enough members with the Executor probably had high enough GP that it really was irrelevant.

So, they wouldn't be able to use the new toy in Phase 2? So, what? We haven't ever been able to use Malevolence in that phase. I bet there were few if any players who obtained the Executor who couldn't win that combat mission with Chimaera and also the Executrix mission.