Guild Wars 2

The event was a bit short. We can all attest to that. Whether that’s a good or bad thing, I’m not sure.

The amount of bloom rewards were fine. GW2 players are just too used to grinding events that will allow them to purchase ALL the rewards offered by event vendors and I feel like some players are upset that this is not the case with the Mordrem invasion event. Personally I’m completely fine with events like these that offer limited rewards during a limited time.

The initial reward bug was unfortunate but it happens, right? The issue was addressed and rectified quickly and players retroactively awarded blooms. That’s great.

Event mobs not dropping loot and event completion not awarding karma was a bit discouraging. Maybe reduced amount of karma and loot drop could be awarded if ANet feels like it might affect the economy.

My biggest gripe was how the event encouraged tagging and running to obtain the largest stack of defender buff. This was a big NO-NO in a game like GW2 where acts of helping each other and cooperating are rewarded.

Overall, the event was more than fine for a limited time event, but the tagging and running nature of it all really turned me off.

Cool, thanks for the replies. Not getting SSD anytime soon, so I guess just have to defrag and hope for the best.

I’ve got a quick question. My Windows is installed in my C drive and GW2 is installed on E drive which is a separate partition on the same hard drive. Will installing GW2 on my C drive increase game performance or loading time in any way? Thanks.

Nobody from ANet is even bothered to reply anything in regards to this and I would deem players not being able to party up into dungeons and fractals a pretty major issue. Weird how an MMO developer that deals solely with online customers has a really bad customer service; time and time again. Just play something else for a few months guys, it’s what I plan to do. Good luck to those who still are trying, hope you make it.

Yeah, lots of people are having this issue right now. My error was 19.9.18.1616.101. It fixed itself after I restarted PC though, not sure if it was a coincidence.