Otherwise, this whole "buff experiments" with tags are attracting more critics than approval.
That's because people aren't even reading the post. All they read is "tags" and then jump on the bandwagon. You now have:
-A way more diverse pool of champions benefitting the nodes with an entire class and sometimes some decently sized tags such as #Avengers or #Symbiote or #Spider-Man.
-If tags work the same as last time, you will be able to gain massive attack bonuses for boss fights making them easier.
Not to mention you aren't even forced to use these champions and champions like CGR and Herc are regularly used to run through content.
Now tell me where people have deciphered "cav difficulty is going to become harder" from? We don't know any nodes yet and if previous cav eq quests are to be gone by, well, they aren't going to much (probably any) headache for anyone with a half decent roster.
The only worry is if the tasks are too bothersome to complete for the benefits but as we haven't seen it in practise yet, we can't judge that and anyways, people are too focused on the words "tags" and "cavalier even quest update" to even notice.
Cav EQ 1.1 is tech, but I thought that wasn't available until April?
Edit: Post wasn't clear -- I thought that all cav eq nodes would be the new ones, but they are every other, starting with 1.2 and Mystic+. 1.1 is still the old Tech.
Why do you guys keep on switching it up like this, it was better last month this Cav difficulty is badly designed just have it like the last few months
So what happened. We won’t be changing cav eq nodes for a while? 3 months later ya changing em. Typical kabam. You can’t keep your word
They said they wouldn't be adding new ones. They didn't say they wouldn't be rotating old ones back in (in fact they said the opposite of that - the whole point of adding node buffs was to allow them to swap around periodically) and I'm pretty sure they never said they would never alter them - they've been tweaking the Cav buffs more or less continuously over time.
The tip off would be the words "can now." All these buffs are older buffs that have been tweaked. In every case it seems like the changes improve the node buffs in ways that make them more manageable for players, not harder to deal with. So in general this seems to be complaining for the sake of complaining, without actually taking time to consider what the announcement actually says. It says older node buffs are coming back, which is to be expected and Kabam never said wouldn't happen, and it says they are coming back with improvements based on player feedback which is generally positive for players (at least those that want things to be easier).
The science crossfight (3.1) is horrible. It suffers from the same bug as the white mags cross fight where the stun sends your champ backwards…. On top of that the controls get a little wonky making it difficult to take advantage of the node
Cross fights worked in only 1 path so far for me and I’ve explored the first 2 cav chapters already. Each time I had tagged or class champs. Didn’t seem to matter 🤷🏻♂️
Science was really a pain somehow. It felt that I didn’t receive much more power in trade off the nodes. I like the previous one more because it’s faster
Why are people upset with this change? It's not like before where we were forced to bring champs with these tags only.
Now, its the same as before, except you literally have MORE options. Like, for once, kabam isn't restricting us, they're giving you even MORE options, and a fun new mod for people who bring those champs that dont have the right champs for the class based node.
You literally have more freedom in completing and exploring the quest now.
Why is that bad? I'm being genuine here, I do not understand
I like this new system, combines the old with the new, the tag based on its own was a major flop IMO, I got it done with my top champs n ignored the tags in the end but it didn't make for enjoyable content, so kudos for this month. Giving us a wider scope of options 👏.
Only issue is, its bugged! My cross fights aren't applying to the next fight in 1.2, I'm told its happening in other quests too but I'm yet to see that for myself.
Wasn't a major issue mind, but a bug is a bug none the less 🤷♂️.
Only issue is, its bugged! My cross fights aren't applying to the next fight in 1.2, I'm told its happening in other quests too but I'm yet to see that for myself.
Wasn't a major issue mind, but a bug is a bug none the less 🤷♂️.
1.2 tags are #dimensional being, #illuminati and #thanos army. Cross fight carries over for these. Mystic champs it will apply for your current fight (unless they so happen to be one of the tagged champs also, Maw for example)
@Kabam Miike i posted in the bug section... these new nodes don't work properly. In 1.2 and 2.2 the tagged champs get the crossfight furies, while the class-paired champs only keep the furies in fight but they don't keep them as crossfight abilities for the next fights. Moreover, I'm exploring 3.1 and I can't get crossfight furies with venom nor with spidey2099. I don't understand this. This 3.1 node doesn't even work with the tagged champs. I wish kabam would just scratch these annoying nodes since they're pointlessly annoying and they don't even work properly. Like for example in 3.1 the opponent's first hit is unblockable but then if you knock them down you gain an evade charge that when they try to hit you you autoevade and passively stun them for 0.9 seconds. Seems fine if not for the fact that when autoevading your champ runs so far from the opponent that by the time you try to hit them they've already recovered from the passive stun. So they either block you or they intercept you. It's utterly pointless to play into this node. I found myself having less trouble by just blitzing through with herc instead of trying to take advantage of the node, which, like I said, is also broken. So it's not like I gain any advantages like building furies through crossfights for the boss for example. Feels really bad when compared to other months with just the regular class based nodes. We keep saying these nodes are bad but we keep getting them thrown at us
@Kabam Miike i posted in the bug section... these new nodes don't work properly. In 1.2 and 2.2 the tagged champs get the crossfight furies, while the class-paired champs only keep the furies in fight but they don't keep them as crossfight abilities for the next fights. Moreover, I'm exploring 3.1 and I can't get crossfight furies with venom nor with spidey2099. I don't understand this. This 3.1 node doesn't even work with the tagged champs. I wish kabam would just scratch these annoying nodes since they're pointlessly annoying and they don't even work properly. Like for example in 3.1 the opponent's first hit is unblockable but then if you knock them down you gain an evade charge that when they try to hit you you autoevade and passively stun them for 0.9 seconds. Seems fine if not for the fact that when autoevading your champ runs so far from the opponent that by the time you try to hit them they've already recovered from the passive stun. So they either block you or they intercept you. It's utterly pointless to play into this node. I found myself having less trouble by just blitzing through with herc instead of trying to take advantage of the node, which, like I said, is also broken. So it's not like I gain any advantages like building furies through crossfights for the boss for example. Feels really bad when compared to other months with just the regular class based nodes. We keep saying these nodes are bad but we keep getting them thrown at us
This is not a bug. If you take a look at the first post in this thread and in game, we explain that only Champions with TAGtical edge can carry the Cross Fight Charges forward, but those of the associated class can use them in the fight they are in.
If there is an issues in 3.1, we need a lot more information to look into it. Please use your thread in the Bugs and Known Issues forum to tell us who you are using, and which paths you noticed the problems on.
@Kabam Miike i posted in the bug section... these new nodes don't work properly. In 1.2 and 2.2 the tagged champs get the crossfight furies, while the class-paired champs only keep the furies in fight but they don't keep them as crossfight abilities for the next fights. Moreover, I'm exploring 3.1 and I can't get crossfight furies with venom nor with spidey2099. I don't understand this. This 3.1 node doesn't even work with the tagged champs. I wish kabam would just scratch these annoying nodes since they're pointlessly annoying and they don't even work properly. Like for example in 3.1 the opponent's first hit is unblockable but then if you knock them down you gain an evade charge that when they try to hit you you autoevade and passively stun them for 0.9 seconds. Seems fine if not for the fact that when autoevading your champ runs so far from the opponent that by the time you try to hit them they've already recovered from the passive stun. So they either block you or they intercept you. It's utterly pointless to play into this node. I found myself having less trouble by just blitzing through with herc instead of trying to take advantage of the node, which, like I said, is also broken. So it's not like I gain any advantages like building furies through crossfights for the boss for example. Feels really bad when compared to other months with just the regular class based nodes. We keep saying these nodes are bad but we keep getting them thrown at us
This is not a bug. If you take a look at the first post in this thread and in game, we explain that only Champions with TAGtical edge can carry the Cross Fight Charges forward, but those of the associated class can use them in the fight they are in.
If there is an issues in 3.1, we need a lot more information to look into it. Please use your thread in the Bugs and Known Issues forum to tell us who you are using, and which paths you noticed the problems on.
About the class types not getting cross fights: well this is what the post on the forum says, but that's not what the nodes in game say. In fact they go like this: "if the attacker is "this class" or has the TAGtical Edge, they gain 2 cross charge(s) each time they do this thing"...
about the champions with the corresponding tag, it's not consistent. I didn't explore everything but I can say for sure that I got no cross fight furies when I defeated beast and stark spidey with venom in 3.1, while I got cross fight furies when defeating psychoman on a different lane with the same champ, venom!
@Kabam Miike i posted in the bug section... these new nodes don't work properly. In 1.2 and 2.2 the tagged champs get the crossfight furies, while the class-paired champs only keep the furies in fight but they don't keep them as crossfight abilities for the next fights. Moreover, I'm exploring 3.1 and I can't get crossfight furies with venom nor with spidey2099. I don't understand this. This 3.1 node doesn't even work with the tagged champs. I wish kabam would just scratch these annoying nodes since they're pointlessly annoying and they don't even work properly. Like for example in 3.1 the opponent's first hit is unblockable but then if you knock them down you gain an evade charge that when they try to hit you you autoevade and passively stun them for 0.9 seconds. Seems fine if not for the fact that when autoevading your champ runs so far from the opponent that by the time you try to hit them they've already recovered from the passive stun. So they either block you or they intercept you. It's utterly pointless to play into this node. I found myself having less trouble by just blitzing through with herc instead of trying to take advantage of the node, which, like I said, is also broken. So it's not like I gain any advantages like building furies through crossfights for the boss for example. Feels really bad when compared to other months with just the regular class based nodes. We keep saying these nodes are bad but we keep getting them thrown at us
This is not a bug. If you take a look at the first post in this thread and in game, we explain that only Champions with TAGtical edge can carry the Cross Fight Charges forward, but those of the associated class can use them in the fight they are in.
If there is an issues in 3.1, we need a lot more information to look into it. Please use your thread in the Bugs and Known Issues forum to tell us who you are using, and which paths you noticed the problems on.
This is stupid. Then what was even the purpose of adding the class base nodes on to it? You changed em cause of the backlash ya got over the tags. Then you do this buff which is still the same as it is of zero help on fights
@Kabam Miike i posted in the bug section... these new nodes don't work properly. In 1.2 and 2.2 the tagged champs get the crossfight furies, while the class-paired champs only keep the furies in fight but they don't keep them as crossfight abilities for the next fights. Moreover, I'm exploring 3.1 and I can't get crossfight furies with venom nor with spidey2099. I don't understand this. This 3.1 node doesn't even work with the tagged champs. I wish kabam would just scratch these annoying nodes since they're pointlessly annoying and they don't even work properly. Like for example in 3.1 the opponent's first hit is unblockable but then if you knock them down you gain an evade charge that when they try to hit you you autoevade and passively stun them for 0.9 seconds. Seems fine if not for the fact that when autoevading your champ runs so far from the opponent that by the time you try to hit them they've already recovered from the passive stun. So they either block you or they intercept you. It's utterly pointless to play into this node. I found myself having less trouble by just blitzing through with herc instead of trying to take advantage of the node, which, like I said, is also broken. So it's not like I gain any advantages like building furies through crossfights for the boss for example. Feels really bad when compared to other months with just the regular class based nodes. We keep saying these nodes are bad but we keep getting them thrown at us
This is not a bug. If you take a look at the first post in this thread and in game, we explain that only Champions with TAGtical edge can carry the Cross Fight Charges forward, but those of the associated class can use them in the fight they are in.
If there is an issues in 3.1, we need a lot more information to look into it. Please use your thread in the Bugs and Known Issues forum to tell us who you are using, and which paths you noticed the problems on.
3.1 spider verse hero tag miles morales
But next fight 0 cross fights
1.2 ebony maw Same results 2 fights with him and 0 cross fights but oddly only right side of map he works on left side
Honestly, one of the most frustrating + uninteresting CavEQ's I've ever played. And that's WITHOUT the bugs, the tags are not the one - I'd rather them just stuck to the classic style tbh.
@Kabam Miike can you explain how in 3,1 spider verse quest. Using the exact same team for all paths that the cross fight works on some paths and not on others? This is beyond stupid.
Here's a thought if you're going to buff the notes how about you buff the freaking rewards... Wtf how are you going to just make it significantly more difficult and keep the rewards the exact same. I'm certainly not going to be 100% in whatever the hell you guys call the event quest this month
Also, when filtering champion you should be able to select more then one filter and not have the results come up blank. If a champ has any of the selected filters they should show up. So if you want to select all three tags for the particular quest you have to do them individually you can't do them all at the same time. That's not the way the tag system should be set up. If you select all three for that particular quest if a champion has any of the three it should come up. Obviously I know they don't have all three. If you try to select all three no champs show up..
As usual did it on first day taking breaks in between This month is total disaster in terms of bugs and inconsistencies
This bug really got me on my nerves. Skill/spider verse chapter is far by most worst chapter. Stun is too short as we are pushed back to due to evade and hence it was really annoying to connect heavy from that distance. I don't see any positive impact of champ usability which falls under tag specific as this bugs plus some of nodes were really polar opposite what champ supposed to do.
But on bright node I liked the boss fights. It was sad that nodes made Omega sentinel a Anit- Medusa but still fun fight. Cap Britain was too smooth and really had fun to fight her. Imo none of the bosses were hard but if I have to draw comparison then Phoenix is hardest among the 6
Comments
You now have:
-A way more diverse pool of champions benefitting the nodes with an entire class and sometimes some decently sized tags such as #Avengers or #Symbiote or #Spider-Man.
-If tags work the same as last time, you will be able to gain massive attack bonuses for boss fights making them easier.
Not to mention you aren't even forced to use these champions and champions like CGR and Herc are regularly used to run through content.
Now tell me where people have deciphered "cav difficulty is going to become harder" from? We don't know any nodes yet and if previous cav eq quests are to be gone by, well, they aren't going to much (probably any) headache for anyone with a half decent roster.
The only worry is if the tasks are too bothersome to complete for the benefits but as we haven't seen it in practise yet, we can't judge that and anyways, people are too focused on the words "tags" and "cavalier even quest update" to even notice.
Edit: Post wasn't clear -- I thought that all cav eq nodes would be the new ones, but they are every other, starting with 1.2 and Mystic+. 1.1 is still the old Tech.
The tip off would be the words "can now." All these buffs are older buffs that have been tweaked. In every case it seems like the changes improve the node buffs in ways that make them more manageable for players, not harder to deal with. So in general this seems to be complaining for the sake of complaining, without actually taking time to consider what the announcement actually says. It says older node buffs are coming back, which is to be expected and Kabam never said wouldn't happen, and it says they are coming back with improvements based on player feedback which is generally positive for players (at least those that want things to be easier).
Now, its the same as before, except you literally have MORE options. Like, for once, kabam isn't restricting us, they're giving you even MORE options, and a fun new mod for people who bring those champs that dont have the right champs for the class based node.
You literally have more freedom in completing and exploring the quest now.
Why is that bad? I'm being genuine here, I do not understand
Only issue is, its bugged! My cross fights aren't applying to the next fight in 1.2, I'm told its happening in other quests too but I'm yet to see that for myself.
Wasn't a major issue mind, but a bug is a bug none the less 🤷♂️.
Mystic champs it will apply for your current fight (unless they so happen to be one of the tagged champs also, Maw for example)
If there is an issues in 3.1, we need a lot more information to look into it. Please use your thread in the Bugs and Known Issues forum to tell us who you are using, and which paths you noticed the problems on.
about the champions with the corresponding tag, it's not consistent. I didn't explore everything but I can say for sure that I got no cross fight furies when I defeated beast and stark spidey with venom in 3.1, while I got cross fight furies when defeating psychoman on a different lane with the same champ, venom!
But next fight 0 cross fights
1.2 ebony maw
Same results 2 fights with him and 0 cross fights but oddly only right side of map he works on left side
Might skip out on this month too
As usual did it on first day taking breaks in between
This month is total disaster in terms of bugs and inconsistencies
This bug really got me on my nerves.
Skill/spider verse chapter is far by most worst chapter. Stun is too short as we are pushed back to due to evade and hence it was really annoying to connect heavy from that distance. I don't see any positive impact of champ usability which falls under tag specific as this bugs plus some of nodes were really polar opposite what champ supposed to do.
But on bright node I liked the boss fights. It was sad that nodes made Omega sentinel a Anit- Medusa but still fun fight. Cap Britain was too smooth and really had fun to fight her. Imo none of the bosses were hard but if I have to draw comparison then Phoenix is hardest among the 6