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 noticed that when I make a call to listLeaderboardRecordsAroundOwner, for some reason, all the leaderboard records are returned. For example, I have these two records in the leaderboard right now.
Here is my code. I am using owner id "d95808c5-a194-4e73-af8d-f07ed58f8253". However, as you can see, two records are returned.
Currently using nakama: ^1.2.0
Has anyone seen this error?
The text was updated successfully, but these errors were encountered:
The method listLeaderboardRecordsAroundOwner retrieves leaderboard records around a given ownerId, allowing navigation up or down using a cursor (which then works similarly to invoking listLeaderboardRecords with a cursor).
For example, if your leaderboard contains 100 records and you set ownerId = "player123" with limit = 5, the result will include the specified user along with nearby records:
This means the method does not return only the user's record, if that’s what you were expecting.
I agree that the method’s description might be misleading—it’s autogenerated from Nakama's proto and Swagger specifications. I’ve already submitted a PR to propose a clearer summary.
By the way, if you want to retrieve just the user's record, you can use listLeaderboardRecords and pass ownerId directly.
Please let me know if my understanding is correct and if this resolves the issue.
In the coming days, I'll review the other issues you've opened. Thanks for your patience!😉
Good evening,
I noticed that when I make a call to listLeaderboardRecordsAroundOwner, for some reason, all the leaderboard records are returned. For example, I have these two records in the leaderboard right now.


Here is my code. I am using owner id "d95808c5-a194-4e73-af8d-f07ed58f8253". However, as you can see, two records are returned.
Currently using nakama: ^1.2.0
Has anyone seen this error?
The text was updated successfully, but these errors were encountered: