Skip to content

feat: per-realm scene-listener AoI, and reassignment without reconnecting - #469

Open
robtfm wants to merge 2 commits into
mainfrom
feat/pulse-scene-listener-update
Open

feat: per-realm scene-listener AoI, and reassignment without reconnecting#469
robtfm wants to merge 2 commits into
mainfrom
feat/pulse-scene-listener-update

Conversation

@robtfm

@robtfm robtfm commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Part of decentraland/sdk-multiplayer-server#132 — rollout plan in this comment.

A scene listener announced one realm for the whole connection, and its parcel set was fixed until it reconnected. Neither holds for an authoritative server: it cohosts scenes from several realms at once (every world numbers its parcels from 0,0, so a flat parcel set cannot express two worlds' 0,0), and its scene set changes while it runs. One connection per realm is not an option either — the wallet-unique session rule and the per-IP listener cap both forbid it.

  • SceneListenerAoi { realm, parcel_rects }, repeated on the handshake as field 2 — the old realm/rects are dropped outright, no listener ever shipped on them.
  • SceneListenerUpdate (ClientMessage oneof 9) replaces the announced AoI in place on a live connection: no reconnect, no re-authentication.

Server side: decentraland/Pulse (linked from the plan). Consumed by bevy-explorer (vendored copy, byte-identical) and unity-explorer.

🤖 Generated with Claude Code

…ting

A scene listener announced one realm for the whole connection, and its
parcel set was fixed until it reconnected. Neither holds for an
authoritative server: it cohosts scenes from several realms at once, and
its scene set changes while it runs.

Replace the handshake's `realm` + `parcel_rects` with a repeated
SceneListenerAoi, one entry per realm. Parcels only mean anything inside
a realm — every world numbers its own from 0,0 — so a server cohosting
cozyfarm.dcl.eth and towerofmadness.dcl.eth has two different scenes at
0,0, which a single flat parcel set cannot express. Keying the AoI by
realm keeps that to one connection, which the wallet-unique session rule
and the per-IP listener cap both require.

Add SceneListenerUpdate (oneof 9) to replace the announced AoI in place
on a live connection, so a scene loading or unloading costs neither a
reconnect nor a re-authentication.
@github-actions

github-actions Bot commented Aug 26, 2026

Copy link
Copy Markdown

Test this pull request

  • The @dcl/protocol package can be tested in scenes by running
    npm install "https://sdk-team-cdn.decentraland.org/@dcl/protocol/branch//dcl-protocol-1.0.0-33072149285.commit-3dcb4b1.tgz"

…eserved fields

No scene listener was ever deployed on the single-realm handshake, so
there is nothing on the wire to stay compatible with. Reusing the field
numbers keeps the message at what it would have been written as fresh.
robtfm added a commit to decentraland/bevy-explorer that referenced this pull request Aug 27, 2026
Tracks decentraland/protocol#469: no listener ever shipped on the
single-realm handshake, so the reserved fields go and `aoi` takes
field 2. Presence harness 36/36 against a Pulse rebuilt on the same
proto.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
robtfm added a commit to decentraland/bevy-explorer that referenced this pull request Aug 27, 2026
Tracks decentraland/protocol#469: no listener ever shipped on the
single-realm handshake, so the reserved fields go and `aoi` takes
field 2. Presence harness 36/36 against a Pulse rebuilt on the same
proto.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant