Your machines

Use the same token on every PC you own. Set threads, pause, a schedule and a name for each machine from anywhere, and let the app update itself.

Same token, every PC #

Install Simhive on your other computers and paste the same token into Your token. Each shows up as you · machine and all of them count for you. Give every machine a name (This machine → Name) so you can tell them apart.

A server, a NAS or a headless box lends cores without the app: see Docker and headless.

Threads, pause, name, from anywhere #

The ⚙ gear top right opens Settings, one category per topic. Pool (also behind the Pool chip) is Your machines: every PC using your token, online or not, with a thread slider, Pause, rename and a schedule (⏱): rules like "weekdays 22:00–08:00: 11 threads" or "Sat–Sun: paused", in that machine's local time. A server that is on 24/7 can lend everything at night and a little by day. Changes apply from the next batch, from any of your machines.

Only you can do that. The pool operator sees your machines but cannot touch them unless you allow it (Who may change… in the settings).

Settings → This machine (also behind the Simhive chip) is this PC: its state, the pool connection, updates, Pause lending while you need every core, "pause by itself while World of Warcraft runs", start with Windows.

Updates #

Simhive looks for a new version at start and every six hours and asks: the Simhive chip turns amber ("update 0.6.0"), Update now is in Settings → This machine and in the tray menu. It waits for a running batch to finish, installs and restarts.

SimulationCraft follows the pool by itself. When the pool moves to a newer nightly, every machine fetches that build and reconnects. Nothing to press, and by design nobody can stay on another build: a Droptimizer split over ten machines must give one answer.

Where things are #

%APPDATA%\simhive\ holds settings.json, data\history and data\simc (the builds). Linux: ~/.config/simhive/. Uninstalling keeps them.