Pyrocat
01-26-2011, 04:20 AM
So, you want to be a beta tester?
Good! The work put in by beta testers and the development staff are the reason this server is the closest thing to classic Everquest in existence! Beta testing is the number one way to contribute to this server, outside of donating directly (http://www.project1999.com/index.php?pageid=donations), so please take some time out of your regularly scheduled entertainment and help out. The hours, minutes, and even seconds you spend beta testing and writing detailed bug reports, the less legwork P99 developers have to do, which means content gets fixed faster. Want Velious out ASAP? Beta Test! In nilbog's own words:
If each person researched a mob and found needed classic changes, I'd spend my time implementing fixes instead of researching (content would be finished sooner).
Imagine the possibilities :P
Now I wish I could say that every bug report ever written has helped the server, but sadly, poorly written and inaccurate bug reports can end up wasting far more time than they save. There are a lot of "best practices", guidelines, and just plain common sense that people are unaware of that can really make a developers day. So if you want to see nilbog with a :D instead of a :mad: I've written this guide to help make better bug reports and hopefully make every devs job a little easier. So without further adieu,
Guide to Better Beta Testing Today
There is a method to the madness! You want your bugs to be:
Legible!
Reproducible!
Well researched!
So how do you start? Well, chances are you've already run into a bug either on the Project 1999 "live" server, or the test server, which is located here:
http://img155.imageshack.us/img155/8876/betatestguideserversele.png
If you haven't, go ahead and log onto the test server and start messing around until you run into one. Test out features and content that aren't live yet, level up an Iksar, do quests that you think no one else has done. Eventually you will run into something "not quite right". Either a quest turn in will break, or an NPC won't respond to hail text, or a spell won't work right, or a monster will have too little hp .etc .etc. Now that you've found a bug, what do you do about it?
Do a quick search to make sure no one else has posted this bug, no need to re-post something that's already been documented (or resolved!)
Start writing! Click that "new thread" button and write down the exact steps that someone would need to follow to recreate the bug. Be descriptive, and legible! No one wants to read a wall-of-text that is all lower case with no punctuation and no paragraphs. Wall-of-texts are otherwise encouraged, if the bug warrants it.
Take screenshots of everything related to the bug (and upload them!)
Gather locs of all the relevant NPCs, pathing beginning/ending points, and anything else that seems appropriate (type /location to get the coordinates of where your character is standing).
Do your research and figure out the correct behavior for whatever is wrong. This can be as simple as posting a link to the allakhazam quest or as complex as digging through decade-old forum posts to prove that a certain mechanic actually worked that way in 1999. Be wary of the 'I remember' trap! "I remember soandso from when I played on live" is not a substitute for evidence, and doesn't help as much as you might think. If you remember something, go find evidence to back it up!
Make sure to post it in the correct forum!
Anatomy of a Bug Report
When you create your bug report, try and follow the format of Zone - Quest/NPC name + bug summary for the thread title. For example, "LOIO - Crusader Quarg is pathing into a wall" would be a great thread title for a bug. For your copy-pasting pleasure, I've created a BBC code template that you can use for any bug report you create.
Description:
Relevant NPCs:
Relevant LOCs:
Steps to reproduce bug:
Expected behavior:
Evidence/Research:
Relevant screenshots:
Beta Testing FAQ
How do I know it's a bug?
It should be fairly obvious in most cases, as the vast majority of players on this server have played Everquest before and know what is expected and what is broken. However, there are some more subtle cases, such as a mob being easier to kill than you remember. The best thing to do in these cases is research and talk to other players.
How do I research if something was classic or not?
It just so happens that nilbog already wrote a very informative thread (http://www.project1999.com/forums/showthread.php?p=42710) on this subject. I highly recommend everyone read it (http://www.project1999.com/forums/showthread.php?p=42710). Additionally, you can find old patch history for the classic era (1999 through December 2001) here:
http://everquest.allakhazam.com/history/patches.html
http://www.tski.co.jp/baldio/patch/
Where do I post?
If it's a bug from the live Project 1999 server that isn't specific to Kunark, post in the Bug Forum (http://www.project1999.com/forums/forumdisplay.php?f=6). If it's from the something in Kunark, post in the relevant subforum of the Kunark Forum (http://www.project1999.com/forums/forumdisplay.php?f=47). Quest bugs go in the Quest subforum, Pathing bugs go in the Pathing subforum .etc .etc. Use your best judgement.
How do I upload screenshots of the bug?
The Project 1999 forums support uploading images, just click the "manage attachments" button when you are creating a new thread. Otherwise, you can use a free image uploading service such as http://imageshack.us/ or http://www.yfrog.com/, either works and they are both quick to upload.
Good! The work put in by beta testers and the development staff are the reason this server is the closest thing to classic Everquest in existence! Beta testing is the number one way to contribute to this server, outside of donating directly (http://www.project1999.com/index.php?pageid=donations), so please take some time out of your regularly scheduled entertainment and help out. The hours, minutes, and even seconds you spend beta testing and writing detailed bug reports, the less legwork P99 developers have to do, which means content gets fixed faster. Want Velious out ASAP? Beta Test! In nilbog's own words:
If each person researched a mob and found needed classic changes, I'd spend my time implementing fixes instead of researching (content would be finished sooner).
Imagine the possibilities :P
Now I wish I could say that every bug report ever written has helped the server, but sadly, poorly written and inaccurate bug reports can end up wasting far more time than they save. There are a lot of "best practices", guidelines, and just plain common sense that people are unaware of that can really make a developers day. So if you want to see nilbog with a :D instead of a :mad: I've written this guide to help make better bug reports and hopefully make every devs job a little easier. So without further adieu,
Guide to Better Beta Testing Today
There is a method to the madness! You want your bugs to be:
Legible!
Reproducible!
Well researched!
So how do you start? Well, chances are you've already run into a bug either on the Project 1999 "live" server, or the test server, which is located here:
http://img155.imageshack.us/img155/8876/betatestguideserversele.png
If you haven't, go ahead and log onto the test server and start messing around until you run into one. Test out features and content that aren't live yet, level up an Iksar, do quests that you think no one else has done. Eventually you will run into something "not quite right". Either a quest turn in will break, or an NPC won't respond to hail text, or a spell won't work right, or a monster will have too little hp .etc .etc. Now that you've found a bug, what do you do about it?
Do a quick search to make sure no one else has posted this bug, no need to re-post something that's already been documented (or resolved!)
Start writing! Click that "new thread" button and write down the exact steps that someone would need to follow to recreate the bug. Be descriptive, and legible! No one wants to read a wall-of-text that is all lower case with no punctuation and no paragraphs. Wall-of-texts are otherwise encouraged, if the bug warrants it.
Take screenshots of everything related to the bug (and upload them!)
Gather locs of all the relevant NPCs, pathing beginning/ending points, and anything else that seems appropriate (type /location to get the coordinates of where your character is standing).
Do your research and figure out the correct behavior for whatever is wrong. This can be as simple as posting a link to the allakhazam quest or as complex as digging through decade-old forum posts to prove that a certain mechanic actually worked that way in 1999. Be wary of the 'I remember' trap! "I remember soandso from when I played on live" is not a substitute for evidence, and doesn't help as much as you might think. If you remember something, go find evidence to back it up!
Make sure to post it in the correct forum!
Anatomy of a Bug Report
When you create your bug report, try and follow the format of Zone - Quest/NPC name + bug summary for the thread title. For example, "LOIO - Crusader Quarg is pathing into a wall" would be a great thread title for a bug. For your copy-pasting pleasure, I've created a BBC code template that you can use for any bug report you create.
Description:
Relevant NPCs:
Relevant LOCs:
Steps to reproduce bug:
Expected behavior:
Evidence/Research:
Relevant screenshots:
Beta Testing FAQ
How do I know it's a bug?
It should be fairly obvious in most cases, as the vast majority of players on this server have played Everquest before and know what is expected and what is broken. However, there are some more subtle cases, such as a mob being easier to kill than you remember. The best thing to do in these cases is research and talk to other players.
How do I research if something was classic or not?
It just so happens that nilbog already wrote a very informative thread (http://www.project1999.com/forums/showthread.php?p=42710) on this subject. I highly recommend everyone read it (http://www.project1999.com/forums/showthread.php?p=42710). Additionally, you can find old patch history for the classic era (1999 through December 2001) here:
http://everquest.allakhazam.com/history/patches.html
http://www.tski.co.jp/baldio/patch/
Where do I post?
If it's a bug from the live Project 1999 server that isn't specific to Kunark, post in the Bug Forum (http://www.project1999.com/forums/forumdisplay.php?f=6). If it's from the something in Kunark, post in the relevant subforum of the Kunark Forum (http://www.project1999.com/forums/forumdisplay.php?f=47). Quest bugs go in the Quest subforum, Pathing bugs go in the Pathing subforum .etc .etc. Use your best judgement.
How do I upload screenshots of the bug?
The Project 1999 forums support uploading images, just click the "manage attachments" button when you are creating a new thread. Otherwise, you can use a free image uploading service such as http://imageshack.us/ or http://www.yfrog.com/, either works and they are both quick to upload.