> ## Documentation Index > Fetch the complete documentation index at: https://docs.evox.wraithesports.app/llms.txt > Use this file to discover all available pages before exploring further. # Market and Plugins > Find, install, configure and remove approved evoX packs. ## Market The Market is the single evoX catalog. The normal view contains only approved native packs; the old Market iframe, smoke/test rows and technical legacy clutter are not shown. * **Ready profile:** Installs a new profile and its controlled assets. * **Action pack:** Enables native behaviors and presets that exist in the app. * **Icon pack:** Adds its content to the local **Icons** library. * **Sound pack:** Installs usable sound content. ### Platform support of packs The Market lists only packs that work on the system you are using. Most official packs can be installed on Windows, macOS and Linux. Packs that depend on a program only available on Windows or on Windows-specific system screens are not listed on other systems: VoiceMeeter Control, Soundpad Integration, ShadowPlay Shortcuts, Wraith W1 Control, Windows Sound Control, Photoshop and Adobe Premiere Pro Shortcuts, Window Switcher, Webcam Control and Memories Slideshow. Voicemod Controls appear on Windows and macOS; the local Voicemod app has no Linux version. Icon and sound packs can be installed on every system; they contain only images and sounds, so they are not tied to an operating system. The packs you export yourself carry no operating system information either: you can move a pack you created on Windows to a Mac or to Linux, and the person you send a pack to can install it on whatever system they use. ## Plugins **Plugins** shows only native action packs installed from the Market. The basic actions that ship with the app stay in the action library; local T1 developer plugins do not appear here. For configurable packs, the gear action opens the pack settings. Pack-level settings are shared by the pack's actions. ## Connection status After you connect an integration, you can see inside the app whether the connection was really established: * **At the top of the pack settings window** there is a status section. If the connection is established, it shows the **Integration successful** heading together with which account is connected (e.g. *Spotify connected ยท your username*) and the last check time. If there is no connection, you see **Not connected** in the same place. * **Plugins cards** and the pack details window have a **Connected** / **Not connected** chip you can read at a glance. * **In key settings**, the same chip appears when you select an integration activity; that way you know whether the key will work without going to the Plugins page. This works the same way for the Kick, Twitch, Streamlabs, Discord, Spotify, OBS and Voicemod integrations. For OBS and Voicemod the connection is a local app connection rather than an account, so the status is shown as soon as it is verified with **Test Connection**. If you change the OBS connection address or password, or an integration's Client ID/Client Key, the previous verification is dropped; test the connection again for the status to become **Connected** again. ## Integration credential security When you connect integrations such as Kick, Twitch, Streamlabs, Discord, Spotify and OBS with **Authorize**, the resulting secret values (access/refresh tokens, client secret, OBS connection password) are stored **only on your own device**: * Secret values are kept **encrypted** on your device with the operating system's encryption (DPAPI on Windows, Keychain on macOS, the system keyring on Linux), and this encryption is tied to your system user account. * These values are **never sent to evoX servers**; they are decrypted on your device only while the related action runs. * The pack settings file (`settings.json`) keeps only non-secret display information (e.g. the public OAuth `clientId`, display name, validity status); raw tokens or secrets are not written to this file. * If secure operating system encryption is not available on your device, authorization does not fall back to plain text; it is safely rejected instead. For security, these secret values cannot be moved to another computer or system user account. When you change device/account, you need to **Authorize** the integration again from the related pack settings. On Linux, if no keyring (GNOME Keyring or KWallet) is running in your session, authorization does not fall back to plain text; it is safely rejected. When you create a Twitch application, choose **Confidential** as the client type. Otherwise Twitch does not generate the Client Secret needed for authorization. ## Likes and downloads On the evoX Market (web), every pack shows server-authoritative **download** and **like** counts. After signing in you can like packs and collect them all in your account's **Likes** list. Liking requires signing in; an anonymous visitor who tries to like a pack sees a sign-in prompt without the download being blocked. Public executable plugin upload and installation are not open yet. Data-only packs work; executable submissions are closed with the `PLUGIN_UPLOAD_NOT_READY` status. ## Updating installed packs When the publisher of a pack you installed releases a new version, evoX shows it on the Market with an **Update available** badge. The **Update** button next to the badge replaces the pack with its new version. Ready profile packs are the exception: they only show the badge, no automatic update is performed. Once installed, a profile pack becomes the live profile you edit; replacing it automatically would erase your key assignments and customizations. If you want the new version, the decision is yours. ## Publish your own pack You can do more than install packs: you can also share a profile, icon pack or sound pack you made on the Market. No code, CLI or publisher application is needed: sign in, export from the desktop and submit to moderation. If approved, it is added to the Market. Step by step: sign in โ†’ export โ†’ upload โ†’ moderation.