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
Currently, Nakama's nk.TournamentRecordWrite function increases the 'num_score' field by one for each call, which is the desired behavior in many cases. However, we have a specific requirement where we need to be able to provide a custom value to update the 'num_score' field with a specific increment.
In our application, we collect user scores on the client side and we send the aggregated scores in a single request to the server. This approach ensures efficient communication and reduces unnecessary overhead.
We propose enhancing the nk.TournamentRecordWrite function to accept an optional count parameter that allows us to specify the desired increment for the 'num_score' field. By including this count parameter in the request, we can update the 'num_score' field in a single call while accurately reflecting the aggregated scores provided by the client.
We appreciate your consideration of this feature request.
The text was updated successfully, but these errors were encountered:
Currently, Nakama's
nk.TournamentRecordWrite
function increases the 'num_score' field by one for each call, which is the desired behavior in many cases. However, we have a specific requirement where we need to be able to provide a custom value to update the 'num_score' field with a specific increment.In our application, we collect user scores on the client side and we send the aggregated scores in a single request to the server. This approach ensures efficient communication and reduces unnecessary overhead.
We propose enhancing the
nk.TournamentRecordWrite
function to accept an optional count parameter that allows us to specify the desired increment for the 'num_score' field. By including this count parameter in the request, we can update the 'num_score' field in a single call while accurately reflecting the aggregated scores provided by the client.We appreciate your consideration of this feature request.
The text was updated successfully, but these errors were encountered: