About Bug Reports
Posted: Tue Oct 01, 2019 8:00 pm
Folks, let me start out by saying that we're really glad that you're testing our content for us. We're still trying to work out a lot of the details of the game and your testing is helping us.
However.
Because we haven't worked out all the details some things don't work right yet. The problem is that we get a lot of bug reports that are not helpful. We know how the game worked. You don't need to tell us that unless we asked how it worked, and you'll find that here on the forums or in discord.
We also get a lot of bug reports telling us that X happens and that's it. We know sometimes X happens. What were you doing when X happened? What were you fighting? What quest were you on. What abilities were you using. Be specific.
We get a lot of bug reports about getting stuck in combat. Yes we know it's a thing. Why does it happen? We don't know. But if you bug report only saying that you get stuck in combat, you don't help us. Did you have a pet/minion out? Were you using DOTS? What were you fighting, where, and what abilities were you using? Trying to track down "I get stuck in combat" is nearly impossible for us. You aren't helping us when you do that.
Another thing we get a lot of bug reports about: "I've completed a quest and I can't turn in. The questgiver has a blue shield and won't let me turn in." Folks. Read that quest. Every single one of these that I've investigated has required that you turn in with a different NPC than the questgiver. Every one. But because it's a bug report, I still need to investigate it. This is time I could be spending rebuilding the game, not chasing ghosts.
Please, if you're going to use the bug report function, use due diligence. If you see a bug, give us as much info as you can. Check the forums to see if one of the designers has mentioned the issue but can't do anything about it. You would save us a lot of time and trouble just reading quest text.
Again, thank you for your testing. We really do appreciate it. But help us help you, and help us work on VGO. Give us more information.
In addition, here's a general primer of what to test and what not to report: viewtopic.php?f=5&t=3002
However.
Because we haven't worked out all the details some things don't work right yet. The problem is that we get a lot of bug reports that are not helpful. We know how the game worked. You don't need to tell us that unless we asked how it worked, and you'll find that here on the forums or in discord.
We also get a lot of bug reports telling us that X happens and that's it. We know sometimes X happens. What were you doing when X happened? What were you fighting? What quest were you on. What abilities were you using. Be specific.
We get a lot of bug reports about getting stuck in combat. Yes we know it's a thing. Why does it happen? We don't know. But if you bug report only saying that you get stuck in combat, you don't help us. Did you have a pet/minion out? Were you using DOTS? What were you fighting, where, and what abilities were you using? Trying to track down "I get stuck in combat" is nearly impossible for us. You aren't helping us when you do that.
Another thing we get a lot of bug reports about: "I've completed a quest and I can't turn in. The questgiver has a blue shield and won't let me turn in." Folks. Read that quest. Every single one of these that I've investigated has required that you turn in with a different NPC than the questgiver. Every one. But because it's a bug report, I still need to investigate it. This is time I could be spending rebuilding the game, not chasing ghosts.
Please, if you're going to use the bug report function, use due diligence. If you see a bug, give us as much info as you can. Check the forums to see if one of the designers has mentioned the issue but can't do anything about it. You would save us a lot of time and trouble just reading quest text.
Again, thank you for your testing. We really do appreciate it. But help us help you, and help us work on VGO. Give us more information.
In addition, here's a general primer of what to test and what not to report: viewtopic.php?f=5&t=3002