Repository navigation
feat(proxy): support standalone server-list templates - #104
Merged
Merged
Conversation
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.
Evaluates the standalone server-list schema for MOTD text, protocol notices, icons, player rules and hover text. Every proxy uses network-wide presence and cached configuration; maintenance overrides inherit independent fields, invalid refreshes retain the last valid snapshot, and placeholders resolve before native text effects and alignment.
Supports the schema-1 documents compiled by
@groundsgg/motd@0.1.1, retaining compatibility with legacy text fields and commands. Ping evaluation samples time once and tolerates concurrent maintenance refreshes, avoiding a null protocol-name failure at the end boundary.Validation: 182 Velocity check/build tests pass on Java 25, including regressions that reproduced both boundary/refresh failures before the fix. An isolated two-Velocity TCP harness verifies shared counts despite different local counts, regional placeholders, icons/hover, count rules, maintenance transitions, invalid refreshes and protocol-specific alignment.
Rollout uses the immutable main-build
sha-*image and updates all Java and Bedrock proxy instances after the JAR server converges. No maintenance activation is part of validation.