RetroAchievements / RetroAchievements/docs

Better rules required for netplay

Open
#341 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
48
Forks
94
Avg merge
8h 9m
Merged PRs (30d)
13

Description

RetroAchievements currently has a bit of a "blind spot" when it comes to netplay.

Picture the following: 2 users initiate a netplay session for Super Mario 64. Player 2 is logged in to RetroAchievements. They (player 2) are not playing. Super Mario 64 is a one-player game. rcheevos has no idea this is a netplay session, or whether the local player is player 1 or player 2. rcheevos just sees stars being collected on both machines.

Therefore, player 2 will start earning achievements, even though they are not playing; they are simply spectating.

My suggestion:

  • For hardcore, emulators should need to indicate to rcheevos/RA API that the session is a netplay session.
  • In hardcore, if it is a netplay session, achievements should only be earned on subsets that have been marked as "netplay approved" (for example, the Mario Kart 64 Multiplayer Subset).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by clarifying how emulators should signal netplay sessions, how rcheevos or the RA API would consume that signal, and where "netplay approved" subsets are defined. Done requires an agreed, documented rule set and implementation scope.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.