For extension authors
Add an optional one-click install link.
AddonPort for FACEIT accepts valid Chrome Web Store extension IDs. A catalog listing or SDK integration is not required.
Website integration
Use the native link directly.
Launch it only after a user action and keep a normal Setup link nearby. Replace the example target with your 32-character Chrome extension ID.
<a href="addonport://install/abcdefghijklmnopabcdefghijklmnop">
Install with AddonPort for FACEIT
</a>
<a href="https://github.com/AddonPort/faceit/releases/tag/dev-latest">Didn't open? Install AddonPort</a>addonport://openOpen the in-client manageraddonport://install/<id>Review and install an extensionaddonport://launch/<id>Open an installed extension action
Protocol
Keep the fallback visible.
Browsers cannot reliably prove that a native protocol handler is installed. Do not launch links automatically during page load or claim that a timeout detected the app.
addonport://open
addonport://install/<chrome-extension-id>
addonport://launch/<chrome-extension-id>install
Always opens an in-client confirmation before download.
launch
Opens the installed extension action in the FACEIT client.
open
Opens the AddonPort manager without selecting an extension.
Native Windows apps
Read the current-user registry key.
Native apps can check the installed loader version without launching FACEIT. Compare ProtocolVersion before relying on newer link actions.
HKCU\Software\AddonPort\FACEIT
DisplayVersion REG_SZ <adapter version>
InstallLocation REG_SZ <payload directory>
Protocol REG_SZ addonport
ProtocolVersion REG_SZ 2A browser timeout is only a usability hint. It is not installation detection, device attestation, authentication, or an anti-abuse signal.