The easiest way to do this is to launch the game and hit "Play" on the main menu, which will try to take you to the lobby. Make sure you have the latest SpyParty build.
Unfortunately, where they're saved differs by operating system, so at the bottom of this post is a guide for finding them. SpyParty saves a bunch of useful information for helping me fix bugs, including logs, screenshots, and replays. The basic rule is one thread per distinct bug. I'll be updating these steps as the beta proceeds, and eventually I'll switch this part of the forum over to a real bug database, but for now, threads in this forum will have to do.
In other words, it's more important to report the bug poorly than it is to not report it at all, but a good repro makes a huge difference. This does not mean you shouldn't report bugs that don't always happen the same way or happen infrequently, or that you can't get a good repro for, but it does mean those bugs will be much harder for me to fix. It's basically a recipe to make the buggy behavior happen for you (and me!). So, when posting a bug report, the key is to do some work on your end to be methodical and give steps to repro the bug as simply and as clearly as you can. It can be the difference between 10 minutes to fix and 10 days to fix, literally. A bug that doesn't repro is very hard to fix, whereas a bug with a "good repro" is usually pretty trivial to fix. The goal of a bug report is to describe the steps to reproduce the buggy behavior (whether it's a crash that deletes your entire hard disk or it's a word that's not pluralized correctly in the user interface somewhere) well enough that I can step through them on my machine and see the behavior first-hand.
0 kommentar(er)
