Skip to content

Docs: note SetReply slot is absent on special _read keys#6264

Open
patrickwehbe wants to merge 1 commit into
ArchipelagoMW:mainfrom
patrickwehbe:docs/setreply-slot-optional
Open

Docs: note SetReply slot is absent on special _read keys#6264
patrickwehbe wants to merge 1 commit into
ArchipelagoMW:mainfrom
patrickwehbe:docs/setreply-slot-optional

Conversation

@patrickwehbe

Copy link
Copy Markdown
Contributor

What is this fixing or adding?

Fixes #5829.

The SetReply documentation listed the slot argument unconditionally, but the server only includes it when the SetReply is triggered by a client Set packet (the Set handler in MultiServer.py). The server-generated SetReplies for the special _read_hints_{team}_{slot} and _read_client_status_{team}_{slot} keys — sent from on_changed_hints and on_client_status_change — do not include slot (nor original_value).

This mirrors the caveat already documented on the original_value row, keeping the two entries consistent.

How was this tested?

Documentation-only change. Verified against MultiServer.py on main: slot is set only in the Set command handler and is not added in the on_changed_hints / on_client_status_change broadcast paths, so it is absent for the _read_-prefixed special keys (same as original_value). No code paths are affected.

@github-actions github-actions Bot added is: documentation Improvements or additions to documentation. waiting-on: peer-review Issue/PR has not been reviewed by enough people yet. labels Jun 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

is: documentation Improvements or additions to documentation. waiting-on: peer-review Issue/PR has not been reviewed by enough people yet.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: Mismatch between Docs and MultiServer's behavior for SetReply

1 participant