English Control Center and RAM

Control Center and RAM management

Optional Darknet console

With --darknet-console, a second smaller window runs on the right. It opens only while the Darknet map is visible, shows authentication progress, and connects the normal terminal on click. See Darknet Console for details and switches.

Control Center

Once enough Home RAM is available, ui/dashboard.js starts automatically in a separate tail window. It refreshes every two seconds by default and displays:

• money, Hacking level, Source-Files, and current city
• used and free Home RAM
• discovered and rooted servers
• operating phase, active modules, and hacking workers
• manual notices and recent activity
• auto-updater version and next-check countdown
• © ame824 · grz-gamerz.de

The DE and EN buttons in the upper-right corner switch all dashboard text, notices, blockers, and toasts. The choice persists across restarts.

Right-side Overview extension

While the dashboard is running, it adds these values to Bitburner's Overview:

• average money per second for the current run
• time since the last augmentation installation
• installed augmentations
• occupied hacking workers
• Home RAM utilization

Disable it in core/config.js:

overviewStatsEnabled: false

Window controls

run ui/dashboard.js
run ui/dashboard.js --refresh 5000
run ui/dashboard.js --no-auto-fit

The window automatically adjusts its width, height, position, and font size to the Bitburner window. --no-auto-fit retains the traditional fixed size. --no-ui on the scheduler disables only automatic dashboard startup.

Operating phases

1. Bootstrap

Below 32 GiB, the dashboard remains closed. Only the smallest foundation tasks are active:

• discover and root the network
• deploy workers
• run the low-RAM hacking manager
• lightweight Home RAM and job recommendation checks

This allows a fresh save to earn money without loading large management APIs.

2. Lightweight start

From 32 GiB onward, the dashboard, normal hacking manager, programs, Casino, Home RAM, cloud servers, Hacknet, and—when Singularity is available—jobs become eligible. At most one management module runs at a time so income workers keep their RAM.

3. Medium phase

At 50% of the dynamic full target, Home RAM expansion and fast BitNode completion receive equal high priority. Factions, backdoors, augmentations, progression, and the current BitNode's special system are released.

4. Full operation

At the full target, every applicable module becomes eligible. A module whose BitNode-adjusted RAM cost still does not fit waits silently for more free RAM.

Dynamic Home RAM target

autoDoIt calculates the next power of two that can hold the scheduler, dashboard, modules, workers, and a safety reserve. For phase-based systems (Gang, factions, augmentations, Sleeves, Bladeburner, stocks, IPvGO, and Corporation), only the largest phase worker that can run at once counts instead of the sum of every worker. The Control Center shows current RAM, medium threshold, and goal.

Automatic Home upgrades require BitNode 4 or Source-File 4. With SF4 level 1, the external Singularity RAM multiplier can require the player to raise Home manually to roughly 64 GiB once before the purchase module can run itself.

Budget logic

Below the medium threshold, Home RAM has primary purchase priority. Hacknet and cloud servers still retain 1% of current money per pass. Unused allocations are banked up to a safe 15% ceiling so upgrades costing more than one allocation do not remain blocked forever.

Normal operation uses higher configurable budgets. Augmentation funds and required reserves are protected before infrastructure purchases.

BitNode strategy

The automation-first route begins with BN1 → BN4 and repeats BN4 until Source-File 4.3 removes the external Singularity RAM penalty. It then discovers missing Source-Files in configured order before raising already-owned files. The projected reward of the current BitNode is included before choosing the next destination.

Quiet Terminal

Success and routine information go to the Control Center. The Terminal is reserved for errors, real manual blockers, updater output, and an explicitly requested self-test.