Module Catalog

What is on this page

Module Catalog in the sidebar is where modules are installed, switched on and off, rolled back and removed. It holds two screens: Built-in — everything the installer brought, and Add-ons — the rest, downloaded from straimer.com when you ask for them.

Every module you have sits on one of those two screens as a card: the name, a small badge with the kind of module (connector, widget, settings-ui and the like — internal words that stay English in every language), the description, the version, and the buttons for what can be done with it. An installed module also shows Module is running or Module is off — background work is paused with a switch beside it.

Refresh, top right, re-reads the list. The server's answer is kept for about a minute, so a press right after your connection changed can hand back the same picture.

Installing a module

1. Open Module Catalog → Add-ons. Built-in has nothing to install — those modules are already here.
2. Find the card and press Install. It reads Installing… while the package is downloaded, checked and unpacked; a second or two is normal.
3. A module installed for the first time is switched on: its page appears in the sidebar and its tiles become available on the control panel. Its background work begins after strAImer is restarted, so restart the app if you have just installed something that has to work on its own — a platform connector, for one.

Installed means the files are on this computer, not that the app has heard of the module. Settings moved from another computer arrive without files, so the catalog offers Install for a module whose settings are already here — and picks those settings up once it is installed.

Turning a module on and off

The switch is on the module's card, on both screens. Off stops the module's background work, and it also takes the module's page out of the sidebar and its tiles off the control panel. That is the usual reason a section "disappears": nothing was deleted, the switch is off.

If the module's own page is open at that moment, a strip appears on it — Module is off — background work is paused, with a Where to turn it on button leading back to this card.

Built-in modules are switched off the same way as add-ons. Switching off deletes nothing: files, settings and platform tokens stay where they are.

Updating

A card with a newer version says Installed: v1.2.0 and, after an arrow, v1.3.0 available; the button becomes Update. The same updates are gathered into one list on Settings → Updates — that page is described in the guide "Updates".

An update can exist on the site and not be offered here, and there are two ordinary reasons:

• The new version needs a newer application. It is listed under Require a newer app version on the Updates page — update the app first.
• The module belongs to a bundle. It has no card of its own — the update waits on the bundle's card, because a bundle is updated as a set.

Rolling back

The app keeps the two most recent packages of each module, so an updated module offers Roll back to 1.2.0 — the version you had before this one. It happens immediately, without a confirmation, and the module's settings are kept.

A built-in module has a second way back, and it needs no cached package: Restore bundled version throws the downloaded copy away and returns the version that came with the app. The button appears once that module has been updated at least once — without a downloaded copy there is nothing to throw away.

An add-on with nothing in the cache has neither button — the version you have is the only one on the disk.

Uninstalling

Only add-ons can be uninstalled, with the bin icon on the card. It asks first, and it means it: the module's settings and stored platform access go with it, and that cannot be undone.

Built-in modules have no bin — their files live inside the program itself, and the app refuses to delete them. Switching off and Restore bundled version are what they have instead.

Bundles

Some things are not one module. The auction is an engine, three OBS overlays and five control panel tiles; apart they do nothing — an engine with no overlay shows nothing, an overlay with no engine has nothing to show. Sets like that appear in Add-ons as a single card marked bundle and install with one press.

Members install one after another, with a progress line naming each one. If one of them fails the rest still install, and the failures are listed at the end.

The line under the name says where the bundle stands. With a nine-module bundle it reads 9 modules in one install before anything is there, Bundle 1.0.0 · 9 modules once the whole set is in on the versions that release fixed, and fully installed (9 modules) for a bundle that has no releases of its own yet.

Bundle members get no cards of their own in Add-ons: install, update, rollback and removal all happen on the bundle's card.

Only part of it is installed

When some of the set is missing, the card says partially installed: 2 of 9 and the button becomes Complete install — it fetches what is missing and leaves alone every member already on the version the bundle expects. The bin is there too: a half-installed bundle can be removed like a whole one, since its modules do not work apart.

The count is made from files on disk, not from records in the app. A computer that received settings from a backup holds a record of every module and none of the files, so the bundle counts as not installed — which is the truth: there is nothing there to run.

The switch only reaches modules that are actually here, and it counts those, not the whole set: with two of nine installed and one of them running it reads 1 of 2 running. One press always takes the whole bundle to one state. Turning on a partly installed bundle starts what is present and then says Some modules are not installed here — their settings are already restored, and installing the bundle picks them up.

The set matches no release

Installing, updating or rolling back members one by one leaves a combination nobody tested together. The card then says Composition changed by hand — does not match bundle 1.0.0 and offers Restore the bundle composition, which puts every member on the version that release fixed.

The other end of the same case has no button: when every member is newer than anything the bundle has released, there is nothing to restore to, and the card says Members are ahead of bundle 1.0.0 — waiting for its next release.

Install refused

The message names the reason. The common ones:

• The module needs Core API 1.4, this app provides 1.3 — update strAImer. The module is newer than the app; update the app first, from Settings → Updates. A module like that shows Incompatible — update the app where the Install button would be.
• The package checksum does not match the registry — it is damaged or replaced / The package signature is invalid — installation refused. The download was damaged or replaced, and installation was refused on purpose. Try again; if it repeats, report it — nothing was installed, so nothing is broken.
• Could not download the package: HTTP 502 / The module registry is unavailable: HTTP 502 — the number at the end is what the server answered. Our server or the connection. Everything already installed keeps working.

Add-ons shows nothing

Without a connection to straimer.com the list of available modules cannot be shown, and the screen says so in place of the list. This does not affect installed modules — they are read from the local database and keep working, and Built-in stays fully populated. On that screen the app adds one line instead: No connection to straimer.com: updates were not checked — "no updates" and "not looked" are different things.

What this page cannot do

• Install from a file. Every package comes from straimer.com, signed; there is no way to point the app at one you downloaded yourself.
• Give you any version you like. Install fetches the newest version your app can run. The only other version reachable is the one named on the Roll back button.
• Delete a built-in module. It can be switched off, and that is the same silence, without losing its settings.
• Update one member of a bundle. The set is tested as a whole; single members are moved by the bundle card, not by themselves.
• Search, sort or filter. There is no search field, no categories and no reviews — the screens are two plain lists.
• Sell you anything. Every module here installs free. What costs credits is the AI work inside some of them — the guide "Account and Credits".
• Undo a removal. An uninstalled module can be installed again, but its settings and tokens were deleted with it.