Not on Test Server- But have a Question

[Kaleyen]

Like the subject says, I'm not on the test server...question being is how do test updates come up?  From in game feedback or through forum posts or other ways?<div></div>

[ZeyGnome]

<DIV>If you are talking about how we find out what is in an update then we usually get update notes on the launchpad just like Live.</DIV> <DIV> </DIV> <DIV>Sometimes we don't though, because it was a fix, or forgotten.  Then we usually find out by suprise or though the GM-QA that inhabit the server from time to time.</DIV> <DIV> </DIV> <DIV> </DIV>

[Kaleyen]

Sorry, poorly worded my question, I apologize.What I meant was were do the developers get their information that something needs a change.<div></div>

[Delameko Stone]

/bug reports and forum posts.You'll see the dev's usually start a new topic if they want something specific testing (like LU updates).

[Kaleyen]

<div><blockquote><hr>Delameko Stone wrote:/bug reports and forum posts.You'll see the dev's usually start a new topic if they want something specific testing (like LU updates).<hr></blockquote>Thank you very much.So it's safe to assume that the posts that go for 30+ pages the devs do look at them?</div>

[Delameko Stone]

Usually, yes.  If you keep an eye on the dev tracker you'll see they often reply to the topics numerous times.  Also they're often reading, even if they're not posting.

[Kaleyen]

<div><blockquote><hr>Delameko Stone wrote:Usually, yes.  If you keep an eye on the dev tracker you'll see they often reply to the topics numerous times.  Also they're often reading, even if they're not posting.<hr></blockquote>Awesome, thank you very much for your help.</div>

[ke'la]

<blockquote><hr>Delameko Stone wrote:Usually, yes.  If you keep an eye on the dev tracker you'll see they often reply to the topics numerous times.  Also they're often reading, even if they're not posting.<hr></blockquote>It seems to me that they seem to avoid posting in certain posts to keep them clean and informitive such as the "unified list" threads, because by not posting those threads don't show up on Dev Tracker and then you don't get the Dev  stalkers posting wich alot of times derails threads. <div></div>

[Pins]

Updates come out because of something a dev sees, a person sees, general claims from population, and so on. There is no 1 way that an update comes out. Updates come out because of everything combined. People see stuff /bug's it, people on the forum post about it, and the devs looks at it, and compares it to the "big picture." And then decides whether or not they should change it, and if so they think about why it should be changed, whether they post why is not really something we need to know, but most things are so obvious, like why does the Matron heal around the druid ring now? Well obviously somebody felt the need to exploit the pathing around at the druid ring to try to kill her.

[Simon Snowlock]

Bugs aren't the only things that need to be worked on. Besides /bug they also look at /feedback. /feedback is used to tell the devs how you feel about certain aspects of the game, what you like, don't like, or would like.

[Ebjelen]

/feedback seems to be just as important as /bug especially on new systems being tested. If you don't like something, it's not a bug. Also, the devs do haunt test server. We've seen simple bugs get fixed on the fly while discussing them on chat. They seldom answer. And, if you start ranting or droning on and on people just ignore you. So the chat there tends to be quite civil. In other words, when we discuss things rationally on the test server chat channels, the devs pay attention. <div></div>