No. Asgaros Forum is free in full, and SleekView reads the core asgarosforum tables directly. No premium add-on is required to drive the board. If you have additional Asgaros add-ons installed, you can use their custom meta fields as sort or status sources, but the base board works on a stock Asgaros install.

Yes. SleekView reads the live reaction counts from asgarosforum_reactions when it renders the board, so every reaction collected before SleekView was installed counts toward the sort order from day one. There is no migration step and no risk of double-counting historical reactions on any thread.

Yes. The query builder accepts a forum ID or a parent forum filter, so you can build a board for a single subforum, a board for two related subforums, or a global board that pulls every thread across the entire site. Filters compose freely so a Bugs-only board for a specific role is a few clicks away.

It writes to Asgaros. The Upvote button inserts a real reaction row in asgarosforum_reactions, which is the same write path the native forum reaction buttons use. Existing Asgaros badge add-ons, moderation logs, and any third-party reporting plugin pick up the engagement exactly as if it came from the forum thread itself.

Yes. SleekView queries threads through the standard Asgaros access layer, which honors per-forum visibility and read permissions. A logged-out visitor never sees threads from a private forum, and a member only sees threads from forums their role can read, so the board never accidentally exposes restricted forum content to anyone.

Yes. The data query accepts an array of forum IDs, so you can build one board that pulls from two or three subforums and another board scoped to a single subforum. Each board reads its own slice of asgarosforum_threads and sorts it by the column you choose during configuration on the WordPress page.

SleekView reads the live thread IDs, so merges that move replies into a target thread leave the merged target on the board with the combined reaction count, while the source thread disappears. Splits create a new thread row that begins with zero reactions and climbs the sort order as the new thread collects new community reactions.

If reactions are disabled inside Asgaros, you can still use the reply count or any custom thread meta as the sort column on the SleekView board. The reaction-based vote source is one option among many, so disabling reactions inside Asgaros does not break the board, it only changes which numeric field drives the order.