Skip to main content
PlayFab Samples is a community-driven library of game developer resources. Contributions of all kinds are welcome — whether you’re fixing a bug, improving documentation, or submitting an entirely new sample.
Have an idea for a sample but not ready to build it yourself? Email [email protected] and share what you’d like to see.

​
Ways to contribute

Report a bug

Open an issue on GitHub describing the problem and steps to reproduce it

Request a feature

Suggest a new sample or recipe via the issue tracker

Submit a pull request

Contribute code fixes or new samples directly to the repository

​
Reporting bugs and requesting features

Submit issues and feature requests through the GitHub issue tracker. Before opening a new issue:
  • Search the existing issues to confirm it hasn’t already been reported
  • Provide a detailed description that includes:
    • Which sample or samples are affected
    • The steps required to reproduce the issue
    • The expected and actual behavior
    • The impact (data loss, security concerns, broken functionality, etc.)
    • A minimal code snippet that reproduces the issue, if possible

​
Getting started

1

Fork the repository

Fork Myst0gan1/PlayFab-Samples on GitHub to create your own copy.
2

Clone your fork

Clone your fork to your local machine:
git clone https://github.com/<your-username>/PlayFab-Samples.git
cd PlayFab-Samples
3

Create a branch

Create a new branch for your changes:
git checkout -b feature/my-contribution
4

Make your changes

Implement your fix, improvement, or new sample. Follow the sample requirements below before committing.
5

Submit a pull request

Push your branch to your fork and open a pull request against the development branch of the main repository.

​
Submitting a pull request

Target the development branch when opening your pull request, not master. Write a detailed PR description that explains:
  • What problem the change solves or what it adds
  • Which sample or recipe is affected
  • Any configuration or setup steps a reviewer needs to know about
Not all pull requests will be approved. The team reviews submissions regularly and will update each PR with its status. Accepted PRs will receive guidance on next steps; rejected PRs will include an explanation of why.

​
Pull request checklist

Before submitting, confirm that all of the following apply to your changes:
  • New functionality is fully documented
  • Any new functionality includes complete unit tests
  • All existing unit tests pass
  • Commits are as small and focused as possible
  • No unnecessary changes are included
  • The branch does not require a rebase on top of unrelated work
  • The PR references the issue it fixes (e.g., Fixes #123)
  • The description clearly lists the changes proposed in the pull request

​
Sample and recipe requirements

A good sample or recipe should be immediately usable by another developer. When contributing one, include:
  • A README.md in the sample directory explaining what it demonstrates and how to run it
  • Working, tested code that follows PlayFab best practices
  • Clear setup instructions including any required Title ID configuration or Game Manager steps
  • All dependencies declared (NuGet packages, Unity version, Azure Functions runtime, etc.)
Look at existing samples like Tic Tac Toe or recipes like Prize Wheel as a reference for structure and documentation style.

​
Community feedback

We’re actively building out the library. If you have ideas for samples you’d like to see — even if you’re not ready to build them — reach out at [email protected].

​
License

All contributions to this repository are subject to the MIT License.
Versions of this repository prior to V2.0.0 were licensed under Apache-2.0. Beginning with V2.0.0, all content is licensed under MIT. See LICENSE for full details.

Build docs developers (and LLMs) love

Get started for freeTalk to us