TBC App/Web - Gamipress Fluent Integration

Reward the moments GamiPress misses — reactions, comments, mentions, follows, messages — with badges, points, ranks and achievement pages.

Price: $29.00

Quantity

Buy Now Add To Cart

v1.0.18 Show changelog

Changelog · v1.0.18 ×

1.0.18 — 2026-10-14

🛠 Fixed

• Several forms on one settings tab each keep their Save in sight. Where a settings tab holds more than one form, each form with unsaved changes now shows its own Save, one above the other, instead of every Save sitting in the same spot on top of the others, and the tab keeps its unsaved dot until every form on it is saved. Every TBC add-on shares one save bar, and WordPress runs the copy from the add-on that loads first, so keep your TBC add-ons current to bring this to every settings page.
• Folding cards point the reading way in right-to-left languages. With WordPress in a right-to-left language such as Arabic or Hebrew, a closed card's arrow on the settings page pointed right, away from the text. It now points left, and down when the card is open.
• A link to a card in the plugin's guide opens it, even inside a closed section. A link straight to a card that sits inside one of the guide's folded sections opened the card but left its section shut, so the page showed nothing where the link pointed. Every fold around the card now opens.
• Fewer database reads on every request. On a site without an object cache such as Redis, each TBC add-on read its licence key and its last licence answer from the database on every page and app request, two reads per add-on. From its next licence check (within a day of the update) WordPress loads both with its other settings, in the one read it already makes. The marker the Achievements page uses to know its web address is set up, read on every request too, now loads with them. Activating, checking and renewing a licence work as before. Every TBC add-on shares this licence code and WordPress runs the copy from the add-on that loads first, so keep your TBC add-ons current to get the whole saving.
• A member's profile loads with fewer database reads. The points, rank and recent badges on a profile, in the app and on the web, read each badge's, the rank's and each points type's post and picture one at a time, up to four reads each. They are now read together in a few reads, however many badges a member has, and the leaderboard's badges use the same path. The profile shows the same.

1.0.17 — 2026-10-10

🛠 Fixed

• "Saved" shows only when a save went through. The save bar on a settings page flashed "Saved" after every save, even one the site refused with an error. It now stays quiet when the page reports a refused save.
• The FluentCommunity Courses note is right again. It said GamiPress can't see a lesson being completed. GamiPress has its own lesson events now, so the note says what ours add: lessons and topics in a chosen course, and lesson videos.

1.0.16 — 2026-10-07

Sync — lockstep bump, no plugin changes.

1.0.15 — 2026-10-03

🛠 Fixed

• WordPress's "Check again" finds our updates. Dashboard › Updates › Check again now asks our licence server too, so an update we've just published shows at once instead of up to 12 hours later. Before, only the plugin's License tab Refresh did that.

1.0.14 — 2026-09-29

🛠 Fixed

• Works with Fluent Community switched off. The trigger checks used to crash.
• A celebration post a site setting rules out is skipped quietly, for example when the member isn't in the chosen space or posting to the main feed is off, instead of reporting an error on every award.

1.0.13 — 2026-09-21

🛠 Fixed

• Sync on the starting rank finds its members. GamiPress stores nothing for a member still on the lowest rank, so it found nobody; it now counts them the way GamiPress does.
• Uninstall removes the flag for the leaderboard page's rewrite rules too.
• An achievements list that could not load while offline says "You're offline", not "Network request failed".

🔧 Changed

• "Delete all plugin data" removes the license key too. With that switch on, uninstalling removes everything the plugin stored — the license key, its licenser records and cached checks included — so a reinstall asks for the key again. With it off, nothing is deleted, as before. Every TBC plugin now does the same; before, some kept the key and some did not.

📡 OTA & Internal

• Fallbacks for older GamiPress versions and unused helpers go.
• The shared licenser drops hooks and an argument nothing used, and its comments say what it does rather than how it got there.

1.0.12 — 2026-09-17

Sync — lockstep bump, no plugin changes.

1.0.11 — 2026-09-12

🔧 Changed

• The documentation stops saying routePrefixes routes the module's screens — the dashboard generates their route stubs from the manifest, and a push tap opens whatever path the server sent — and lists Dutch among the module's languages.

1.0.10 — 2026-09-07

🔧 Changed

• The admin explains itself on request, not on sight. The paragraphs printed beside each control — read once, taking room forever — are behind a ? now, the same one on every screen in the suite. Orientation goes behind it; warnings, legal text and anything describing what is currently set stay visible, because a message you have to click to discover is not a warning.

1.0.9 — 2026-09-03

Sync — lockstep bump, no plugin changes.

GamiPress for Fluent Community · WordPress plugin · web + app

You already run the gamification. Nobody can see it.

GamiPress awards the badges, ranks and points — it just has nowhere to show them inside Fluent Community. This is the bridge: notifications, badge chips beside member names, points and rank on profiles, a trophy case and a leaderboard. It never awards anything itself.

0changes to GamiPress data — it listens and publishes, nothing else

4places an award shows up: bell, push, feed post, badge chip

2surfaces — the website, and the app when you run one

1settings page, with templates you write yourself

Three parts · one add-on

What members earn, where it shows, what you configure.

Click a tab. Every capture opens full size and is a real screen.

GamiPress › How it works Included

Choose a view

Where it shows Awards & triggers What you configure

Gamification people can actually see

A trophy case and a leaderboard

Members get a full achievements screen and a configurable points leaderboard. Earned badges become chips next to member names everywhere Fluent Community renders one, and points and rank appear on profiles.

Close

Close

The moment somebody earns something

A bell, a push, and a post if you want one

Badges, steps, points awards and rank changes all converge on one path, whether they came from an Automator recipe, native step completion or an admin awarding it by hand.

• Bell notification and native push — the same award, both places
• An optional feed post celebrating it publicly
• Badge chips synced into Fluent Community’s own badge store, so they appear beside a name everywhere
• Rank chips swap automatically when a member’s rank changes
• Fluent Community achievement triggers that GamiPress’s own integration does not cover

Close

One settings page

Your words, not ours

Notification and feed-post copy is written from templates with placeholders, so a celebration sounds like your community rather than like a plugin.

• Message templates for each kind of award, with placeholders
• Choose the surfaces — bell, push, feed post and chips are each yours to turn on
• A leaderboard you configure rather than one that is simply on
• Nothing written into GamiPress — it stays the source of truth for every badge, rank and point

Close

What you get

• Award notifications in the bell, and as native push
• Optional feed posts celebrating an award
• Badge chips beside member names, everywhere FC renders one
• Points, rank and recent badges on member profiles
• An achievements tab and screen, plus a points leaderboard widget
• Extra Fluent Community achievement triggers for GamiPress

What you need

• GamiPress and Fluent Community — both required; with either missing the plugin only shows a notice
• Fluent Community Pro for badge chips specifically (its User Badges module). Everything else works without it
• The TBC Community App is optional — the web surfaces work on their own, and the app ones light up when it is present

Pricing

One payment. Then it is yours.

A lifetime licence for the plugin and its app module. No subscriptions and no per-member fees.

GamiPress for Fluent CommunityWordPress plugin + app module$29

At checkout$29

Related Products

TBC - Web - Admin Columns

Fluent Community fields, stats, roles and user-meta as sortable, inline-editable columns on the Users list and WooCommerce Orders.

Price: $0.00

Add To Cart

TBC - Web - Automations

Eighteen Uncanny Automator triggers and actions for Fluent Community — DMs, notifications, follows, points, spaces, posts.

Price: $0.00

Add To Cart

TBC - Web - User Switching

Puts the free User Switching plugin's buttons in the Fluent Community portal: Switch user on a member's profile, and Switch back in the header to return to your own account.

Price: $0.00

Add To Cart

TBC -App - Better Messages Addon

Hand the app’s messaging to Better Messages — threads, group chats, attachments, reactions, rooms — with push that deep-links to the conversation.

Price: $0.00

Add To Cart

TBC App - Community App (Dev Bundle)

The full React Native source plus the build dashboard. Configure your site, drop in your assets, and ship to both stores yourself — no coding required.

From $50.00

View Options

TBC App - Community App (Managed)

Your own branded community app on iOS and Android — built, published and kept up to date by us, under your accounts. You bring the content and branding; we handle every build and update.

From $33.00

View Options