Repository navigation
Clarify Java whitelist console setup and JSON edits - #457
Open
bullishlucas wants to merge 1 commit into
Open
bullishlucas wants to merge 1 commit into
bullishlucas wants to merge 1 commit into
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
This branch was successfully deployed
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.
The Java guide mixes in-game command syntax with panel-console instructions and labels JSON examples as YAML. This change separates the console and in-game forms, adds a group example with a final list check, and explains how to preserve existing JSON entries without trailing commas. It also fixes two typos in the Java section.
Disclosure: I maintain ServerBuddy. The optional roster helper removes duplicate names and flags invalid syntax; the example works without it, and the text explains that syntax checks do not verify account existence. I can remove the optional link while keeping the documentation corrections.
Validation:
npm ciusing the existing lockfile andnpm run buildpassed. All four Java JSON examples parse, the local/whitelistpage returns HTTP 200, and a separate typo/claim review found no blocking issue. The helper was checked with duplicate and invalid names; three valid add commands remained, two invalid entries were excluded, and no UUIDs were generated. The final guide was also inspected in Stagehand.