Glorious Alpha Two Testers!
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
Feedback Thread for bug report sceen
BluBOo
Member, Alpha One, Alpha Two, Early Alpha Two
Feel free to add what you think the bug report sceen is missing. The following is what I think:
Missing features:
1. A checkbox to add the player's coordinates.
2. Maybe some kind of overview of the recent bugreports from the player, with the ability to add things like reproduction steps.
3. Locking the controls while the player is in the bug report screen. I frequently cast spells and attack mobs or jump forward into mobs when typing out the coordinates or other things.
4. If not already the case; include a screenshot & maybe add a checkbox for that so the player can decide if its necessary.
4.2. being able to paste an edited/highlighted screenshot from the clipboard
5. Being able to Select NPCs, gatherables, items and other interactive things in the world to pinpoint the important object.
5.1. Being able to bind those selected objects as some kind of hyperlink in the bug report text.
I will edit this if I have additional ideas. Feel free to add your own.
Missing features:
1. A checkbox to add the player's coordinates.
2. Maybe some kind of overview of the recent bugreports from the player, with the ability to add things like reproduction steps.
3. Locking the controls while the player is in the bug report screen. I frequently cast spells and attack mobs or jump forward into mobs when typing out the coordinates or other things.
4. If not already the case; include a screenshot & maybe add a checkbox for that so the player can decide if its necessary.
4.2. being able to paste an edited/highlighted screenshot from the clipboard
5. Being able to Select NPCs, gatherables, items and other interactive things in the world to pinpoint the important object.
5.1. Being able to bind those selected objects as some kind of hyperlink in the bug report text.
I will edit this if I have additional ideas. Feel free to add your own.
4
Comments
Background:
Pre-Alpha weekend and A1 month-long there was a dedicated discord channel for "screenshot bugs" allowing players to share what they were seeing and experiencing as bugs "visually". This was removed eventually, and possibly rightly so as interpreting images to guess what the bug was I'm sure was not as useful and potentially very time consuming to devs. Starting with Alpha weekend the push was to either use the in-game Bug Reporting feature or the Forums for feedback and bug submission; with a strong Community Manager push towards "just report it to us in-game". This led many of us, myself included, to make certain assumption about what additional information the in-game bug reporting feature embeds alongside the free-form text write-up. Later I was informed that my assumption that X,Y,Z, server name, server time, etc. were all captured are incorrect. Hence this post.
Requested Enhancements:
1) Automatically capture the coordinates and information provided that "PageUp" keybind provides automatically with every bug report submission when the bug-report UI is brought up (in case you move while writing report and change it)
2) Automatically include server Name and server localized timestamp (to enable developers finding server log sections easily if needed)
3) Disable the ability to move and cast abilities while the in-game bug report UI is up. When typing the body of the Bug Report it is really annoying to hit a key like "W" or "2" (which on my Mage tends to be Blink) and thus have character move in-game and change the X,Y,Z coordinates of their location which might be critical information to the bug report submission (see #1 above). Don't disable all keybinds though.. often times I need to bring up Quest and Minimap information to provide a good bug-report that really drills down to the actual issue I'm reporting.
4) Add Category DropDown List for categorizing the type of bug being reported (this is more for Intrepid as a QoL feature than submission). Categories could be: "Environment", "Quest", "Raid", "Party", "Combat", "Other" to begin with. For example, "Environment" would cover falling through world, getting stuck, flying trees or other in-game elements, etc.
5) IMPORTANT: Fix the bug report submission bugs - when I spend 10+ minutes writing up a very good bug report and then click submit and get a "Bug Report: Error 6" I get very discouraged. Community Managers say "sorry, that can happen, please wait a little bit and submit again". Well, my 2nd submission is always a worse version of my initial writeup or doesn't ever happen. Please fix this. Add a queue of some sort ahead of the mutex lock on the submission or if that doesn't work, at least cache the bug report text body and if the bug submission is not successful re-populate the text body from the cache when the in-game bug report UI is brought back up.
6) Allow the in-game Bug Report UI frames to be movable in game like all the other pop-up elements (inventory, minimap, etc.)
7) Develop a checkbox on the in-game Bug Report UI that when clicked will include a screenshot of what the player is seeing with the bug report. Default should be unchecked to save space, but allow us to include a screenshot if we believe it helps inform the bug.
Thanks,
Nostra
Other enhancements that would help:
* Auto-completeing nouns throughout the world (NPC names, places, skills/abilities, etc.).
* Screen Shot button, tester looks at issue, hits a button, and it captures field-of-view image and attaches to bug report.
* Add supporting testers. When testing I try to get others to reproduce the issue before reporting. It would be great to be able to have them as a "supporting tester" to help rank the bug report a bit higher for QA.
I also would love feedback from QA on my tickets and a way to see bugs I've reported.
Other enhancements that would help:
* Auto-completeing nouns throughout the world (NPC names, places, skills/abilities, etc.).
* Screen Shot button, tester looks at issue and hits a button and it captures field-of-view image and attaches to bug report.
* Add supporting testers. When testing I try to get others to reproduce the issue before reporting. It would be great to be able to have them as a "supporting tester" to help rank the bug report a bit higher for QA.
I also would love feedback from QA on my tickets.
and then instead of the current suject a title line
also would it be nice that the bug report system automaticly adds the coordination of where the char currently is located, as well information like character name, server, servertime (best if visible fro the reporter)
with an addiontional map on the side where the player can mark the location the bug happend
looking kinda that way
is a quick design with google calc
coordinates displayed character location if map is used to mark the location it switches to the selected locations
If you want higher quality bug reports, give us the tools and make it easy to make them. Having a tool that provides standard info would help devs filter out duplicates, grouping, finding quest/item quicker to verify ticket and provide much needed context when debugging.
Some suggested features:
1. link to forum post of known bugs to help reduce duplicates (nobody keeps this in their head)
2. dropdown list of bug categories (ui, account, quest, pvp, etc...) for basic ticket grouping
3. Have text box auto insert suggested qa format ```
Subject
Description
Include a concise description of the bug, 1-2 sentences max.
Bug Reproduction Steps
Provide the sequence of actions which reproduce the issue that you're seeing reliably (i.e. what were you doing when you encountered this issue?), as clearly as possible.
Expected Result
What was the expected result of the action(s)?
Bug Report - Actual Result
What was the actual result of the action(s)? Please be sure to include any error messaging or relevant diagnostic information.
```
4. auto include player coordinates
5. option to include screenshot for more context
6. list of previous submitted tickets so people can remember what was already done. (like just keep a text file of what they submitted and put it in a list so they can view it)
Nice to have features:
1. ability to link quest by shift clicking on quest log so you can capture better info instead of having to search for quest by name and would get the id's instead
2. link items by shift clicking similar to quests
Other than that, player states before/during bug report should be logged automatically in the bug report for context for the developers. Basic info such as selected quests or list of accepted quests and the player's last few actions.