RetroAchievements / RetroAchievements/RABot
[Feature]: Gameplay Check upon UWC Report
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Problem or Use Case
There's been a decent number of (invalid) unwelcome concept reports coming in from players that haven't played the game they're reporting, and have very little experience with RetroAchievements overall. While the reports are still useful, it would be nice to give extra consideration to reports from players that have actually played the set.
Proposed Solution
Would be be possible to have RABot let us know when a UWC report comes in if the player has ever booted the game that they're reporting an achievement from? I'd assume a check for any session should be fine - can't rely on unlocks in case someone reset, and we don't want to outright disallow reports from players who haven't played a game on RA.
If possible, it'd be great for it to provide unlock counts and game session time as well, but even just knowing "has the reporter attempted this game" is useful info.
Alternative Solutions
We can check manually by looking at the reporter's completion progress, but it's a lot of work.
Command Type Preference
Not applicable
Feature Scope
Team members only
Usage Examples
No response
Additional Context
No response
Checklist
- I have searched existing issues to ensure this feature hasn't been requested
- This feature would be useful to multiple users, not just me
- I have provided clear use cases and examples
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the UWC report handling entry point and how RABot accesses reporter and game data. Determine whether session history, unlock counts, and game session time are available for the reported game. Done means team members receive a useful gameplay check when a UWC report arrives, without blocking reports from players who have not played the game.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100