A way to control when GameSparks connects on startup?
J
Jason McIntosh
started a topic
over 4 years ago
I would like to defer connection to the GameSparks service until some startup operations complete. Currently, the PlatformBase implementation will connect as soon as it is created.
Is there a way around that so that I can control when the connection should be made?
Best Answer
C
Customer Support
said
over 4 years ago
Hi Jason,
A simple way to do this would be to have the GameSparks object as a prefab and instantiate it when required, once in the scene it will make a connection with GameSparks.
A simple way to do this would be to have the GameSparks object as a prefab and instantiate it when required, once in the scene it will make a connection with GameSparks.
Thanks,
Liam
J
Jason McIntosh
said
over 4 years ago
Hi Liam,
I am actually doing that already, but it is one of a group of prefabs which orchestrate initialization of various services within my game. It's not critical. I can hack around it, but it would be nice for the library to not assume anything about the usage patterns of its users.
Jason McIntosh
I would like to defer connection to the GameSparks service until some startup operations complete. Currently, the PlatformBase implementation will connect as soon as it is created.
Is there a way around that so that I can control when the connection should be made?
Hi Jason,
A simple way to do this would be to have the GameSparks object as a prefab and instantiate it when required, once in the scene it will make a connection with GameSparks.
Thanks,
Liam
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstCustomer Support
Hi Jason,
A simple way to do this would be to have the GameSparks object as a prefab and instantiate it when required, once in the scene it will make a connection with GameSparks.
Thanks,
Liam
Jason McIntosh
Hi Liam,
I am actually doing that already, but it is one of a group of prefabs which orchestrate initialization of various services within my game. It's not critical. I can hack around it, but it would be nice for the library to not assume anything about the usage patterns of its users.
Thanks!
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2485 topics