Does anyone know whether the devs plan to still update the descended characters to be max Champed level at one point? I reread the release notes of 338, 339, and 340 and it’s very unclear to me.
it was released in 338. Right at launch, the notes mentioned a known bug “(Fixed in 339) Descendable Heroes do not use their max level in some circumstances”
After 339 hit, they are still only descended to max level before champing. There is this in the release notes: “Descended characters are no longer being set to minimum level for the required rarity” But they are? At least for me…
There is no mention of the feature in the 340 release notes. This makes me wonder the following:
Did I just read their plans wrong and they never intended to update it to be Max champed level for descended characters?
Did they just forget to work on this?
Is an update still coming?
What do those specific release notes I quoted actually mean?
If the feature will just stay as it is, it has no value to me. I will just keep using the same characters I had before this got released, who are all at their max level for the rarity that is required. But I still hope an update is coming.
Anyone have a clue? Also, I can’t be alone in this, that it doesn’t really change anything in the current format?
Is it really that much of an issue? We had DDQ for a full year before Championing existed. Max level characters can easily win these nodes. No need for them to be max champed outside of comfort.
Of course comfort is the entire reason they implemented this useless feature (that goes against the whole point of the game asking you to roster wideà, so one would indeed assume that if you’re gonna have descended characters they would be max champ versions.
The way it stands, descended character feature is only detrimental with clutter.
If they added a “Desended” filter in the drop down, we could uncheck it, and things are back to the way they were. I appreciate the fact that they are adding features that help new players with small rosters in DPD. This is pretty low on the list of things that need addressing however. Of course the character level sort order is still messed up.
Initially the descended were like the lowest level in the tier. So iirc any 3 was descended to level 40.
Now the 3s show up as 166. The problem is of course you’d want it to be 266 and it should be in the sense that any ascended copy has been 266 minimum (plus a 166).
There may be a problem with making the game deliver - even temporarily- a max level character as every time you get an ascended one from an offer or vault it’s the minimum level that the ascended one can be. So maybe it would be a lot of work to make them be 266 since the game doesn’t have that type of pre-built version already in code. .
I hope they can add some save team slots since that may be the simplest workaround to these problems.
Yeah, here’s a very specific example for why I’m hoping they fix it:
For the 2* DDQ, I used 1a2Spiderman, Headpool, and 1a2Yelena. In the past I’ve always kept a maxed version of these and then built any duplicates knowing I would not be touching these because they help me do those nodes quickly.
But NOW I have my 1a2Yelena at 144 AND a duplicate at 140. I also have a 1a4 at 370 and a 1a3 at 266, so if the descended characters would be done correctly at max (144), then I will bump my 1a2 duplicate to 144, then ascend and keep pumping covers into the new 1a3 until its max, etc.
BUT if they don’t fix this, then I need to roster TWO new Yelenas, and then ascend them to a 1a2, then bump her up to 144 and then ascend, just to keep a 144 1a2 rostered for my DDQ node.
Very complicated, but it’s the difference between saving 126 covers…
I’ve used Storm, Magneto, HE for the 2 node forever, and keep 144s of all 3 even when 2 farms were a thing. The node defaults back to that team every time at this point since they are the only 2* I use. I use May, Thanos, Vampire Jubilee for the 3 & 4 usually, but have to search for them most of the time.
It is a little annoying to find who you’re looking for, and might be less of a concern if we had more saved team slots. I was hopeful descended characters would let me try out a few more options since they have expanded the 2s a bit, but everything still feels so slow compared to what I’ve been using & I’m not sure if the rest really are that slow, or if it’s because they aren’t at the proper level when descended?
I know this thread is 2 months old, but had a new experience with descended characters on my roster today. I went into the 2* node for the Deadpool Daily, searched for widow as I’ve been using OBW & widow horse with Storm for a bit. This is what showed up. Oddly, I did the same thing late last night, so this happened in the span of about 8 hours.
I often see some similar things. I think it has to do with whether you ascended the character yourself or if any constituents of the character came preascended from deals/vaults.
I did just ascend 2 2* dupes to a 3 last night, and I don’t think I’ve pulled a pre-ascended version of her yet, so it would make sense that I have had that many total. Just odd that I’ve never seen it do that before. Hopefully we’ll get a better interface for them in the roster at some point.
How did it look before? I feel like mine has always looked like this. I actually waited for someone else to reply because I didn’t know what the problem was just from the picture. This is a genuine question, in case it isn’t coming across that way.
I also just did a filter by colour on the 3 star node today and it produced considerably more dupes than in the picture! I guess there are multiple things affecting whether dupes are displayed or not!
In all seriousness though, if the descended characters are going to continue being L94, L166 can we either get a filter for them, fix sorting by level or just turn the feature off? It’s literally only helpful on the 1 star node at the moment.
What i hate the most about it is that it’s no longer in max level order.
If the descended population has to be at lvl 166, fine, so be it, but why does that have to come before my lvl 266 characters? Put it back to level order and I won’t ever scroll far enough down to be inconvenienced by all the descended I don’t intend to use.
Alternatively, it would be great to have a filter, same way as “Has costume: Yes/No” we should have an “Is descended” filter. Would declutter the selection screens significantly.
