Yes. SleekView reads the standard GamiPress achievement post types, the documented meta keys, and per-user point totals, so it works on any site running the free GamiPress plugin. Premium GamiPress add-ons are supported but not required, and the typical setup takes about five minutes.

Yes. The data source picker lets you point the upvote column at any per-user point type total. A board sorted by Reputation produces a different ranking than one sorted by XP, so sites running multiple point types can publish a dedicated board for each audience without duplicating achievement data.

Yes. SleekView queries achievements through the standard WordPress meta_query and tax_query layer, which respects the rank requirements GamiPress enforces. A rank-gated achievement only appears on the board for members whose rank meets the requirement, keeping the spoiler-free flow intact.

Only if you mapped the upvote column directly to the earned count meta. The recommended setup uses a separate _upvote_count meta for pledged interest, which keeps the leaderboard accurate while still giving admins a clean signal for which proposed badges deserve dev time.

GamiPress Notifications fires on real achievement and rank events on the underlying post type, which SleekView does not interfere with. Upvote events on the board can be wired to a custom notification template if desired, but the default behavior is to leave the notification stream focused on real earnings.

No. SleekView paginates the underlying query, caches the sorted set, and only fetches the rows it needs for the current page. A board with ten thousand GamiPress achievements and five active point types renders at the same speed as a small one because the database does the sort once.

Yes. Each SleekView block on the site can be configured with its own data source filter, status mapping, and category column. A Daily Login board, a Course Completion board, and a Community Contributor board can all live on different pages with their own pills and their own upvote meta keys.

Nothing. SleekView only reads from and writes to the meta keys you explicitly map, so reconfiguring the board does not touch the underlying earned counts, rank progress, or point totals. Earned data remains the canonical source whether the board is active, deactivated, or removed.