Skip to content

Conversation

@simon-lemay-unity
Copy link
Contributor

Purpose of this PR

As the title says, this PR makes NetworkMetricsPipelineStage public. This is required if you want to use custom drivers that are compatible with the multiplayer tools package as you need to register that pipeline stage before it can be used to create pipelines.

Jira ticket

N/A

Changelog

  • Added: The NetworkMetricsPipelineStage for Unity Transport is now part of the public API. This allows using it in custom implementations of INetworkStreamDriverConstructor that want to maintain compatibility with the multiplayer tools package.
  • Fixed: Prevented a NullReferenceException in UnityTransport when using a custom INetworkStreamDriverConstructor that doesn't use all the default pipelines and the multiplayer tools package is installed.

Documentation

  • Includes documentation for previously-undocumented public API entry points.
  • Includes edits to existing public API documentation.

Testing & QA (How your changes can be verified during release Playtest)

Functional Testing

Manual testing :

  • Manual testing done

Automated tests:

  • Covered by existing automated tests
  • Covered by new automated tests

Does the change require QA team to:

  • Review automated tests?
  • Execute manual tests?
  • Provide feedback about the PR?

Backports

N/A

@simon-lemay-unity simon-lemay-unity requested review from a team as code owners January 22, 2026 16:01
/// </summary>
[BurstCompile]
internal unsafe struct NetworkMetricsPipelineStage : INetworkPipelineStage
public unsafe struct NetworkMetricsPipelineStage : INetworkPipelineStage
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that due to this change you should bump package version in package.json to 2.9.0. But vetting test should verify this (will fail if you should bump it)

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.

3 participants