Updating NetcodeSamples to latest version after N4Ev1.9.0 release #301
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
BrianWill-Unity
approved these changes
Sep 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PR purpose
This PR is a step towards automating and improving the quality of NetcodeSamples and updates them to the latest version.
NetcodeSamples were not updated since long time so amount of files is quite a lot (each next time the amount should be managable)
Note that we removed Asterids/CI folder since it's not needed for the users and creates unnecessary noise
Future Plans
Note that N4E has different and faster release schedule to other DOTS packages so we aim to update NetcodeSamples together with each release, making sure that latest changes/improvements/corrections and landing to our users as soon as possible.
Because of that the PR creation will be automated and timing will be the same as branching to new release. The PR will be a draft and as soon as we release the person responsible for the release will open the PR and make sure that the changes land and are correct