160 earlier updates, newest first. Showing 61–80 on page 4 of 8.
Released
iOS
iOS 1.1.6: more reliable seating, history, and review
BluffKing iOS 1.1.6 build 386 is now public on the App Store. Resuming returns players to their actual seat; leaving a public table joined by room code correctly frees the chair, and stale private-room codes no longer follow players into public tables. Session details now use the server ledger for one row per player, real hand counts, and buy-ins including rebuys. Unrevealed cards from advanced encrypted dealing appear as card backs with a clear review limitation. Membership copy now distinguishes recurring subscriptions from gifts and one-time entitlements. Games continue to use practice chips only.
The public App Store listing now shows iOS 1.1.6 build 386.
Resume, public-table exit, and room-code cleanup are more reliable.
History, encrypted-deal review, and membership status are described more accurately.
Released
Android
Android 1.1.9: complete notifications and longer-lived sessions
BluffKing Android 1.1.9 build 401 is now public on Google Play. Notifications open a full detail view so long and localized messages are no longer limited to an ellipsized preview, and only strictly verified BluffKing X and Telegram feedback links can appear. Signed-in sessions in the embedded table and support pages now align with the server's 90-day inactivity window. Poker rules, chips, membership prices, and payment settings are unchanged; games continue to use practice chips only.
The public Google Play listing now shows Android 1.1.9 build 401.
Notification details preserve complete localized messages and restrict actions to official feedback links.
Embedded table and support sessions align with the server's 90-day inactivity window.
Released
Backend
Daily operations report moves to 8 a.m.
The internal daily operations report is now sent at 08:00 every day in UTC+08:00. It still summarizes the previous complete calendar day and retains automatic catch-up after temporary service unavailability. Reporting definitions, player-visible behavior, poker rules, account entitlements, and payments are unchanged.
Daily delivery moves from 10:00 to 08:00 in UTC+08:00.
The data window remains the previous complete calendar day, including late catch-up deliveries.
Only internal operations timing changes; player-visible behavior is unchanged.
Released
Backend
More reliable follow-up for Max gift notification reads
When either login-gift or registered-user Max campaign notifications are opened individually, the system now records the read in a reliable internal follow-up queue; matching notifications opened before this release are backfilled as well. Repeated opens do not create duplicate alerts, temporary delivery failures are retried, and “mark all as read” is still not mistaken for an actual open. Internal alerts use only shortened internal identifiers and aggregate progress, never email addresses, display names, or notification copy. Campaign eligibility, Max entitlement duration, player UI, gameplay, and billing are unchanged.
Individual opens of both login-gift and registered-user Max notifications enter the reliable follow-up queue.
Matching pre-release reads are backfilled; repeated opens stay deduplicated and temporary failures are retried.
Internal alerts exclude email addresses, display names, and notification copy; player-visible behavior is unchanged.
Released
H5BackendMarketing site
Smart coach chat and more reliable seat assignment
The post-hand coach now includes an optional smart chat grounded in the hand and solver results; when the service is not configured, it fails closed without affecting the existing local-solver analysis. Seat assignment also keeps runtime and persisted state more tightly reconciled, reducing seat conflicts during concurrent claims or stale-state cleanup. The marketing site adds an engineering article on making public product claims verifiable and tightens the related wording. Poker rules, dealing, chip settlement, membership prices, and payment behavior are unchanged.
Post-hand review gains optional smart chat grounded in the hand and solver output.
Seat state stays more reliable during concurrent claims and stale-state cleanup.
The marketing site adds a bilingual engineering article on verifiable product claims.
Released
Backend
Daily operations report adds active and registration source breakdowns
The internal daily operations report gains two source-breakdown lines: active users and the day's new registrations are each classified by environment — WeChat in-app browser, Telegram, in-app (Flutter), regular browser, or unknown — with every user counted in exactly one bucket, making growth channels visible. Internal-report-only change; no player-visible behavior, poker rules, account entitlements, or payments change.
90-day sessions, seed-tester invites at sign-up, and operations clarity
This release carries three improvements. Login sessions are now preserved for up to 90 days so active players are no longer signed out prematurely, with the legal pages updated to match. During seed-tester recruitment (through September 2, 2026), newly registered accounts automatically receive the recruitment notification in-app, and recent registrants who missed the original broadcast have been sent it retroactively. The internal daily operations report also splits active users into registered and guest columns, removing the ambiguity of rolling actives exceeding total users. Poker rules, dealing, chip settlement, membership prices, and payment behavior are unchanged.
Login sessions persist for up to 90 days; active players stay signed in.
New sign-ups get the seed-tester invitation automatically during recruitment; recent registrants received it retroactively.
The operations report splits registered and guest activity, removing the metric ambiguity.
Released
H5BackendMarketing site
WeChat in-app browser error-noise filtering and operations-metric accuracy
Opening BluffKing inside WeChat's in-app browser produces error records thrown by WeChat's own injected script, unrelated to the product. This release recognizes and ignores that host-script noise in the page, and backend error statistics no longer count it as a client anomaly, so the operations team is escalated only for real product errors. Seed-tester notification read confirmations now also count internal test accounts separately from real users, so internal activity is never misread as player engagement. Poker rules, dealing, chip settlement, player UI, account entitlements, membership prices, and payment behavior are unchanged.
Errors thrown by WeChat's injected in-app browser script no longer count as client anomalies.
The daily report's error escalation reflects only real product errors.
Seed-tester notification read confirmations separate real users from internal accounts.
Released
Marketing site
Release records and operations materials synchronized
This maintenance release synchronizes the public version record and organizes internal collaboration materials used for seed-tester invitations, product review, and community-content preparation. It keeps production bound to an exact reviewed commit while removing release drift left by completed development branches. Poker rules, dealing, chip settlement, player UI, account entitlements, membership prices, and payment behavior are unchanged; internal operations materials are not exposed to players in the product.
The public version record now matches the exact production commit.
Completed internal operations and product-review materials are archived in the same reviewed version.
This maintenance release changes no player-facing product behavior.
Released
Backend
Membership campaign gifts now reach internal and test accounts
Membership campaigns (such as the login Max gift) previously skipped our own staff and test accounts, so the grant-and-notify path could not be verified end to end with a real login. This release removes that exclusion: internal accounts now go through exactly the same grant, notification, and deduplication logic as real players, letting the team validate every campaign with a test account. Eligibility rules for real players, campaign terms, gameplay, and billing are unchanged; guest and deleted accounts still do not participate.
Staff and test accounts now share the exact grant-and-notify path real players use.
Repeat logins never double-grant, and accounts already on Max are still skipped.
Growth and revenue metrics are unchanged: internal accounts remain excluded from reporting.
Released
BackendMarketing site
Reliable seed-tester follow-up and a new read-cache article
When a seed-tester invitation is opened individually, the system now records that action in a reliable internal follow-up queue. Temporary delivery failures are retried automatically, repeated opens are deduplicated, and “mark all as read” is not mistaken for an actual open. The website also publishes a new bilingual engineering article on protecting authenticated read caches with explicit TTLs, field allowlists, synchronous invalidation, and generation checks. Notification copy, enrolment rules, gameplay, and account entitlements are unchanged.
Only opening the invitation itself or using its application action counts as a confirmed read.
Repeated opens do not create duplicate follow-ups, and temporary delivery failures are retried.
Internal alerts contain only shortened internal identifiers and aggregate progress, never email addresses, display names, or notification copy.
A new bilingual article, “Write the read-cache contract first,” covers session revocation, expiry, and late-fill races.
Released
H5Marketing site
Clearer bet ownership and showdown results
Every current-street bet now stays attached to its owner, while the local player's amount sits separately above the stack balance instead of blending into balances or another seat. At showdown, opponents' cards remain full-size over the avatar area, and the winning hand category appears both beside the cards and in the result banner; the banner and completed chip flight no longer cover the cards. Rank and suit spacing is also clearer on Android H5, and the bilingual product-page captures now show this table version. Poker rules, dealing, and chip settlement are unchanged.
All bets use one owner-attached placement, with the local bet clearly separated from the stack balance.
Showdown cards retain their normal size while names, stacks, and the winning category stay readable.
The result banner sits below the board, and finished chip flights no longer cover the winning cards.
Card ranks and suits no longer crowd each other on Android H5.
The bilingual product-page table captures now show the updated interface.
Released
H5BackendMarketing site
The open-source mirror's default branch is synchronized again
BluffKing's open-source subset publisher now always creates an isolated workspace from the public repository's main branch and explicitly pushes updates back to main. It also byte-checks the published code and can recover from an interrupted publication. Updates that previously reached the sync branch and immutable source tag but not public main are now present on the default branch. Poker rules, dealing, accounts, memberships, payments, and interfaces are unchanged.
Public main now byte-matches the open-source subset defined in the private repository.
Synchronization no longer depends on whichever branch the local public clone has checked out.
A rerun after interruption can complete the tag and lock metadata without rewriting history.
Released
Android
Android 1.1.8 is live: clearer bot-action countdown feedback
BluffKing Android 1.1.8 build 396 is now public on Google Play. The native client now recognises server bot-action countdown updates instead of reporting them as unsupported native frames, improving table feedback while keeping the native fairness boundary fail-closed. Games continue to use practice chips only.
The public Google Play listing now shows 1.1.8 build 396.
Bot-action countdown updates no longer trigger unsupported-frame errors.
The native fairness boundary remains fail-closed.
Released
Marketing site
A coordinated marketing layout and clearer blog discovery
The marketing site now uses a consistent desktop content frame instead of stretching across ultra-wide screens. The blog keeps a chronological single-column feed while adding earlier access to Poker & Fairness, Performance & Capacity, AI Engineering, and the full archive; Product Updates and legal documents also use coordinated reading widths. Mobile pages gain safer side gutters and shorter list summaries without horizontal overflow. Gameplay, accounts, memberships, payments, and native apps are unchanged.
Desktop content, navigation, and footer return to one coordinated brand grid.
The blog adds topic discovery and earlier archive access while retaining a chronological single-column feed.
Mobile gutters, list summaries, and navigation keyboard behavior are clearer.
Released
H5BackendMarketing site
Max yearly is now half price on H5: US$149.50
Max yearly on H5 is now US$149.50, half of its US$299 regular price. The membership page, checkout amount, and website pricing copy are aligned, and the saving is stated as US$149.50 versus the regular price. iOS and Android continue to use their respective App Store and Google Play prices; this H5 release does not change native subscription pricing.
H5 Max yearly is updated to US$149.50.
The website clearly shows the US$299 regular price and US$149.50 saving.
iOS and Android store yearly prices remain unchanged.
Released
H5BackendMarketing site
A one-month Max welcome offer and clearer website reading
During the offer window, eligible users receive 30 days of Max on their first successful login, while users with an active Max term are not granted another one. The server applies the gift when it creates a login session, preventing duplicate entitlements from repeat, concurrent, or retried logins. Grants stop automatically when the campaign expires. The website also gives sustained-reading content a more focused measure and confines wide mobile tables to their own horizontal scroll region; games continue to use practice chips only.
The first successful login grants 30 days of Max; active Max users are not granted it again.
Repeat, concurrent, and retried logins cannot create multiple entitlements.
The offer runs for 30 days from activation and stops automatically at expiry.
Website long-form reading is more focused, and wide mobile tables no longer widen the page.
Released
Android
Android 1.1.7 is live: unified table entry and cleaner hand review
BluffKing Android 1.1.7 build 393 is now public on Google Play. Every native table entry point now opens Table 2, and the retired table-design switch is gone. Hand review also removes redundant export and drill shortcuts that had no separate supported flow. Games continue to use practice chips only.
The public Google Play listing now shows 1.1.7 build 393.
Every native table entry point now opens Table 2.
Hand review removes redundant export and drill shortcuts without a separate supported flow.
Released
Marketing site
Website reading improves: focused long-form layout and readable mobile tables
This website update separates continuous reading from comparison tasks: blog archive and recent-story lists are single-column, while article, Product Update, and legal prose use a more focused reading width. Long paths now wrap on mobile, and data tables with three or more columns preserve readable columns inside their own horizontal scroll area rather than widening the page. Product capability matrices, pricing plans, and contact channels retain multi-column layouts where comparison is useful. Gameplay, accounts, memberships, and payments are unchanged.
Blog archive and recent-story lists become continuous single-column reading, while editorial curation is labeled “Editor’s Pick.”
Blog posts, Product Updates, and legal documents now use desktop widths suited to sustained reading.
Wide mobile tables scroll inside their own region, so long words, paths, and data columns no longer create page-level horizontal overflow.
Released
Marketing site
Website adds a Telegram admin contact and widens Product Updates
The Contact page now labels the Telegram bot as a game entry and adds the administrator's direct Telegram contact without publishing a phone number. Product Updates and its archive now use the same desktop content width as the blog index while retaining a narrower title and lead for readability. Gameplay, accounts, memberships, and payments are unchanged.
Contact adds a direct Telegram administrator link, while the bot is no longer presented as a chat channel.
The Product Updates index and archive grow from 920px to the blog index's 1180px desktop content width.
Channel cards remain free of horizontal overflow on mobile.