**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Comments
It’s not ideal, and will take some practice but that’s how I’ve been doing it.
Hate it
It's terrible, i preferred the way it was before, i
will stop doing Cavalier from now until they come with something different!
Also, you should be using 3-4 champs to clear the path so they spread out the cross fights and take more to the boss. You can have champs boosted by 150-150-150 or 150-150-75-75 then an extra champ for the boss who doesn’t fit the nodes.
Too much planning to do simple monthly content
Yes, kabam could’ve done better by using broader tags - as somebody earlier mentioned, villain, hero, size tags, etc. But I still see it as a positive step.
That is, until I got to the mercenaries nonsense. I hate that one single chapter with a passion.
This time they make me read a lot, after reading, feel tired to play, and forget what the first line said 😄
Interesting nodes and quite fun. I'm sure it'll get better. Something interesting every month if they keep it updated.
I'm talking about the cav difficulty. Taking on the boss with boosted champs is a plus , so is the fact that bosses aren't just +300% health but a combo of interesting nodes.
3.1 is total exaggeration and lack of ideas probably out of desperation.
Bad choice kabam, keep on doing this and all what is left is only you playing the game.
The tag-based nodes this month are different in a couple of ways, but most significant for this discussion is that the downside element of them seems to be more ignorable or easier to mitigate without a filtered champion. For example:
Energy Interference: Every 4 seconds the Attacker is inflicted with a Power Lock Passive for 6 seconds. If the Defender is inflicted with a Debuff this timer is reset.
The number of champions outside the filter that can turn this off by landing debuffs is quite large. Or:
Robust Rivalry: Whenever the Attacker does not have any Buffs applied to them, the Defender passively Regenerates 1% of their Max Health every second.
Not only are there a lot of champs that can turn this off, you could even argue that the way the filter champs do is harder to execute than just bringing an attacker with a lot of intrinsic buffs.
In general, the penalty for not having the filtered champions is low, much lower than I think it generally is with the Class based nodes. But there tends to be noticeable penalties for not bringing members of the Class with the class based nodes, at least to a much higher degree than the tag based nodes.
I described this as a case between players "having" or "not having" the champions targeted by the nodes, but that's an oversimplification that masks the non-binary nature of what challenge the nodes pose. For most players, it is not enough to have "a champion" that fits the node. One champion will do better than none, but one champion will not likely solo the entire path. For most players, two is better than one, and three is better than two. The larger the filter is, the more likely it is that most players will have more of those champions to bring. The smaller the filter is, the more likely it is that most players will have fewer of those champions to bring. If we make the filters larger, we are in essence allowing players to bring a stronger roster on average. We then can - and in fact must - make the difficulty of the content higher to counterbalance this, by making the penalty when you're not using those champions higher. Across the entire playerbase this will average out: some players (those with more developed rosters) will have a much easier time, and those with less developed rosters will have a much harder time. Which is another way of saying there's a reward for developing rosters beyond ranking up a couple strong champions. That's one goal of the Cav nodes.
The converse is also true. If the filters are smaller and players are less likely to possess and have ranked up the champions in the tags, then players will be bringing fewer of them to the content. On average they will be getting less of the Cav node benefits, which is another way of saying on average players will be bringing less strong teams to the content. So the content has to be balanced around that: with teams that are closer together on average and less strong (less benefiting from the nodes) on average. That makes the content's base line difficulty generally lower and the penalty for not having the filtered champs closer to zero.
3.1 sucked as a node forcing you to reparry but ai goes mh 90% of the time is terrible, but mascre spamming sp1 for those bleeds was so satisfying seeing the damage he could get upto.
3.2 was the funniest if it didn't give glaive a charge I used maw. It was so good seeing how good he could be just with some raised attack.
The others were ok falcon on the avengers one was so good though. Or sparkles on the aforce one, nothing like binary and give her even higher attack.
The concept is solid as you can use off tags and get it done reasonably fast where as the class ones took forever if you didn't have that class specific counter.
I wouldn't mind this staying at all but never repeat 3.1 in future content would be welcome for sure.
If it is the Epic difficulty, that’s good to see a return to the usual level.
Not happy with Epic, do the others.
Instead we got THIS, whatever this is... but definitely not something to enjoy the game.
Kabam finally listens to the Voice of the People!!!!
Not sure why they’ve decided to bring it back.