Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: v2.5.0 #887

Merged
merged 9 commits into from
Apr 18, 2024
Merged

release: v2.5.0 #887

merged 9 commits into from
Apr 18, 2024

Conversation

fernando-cortez
Copy link
Collaborator

@fernando-cortez fernando-cortez commented Apr 17, 2024

Description

v2.5.0 release changes including changelogs, readme, and project version.

Issue Number(s)

MTT-8318

Contribution checklist

  • [ N/A ] Tests have been added for boss room and/or utilities pack
  • Release notes have been added to the project changelog file and/or package changelog file
  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • JIRA ticket ID is in the PR title or at least one commit message
  • Include the ticket ID number within the body message of the PR to create a hyperlink
  • An Index entry has been added in readme.md if applicable

fernando-cortez and others added 9 commits February 13, 2024 14:32
)

* removed NetworkObject from scene state game object

* Applied network object removal to prefab

* Update Changelog.md

* Update CHANGELOG.md PR commit number
#880)

* Added null reference check to ClientInputSender script

* Fixed whitepsace issue

* Update CHANGELOG.md

* Update CHANGELOG.md pr number

* Revert "Fixed whitepsace issue"

This reverts commit edc03c3.

* fix line 478

* Update CHANGELOG.md

Co-authored-by: Fernando Cortez <[email protected]>

---------

Co-authored-by: Fernando Cortez <[email protected]>
…87] [MTT-5711] (#879)

* changed sort layer of popup panel to bring it to the front

* panel sort order adjustments to fix RNSM hidden under loading screen issue

* fix settings UI order

* changed UI canvas sort order to -1 to fix small issue

* Update CHANGELOG.md with PR number

* Revert "changed UI canvas sort order to -1 to fix small issue"

This reverts commit d399dc8.

* changed MainMenu UI Canvas to -1

* adjusted sort order according to jils suggestion

Sort Orders:
PopUpPanel = 1
Loading Screen = 0
SettingsPanel Canvas = -1
Boss Room HUD = -2
Main Menu UI Canvas = -3
UI Root (PostGame) = -3

* update NetStatsMonitorPrefab sort order to -3

fixed that it does not block join game option on startup

* updated CharacterSelectCanvas sort order to -2

* changed NSMPCanvas to scale with screen size and adjusted text size to 45

* addressed feedback and adjusted RNSM size, created UIRoot prefab

* added UI toolkit theme to make new RNSMSettings asset work

* enabled sort order override and adjusted sorting order of MessageWindow.prefab to -1 and renamed UIRoot to PostGameUICanvas
…sembly includes Unity.Collections [MTT-8188] (#883)

* upgrade to NGO v1.8.1, conversion to universal Rpcs, utility assembly includes Unity.Collections

* fix for connected clients receiving new shutdown message from host

* Utilities package also upgraded to NGO v1.8.1

* changelog additions

* readme badge with NGO upgrade updated

* added Server/Client prefixes for previous Rpc methods

* update to Utilities changelog

* using RpcTargetUse Temp since clientId may change frequently
* upgrade to 2022.3.22f1 LTS

* changelog addition

* setting yamato tests to 2022.3

* fixing the ClientLoadingScreen ondestroy null reference
…onizations [MTT-3152] (#886)

* ClientPlayerAvatarNetworkAnimator introduced to handle client syncs

* reformat class

* format

* changelog addition
@fernando-cortez fernando-cortez added the 1-Needs Review PR needs attention from the assignee and reviewers label Apr 17, 2024
@fernando-cortez fernando-cortez requested a review from a team as a code owner April 17, 2024 20:14
@Elfi0Kuhndorf
Copy link
Contributor

The changes and version numbers look good to me! The only thing I found were the errors (see picture below) when trying to join in a build with the same profile (does not let you as profile already used) and then changing to another profile and joining (now being allowed to join). Is this error expected?

image

@fernando-cortez
Copy link
Collaborator Author

@Elfi0Kuhndorf

The changes and version numbers look good to me! The only thing I found were the errors (see picture below) when trying to join in a build with the same profile (does not let you as profile already used) and then changing to another profile and joining (now being allowed to join). Is this error expected?

So the flow seems like it's correct? If so, let's create a ticket to review that error being logged post-release.

@fernando-cortez fernando-cortez merged commit 74afaeb into main Apr 18, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-Needs Review PR needs attention from the assignee and reviewers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants