photonnetwork integration

Question

question

woojoo asked Feb 17, '17

photonnetwork integration

    this.playfabId = result.PlayFabId;
    GetPhotonAuthenticationTokenRequest request = new GetPhotonAuthenticationTokenRequest();
    request.PhotonApplicationId = photonComponent.AppId.Trim();

this is on https://api.playfab.com/docs/using-photon-with-playfab/

but the code photonComponent.AppId.Trim();

is not quite making sense..

my question is what should i do to get photon app id via script?

should is set as const value/ set from inspector??

wouldn't there be any smarter options..?

Authentication

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2017-02-17T22:09:52Z

brendan answered Feb 17, '17

Our integration with Photon Cloud includes simplified authentication using the auth token API you mentioned above, and pre-configured calls into Cloud Script handlers for your Photon Realtime webhooks. However, to use Photon Cloud, you would need to use the Photon API calls (usually using their SDK) for all the Lobby/Room logic, which requires that you have the App ID in your game somewhere. Rather than adding it to the PlayFabSettings in our SDK (which would force you to define it twice in your project), the sample is showing where to add the ID in your calls to our service. You obtain the ID via the Photon page in the Add-ons Marketplace for your title.

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 2 · 2017-03-20T17:22:13Z

dev-3 answered Mar 20, '17

Hi Brendan

The following link doesn't work anymore.

https://api.playfab.com/docs/using-photon-with-playfab/

Could you please bring it back?

1

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

brendan commented · Mar 20, 2017 at 05:24 PM

Thanks for letting us know! As I'm sure you noticed, we just completed a major update to the site, and it looks like that page wasn't pulled over correctly. We should have that fixed shortly.

0 ·

question