In the Big Enchilada node, my saved team #1 has a locked strang3.
But if I search for ‘strange’ in the roster select, he’s available?
Is it just Strange being saved the error/bug?
Edit fixed in r330 update.
re-edit: it’s not fixed.
I have the same issue with this node in DDQ. My 3*KK seems to be locked, but if I manually select the same team, it works.
@Kalidor - Do you also have an ascended Kamala Kahn?
I wonder if the bug is that saved teams by default always selects the highest level character when you have duplicates. It may be getting messed up with ascended characters especially if the ascended character isn’t allowed for that node because of level restrictions.
KGB
@KGB it’s the big enchilada node, you can use any character, ascended or not. I have Thanos ascended too, but he’s not locked in that team.
Looks like it’s fixed with the updated version. @Kalidor check to confirm it’s fixed for you too.
It is NOT fixed in 330
Step 1) select The Big Enchilada
Step 2)
Pick a favorite/saved team of all 1* characters that have ascended duplicates.
Video:
i stand corrected
Hey KGB. Apologies for the delay replying.
Yes, I do have an ascended 4*Kamala Kahn. Thanks for your insight. I’ll create a team with a character that I have 4a3 cover in and test it
I’m up to date on the latest version but I still have the issue
Just to update on the test… I created a team of 3* characters where I have an ascended cover for each (4a3), but the team selection worked. This bug seems to affect only 3* KK for me
the bug seems to have crept out of just ddq. in one of my images, which the forums resized to be absolutely small, shows that it has leaked into pve nodes too.