GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - dylanh724/JavaScriptSDK: JavaScriptSDK for the Client API of PlayFab

BranchesTags
Open more actions menu
 
 

Latest commit

 

History

117 Commits
117 Commits

Folders and files

NameName
Last commit message
Last commit date
PlayFabSDK
PlayFabSDK
 
 
code.jquery.com/qunit
code.jquery.com/qunit
 
 
licenses
licenses
 
 
.arcconfig
.arcconfig
 
 
.gitignore
.gitignore
 
 
LICENSE
LICENSE
 
 
PlayFabApiTest.html
PlayFabApiTest.html
 
 
PlayFabApiTest.js
PlayFabApiTest.js
 
 
README.md
README.md
 
 

Repository files navigation

JavaScriptSDK README

  1. Overview:

JavaScriptSDK for the Client API of PlayFab

  1. Prerequisites:

  • Users should be very familiar with the topics covered in our getting started guide.

To connect to the PlayFab service, your machine must be running TLS v1.2 or better.

  • For Windows, this means Windows 7 and above
  • Official Microsoft Documentation
  • Support for SSL/TLS protocols on Windows
  1. Example Project: PlayFabApiTest.html & PlayFabApiTest.js:

These files are an internal PlayFab testing project, which activates and tests the core functionality of the sdk. They are not part of the sdk. You should delete these two files before integrating the sdk with your project.

They require a testTitleData.json file to exist, which is described below.

  1. testTitleData.json file required for example test files.

This sdk includes an optional example project that is used by PlayFab to verify sdk features are fully functional. The testTitleData.json file provides your secret title information to the unit-test project, so it can execute tests in your own PlayFab title.

The format is as follows:

{
	"titleId": "your Game Title ID, found in the settings/credentials section of your dashboard on the website",
	"developerSecretKey": "your PlayFab API Secret Key, found in the settings/credentials section of your dashboard on the website - NEVER SHARE THIS KEY WITH PLAYERS",
	"titleCanUpdateSettings": "false",  // "true" or "false", based on your Allow Client to Post Player Statistics option, found in the settings/general section of your dashboard on the website
	"userName": "testUser", // Arbitrary username, you can change this to any valid username
	"userEmail": "[email protected]", // This email address will be bound to the username above
	"userPassword": "testPassword", // This must be the correct password for the testUser above (if that user does not exist yet, this will be the new password)
	"characterName": "testCharacter" // Arbitrary characterName, you can change this to any valid characterName
}

This file must be created and placed in the root of the sdk (beside PlayFabApiTest.html & PlayFabApiTest.js), and must be named "testTitleData.json"

  1. Troubleshooting:

For a complete list of available APIs, check out the online documentation.

Contact Us

We love to hear from our developer community! Do you have ideas on how we can make our products and services better?

Our Developer Success Team can assist with answering any questions as well as process any feedback you have about PlayFab services.

Forums, Support and Knowledge Base

  1. Copyright and Licensing Information:

Apache License -- Version 2.0, January 2004 http://www.apache.org/licenses/

Full details available within the LICENSE file.

About

JavaScriptSDK for the Client API of PlayFab

Resources

Readme
Apache-2.0 license
Activity

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.