A Lesson to be Learned

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: Morfedel.4165

Morfedel.4165

So I was a bit trepedatious about posting this video, as it isn’t about guild wars 2, but I think it preaches an important lesson… not just for devs, but for players too.

https://youtu.be/BpS6odMAAJ4

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: DreamyAbaddon.3265

DreamyAbaddon.3265

watching it………

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: DreamyAbaddon.3265

DreamyAbaddon.3265

While it’s interesting to see that other side perspective…
I think in my opinion going silent on a project during development is not the way to go.
Sure the devs dont want to over promise and under deliver, and sure they dont want to promise something they may not be able to achieve, however, the players will understand if they just communicate with us and let us know: “Hey we tried but due to this issue (Reason) we discovered we are unable to solve the problem to make this feature possible so for that reason we are putting this project at hold until we discover another solution.” - I feel this kind of communication is important. Early stage development should be communicated with players in MMO and so should an update on near release if it’s just about to get ready.

Again this is my opinion since I want to hear about SAB which they went silence, I want to hear about restoring Visual effects and adding visual noise slider, I want to hear about these matters but when they dont communicate it feels they are doing nothing. This is why I oppose the idea of “We are being silence because we are working on it and dont want to promise something we may be unable to achieve” bs….

(edited by DreamyAbaddon.3265)

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: TexZero.7910

TexZero.7910

I’m just tired of the delay, the wait and the when it’s ready philosophy that seems to only be applied when its convenient.

It also does not help when you have dev’s commenting that things are okay when there’s a vocal outcry for change. See pretty much everyone’s disdain for the current state of dungeons and the economy. While yes these need a shift, they did not need such a shock as to actively remove people from the game which is the result they have actually had.

Then there’s the whole i’ve seen this awesome thing, that you are going to have to wait 4-6 months to even get a preview of. A sheer dev blog would do wonders, show us some of the production cycle even if it shifts so everyone can be hype and not just shareholders and developers. Because as is, all players see are empty words.

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: Inculpatus cedo.9234

Inculpatus cedo.9234

We can hope the community would react favorably to announcements of such delays, though it didn’t go over too well when the announcement of Precursor crafting/scavenger hunt would be delayed/started over from scratch was released. Players still seem to bring that up often.

Perhaps, the community will react differently this time; I have no idea. It’s good we have State of the Game addresses back.

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: TexZero.7910

TexZero.7910

We can hope the community would react favorably to announcements of such delays, though it didn’t go over too well when the announcement of Precursor crafting/scavenger hunt would be delayed/started over from scratch was released. Players still seem to bring that up often.

Not really a comparable situation.

This “feature” was supposed to go in Pack 2. Then we had silence. The topic was burred and we never got word of it up until way later when Colin had to apologize for it. Then people were upset by the fact that a feature long in development was stuffed into the expansion pack. When its something that should have just been part of the core game experience. There was no dialogue to be had about it until after the fact.

See the difference ?

People actually want to feel vested in something that they are passionate about, long periods of silence because you feel you can do better isn’t helpful for either side of the community and some blunt and honest communication goes a long way.

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: Inculpatus cedo.9234

Inculpatus cedo.9234

I don’t believe it was Colin that announced that the Precursors would be delayed, and I don’t remember any apology in that post.

Regardless, is there a time limit on when the Devs can decide to scrap an idea? Perhaps the quarterly State of the Games will help keep the community informed on what’s coming; not so sure about what might be scrapped, though.

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: TexZero.7910

TexZero.7910

I don’t believe it was Colin that announced that the Precursors would be delayed, and I don’t remember any apology in that post.

Regardless, is there a time limit on when the Devs can decide to scrap an idea? Perhaps the quarterly State of the Games will help keep the community informed on what’s coming; not so sure about what might be scrapped, though.

….

https://www.guildwars2.com/en/news/looking-ahead-guild-wars-2-in-2013/

And he apologized on stage at each PAX event for HoT. He’s been very straightforward about acknowledging it was a mistake. What they choose to do with that experience going forward is key. The state of the game, while nice would be a bad move to make as a one-off thing.

Yes, there’s always twitch (Guild Chat), but this comes with other problems that always boils down to communication. You can say you’ve seen awesome, but what can we as players see outside of more empty words ? Even the slightest tease or concept art goes a long way.

A Lesson to be Learned

in Guild Wars 2 Discussion

Posted by: Pandaman.4758

Pandaman.4758

I think part of the problem about communication about features is that there’s no real central repository for updates on projects (or even mentioned features). There’s a wiki page called Upcoming changes and features that kinda does this, but since it’s the wiki there’s a limit to how accurate or comprehensive it is. Beyond that we’re pretty much limited to hunting for statements made on twitch, or youtube interviews, or reddit posts, or official forum posts, or blog posts, or twitter posts (tweets?), or gaming mag interviews, or wherever else we’re supposed to scrounge for information.

It would be nice (probably not easy, but nice nonetheless) if we had a “Project Status” page on the site that would list out various features that are being worked on, something like:

Current projects

  • World Boss updates. Status: on track. Reason: N/A.
  • Build templates. Status: delayed. Reason: higher priority project took precedence.
  • PvP rebalancing. Status: delayed. Reason: cannot rebalance mid-tournament.
  • Raid updates. Status: on track. Reason: N/A.
  • Capes. Status: cancelled. Reason: capes twisted into eldritch sign, summoned Cthulu, send help.
    etc.

Would probably benefit from being on a spreadsheet that we can sort by project name, status, and maybe even date first mentioned.