Ryz-aus wrote: I just don't understand the complaint from others with strong rosters that they are facing a challenge that is unfairly hard - it's supposed to be a challenge, that's one of the things that I find enjoyable. It's not like this event is offering rewards like a new character - they are covers that those with established rosters already have and if the difficulty isn't your cup of tea then "oh noes", you lose out on a bit of ISO. FYI - every node is beatable without boosts as long as you have the required characters. I was able to make it through each one, and another member of my alliance was able to beat the final node of 395s with a couple of 2*s. You might lose out to a cascade, or get frustrated that hood seems to be the answer to the toughest nodes, but if you are constantly losing maybe it's an indicator that you should mix up your teams and try some new combinations.
atomzed wrote: Unfortunately, they are not going to make it a walk in the park where everyone breeze through it. They HAVE to ensure that covers are only given to top performing players, so they need to make it hard to differentiate players.
arktos1971 wrote: The scaling is pretty bad unfortunately, and I am not sure I am going to complete the 3rd board given the time that is left. I'm not motivated to kill my entire roster and boost for unworthy rewards. There is a balance to be found on this Gauntlet which is a very good idea initially.
atomzed wrote: However, I want to say that the gauntlet appears to be created because people want pve to be PURE pve. It was fixed, according to what ppl want.
_RiO_ wrote: atomzed wrote: However, I want to say that the gauntlet appears to be created because people want pve to be PURE pve. It was fixed, according to what ppl want. Uhhmm.. no? Whenever the concept of a pure PvE came up and whenever the idea of gradually increasing node levels within such a PvE came up, invariably multiple posts would surface that explicitly talked about the balance aspect and the fact that it would be critical to properly manage the risk vs. reward balance as well as difficulty across roster types. What Demiurge delivers is an event that was obviously designed with callous disregard for those warnings, or they'd have been more conservative with the level scaling for the initial run. Better to give your players too many rewards one or two times while tuning difficulty than to have players run face first into brick walls.(I almost wonder if this level of screw-up is intentional, so that Demiurge can later cite lowered metrics for player engagement as a basis for an argument to not run a 'pure' PvE again.)
NCSTL wrote: Just wanted to say i really enjoyed this event. However, I am stuck on node 39. As much as I'd like to continue I dont see myself going forward. I'm up against a deadly node comprised of lvl 200, 200, and 201 enemies (deadpool, OBW, and Ares). My punisher is 156, and magneto and storm are 130. This is the closest i can get level wise to this node. I've got 1 toon 128 (patch) rest of my toons are 94 and under. I've already gone through all the boosts am willing to spend and the bootmline is that i dont see a way through this node. So i'm pretty much stopping here and i'm ok with it. Would have loved the Psylocke cover, but will backtrack to work on getting the OBW and black Panther covers.
BearVenger wrote: So, just to address the "level 166s have it sooo easy" argument, does observation show that enemy levels correspond to your highest levelled character? If that is so, then the people who are "luckiest" are those with a broad roster of over-covered, under-levelled characters. Now that I'm near the end, I'll post my roster and the level of opposition I face in each node tonight.
Cryptobrancus wrote: I did finish the whole thing and really enjoyed the challenge though I will admit to cheesing #42 and dropping the big whales on them with a team-up. Felt a little dirty to use modern storm hiding behind hulk and BP to get the team-up AP but it was quite satifying that it worked so well first try, and there was absolutely no need to 'go again' on that node.