I am sure we are all excited to get in to the beta test, and I am not sure if such guide exists on the beta forums. But if you make it into the beta and aren't exactly sure how you can assist Zenimax improving their game, here are few things to remember:


Discovering a bug:
- Don't just write to your report that you "ran into few bugs." Once you discover a bug, anolyze its status. Is it something ground-breaking or a minor one? How did it affect your gameplay? Test the bug out, attempt to reproduce it, write down its location and how you encountered the bug. What was your expected result? And what truly happened. If you fail to reproduce the bug, make sure you mention it, that typically means its a more tricky one to fix.

Discovering a graphical glitch:
- Again, make sure you mark down its location, but more importantly; How badly did it affect your game play? Was a piece of hay just floating in the air, or was there a way to exploit the graphical glitch? (Example a floating rock you could use to kill the NPC's without trouble).

Voicing your opinion:
- Make sure you provide rational arguments. Let's say you feel a spell is too powerful; anolyze its contents, but your emotions aside and truly think it from the game mechanics perspective. Always provide some valid proof or argument to support your claims. That way the feed back is more efficient. Strong and shallow opinions make a ton of difference. You say you had fun, why did you have fun? You got bored? Provide information why you got bored. Just stating you had fun / got bored provides nothing but one shallow opinion, but if someone writes a two-page essay explaining why he had fun and what made him bored gives the developer's real perspective of whats there to improve.

The writing point:
- Lets say you found the game difficult to handle. Provide your gaming background, it makes a ton of difference whether the combat system felt difficult for a first time MMORPG & TES gamer versus a veteran MMORPG player and a TES fan. No one is going to flame you for it, but it provides developer's with more accurate feed back.

Suggestions:
- If you feel something is wrong, and you have an opinion to solve the issue. Write down the opinion and the arguments backing your opinion. Not only this again makes the feed back more efficient, clear and more believable, it also provides some proof for your claims and provides depth to your anolysis.

Think of reporting stuff like essays, you need the sources, you need proper arguments or otherwise your whole essay will be shallow and null.