You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the sort rank only affects the results from the API calls from the game (such as dispaying the Achievement UI). I am curious, why does the sort order on in the console matter?
I can confirm the same as well. draft_sortRank only works when adding localizations to already existing English l(locale) achievements. Lets say when you add English only achievements for the first time, it doesnt work and the achievements are uploaded in random order.
Sort order matters because we want the achievements to displayed in a certain linear order and not randomly so that the player knows what the next one to unlock easily.
A few years later...
As the tool is still working (with some modifications) my solution for adding the achievements in the right order is, creating separat csv-files for each achievements and insert them one after the other.
We often use this tool to register achievements. We set draft_sortRank to sort achievements, but doesn't work.
Although we tried to register achievement that is divided into a single one csv file in order, achievements are registered in random order.
ex)
On Google Developer Console Game Service Tab, We expect that achievements are sorted and registered according to draft_sortRank. Is it right?
The text was updated successfully, but these errors were encountered: