This repository contains complete working samples that demonstrate best-practice usage patterns for PlayFab features.
| Sample | PlayFab features |
|---|---|
| Fantasy Soccer Web Application | OpenID/Playfab Login, Economy, Inventory management, Automation |
| PlayFab Azure B2C integration using custom policies | Custom ID login/registration |
| PlayFab Azure B2C integration using ASP.NET Core Identity | Login, MSIdentity |
| Multiplayer Tic-Tac-Toe | Matchmaking Queues, Shared Group, Login |
| P2P Multiplayer Tic-Tac-Toe | Matchmaking Queues, PlayFab Party, Login |
The Multiplayer Tic-Tac-Toe sample demonstrates how to configure a multiplayer Tic-Tac-Toe game using Unity, PlayFab, Azure Services and Cosmos DB.
This project also has a set of specifics instructions on how to implement these features:
- How to turn a single player game into multiplayer.
- How to support Match Lobbies in a multiplayer game.
- This includes an integration with Cosmos DB to support Match Lobby listing.
As PlayFab's documentation states, Shared Group Data should not be used by groups larger than a dozen or so players, at most.
- Matchmaking Queues. Used to match random players together.
- Shared Group. Used to store the game state, and for manual matchmaking through Match Lobbies.
- Basic Login. Used to identify each game instance as a different user.
The P2P Multiplayer Tic-Tac-Toe sample demonstrates how to configure a multiplayer Tic-Tac-Toe game using Unity, PlayFab, Azure Services and Cosmos DB.
This project also has a set of specifics instructions on how to implement these features:
- How to support Match Lobbies in a multiplayer game.
- How to turn a single player game into multiplayer.
- How to use PlayFab Party to manage communication between players.
- Matchmaking Queues. Used to match random players together.
- PlayFab Party. Used to manage most communications between players during the game.
- Basic Login. Used to identify each game instance as a different user.
Got ideas for samples that you would like to see developed? Let us know at [email protected].
This repository is covered under the MIT License.