How to be useful on the PTR

My real reason for writing this is that a lot of people in the beta seemed to treat the server as an extended vacation from the live realms, and this upset a lot of old PTR hands who assumed people knew they were supposed to submit feedback, and not just play with all the cool new toys. Yes, you should have fun, and you can contemplate the trippy philosophical notion of your character's existence in an alternate universe (duuuuuuuuuuuuuuude!), but you can do a lot of things to help patch 3.1 launch without issues. The point of the test realms' existence is for Blizzard to test everything new with as large a population of players as possible. If you're uninterested in submitting polite, honest, and frequent feedback, you're making it harder for them to get an accurate sense of the patch's impact on live realms.
If you find a bug, reporting it is good. Being able to reproduce it is even better.
It's hard to get an accurate sense of the seriousness and frequency of a bug unless everyone who encounters it reports in. Blizzard tests internally, but it's not always possible to extrapolate results to a population of 11 million players. Even the PTR isn't always a good statistical sample, but you can help improve that by submitting bug reports whenever you encounter one, and providing as much information as possible on the bug's context and (most importantly) whether you can reproduce it. The inability to reproduce a bug makes figuring out what's causing it a lot harder.

If you don't like something, say so and give reasons. If you like something, say so and give reasons. If you're indifferent, say so and give reasons.
This is a little more true of individual boss encounters and raids because then there's a unified something on which to write feedback, but it's still true for the rest of the PTR as well. Writing "This encounter sucks!" on the feedback form and clicking the submit button is not quality feedback. Writing "This encounter is amazing!" on the feedback form and clicking the submit button is not quality feedback. Writing nothing on the feedback form because you really don't care is even worse than hating or loving it. At least with the first two Blizzard can get a rough sense of whether people like or don't like the encounter, even if they'll have no clue why people feel the way they do.
If you don't like something: Why didn't you like it? Did it seem needlessly difficult or convoluted for certain classes and specs? Are there factors that might have made it harder than it had to be that Blizzard can't actually control for (e.g. a raid with players in Naxx-10 gear trying Ulduar-25)? Or was it just plain boring or too easy?
If you like something: Was the encounter totally awesome? Was it made with 100% pure win sauce drizzled over an entree of amazingness and served with balsamic woot? What element or elements made it especially fun? Does it feel tuned correctly? Did it seem undertuned for your group in good gear? Do you think a raid group in gear similar to, better than, or worse than yours would have a different experience?
Or did you not really feel strongly either way?: Even if you fall into the third group, write something honest. Do any classes or class abilities seem very overpowered, necessary, or undesirable for success in the encounter? Does trash respawn time seem reasonable? Does the amount of trash seem appropriate for the size and length of the instance? Does the quality of itemization seem commensurate with the difficulty of the encounters?

Technical problems are functionally the same as bugs. If a lot of people have issues, they need to know about it.
Everybody's system is different, but there may be consistent complaints concerning bad framerates, lag, or disconnects on certain encounters. This is not an infrequent problem on instance servers that get overrun (see: Naxxramas, popularity thereof) and/or encounters with heavy AoE damage. If this seriously impacts the viability of an encounter or achievements associated with it, write in.
On that note, the test realms are not always meant to run smoothly.
Part of the process involves stress-testing to see how many characters a zone or server can realistically support before the game is basically unplayable. It sucks, but you may very well be one of the players unwittingly testing this. Cowboy up, and submit feedback when gameplay is rough. If a few nights of nasty lag ensure a more smoothly-running game when 3.1 goes live, Blizzard did its job and you did yours.
A note concerning the 3.1 PTR: not everything is going to be available all the time.
Certain boss encounters in Ulduar will only be available in the EU, certain ones will only be available on North American servers, and for the moment none will be accessible when the encounter team isn't around to watch what's happening. Don't count on being able to schedule consistent, unchanging raids if you manage to get a raid team imported.

