On the frontend, RCA ArrowChat’s job is to load ArrowChat for logged-in users who should see it, keep your template custom.css authoritative for styling, and optionally show a staff presence dock. Guests typically do not get the full chat experience unless your ArrowChat and site configuration says otherwise; this package does not replace ArrowChat’s own guest rules.
When System - RCA ArrowChat is enabled and component Options point at a valid ArrowChat folder with autoload.php on disk, logged-in users should see ArrowChat’s UI according to ArrowChat’s own templates and your friend list mode. If chat never appears, the problem is usually disabled plugin, wrong folder name, missing Write bridge, or cache—not a mystery template gremlin.
Put durable chat chrome overrides in your template css/custom.css. The system plugin keeps that file last in the CSS cascade so your rules can win without an important-flag arms race. Staff module appearance uses module parameters for ring colors and CSS variables you can override in the same custom.css file.
When you publish RCA ArrowChat Staff with viewport dock enabled or assign the module to a visible position, frontend users who pass module access checks see online staff with colored status rings. Presence comes from ArrowChat; an empty dock often means nobody is online in ArrowChat’s session model, not that the module is broken.
Chat profile links use component Options, Profile URL pattern. Use {id} where the user id belongs and point the pattern at the real profile route your site uses. Test a link from chat after you change the pattern because a wrong pattern sends users to 404 pages that look like chat is broken.
If the mobile Chat launcher is missing after an upgrade, update pkg_rca_arrowchat to the current package, confirm System - RCA ArrowChat is enabled, confirm you are logged in on the frontend, and clear template and Joomla cache before opening a support ticket.