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

feat: dedicated game server sample - upgrade to multiplayer services sdk [MTT-11329] #274

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from

Conversation

fernando-cortez
Copy link
Collaborator

@fernando-cortez fernando-cortez commented Mar 3, 2025

Description

This PR integrates the Multiplayer SDK to the Dedicated Game Server Sample.
Introduced are a few key changes to the sample's workflow. There are now 4 new Play Mode Scenarios:

  • EditorAsClient: One Virtual Player is Server and autoconnects with IP. Editor and all other Virtual Players are Clients that autoconnect with IP.
  • EditorAsServer: Editor is Server and autoconnects with IP. All Virtual Players are Clients that autoconnect with IP.
  • DeployToUGS: Deploys a remote instance of a build to a fleet defined inside your environment.
  • Live: All Virtual Players are Clients.

The first 2 are meant to server as quick feature validation scenarios, using direct IP connection. DeployToUGS deploys a build to the user's Cloud environment, where they are able to validate a server being allocated -- once allocated, they are able to connect via Direct IP, as shown in the Play Mode Status Window. The last, Live, validates the live workflow, where each client connects through the UI, with sessions/matchamaker tickets.

To validate the PR, go through each play mode scenario, making sure you switch to the appropriate build profile in the Editor.

Issue Number(s)

MTT-11329
MTT-7778
MTT-7777

Contribution checklist

  • [ N/A ] Tests have been added for the project and/or any internal package
  • [ N/A ] Release notes have been added to the project 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

@fernando-cortez fernando-cortez marked this pull request as ready for review March 3, 2025 21:57
@fernando-cortez fernando-cortez requested a review from a team as a code owner March 3, 2025 21:57
@RikuTheFuffs
Copy link
Contributor

There's a lot of changes in this PR that do not seem related to its scope. I see changes in Starter assets, prefabs and sounds. Are these changes on purpose, or were they pushed by mistake?

@fernando-cortez
Copy link
Collaborator Author

There's a lot of changes in this PR that do not seem related to its scope. I see changes in Starter assets, prefabs and sounds. Are these changes on purpose, or were they pushed by mistake?

I did update packages to the latest recommended version, and that included Starter Assets, so its packaged assets were updated.
I could split those out as individual PRs if you'd like. But since NGO components were upgraded, it was nice to have those changes included in one go with the art side of changes.

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.

2 participants