Replies: 2 comments 1 reply
-
|
I now have access to our S3 bucket and plan on investigating how feasible direct uploads of save states might be in the near future. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Things to consider:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As we are nearing 3,000 open tickets, having a way to quickly identify low hanging fruit would be very helpful to efficiently reduce volume. By far the biggest barrier to fixing a ticket is being able to reproduce the issue and save states/file are the shortcuts to enable this.
I'm envisioning a game's ticket page would have some sort of new column/indicator to communicate if a link to a save state download was provided via a new "action" on the ticket itself. This would allow players interested in helping to see which achievements need states and they could collect them as they played through and submit a link to a save file that would be captured on the ticket page.
Kindergarten mock ups aside, I think this would encourage some players to check out the open tickets before they begin playing the set and be more likely to submit a state for a known problematic achievement. This could be combined with some sort of point system either now or later to reward players who submit states and has a lot of overlap with the idea proposed in #1579
It also would help developers know that a state was available which should lead to significantly more ticket fixes, especially during events like Devember and make DQ1 more accessible.
Beta Was this translation helpful? Give feedback.
All reactions