Releases: heroiclabs/nakama-dotnet
Releases · heroiclabs/nakama-dotnet
v3.14.0
v3.13.0
Added
- Satori: Added
ImageUrl
andTitle
toIApiMessage
.
v3.12.1
- Nakama: Fixed an issue where notifications from other users could appear as if they were sent by the recipient user.
- Nakama: Fixed a potential
NullReferenceException
that could occur when passing anull
username toIClient.UpdateAccountAsync
.
3.12.0
Added
- Satori: Added
IApiLiveEvent.Id
for accessing live event identifiers. - Satori: Added support for new Satori Messages API:
IClient.GetMessageListAsync
,IClient.UpdateMessageAsync
andIClient.DeleteMessageAsync
.
v3.11.0
Added
- Nakama: New
IClient
event calledReceivedSessionUpdated
when session expires and is refreshed. - Nakama: New
Session.Update
method to allow for in-place updates to the session object.
Changed
- Nakama:
IsConnected
andIsConnecting
will now read directly from the underlying .NET socket status. This will allow application code to more quickly and easily detect connectivity loss arising from a lack of internet access. - Nakama: Default socket adapter changed from
WebSocketAdapter
toWebSocketStdlibAdapter
. This was done to utilize the native .NET Websocket library for improved stability and maintenance.
Fixed
- Nakama: Trying to connect a socket that is already connecting now results in a no-op instead of an error.
v3.10.0
Notable changes
Added
- Nakama: Rank count is now returned with tournament record listings.
- Nakama: Added ability to delete tournament records with
DeleteTournamentRecordAsync
. - Nakama: Hostnames passed to the client now preserve their hardcoded paths.
- Nakama: Create and update times are now returned with notifications.
- Nakama: Added Facebook Instant Games purchase validation.
Changed
- Nakama: Mark socket as connected before event handler is called.
- Nakama: Limited scope of retry logic to very specific 500-level codes from the server.
v3.9.0
Added
- Satori: Added
recompute
option toUpdatePropertiesAsync
which allows audiences to be recalculated on property update.
Changed
- Satori: Decreased size of JSON payloads.
Fixed
- Satori:
DeleteIdentityAsync
no longer accepts an explicit ID.
v3.8.0
Added
- Nakama: Added
Authoritative
flag to tournaments returned from the server. - Nakama: Added
RefundTime
andUserId
to purchases and subscriptions returned from the server. - Nakama: Added raw subscription provider information.
- Nakama: Added
DeleteAccountAsync
for deleting user accounts. - Satori: Added
DeleteIdentityAsync
for deleting user identities.
Changed
- Nakama: Used
session.Username
wherever outdated state might be returned.
Fixed
- Nakama: Fixed issue where outgoing payloads could include unnecessary JSON.
v3.7.0
Added
- Nakama: Added an
UpdatePresences
utility toIMatch
andIParty
. Use this method as a helper to update the local tracking of your presences in your matches and parties when anIMatchPresenceEvent
orIPartyPresenceEvent
is dispatched. - Satori: Added optional default and custom properties that can be attached to authentication requests.
Changed
- Satori:
GetFlagDefault
andGetFlagsDefault
now use theapiKey
passed to the client constructor rather than accepting it as a unique parameter.
v3.6.0
Added
- Satori: Adds the Satori .NET SDK. Satori is our liveops server for game studios. Read more about it in the documentation.
- Nakama: Adds support for calling RPCs with a HTTP key via POST when a payload is provided.
- Nakama: Expose the
Logger
object onIClient
. - Nakama: Adds support for POST RPC requests when using HTTP key with a payload
Fixed
- Nakama: Prevent race condition when
Close
is called while receive loop has an incomplete read buffer. - Nakama: Fixed an issue where 500 errors could cause parsing issues on the client.
- Nakama: Added ability to specify
path
parameter to client urls.
Changed
- Nakama: Fixed an issue where our websocket would throw an exception on
CloseAsync()
in certain situations.