And as a final note, don't get too attached to anything you see on a test realm.
Blizzard may be trying out the most awesome, unbelievable, jaw-droppingly overpowered ability of all time and holy s#^$# you can't believe it's actually in the game and it's so much fun and it's amazing....and the next day it might be gone. To take some creative license with an old saying, every skill and talent is perfect until it makes contact with an 11-million count playerbase. There's always some weasel out there who will figure out some diabolical means of using an ability or item in a fashion other than intended. Sans weasels, sometimes new stuff just doesn't work, so out it goes. Plenty of stuff hits the PTR that I suspect the developers are either divided or ambivalent on, just to get some sense of how it would play out on a live server. No matter how badass your PTR Ulduar raid stategy is, or how cool your talent changes, etc. -- don't toss a fit if it gets axed.
Filed under: Patches, Analysis / Opinion, Bugs, Blizzard, Features, Guides, Hardware, Rumors






Reader Comments (Page 1 of 1)
matt Feb 21st 2009 7:08PM
awesome article.
Jesse Feb 21st 2009 7:19PM
amusingly enough, exactly the kind of feedback she characterized as bad.
it's like a meta-joke!
matt Feb 21st 2009 8:03PM
sorry if my first comment wasn't the greatest. i love this article. mainly because i hate the ptr's with a passion. the fools that run around on there ruin it all for me. then when they release the Pre-mades i cry. that is when i run back to live servers. the reason being you don't have to have a certain level toon to make one. so you could have a person that on live plays a 30 hunter and rolls a geared 80 shaman and joins a raid, and when you ask them to drop a totem they just stand there not doing anything. if people would go on the Ptrs to play and help i would love to test but i cant stand those servers.
WoWie Zowie Feb 21st 2009 9:16PM
awesome article!
Cuetip Feb 21st 2009 7:15PM
great article and matt props for not saying first, this is some great advice and i think everyone should do this, if you don't give feedback you really aren't using the PTR for what it's meant for (i haven't always given advice =/ ) but i will now that i realize that's what it's for
Firestride Feb 21st 2009 7:23PM
So how's it work? Are there more specific feedback forms, or do you just submit a ticket like on the live realms?
Tumleren Feb 21st 2009 7:34PM
I haven't been on a PTR before, but in the wrath beta, everytime you completed a quest you would a blue exclamation mark (like the tips when you first started playing), and that would open a feedback form.
Other than that, you can click on a 'B', which opens a feedback form for you to fill out (quest, zone, item etc.) - At least as far as i remember
mysticalos Feb 21st 2009 7:34PM
the UI on the test client has an additional blue ! button for submitting feedback. You do it within the client UI, pretty straight forward form.
Jorelos Feb 21st 2009 7:37PM
Even if it takes bans to do it the best step blizz could take to getting rid of the crappy attitude players have towards the PTR now is to, not stop people who aren't interested in bug testing because they can become the ones who inadvertently find and report bugs, but stop the people who exploit (and that is the accurate word in this case) solely as a means of strat testing for their guild.
Maybe the best way to do this would be for blizz to limit the number of people in a single guild who can join the PTR or make there be a delay before another guildie can transfer a character after another guildie has joined. The fragmenting the test instance to stop people strat testing may work somewhat but you'll still end up with people who are strat testing, see a bug, and go ok that's cool but instead of reporting the bug like they should if they're on the PTR will either note it to exploit it if it survives 'til live or will just continue on their way.
Jorelos Feb 21st 2009 7:43PM
In the first paragraph meant to say exploiting the PTR, not just exploiting since the people/guilds that exploit the PTR just to raid strat are using up resources that could be better used for people who actually are interested in testing other changes and/or for bugs, although they might as well be exploiting game mechanics.
hagu Feb 24th 2009 5:41PM
Provided they give feedback, I tend to think that strat testing helps as well; after all they will tend to be doing the most complicated things in the most complicated places. Maybe some more Wintergrasp testing would have caught that subtle bug where winning WG crashed the world server.
Cy Feb 21st 2009 8:03PM
I would also stress that if you plan on testing, please check the PTR forums. There you can see and discuss known issues (no point in reporting something that's a known bug) or start a discussion about a mechanic or anything that just doesn't seem right, but also isn't a blatant bug.
It's a good tool and the forum is pretty heavily moderated (read the stickies!) and can be quite useful while testing.
Grumaya-Sargeras Feb 22nd 2009 2:00AM
Another thing that i've found in my experience beta-testing anything (which, essentially, is what these PTRs are), Devs WANT you to try to break things.
Try using an ability in a way that it's not intended. Try blinking across a pit of lava to reach an area that will kick you out of the instance for example. Glitches discovered once the patch reaches live is what calls for hotfixes, however, if someone performs something that could cause the SAME glitch on the PTR, it can be fixed before it goes live.
Also, just because it didn't work on the last PTR version, doesn't mean it won't work on THIS version. Any change to code can cause another glitch to pop up.
Now, even though I've said that you should try to break the game, if you find something, don't run around town exploiting it. Report it first, THEN have a little fun with it- but don't impede on other people's testing.
Beta-testing is an important part of any online game, and WoW is no different. If you're not going to be honestly testing, then there's not much of a reason for you to be on the PTRs. If the attitude you have going into the test is "omg i gets to see phat lewtz furst" then go back to grinding. Numbers ARE important, but people who are just there to see content and give people a hard time need to get off.
Report, Report, Report, and be detailed about it, like the article said. Great article.
Arashikou Feb 21st 2009 11:08PM
The step about reproducability is particularly important, because a lot of people don't bother to even test whether they can produce the problem multiple times. Trying to reproduce the problem can help you narrow down the steps necessary to something very specific. (From "walking into the inn causes me to fall into the basement" to "walking into the inn while hugging the left wall causes me to fall into the basement" to "walking into the inn while hugging the left wall and trying to flirt with a dwarf causes me to fall into the basement.") I know it's boring and tedious and eats into your time to play the game... but the thing is, the PTRs aren't there for you to play the game on - They are there for you to TEST the game on. (Which, yeah, usually means playing it... until a bug crops up, that is, and then you have extra work to do. It's what you signed up for when you downloaded the test client, after all.)
Perhaps even MORE important, though: Even if you can't (or won't) reproduce a bug, try to at least be detailed about what you were doing before the bug happened as possible. What may seem inconsequential to you can be the crucial detail that causes some developer at Blizz to go "EUREKA! We're overloading the Funk Capacitor, resulting in a physics hash underrun, turning Arthas' underwear plaid. Why didn't I see that before?" and thus leading to getting the bug fixed. Sure, your details may also NOT contain the vital clue, but they CERTAINLY won't if you don't even include them! If you only tell Blizz "This thing broke." then they can only guess at what caused it, and it's very unlikely they'll stumble upon the cause at random and be able to fix the bug. If the bug is fixed at all, it will be because of someone ELSE's more-detailed bug, and then your leetness will be reduced in the eyes of the gaming gods, and your e-peen will be shrunk as karma.
So for your e-peen's sake, if nothing else, be detailed in your bug reports. Try to reproduce bugs, and tell Blizz as specifically as possible what causes the bug. Then after the patch goes live, when absolutely nothing goes wrong during that one boss fight, you can turn to your raid and say "Yeah... that lack of bugs right there? The way the server didn't turn us into murlocs? That was all me."
Whyisretgimped Feb 21st 2009 11:20PM
I can't believe the author of this article is admonishing people for not giving Blizzard free quality control. One of the absolute most asinine things I've ever seen on WoWinsider...
Go on the PTR's and do whatever you want. You've paid for the time and Blizzard can certainly afford more in house testing...
Jack Feb 22nd 2009 3:12AM
You're completely right, and people do have the right to go on the PTR and do whatever they feel like. They'll still be helping out with testing, as well, because having more people around besides just the hardcore testers is a more accurate simulation of live conditions.
But from the point of view of someone who would like to make the game better, and who wouldn't mind helping out a bit, the PTR is the best place to give feedback and find things that are over/underpowered or broken. For every bug you find, that's one less you'll have to deal with on live.
Hansbo Feb 22nd 2009 11:24AM
You did notice the title said "how to be useful on the ptr", and not "how you must behave on the ptr or blizzard will eat your soul", right?
Owen Feb 21st 2009 11:44PM
"for the moment none will be accessible when the encounter team isn't around to watch what's happening."
Until the EU PTR encounter team gives up trying to watch how fast Ensidia clears Ulduar no matter how many times they ask Ensidia to slow down.
sephirah Feb 22nd 2009 6:09AM
They don't have to watch only Ensidia, but Inner Sanctum, Irae AoD, For the Horde, in Harmony, The Legacy, Last Resort, Method... too
Tenchan Feb 22nd 2009 2:28AM
Give it up. People didn't even grasp this concept on the Betas. Hell, the Wrath -Alpha- already had people bitching that they are not having 'enough fun'.