-
Notifications
You must be signed in to change notification settings - Fork 3
English Configuration
Safe defaults are stored in core/config.js. Restart autoDoIt after editing
that file. A later GitHub update may overwrite local changes, so keep a copy of
custom values.
| Setting | Default | Purpose |
|---|---|---|
schedulerTickMs |
1000 |
Scheduler base tick |
failedTaskRetryMs |
15000 |
Delay after a failed launch |
lightweightModeHomeRam |
32 |
Lightweight-phase lower bound |
fullModeHomeRam |
128 |
Minimum full-operation baseline |
dashboardMinimumHomeRam |
32 |
Automatic dashboard RAM threshold |
overviewStatsEnabled |
true |
Efficiency block in Bitburner's Overview |
The real full-operation target is also calculated dynamically from all installed modules.
| Setting | Default |
|---|---|
autoUpdateEnabled |
true |
autoUpdateIntervalMs |
15 * 60_000 |
autoUpdateRepository |
"ame824/autoDoIt" |
autoUpdateBranch |
"main" |
| Setting | Default | Purpose |
|---|---|---|
hackMoneyFraction |
0.10 |
Target fraction per hack batch |
growMoneyThreshold |
0.75 |
Money is rebuilt below this level |
securityTolerance |
5 |
Allowed distance above minimum security |
A small beginner save may intentionally use only foodnstuff or another early
server. The manager evaluates profit, chance, time, security, and thread cost;
more rooted servers mainly provide worker RAM and are not automatically better
money targets.
Important defaults:
- Cloud servers begin at
2GiB. - During normal operation, cloud servers may use up to 15% of current money.
- During RAM focus, cloud servers and Hacknet each retain 1% per pass.
- Unused infrastructure budget is banked up to 15%.
- Home RAM can use up to 25% while expanding and protects a reserve.
- Hacknet normally uses 5%.
- Stocks use 10%; gang equipment, sleeve augs, and other smaller systems have their own restricted budgets.
These limits prevent one module from consuming all augmentation or progression funds.
minimumAugsBeforeInstall: 5
augmentationMoneyReserve: 1_000_000Normal augmentations are collected and installed in batches. Each queued NeuroFlux level counts separately toward the threshold even though the game UI combines all levels into one row. Darknet labyrinth rewards are installed immediately because their progression requires it.
casinoEnabled: true
casinoMinimumMoney: 1_000_000
casinoMaximumBet: 100_000_000
casinoTargetEarnings: 10_000_000_000Set casinoEnabled: false to disable visible blackjack automation and its
save/reload opening phase.
ipvGoEnabled: true
ipvGoBoardSize: 9
darknetEnabled: true
darknetAutoStormSeed: trueOpponent order, worker limits, scan intervals, labyrinth step cap, and the
STORM_SEED safety delay are configurable in the same block. To play Darknet
exclusively by hand, set darknetEnabled to false.
exploitsEnabled: falseExploit automation is completely disabled by default. Players who want
automatic Source-File -1 handling must deliberately change this value to
true. This still does not permit the risky save edit; every scheduler
launch additionally requires an explicit --agree-exploit-risk.
-
preferredCityFactionsdetermines which incompatible city faction is preferred. -
companyTargetsandjobFieldscontrol applications and company work. -
bitNodeOrderdefines the Source-File-oriented route. Automation may still force BN4 until SF4.3 is reached.
run autoDoIt.js --lang de
run autoDoIt.js --lang en
You can also click DE/EN in the Control Center. The selection is stored in
a data file and applies to notices and toasts as well.
run autoDoIt.js --darknet-console
The switch is stored in /data/autoDoIt-darknet-console.txt, so it remains
active after augmentation resets and automatic updates. The console opens only
on the Darknet page. Disable it with:
run autoDoIt.js --no-darknet-console
Install and start it directly with:
run git-pull.js --start --darknet-console
© ame824 · grz-gamerz.de · Repository · Deutsch · English
- Übersicht
- Installation
- Control Center & RAM
- Module
- Konfiguration
- Forks & Urheberrecht
- Manuelle Schritte & Risiken
- BitNode-Zielmatrix
- Fehlerbehebung
- Architektur & Tests
- Overview
- Installation
- Control Center & RAM
- Modules
- Configuration
- Forks & attribution
- Manual steps & risks
- BitNode goal matrix
- Troubleshooting
- Architecture & testing