51 replies to this topic

[ASC]

To all those of you who get beta keys, Well done and good luck.

But please do remember that the purpose of the beta is to give the devs feedback to make MWO the best game it can possibly be. To that purpose, please keep up to date with, and contribute to the beta/error reporting system in any way you can.

Now, for what is hopefully some useful information on what you might look for/encounter when testing.

Procedural errors:
When certain actions/choices matched together cause unexpected behaviour - In other words: Do A, Do B, Do C = error. To take an example of this sort of error from other games, by equipping/unequipping items in a certain order managing to generate configurations which shouldn't be possible. With a case like this the devs need to know the steps which generate the problem and any other specifics you can find.

Event errors:
When you’re playing along as normal and something unexpected goes wrong. Again to take from other games: clipping issues - where you fall through an object, or even out of the map entirely (Have seen this happen in several different games). In cases like this where we can't see a specific cause the devs need as much relevant information as possible, what mech was being used?, Map?, location?, and just what was happening which lead up to the issue.

Balancing:
The most unspecific category, yet just as critical. Apart from the inevitably ongoing discussion on weapon balancing there are always other balancing issues to consider, such as mech design and tactics. Remember we want to make it do as many things as possible, but avoid having any one thing be outright superior. Players should be allowed to make 'boating' setups, but they should not be outright better than others: also players should be able to use tactics such as 'scout rush' or running mostly assaults, but if one tactic wins 9 times out of 10 then we have a problem.

So, as you play:
Make sure the devs are aware of any problem you encounter.
Check if anyone else has reported the error before opening a new topic; if they have, just add any new information you can to the existing conversation.
And never forget...

HAVE FUN


Additions suggested in the following conversation:

Blackfire1, on 23 May 2012 - 02:49 AM, said:

When you test TRY to break the game in as many ways as possible and tell the Devs about it asap. If you can break it in testing and it get fixed for later. You probably kept an entire string of errors from popping up.... sometimes.

Edited by ASC, 23 May 2012 - 03:02 AM.

[Stormeris]

Meh, i didnt get a beta key, wasnt expecting to get it either,

Edited by Stormeris, 23 May 2012 - 02:48 AM.

[Blackfire1]

This. I was a member of the Online Beta Testers Guild back in the day. We helped train hobbist who wanted to test games. Teaching them what to look for and how to apply it into a document the devs can use. We used a different format, but general same idea you posted here.
It can be even more helpful if someone has any sort of background in art or IT. I pick up animation/graphics problems alot faster then most simply due to my background. People can use their personal skills to their advantage.

One things I would add is when you test TRY to break the game in as many ways as possible and tell the Devs about it asap. If you can break it in testing and it get fixed for later. You probably kept an entire string of errors from popping up.... sometimes.

Edited by Blackfire1, 23 May 2012 - 02:51 AM.

[Adridos]

Stormeris, on 23 May 2012 - 02:48 AM, said:

Meh, i didnt get a beta key, wasnt expecting to get it either,

They didn't even start handing them out...

[pursang]

There is going to be many face-planting Hunchbacks tomorrow, oh yes.

[ASC]

Blackfire1, on 23 May 2012 - 02:49 AM, said:

One things I would add is when you test TRY to break the game in as many ways as possible and tell the Devs about it asap. If you can break it in testing and it get fixed for later. You probably kept an entire string of errors from popping up.... sometimes.

Absolutely.

[zudukai]

i love pushing boundrys and flying out of the map! i hope i get a key, been here since day one!

[StandingCow]

Adridos, on 23 May 2012 - 02:50 AM, said:

They didn't even start handing them out...

He knows preemptively that he isn't getting one.

[Seagon]

I'm guessing the handouts will commence in what... 3 hours from now approximately?
Just like the usual ISN updates get posted at 9am PDT.

I think i'm going for an easy moment of D3 in the sun!

And... it's always nice for people to create topics like this to remind the ones that are here to only want to play during beta tests to do what they are asked to do rather then just to get a sneak preview and (usually) end up disappointed cause it's not a finished game yet

[sarcasm] Can't wait for all those kind of posts to pop up on the forums after the invites go out. [/sarcasm]

Edited by Seagon, 23 May 2012 - 03:16 AM.

[FoXabre]

This is a very helpful guideline. i just wanted to add that keeping track of the date and time of an issue can help the devs as well (in checking logs, server events, etc).

[ASC]

zudukai, on 23 May 2012 - 03:02 AM, said:

i love pushing boundrys and flying out of the map! i hope i get a key, been here since day one!

I once spent half a Mass Effect 3 multiplayer game about a mile beneath the arena with the graphics freaking out on me. pretty darn funny, but not something i'd like to repeat

[zudukai]

ASC, on 23 May 2012 - 03:14 AM, said:

I once spent half a Mass Effect 3 multiplayer game about a mile beneath the arena with the graphics freaking out on me. pretty darn funny, but not something i'd like to repeat

lol, all the better to.... wait... BUG CHECK!

[Redshift2k5]

I have heard of cases where players given early access to a game found exploits and kept them to themselves for their own gain.

I trust we're all better than that

[Seagon]

Redshift2k5, on 23 May 2012 - 03:27 AM, said:

I have heard of cases where players given early access to a game found exploits and kept them to themselves for their own gain.

I trust we're all better than that

I sure hope everyone is... Though, if not, it will be found eventually and they will hopefully be penalized for their transgressions.

Exploits are game-breakers, and even though Beta testing is all about trying to break the game on purpose so it all can be fixed, on release it should be heavily frowned upon... No Mercy!!!

Edited by Seagon, 23 May 2012 - 03:49 AM.

[Black Mamba]

Redshift2k5, on 23 May 2012 - 03:27 AM, said:

I have heard of cases where players given early access to a game found exploits and kept them to themselves for their own gain.

I trust we're all better than that

Its sad if people do that with this game. I want this game to succeed not only for us but especially for the people who are involved in the production of it. The passion they are showing is expanding in the community and I know it will show when we get our hands on it.

[ASC]

Well...

If i were to see a catapult with an AC/20 or a hunchback with missiles i'm going to at least note the pilot name and watch to see if the config gets reported.

As for more subtle exploits... who knows - but anyone caught messing with the system for personal gain may well get BANNED

[OZYM4NDI4S]

Yeah I never get Beta keys on anything

[adhale2]

Hope I get to test this game! I'm PUMPED!

[Stormeris]

OZYM4NDI4S, on 23 May 2012 - 05:42 AM, said:

Yeah I never get Beta keys on anything

I have gotten a beta key once...for tribes ascend because i "liked" them on facebook...so did everyone

[mechnut450]

so much time on my hands I prolly not get a beta key ( and if i do then I be too busy to play) lol
dang weather screws up everything when don't want it too lol