I noticed that in player detail there is part "location": {
"country": "**",
"latitide": **.818603515625,
"city": "*******",
"longditute": **.468093872070312
},
Why are latitude and longitude named as latitide and longditute?
Best Regards,
Sasha
Best Answer
T
Tech Support
said
over 5 years ago
Hi Sasha,
Unfortunately these were named incorrectly when this functionality was originally introduced to the platform.
Because these are publicly available fields, which our existing customers are currently referencing, we cannot just rename them (since this would break functionality for customers who currently use these fields).
Unfortunately these were named incorrectly when this functionality was originally introduced to the platform.
Because these are publicly available fields, which our existing customers are currently referencing, we cannot just rename them (since this would break functionality for customers who currently use these fields).
Kind regards,
Jonathan,
N
Nathan Kerr
said
over 5 years ago
There's no reason why you can't have both the old one and the correct spellings.
SashaMirkovic
Hello,
I noticed that in player detail there is part
"location": {
"country": "**",
"latitide": **.818603515625,
"city": "*******",
"longditute": **.468093872070312
},
Why are latitude and longitude named as latitide and longditute?
Best Regards,
Sasha
Hi Sasha,
Unfortunately these were named incorrectly when this functionality was originally introduced to the platform.
Because these are publicly available fields, which our existing customers are currently referencing, we cannot just rename them (since this would break functionality for customers who currently use these fields).
Kind regards,
Jonathan,
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstTech Support
Hi Sasha,
Unfortunately these were named incorrectly when this functionality was originally introduced to the platform.
Because these are publicly available fields, which our existing customers are currently referencing, we cannot just rename them (since this would break functionality for customers who currently use these fields).
Kind regards,
Jonathan,
Nathan Kerr
And then mark the old ones as deprecated.
6 people like this
-
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 2487 topics