Settings and permissions

Plugin controls live under Fluxer Settings → FluxPlugs.

Change settings

Open Settings to edit the settings declared by installed plugins. Controls may be switches, text fields, or numbers. Text and number changes save when the input loses focus; check the save feedback.

A settings change restarts the plugin’s instance so it can apply the new values. If a value is rejected or not saved, correct it before continuing.

Fields for secrets such as API keys are masked, but the value is still stored unencrypted on your computer.

Plugin pages

A plugin with the UI permission can add one page of its own under FluxPlugs, after Plugins and Settings. Hover over the entry to see which plugin added it. The page’s content comes from the plugin. Keyboard focus may stay on Fluxer’s settings window, so typing into a plugin page can fail; clicks and scrolling work.

Understand the confirmation

Enabling a plugin asks you to trust its particular code hash and requested capabilities. A hash identifies the code you reviewed; it is not a publisher signature or a guarantee of safety.

Capabilities describe what a plugin can request. Examples include saving private plugin data, displaying dialogs, loading restricted images, or sending an embed to the currently open channel.

A plugin with the network permission lists the servers it connects to under Connects to, in the prompt and in its row on the Plugins page. It can send requests to them without asking you each time. If it can also see messages on screen, the prompt warns that it can send their text and ids to those servers. An update that changes the servers needs your confirmation again.

The activity permission tells a plugin whether Fluxer is focused and shown, and whether you’ve been idle; it never sees what you type or click. The voice permission tells it whether you’re in a voice call, and the ids of its channel and community. If such a plugin also has the network permission, the prompt warns that it can send when you use Fluxer and which voice channel you’re in to its servers.

Read the capability reference if you want the exact technical limits.

Changed code needs a new review

Importing an update clears enabled/trusted state. This prevents an update from silently inheriting your approval of older code. Review the new permissions even if the plugin has the same name.

Only grant permissions for a plugin you intend to use. If its behavior surprises you, disable it and check its source or contact its author.