i need to store some data about match to mark state, and when it reaches certain value i'll take an action. but i am not sure how to store a variable on match instance.
Best Answer
C
Customer Support
said
about 3 years ago
Hi Future,
As mentioned in your recent ticket, I would store this data in a runtime collection as the matchInstance collection (like most system collections) is ReadOnly.
As mentioned in your recent ticket, I would store this data in a runtime collection as the matchInstance collection (like most system collections) is ReadOnly.
Thanks,
Oisin
T
Thibaud de Souza
said
almost 3 years ago
Hi, I'm reading this answer as I'm looking into ways of storing data that is easier to relate to the current match / campaign / world instance than to any player in particular. "runtime collection" seems to imply that this is transient? Though reading through the tutorials I've seen it used to store (alas player specific) race data, and retrieve it later?
Or would it be necessary to setup a fake user ("Gamemaster") to store this type of data? After spending reasonable time reading the documentation it would appear that you're not really supporting this use case.
E
Eric Moncada
said
almost 3 years ago
Why don't you create a runtime collection with the matchId as the key of the document ?
Future Fart
i need to store some data about match to mark state, and when it reaches certain value i'll take an action. but i am not sure how to store a variable on match instance.
Hi Future,
As mentioned in your recent ticket, I would store this data in a runtime collection as the matchInstance collection (like most system collections) is ReadOnly.
Thanks,
Oisin
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstCustomer Support
Hi Future,
As mentioned in your recent ticket, I would store this data in a runtime collection as the matchInstance collection (like most system collections) is ReadOnly.
Thanks,
Oisin
Thibaud de Souza
Hi, I'm reading this answer as I'm looking into ways of storing data that is easier to relate to the current match / campaign / world instance than to any player in particular. "runtime collection" seems to imply that this is transient? Though reading through the tutorials I've seen it used to store (alas player specific) race data, and retrieve it later?
Or would it be necessary to setup a fake user ("Gamemaster") to store this type of data? After spending reasonable time reading the documentation it would appear that you're not really supporting this use case.
Eric Moncada
Why don't you create a runtime collection with the matchId as the key of the document ?
It would not be linked to a user in particular...
-
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 2317 topics