Server issue aside, the only problem I had with this pve was the change in rubbbanding without any communication of that change. Other than that, lots of props for the dev’s.
more consistent points, which was fairer to euro players.
achievable progressive rewards (no clue, why people are complaining about this. guess people need something to complain about out of habit).
sentry as a node reward, so everyone had access to essential nodes in pve.
While the changes aren’t without faults it showed tremendous effort to correct perpetual past problems.
Even the scaling was not out of control.
There were ways for the pve to be better and other areas of the game with problems, but for once I’ll leave those for another thread.
You deserve it after providing a small glimmer of hope for improvements after such a huge downside in recent weeks. I genuinely hope you all continue to build on this great effort.
I agree mostly. I still think that progression rewards need some tweaking. Not a huge deal, but I know a lot of people that hit the Daken reward before or just after this sub. If they can cut the point meter for the final sub in half during the sub, they can add some progression rewards to the event too.
Like I said though, not a huge deal and a great PVE overall.
For example, in this PvE… 45K Daken. And than every say, 10K after that, 50HP or 1000ISO. Nothing spectacular, just extra rewards for those willing to go that extra mile…
I agree. I think that giving Sentry in an “easy” node was their way to say sorry without actually saying sorry.
This PVE, while a bit grindy, and could have used a little more ruberbanding to make it feel like you were moving more, does seem to have some benefits over the old style of playing. Especially making the progression reward actually obtainable. I have never hit the top progression reward before, even when I was grinding every node to 1 and waiting for refresh. So while I’m not ruberbanding into the top 10, I am happy with the progression set up this time.
I am sad that I can’t just wait for rubberbanding to shoot me up into the top 10, but I do understand that this is more fair across the board. If you want it, you have to play for it, not just jump in last minute. So I am happy and content with my #30 spot because I know that I earned it by playing fairly with everyone on the same playing field.
Overall, I think they made some good changes. It’s not perfect, but it feels like a step in the right direction.
Although, I am not sure why they put an end time and a points count down bar in the subs?
This was the most fun PvE I think I’ve played. Vastly reducing the rubberbanding was fantastic. I felt like I could play for fun without needing to grind nodes on each refresh. If I had spent more time grinding I’d have been able to get the Daken cover, but I think that’s very fair. If you play harder, you get an additional reward. But even without grinding it looks like I’ll end in the Top 20 in my bracket. So I played the amount I wanted, enjoyed the story, and got some good rewards to boot. Perfect!
I will admit though that I have to laugh a little bit about the idea of having some smaller rewards after the Daken cover. The Season 1 thread was so full of comments about how upset people were with the small ISO and HP awards after the 5000 point Heroic 10 pack. I think Demiurge learned their lesson from all that abuse… If you don’t give additional rewards then people complain. If you do give additional rewards then people complain. So you might as well do whatever you want.
Then you’d have people complaining that progression rewards are, OMG yet again, completely unachievable because the devs are totally idiotic poopyfaces.
I remember people complaining about the puniness of the 50/100 HP S1 progression reward that was a few tiers higher than the Heroic ten-pack progression reward. Some extra HP at higher progression points would be nice, but someone will always complain.
2 days shorter to give people more of a break during this congested season schedule would have made it just about perfect tbh. Yeah, fair play for getting it right on this one devs.
I’m just crossing my fingers hoping this is more a sign of things to come rather than a one time sorry to the players, and a bit of a gift since many people (i.e. americans) had the holiday weekend away from MPQ and were probably looking at not placing highly enough for Sentry.
scaling and burn out induced from it aside I have to say that the devs managed to hit the progression rewards just about dead on this time.
Also the Sentry cover as a gift to us is a nice step in the right direction.
Infact it’s helped me from going back into the grind and burn myself to try to re-obtain my top 20 spot.
The only thing that bothered me about this PvE was that I didn’t become aware of the relative lack of rubberbanding until it was too late to make up the ground on the leaders. Beyond that, it was a really enjoyable event and I hope it continues in the future.
Through my own lack of attention I didn’t fully recognize the 45k reward as being 1) the one color I didn’t already have, and 2) the one they’ve been stingily keeping to the top 100 whales^H^H^H^H^H^H alliances until about oh… monday sometime, with about 3 days left. I was sitting somewhere in the 25-27k range. Just managed to grind out that last point for 45k.
In case you come back to check - I think the OP was referring to the fact that everyone getting Sentry in this PvE sets them up to place well (or at least be competitive for placement) in the NEXT PvE where Sentry is all but guaranteed to be required for some essential nodes, as well as any other future PvEs where he might be required.
The only thing I’m hoping for is that my Sentry doesn’t end up like my Hulk where I had 5 of one single color before seeing a second one. Its gonna be a dark day if I end up 5 red before anything else.
Just wanna agree with the OP. I’ve enjoyed this PVP a lot. The lack of rubber banding is great IMO.I had to grind my ass off to to get into tje top 10, and likely don’t have to worry about dropping 40 spots ni the last hour due to not timing nodes correctly.
