Skip to main content

​
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.
While installing a pack, evoX clears the program and folder paths it carries: the Open File / App and Open Folder keys that come from a pack arrive with no target, and you decide what they open. In the Website actions that come from a pack, only safe kinds of addresses are kept. Market packs are also scanned on the server before they are published; the check here is a second layer.

​
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 and Presentation Control appear on Windows and macOS; the local Voicemod app and PowerPoint/Keynote have no Linux version. CS2 Control appears on Windows and Linux; CS2 has no macOS 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.

​
Food Order

The Food Order pack puts your favorite order on a single key. When you press the key, evoX opens the restaurant page in its own window, adds the items you chose with their options to the cart and places the order with the card and address saved in your account. Your card and address details and your password are never stored in evoX; you stay signed in only in the evoX order window on this device.
  1. Install the pack from the Market and drag the Food Order action onto a key.
  2. Paste the restaurant page link into the Restaurant field.
  3. Type the items into the Items field with the name shown on the menu. Separate several items with ; and add 2x in front for a quantity. Write the choices from the product window (portion, sauce, garnish, drink, “Yanında İyi Gider” items) after the item name, in square brackets and separated by commas: 2x Pilav Üstü Tavuk [1 Porsiyon, Mısır, Sos İstemiyorum]; Ayran
  4. Type the name of your saved delivery address into the Address field (for example Ev). When the site asks for an address, evoX picks this one.
  5. On the first press, sign in to your account once in the window that opens and press the key again. You stay signed in in that window.
Each option you write picks one place; if you want the same option in two groups (for example two separate İstemiyorum), write it twice. evoX never guesses a required choice: if a required group is missing from your list, it stops and shows the group name with its choices. With Test mode on, evoX prepares the cart and stops before confirming the order; use it to try your settings. If you enter a Max total, the order is not placed when its total is above that amount. Items left in the cart by an earlier try are removed first on every press. If an item or option is not found, an item does not reach the cart (for example because the restaurant does not deliver to the selected address) or the total cannot be read, evoX does not confirm the order and shows the reason in the order window.

​
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.

​
Presentation Control

The Presentation Control pack runs your presentation from the deck. The app is picked automatically for your system: the Microsoft PowerPoint desktop app on Windows, Keynote on macOS. It is not supported on Linux and is not listed in the Market there.
  • evoX never opens the presentation app for you: open your presentation in PowerPoint or Keynote before using the actions. If the app is closed or no presentation is open, the key shows a message saying so.
  • Control works while the presentation app is in the background, that is, while another window has focus.
  • First use on macOS: evoX asks once for Automation permission to control Keynote. Choose Allow in the prompt. If you denied it by mistake, turn on the Keynote switch next to evoX under System Settings → Privacy & Security → Automation.

​
CS2 Control

The CS2 Control pack lets you use Counter-Strike 2 from the deck. It does two things: it shows on a key what is not on your screen, or does in one press what you cannot do by hand right then. Things the game already shows, such as health, money or score, are not copied to the deck. It works on Windows and Linux; CS2 has no macOS version, so it is not listed on a Mac.

​
Setup

  1. Add a CS2 key, open its settings and click Set up. evoX asks for confirmation, then adds two files to the CS2 cfg folder: gamestate_integration_evox.cfg (CS2 sends game state only to evoX on this computer) and evox.cfg (the binds your deck keys trigger). No other game file changes; if you already have your own file with the same name, evoX leaves it alone.
  2. In Steam, add +exec evox under CS2 → Properties → Launch options.
  3. Restart CS2. When the CS2 Connection key shows the map name, you are ready.
To remove it, click Remove in the same place. CS2 keeps binds in its own settings, so evoX first replaces evox.cfg with a file that clears them: open CS2 and press Reload Binds on your deck once (or type exec evox in the console). evoX then deletes only the files it created. If you can’t open CS2, use Finish removal; the keys may then stay bound in the game. When you remove the CS2 Control package from Plugins, evoX offers the same cleanup itself.

​
How it works

  • Each press sends exactly one key to the game. evoX writes the game’s own binds for unused numpad keys into evox.cfg, and the deck key triggers that bind. A buy combo, for example, is the same as pressing a key with a buy bind on your keyboard. So do not use the numpad keys for anything else in the game. You can also add Insert, Home, End, Delete, Page Up, Page Down and Scroll Lock under Advanced in the settings.
  • Numpad 0 reloads the binds. If you change a CS2 key while the game is open, press Reload Binds or type exec evox in the console.
  • On Windows, no key is sent when CS2 is not the active window, so a numpad key never lands in another app by mistake.
  • CS2 keys do not run inside a multi action with several steps; every press is one key.
  • evoX never reads the game’s memory or adds code to the game. Data comes through Valve’s official Game State Integration and stays on this computer.

​
Do: in one press

Your in-game loadout decides some weapons (for example M4A4 / M4A1-S, Desert Eagle / R8). Make the same choice in the buy combo settings so the right weapon is bought and the price is right.

​
Show: what is not on screen

Tournament rules can restrict bind files in the game folder and external tools. Before a league or LAN match, check that organizer’s rules; if needed, delete the CS2 Control files with Remove.

​
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.

Publish your own pack

Step by step: sign in → export → upload → moderation.