Mythic+ Party Shuffle

v0.5.1 (2026-06-14)

Full Changelog Previous Releases

• refactor(comm): drop redundant VISIBILITY on the resync answer
  The resync answer re-announces CREATE with meta = self.event, which already
  carries the current arePartiesVisible; the CREATE handler stores it
  unconditionally (self.event = p) and every visibility read goes through
  ArePartiesVisible() -> GetEventMeta(). The trailing VISIBILITY message just
  repeated it, costing one message per resync answer under the per-prefix
  throttle.
  Remove the VISIBILITY send from the ROSTER_REQ answer and from the organizer
  RestoreSession. The live-toggle VISIBILITY (SetPartiesVisible) is unchanged —
  it remains the only path to propagate a visibility change to already-synced
  participants. No wire-format change, no PROTOCOL_VERSION bump.
  Tests: comm-reconnect updated to assert the re-announced CREATE carries the
  current meta.arePartiesVisible (instead of a separate VISIBILITY), plus a new
  "late joiner converges on visibility from the CREATE meta alone". 158/158
  green. Spec synced (comm-protocol) and change archived.
  Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com