Expectations about development of the game

[Hestzhyen]

Translation: it's the dev's job to read in between the lines of thousands of users and implement content in a way that will not offend the existing player base and attract new ones. Why? Because we are paying you!

And this, my friends, is why I never got into game development.

It is quite literally a dev lead's job to get their team to execute the designer's gameplay vision based in large part on user expectations and feedback. The dev team gets the level set and specifications and works with the designers and testers to make it reality. So no, I have no pity for them- they signed up for the job of making the fun happen and should know quite well that playing the finished product is night and day from building it. If not, then the first experience will be an educational one.

If anything, the designer is the one who has the hard job of reading in between the lines and making compromises to find common ground... and again, that is their job. They were hired because they could and wanted to do it. It's not an easy job and it's not one I'd want either. But the people who signed up for it need to deliver. Right now, with Eureka the latest example, they aren't.

[Asiragan]

While i can understand that people playing since the beginning of the game can get bored with it not seeing enough "new" content, i think you are kinda expecting way too much, and even become out of touch with reality, ifyou are waiting for totally new concepts every 6 months. Even if the developpment team wanted to do that people above them would never allow it to happen. Not when making video games have become that costly and when investors wanting to be sure to get their cash back prefer to copy what is already selling.

I don't even think the players want a complete revolution every 6 months. A game also need some stability, let's not go into the extremes. They just want to go out of the perpetual circle that last for 2 years of patchs that looks exactly the same without any flavor to it. To get out of the usual cap tomes, savage raid if you feel like it, msq, dungeon run and such.
Some piece of content that last more than a few days at most, that bring some kind of change and make the devs go out of their comfort zone while being fun and rewarding for the players. And I don't think that's asking for a lot ^^'

It is quite literally a dev lead's job to get their team to execute the designer's gameplay vision based in large part on user expectations and feedback. The dev team gets the level set and specifications and works with the designers and testers to make it reality. So no, I have no pity for them- they signed up for the job of making the fun happen and should know quite well that playing the finished product is night and day from building it. If not, then the first experience will be an educational one.

If anything, the designer is the one who has the hard job of reading in between the lines and making compromises to find common ground... and again, that is their job. They were hired because they could and wanted to do it. It's not an easy job and it's not one I'd want either. But the people who signed up for it need to deliver. Right now, with Eureka the latest example, they aren't.

You explained my point better than I did. Thanks