# The Big Enchilada saved team bug

**URL:** <https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889>\
**Category:** MPQ Bugs and Technical Issues\
**Created:** [September 13, 2025, 4:00am UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889 "2025-09-13T04:00:54Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![axmoss](https://sea1.discourse-cdn.com/flex023/user_avatar/forums.505go.com/axmoss/32/3121_2.png) [@axmoss](https://forums.505go.com/u/axmoss)\
**Post date:** [September 13, 2025, 4:00am UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/1 "2025-09-13T04:00:54Z")

</div>

In the Big Enchilada node, my saved team #1 has a locked strang3.

 ![image.jpg](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/2X/4/49a6b74cf3fe0459c8a7f282b1f342dd04846d27.jpeg)

But if I search for ‘strange’ in the roster select, he’s available?

 ![image.jpg](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/2X/2/239abeeff8c1b27d9c68d70250802b1a26fd2a08.jpeg)

Is it just Strange being saved the error/bug?

**Edit** fixed in r330 update.  
**re-edit: it’s not fixed.**

---

<div class="post-metadata">

**Author:** ![Kalidor](https://avatars.discourse-cdn.com/v4/letter/k/3ec8ea/32.png) [@Kalidor](https://forums.505go.com/u/Kalidor)\
**Post date:** [September 18, 2025, 11:52am UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/2 "2025-09-18T11:52:29Z")

</div>

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.

 ![image.jpg](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/2X/1/1b6926627861bad572a7ae6fd7463958b941cb67.jpeg)

---

<div class="post-metadata">

**Author:** ![KGB](https://avatars.discourse-cdn.com/v4/letter/k/74df32/32.png) [@KGB](https://forums.505go.com/u/KGB)\
**Post date:** [September 18, 2025, 1:05pm UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/3 "2025-09-18T13:05:27Z")

</div>

@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

---

<div class="post-metadata">

**Author:** ![axmoss](https://sea1.discourse-cdn.com/flex023/user_avatar/forums.505go.com/axmoss/32/3121_2.png) [@axmoss](https://forums.505go.com/u/axmoss)\
**Post date:** [September 19, 2025, 9:31am UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/4 "2025-09-19T09:31:07Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![axmoss](https://sea1.discourse-cdn.com/flex023/user_avatar/forums.505go.com/axmoss/32/3121_2.png) [@axmoss](https://forums.505go.com/u/axmoss)\
**Post date:** [September 19, 2025, 9:51am UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/5 "2025-09-19T09:51:26Z")

</div>

Looks like it’s fixed with the updated version. @Kalidor check to confirm it’s fixed for you too.

---

<div class="post-metadata">

**Author:** ![Krazy](https://sea1.discourse-cdn.com/flex023/user_avatar/forums.505go.com/krazy/32/4516_2.png) [@Krazy](https://forums.505go.com/u/Krazy)\
**Post date:** [September 21, 2025, 7:07pm UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/6 "2025-09-21T19:07:52Z")

</div>

It is **NOT** fixed in 330

Step 1) select The Big Enchilada

 ![image.jpg](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/2X/e/eab0309798727f2ebc173e853cd7174d54bdeb02.jpeg)

Step 2)  
Pick a favorite/saved team of all 1\* characters that have ascended duplicates.

 ![image.png](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/2X/3/3491bd408ee31b930ce18a8fd0c390a309d3ccfa.png)

Video:  
 ![image.gif](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/1X/37b9d3f47525a5cf3e35c2bd7378bd3322d096b2.gif)

---

<div class="post-metadata">

**Author:** ![axmoss](https://sea1.discourse-cdn.com/flex023/user_avatar/forums.505go.com/axmoss/32/3121_2.png) [@axmoss](https://forums.505go.com/u/axmoss)\
**Post date:** [September 23, 2025, 8:17pm UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/7 "2025-09-23T20:17:24Z")

</div>

i stand corrected

---

<div class="post-metadata">

**Author:** ![axmoss](https://sea1.discourse-cdn.com/flex023/user_avatar/forums.505go.com/axmoss/32/3121_2.png) [@axmoss](https://forums.505go.com/u/axmoss)\
**Post date:** [September 29, 2025, 6:29am UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/8 "2025-09-29T06:29:12Z")

</div>

It’s now showing up on pve events.  
Saved team not allowed.

 ![image.jpg](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/1X/242e2273e32396b049a85ea1ba44413799fdd7b0.jpeg)

Locked char available.

 ![image.jpg](https://us1.discourse-cdn.com/flex023/uploads/x505go/original/2X/b/bb45986e7bedf1ad755cbb1f8761d4a5d72d5667.jpeg)

---

<div class="post-metadata">

**Author:** ![Kalidor](https://avatars.discourse-cdn.com/v4/letter/k/3ec8ea/32.png) [@Kalidor](https://forums.505go.com/u/Kalidor)\
**Post date:** [October 1, 2025, 8:48pm UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/9 "2025-10-01T20:48:07Z")

</div>

> [@KGB](#):
>
> @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

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

---

<div class="post-metadata">

**Author:** ![Kalidor](https://avatars.discourse-cdn.com/v4/letter/k/3ec8ea/32.png) [@Kalidor](https://forums.505go.com/u/Kalidor)\
**Post date:** [October 1, 2025, 8:49pm UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/10 "2025-10-01T20:49:52Z")

</div>

> [@axmoss](#):
>
> Looks like it’s fixed with the updated version. @Kalidor check to confirm it’s fixed for you too.

I’m up to date on the latest version but I still have the issue

---

<div class="post-metadata">

**Author:** ![Kalidor](https://avatars.discourse-cdn.com/v4/letter/k/3ec8ea/32.png) [@Kalidor](https://forums.505go.com/u/Kalidor)\
**Post date:** [October 2, 2025, 7:24pm UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/11 "2025-10-02T19:24:46Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![axmoss](https://sea1.discourse-cdn.com/flex023/user_avatar/forums.505go.com/axmoss/32/3121_2.png) [@axmoss](https://forums.505go.com/u/axmoss)\
**Post date:** [October 2, 2025, 10:54pm UTC](https://forums.505go.com/t/the-big-enchilada-saved-team-bug/62889/12 "2025-10-02T22:54:56Z")

</div>

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.
