iaincollins

Here is an example of how it's possible to do something like player matching with Unity Cloud Save SDK 3.1

1. Write to the data you want to use for matching (e.g. region, language, level, etc) to Player Data in the Public Access Class (Public Data is readable by other players).

using SaveOptions = Unity.Services.CloudSave.Models.Data.Player.SaveOptions;

var data = new Dictionary<string, object> { { "location", "Paris" } };
await CloudSaveService.Instance.Data.Player.SaveAsync(data, new SaveOptions(new PublicWriteAccessClassOptions()));

iaincollins

Elite Dangerous Events
https://elite-journal.readthedocs.io/en/latest/

Journal Events

Cargo
ClearSavedGame
Commander
Loadout
Materials

iaincollins

iaincollins

// Long form example
const pizzas = [
  {
    name: 'Margarita',
    toppings: ['Cheese', 'Tomato']
  },
  {
    name: 'Hawaiian',
    toppings: ['Cheese', 'Tomato', 'Ham', 'Pineapple']
  },

iaincollins

name: Deploy on push to master
on:
  push:
    branches:
      - master
jobs:
  deploy:
    name: deploy
    runs-on: ubuntu-latest
    steps:

iaincollins

// 1. Add your API key and secret below
// 2. Run `npm i flickrapi` to install the SDK dependency
// 3. Run 'node auth.js` and follow the instructions
// (will open browser window, need to paste number back in terminal and copy entire output)
const Flickr = require('flickrapi')

const FLICKR_API_KEY = 'YOUR-API-KEY'
const FLICKR_SECRET = 'YOUR-API-SECRET'

Flickr.authenticate({

iaincollins

Keybase proof

I hereby claim:

• I am iaincollins on github.
• I am iaincollins (https://keybase.io/iaincollins) on keybase.
• I have a public key ASDf9ymZvYwN7R-sHq0yoHEa8kvW_5i1MmIK_cbroZLEBAo

To claim this, I am signing this object:

iaincollins

How to contribute

See the instructions in README.md for how to run the code.

When developing a feature, you should start by scoping out a spec, developing tests against that spec and writing code against the tests. Working with others to review the spec before starting development is encouraged.

Raise a Pull Request

1. When you create a branch, it should reflect the nature of the change.

iaincollins

Summary

A sentence describing the reason for the changes in this pull request.

Description

A few sentences / bullet points describing the goals of this change and the implementation.

Link to Issue

iaincollins

[short title of solved problem and solution]

• Status: [accepted | superseded by ADR-0005 | deprecated | …]
• Deciders: [list everyone involved in the decision]
• Date: [YYYY-MM-DD when the decision was last updated]

Technical Story: [description | ticket/issue URL]

Context and Problem Statement