Repository navigation
zdxsv docs: split release features from development and rig paths - #656
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
docs/zdxsv/features.md: new section "Development and rig paths" with the features a release does not run (TCP battle to the battle server, playing as a console, console behind zproxy, GGPO with a fake lobby, GGPO without servers, GGPO synctest). "Online without DEV9" no longer claims a TCP battle.docs/zdxsv/lobby.md: the battle server connect is refused without DEV9; real PS2 consoles still battle on the battle server.Rationale behind Changes
A release always has a server host, so the game takes the No DEV9 path, where
NoDev9.cpprefuses every connect but port 8200 and battles run only over GGPO. The online feature list mixed that product behavior with DEV9-path rig scaffolding. Feature names are unchanged, sotests/zdxsv/README.mdstill maps one to one.Suggested Testing Steps
Docs only. Checked against the code (
NoDev9.cppConnect,LobbyConnection.cppplatform info switch). No build or rig run. Applies cleanly on top of PR 655 (same files, separate hunks).Did you use AI to help find, test, or implement this issue or feature?
Yes: written by an AI agent (Claude Code) from a docs review.
🤖 Generated with Claude Code