Is this just another on the list of “oops, we didn’t think about the timing of the saga switch being mid-war” or “we didn’t notice we coded for ‘current saga’ and not specifically for the the previous saga tags until it was too late” or was this intentional but not communicated?
All three are bad and whichever one it was should be fixed by an internal process change going forward. Some explanation would be nice along with either a commitment to a fix to avoid it in the future or confirmation that it was the plan all along and they thought it was fun to induce some extra chaos to the season.
How much affected are the DEFENDERS having their Saga removed ? (Just asking, don't know) Attackers at least can easily be changed every war (and may be anyways because of different defenders you'd face).
Aspect of joining with your Saga Attacker, but not actually doing (or finishing) your fight until after getting the Update and losing Saga probably hurts more, but affected less people because timing of your fight was at least more in our control.
Only realistic thing regarding monthly updates would be to shut down the game for 1-2 days each month, have ALL events, seasons, etc, END beforehand, and then all new seasons startup after the new update. But sort of unrealistic, (BG, AW, Incursion, AQ, all have different start/end ranges).
If game is just switching to a new Saga set of champs, would sort of be a letdown to not be able to use them for 3 of the 4 weeks worth of remaining AW this month, just because AW started a week before the Saga Change. (Similar, would it be fair to only start new Saga early for just AW, but not other stuff ?)
If a new monthly champ becomes available in the middle of AW season, and someone uses them (as attacker or defender, or even in BG season deck) starting in middle of Season, would you say new champs could not be used then, would have to wait until a new starting point ? No. (OK, very different, but still you can see the monthly changes and what is a result)
Events could more specifically callout WHICH Saga set would get the benefit (by Saga Names), instead of just saying Saga. But then the Saga Filter button should really have 2 different Saga Filter buttons (on main pre-filter tab, not inside where you can indeed select specific Sagas) “Ending Saga” vs “New Saga” Filter Buttons. But again would start to get confusing, and also not have a dedicated Saga apply to everything at once.
So, shut down everything for 1-2 days every new month, while the App Stores make the update available and let everyone have time to download it. Not letting anyone do anything inbetween a HARD END/START to things, Or run into these cross-month issues to one degree or another every month.
Do you understand what it means to use random champs that have new saga tag without any idea about their performance with vigor boost and their interaction with the nodes? There is 0 chance for testing. We've played 6 off season wars + 3 season wars with 1 saga pool and now it's gonna be all new stuff. Like what's the thinking behind all this?
I talked with the big league teams. They are going with the new Saga pool.
Shameless guys at kabam couldn't even bother to comment.
yup we are all trying to find a way to implement the new saga champs, although it is hard bc of how few good ones there is. its just wild they did this mid sszn
Comments
All three are bad and whichever one it was should be fixed by an internal process change going forward. Some explanation would be nice along with either a commitment to a fix to avoid it in the future or confirmation that it was the plan all along and they thought it was fun to induce some extra chaos to the season.
Some logical people are in this thread.
Abandon the other one.
I am not looking for anything else at this point.
Attackers changed mid war, planning went into the bin with surprise timeouts.