Clarify Mobile Platform Guidance for Game Requests #763

New issue

Open

opened 2026-06-19 13:47:24 -05:00 by Veilor · 0 comments

Veilor commented

2026-06-19 13:47:24 -05:00

Member

The How to Request Games guide should no longer list Oculus/Meta Quest games as Mobile examples because MyVideoGameList has dedicated Meta/Oculus Quest platform entries.

The request guidance should steer users toward selecting the most specific platform available while still explaining when broad mobile categories are appropriate.

Scope

Public How to Request Games support guide copy.
Mobile platform example wording.
Existing links from Support, Knowledge Base, and the request-game page.
Existing request-game form behavior and validation.

Acceptance Criteria

The Mobile guidance no longer lists Oculus/Meta Quest as a mobile example.
The guide still mentions appropriate broad mobile examples such as iOS, Android, older cell phone systems, and Alexa-style cases.
The copy tells users to choose the most specific platform available when one exists.
The support guide remains reachable from the support and knowledge-base pages.
The request-game page continues linking users to the guide before submission.
No request form behavior, database behavior, or admin review workflow changes are introduced by this issue.

Test Coverage Required

Update SupportGameRequestGuidanceTest so Oculus/Meta Quest is asserted absent from the mobile examples.
Preserve assertions for iOS, Android, older cell phone systems, Alexa, and guide discoverability.
Preserve request-game link coverage from the public form and support navigation.
Run focused support guide tests before closing the issue.
Run vendor/bin/pint --dirty --format agent before implementation closeout if PHP files change.

Progress Checklist

Update the How to Request Games platform guidance copy
Remove Oculus/Meta Quest from Mobile examples
Keep broad mobile examples that still match site taxonomy
Preserve support and request-game guide links
Update focused support guide assertions
Run focused support guide tests
Run vendor/bin/pint --dirty --format agent if PHP files changed
Move the issue out of Codex review once verification is complete

The How to Request Games guide should no longer list Oculus/Meta Quest games as Mobile examples because MyVideoGameList has dedicated Meta/Oculus Quest platform entries. The request guidance should steer users toward selecting the most specific platform available while still explaining when broad mobile categories are appropriate. ## Scope - Public How to Request Games support guide copy. - Mobile platform example wording. - Existing links from Support, Knowledge Base, and the request-game page. - Existing request-game form behavior and validation. ## Acceptance Criteria - The Mobile guidance no longer lists Oculus/Meta Quest as a mobile example. - The guide still mentions appropriate broad mobile examples such as iOS, Android, older cell phone systems, and Alexa-style cases. - The copy tells users to choose the most specific platform available when one exists. - The support guide remains reachable from the support and knowledge-base pages. - The request-game page continues linking users to the guide before submission. - No request form behavior, database behavior, or admin review workflow changes are introduced by this issue. ## Test Coverage Required - Update `SupportGameRequestGuidanceTest` so Oculus/Meta Quest is asserted absent from the mobile examples. - Preserve assertions for iOS, Android, older cell phone systems, Alexa, and guide discoverability. - Preserve request-game link coverage from the public form and support navigation. - Run focused support guide tests before closing the issue. - Run `vendor/bin/pint --dirty --format agent` before implementation closeout if PHP files change. ## Progress Checklist - [ ] Update the How to Request Games platform guidance copy - [ ] Remove Oculus/Meta Quest from Mobile examples - [ ] Keep broad mobile examples that still match site taxonomy - [ ] Preserve support and request-game guide links - [ ] Update focused support guide assertions - [ ] Run focused support guide tests - [ ] Run `vendor/bin/pint --dirty --format agent` if PHP files changed - [ ] Move the issue out of Codex review once verification is complete

Veilor added the

status

needs codex review

label

2026-06-19 13:47:24 -05:00