One version number for every platform. On the registries now: 2.2.0.
Install lines in the docs still give 2.2.0. Until this release is published, its features reach you through the drop-in files, which are always current.
sdk/VERSION stays 2.2.0 until Playmez publishes it. Every package already opens Slide Blast and relays its events, so the drop-in files carry it today.slide), a solo block puzzle played on the device. The frame offers today's game (the same board for everyone, 3 tries), practice and duels. It takes no mode (400 PUZZLE_MODE) and no tableCode (400 PUZZLE_TABLE_CODE). slide joins PlaymezGameId; JS adds PlaymezPuzzleGameId.POST /partner/launch takes shareUrl, your page a friend opens to take a duel (https on one of your allowed origins, {code} exactly once, e.g. https://yourapp.com/play?duel={code}; else 400 INVALID_SHARE_URL), and duel, the 6-character code a friend shared. Both are for slide only (400 DUEL_GAME). Inside your frame every share link points to your shareUrl, never to playmez.com; without one the frame shows the bare code.solo_finished (game, mode: daily, practice or duel, score, best) for every run the server checked.challenge (game, code, score, url) when the player makes a duel from a finished practice game. url is your shareUrl with the code filled in, null without one; share it and launch the friend with duel: code.PlaymezEvent gain mode, score, best and url (code carries the duel code); the JS and React Native PlaymezEvent unions list both events, and JS adds PlaymezPuzzleMode.og:image of your table invite page, https://playmez.com/og/join/<code>?from=<name>, which draws a verified partner's own logo, name and colour in WhatsApp, Telegram and X link previews. JS and React Native inviteCardUrl(code, { from }) (also Playmez.inviteCardUrl in the script tag), Flutter playmezInviteCardUrl, Android PlaymezGameView.inviteCardUrl, iOS PlaymezInvite.cardURL(tableCode:from:); server helpers playmezInviteCardUrl / playmez_invite_card_url.duelCardUrl(code, { from }) (JS, React Native, Playmez.duelCardUrl), Flutter playmezDuelCardUrl, Android PlaymezGameView.duelCardUrl, iOS PlaymezInvite.duelCardURL(duelCode:from:), server helpers playmezDuelCardUrl / playmez_duel_card_url: the og:image for your duel page, https://playmez.com/og/duel/<code>, with the sender's score in a verified partner's brand.playmez.com/s/<id> result cards and your hosted page playmez.com/p/<slug> now draw a verified partner's logo, name and colour in WhatsApp, with nothing to build.web-share to allow, so a phone sends the picture with the link; add it to your own iframe too.leaderboard.final (week, winners [{ rank, player, wins, games, prize }]), sent Monday after a week ends when you set weekly leaderboard prizes in your portal. The JS PlaymezWebhookEvent union lists it.shareUrl./embed, /p/<slug>) on the launch URL's own scheme and host load in the view; every other link opens in the system browser. Before, iOS, React Native and Flutter followed any link inside your app, and Android loaded the whole Playmez site and dropped other links. The microphone is granted to that host only.error codes the SDKs raise themselves (PlaymezSdkErrorCode): app views send LOAD_FAILED, HTTP_ERROR and RENDERER_GONE instead of showing a blank view, and on Android a stopped renderer no longer takes your app down with it. JS mount sends TIMEOUT when the game says nothing within readyTimeoutMs (default 20000, 0 switches it off); the frame stays.mount: allowMicrophone (default true); false leaves microphone out of the frame's allow.playmez_embed now depends on url_launcher; a project using the drop-in file adds it to its pubspec.https://playmez.com/sdk/<version>/playmez.js, an address that never changes, for use with an integrity hash.POST /partner/shows, then launch the presenter with role: "host" and players with POST /partner/shows/:code/launch. Every package opens the launch URL with no code change.ready of a show launch carries game: "show", show (the kind), showCode and role. Android, iOS and Flutter PlaymezEvent gain show, showCode and role; JS and React Native add PlaymezShowKind and PlaymezShowRole (JS also PlaymezShowAudience).session.opened carries showCode for a show launch, where game is null.launch.mjs, launch.php, launch.py) gain createPlaymezShow, launchPlaymezShow and closePlaymezShow (create_playmez_show… in Python).court_piece, twenty_nine, draw_guess (Draw and Guess) and antakshari join PlaymezGameId; court_piece, twenty_nine and draw_guess join PlaymezLocalGameId, and draw_guess joins PlaymezLocalTogetherGameId (people only, 2 to 12 passing one device; no computer player). Draw and Guess and Antakshari are held until Playmez releases them: a launch fails with 403 GAME_HELD until then. Every package opens them with no code change.game="court_piece", "twenty_nine" and "draw_guess".ipl (IPL live room) joins PlaymezShowKind. A partner's players call each over of a live match together. Held until Playmez releases it: POST /partner/shows with kind: "ipl" answers 403 until then. Every package opens the launch URL with no code change.mode: "local" runs the game on the player's device with no network once loaded. Every table game plays alone against the computer (Ludo, Chess, Carrom, 8-ball, Callbreak, Rummy, Teen Patti, Tambola, Trivia, Roulette, Crash), and Ludo, Chess, Carrom and 8-ball can also be played by people passing the device. Every package runs it with no code change.local_finished (game, draw, won) when a local game ends. won is the player's result against the computer, null for people together or a game of chance. No names leave the device. Android, iOS and Flutter PlaymezEvent gain draw and wonVsComputer; the JS and React Native PlaymezEvent unions list the event.PlaymezLaunchMode (computer, online, local), PlaymezLocalGameId and PlaymezLocalTogetherGameId; PlaymezGameId lists pool.[playmez game="rummy" mode="local"]; mode="online" joins the older online="1".playmez-embed and playmez-embed-react-native (npm), playmez_embed (pub.dev), com.github.playmez:playmez-android (JitPack, package com.playmez.embed) and the Swift package PlaymezEmbed at github.com/playmez/playmez-swift. Classes follow: PlaymezGame, PlaymezGameView, PlaymezEvent, PlaymezBridge.window.Playmez; window.Spinline stays as a deprecated alias and https://playmez.com/sdk/spinline.js keeps serving the same bundle until 3.0.Playmez-Event, Playmez-Delivery, Playmez-Timestamp, Playmez-Signature and Playmez-Attempt; the Spinline-* names are sent alongside until 3.0. The user agent is Playmez-Webhooks/2.0.source: "spinline", so 1.x packages keep working against playmez.com.com.github.anoopKumarChaudhary:spinline-android artifact resolves again (1.0.1 never built there). No code change for any package.https://playmez.com and https://api.playmez.com. No behaviour change; the launch URL's origin is still read from the launch response.mount(), React <SpinlineGame>, React Native <SpinlineGame>, Flutter SpinlineGame, Android SpinlineGameView, iOS SpinlineGameView + SwiftUI SpinlineGame.ready, result, close, error and resize events and keeps the launch URL's origin as the only trusted sender.Packages: playmez-embed, playmez-embed-react-native, playmez_embed, com.playmez:embed, PlaymezEmbed.