Ideas

freelancefox's avatar
freelancefox
Rising Novice
4 months ago
Status:
Fixed

Yesterday's Patch may have Pushed my Guild's ROTE planet Mustafar over 1 star

I've been playing detective all day today trying to verify if there's any other possibility... and unless one of my guild members is lying to me, there appears to be a bug with the way patches that fall during Territory Battles effect your deployed GP.

In phase 2 of this ROTE territory battle, my guild pushed Mustafar up to just below 1 star (within ~4,000) and left it there to continue with in phase 4. During phase 3, in the middle of the night around 5:30am, people began to notice that Mustafar was appearing as 1-starred and so two of them decided to go ahead and continue working on Mustafar by assigning a platoon member they had forgotten earlier, and then another person deployed around 3.6m GP. Just before that I had personally checked our TB progress before bed around 5am and another officer also looked between 4 and 5 am, so that we have near certainty that the game client was NOT showing that star as earned before.

Later in the morning, people began to notice the mistake but as officers started to go back into the logs to figure out what happened, there was no indication that the first star had ever been earned, and also no indication of a rogue action (the planet, we are 99.9% certain, was marked Prohibited at the time).

The only log entry before the ~20k platoon assignment is a deployment nearly 24 hours before that.

Obviously for future reference I need to also mention that yesterday's patch, which happened later in the day than usual, was the one that added Scorch and Tarkin's rework to the game.

My current leading theory, again assuming that my guild mate didn't just make a mistake, is that somehow the changes to Tarkin caused the Tarkins we had already Deployed on Mustafar to gain GP UNINTENTIONALLY, which is where the bug comes in. Normally the player's GP is snapshotted when they deploy to a zone in TB, but if this patch added new zetas and omicrons to an existing toon, I believe it would be possible for the patch to have unintentionally pushed my guild's Mustafar over the 1-star breakpoint—crucially, this is the only explanation I have come up with that explains why there's no log entry. We all refreshed our phone clients, checked the PC client, and as I already mentioned interviewed the guild members who were part of the incident, but with the information I have for you this is the only theory that makes sense. I'm guessing that when the 24-hour server cycle reset at 3am, the game server checked its schema for Tarkin, noticed the new zetas and omis added in the patch, and somehow was not coded with the intelligence to continue using the old version of Tarkin so that anyone who refreshed our ROTE after 3am was seeing the 1-star version, while my officers who checked after 3am most likely hadn't refreshed their clients and so saw the cached version where we still had <1 star.

 

Regarding the attached screenshot, the -13h18m deploy for 20,842 was the person who first discovered the 1-star around ~5:30 am EST, and the Tarkin patch was the previous day between that entry and the entry ~21 hours earlier. I cannot verify how many Tarkins we have on Mustafar but I'm pretty certain that one Zeta or Omi would account for the ~4,000ish gap we left (we definitely won't be cutting it that close in the future!).

 

2 Comments

  • Status changed:
    Troubleshooting
    to
    Reviewed

    It's possible that some logs might be missing due to the patch deploys. 

    We checked the data, but have not received any other reports related to TB issues. Studio hasn't noticed any issues in the current TB and our production testing shows it as working as intended. 

About SWGOH Bug Reports

Report bugs in Star Wars: Galaxy of Heroes and see what other players are talking about.Latest Activity: 43 minutes ago