Version Packages#26
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
kit@2.5.0
Minor Changes
ae1e169: Large-room scale: the guest SDK now supports rooms of up to 1024 players.
used to silently drop
Sendfor a roster index ≥ 16; the per-slot baselinetable is now sized for 1024 consumers but each ~45 KiB slot is allocated on
first commit, so guest linear memory tracks the ACTIVE roster, not the cap.
A broadcast (
Identical) reconciles only allocated slots; a never-sent-toslot recovers via its first send opening with a keyframe (unconditionally
accepted) — the same path as a roster change. No wire/ABI change.
every callback payload, but rosters change only on join/leave/index-shift.
The SDK now skims the member section's raw bytes (new additive
wire.(*Rd).SkipStr) and compares them to the previous callback's: on amatch the previously decoded
[]Playeris reused with zero allocation;only a real roster change re-decodes. This replaces the roster fingerprint
hash (the byte compare is strictly stronger) and removes an O(members)
allocation from EVERY callback — which, under
-gc=leaking, leaked theroster at callback rate and OOM'd long-lived large rooms (~100 KB/callback
at 1000 players). Lifetime contract: the slice from
Room.Members()isvalid for the duration of the callback; copy
Playervalues you retain(long-lived state should be keyed by
AccountID, as before).