Clarify native multiplayer development versus public submission - #6
Draft
VelizarSeleznev wants to merge 1 commit into
Draft
VelizarSeleznev wants to merge 1 commit into
VelizarSeleznev wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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
1 participant
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.
An agent with a native multiplayer development build currently follows the public SDK prompt into legacy GDScript stubs and PCK submission, then treats the production playback limitation as proof that its staging environment cannot work. Add an early environment distinction to the agent entry pages and SDK hub, with native development requirements on the existing canonical status page.
The guidance identifies the editor/API, publication, build/release, and per-device launcher inputs needed before an online test; it permits useful development while reporting the specific missing launch prerequisite. It preserves all production capability disclosures and does not advertise general staging access, invent public bootstrap URLs, or present a local prototype as completion of cross-device gameplay.
Validation:
npm run checkpasses (compatibility, language, capability policies, policy mutation fixtures, routes, docs links);git diff --checkpasses. The three orphan-page warnings predate this change. This documentation clarification does not deliver a self-service native installer or hosted launch flow.