v3.0.3

Fixed

• Fixed issue with incorrect match data property being used in socket_send function.

v3.0.2

Changed

• Allows optional parameters to be nil in socket functions

v3.0.1

Fixed

• Runtime error when an unhandled socket message is received (#43)

Nakama Defold Client 3.0.0

• [BREAKING] Major overhaul of the generated code and how it interacts with the Nakama APIs.
• Socket creation and socket events have been moved to nakama/socket.lua. This includes sending events and adding socket event listeners.
• Removed message creation functions in favor of including all message arguments in the functions sending the messages.
• Added message functions to the client and socket instances. Compare nakama.do_foo(client, ...) and client.do_foo(...). The old approach of passing the client or socket instance as the first argument still exists to help with backwards compatibility.

Fixed status follow and unfollow messages

FIX: Status follow and unfollow messages used the wrong argument name (#33)

Fix encoding of empty status update message

FIX: Encoding of empty status update message (thanks @uncleNight)

Generated new version of API

NEW: Generated new version of the API. New API functions:

• nakama.validate_purchase_apple()

• nakama.validate_purchase_google()

• nakama.validate_purchase_huawei()

• nakama.session_logout()

• nakama.write_tournament_record2()

• nakama.import_steam_friends()

CHANGE: Signatures for a few functions operating on user groups and friends.

WebSocket update and improved error handling

BREAKING CHANGE: Updated to the new native WebSocket extension for Defold (https://github.com/defold/extension-websocket). To use Nakama with Defold you now only need to add a dependency to the WebSocket extension.
FIX: HTTP requests handle HTTP status codes outside of the 200-299 range as errors. The general error handling based on the response from Nakama has also been improved.
FIX: Match create messages are encoded correctly when the message is empty

Authentication fix

This version fixes some issues with re-authentication (by dropping an existing bearer token when calling an authentication function). Thanks to @uncleNight for the contribution!

Match data and SSL fix

• NEW: Support for encoding of match data (json+base64) using new utility module
• FIX: http vs https connection via config.use_ssl