-
Notifications
You must be signed in to change notification settings - Fork 3
English Manual Steps and Risks
autoDoIt automates only functions for which the current save provides a suitable API or a sufficiently safe visible workflow. Missing requirements appear as yellow manual actions in the Control Center with an explanation.
Without BitNode 4 or Source-File 4, large parts of the Singularity API are not available. These actions may therefore require manual input at first:
- purchase Home RAM
- purchase or create TOR/port programs
- apply to the recommended company and position
- accept faction invitations and begin work
- install important server backdoors
- travel and open visible locations
The lightweight job check recommends a reachable Software position based on current skills, with IT as a fallback. Once Singularity and enough RAM are available, the normal module takes over automatically.
Bitburner does not provide an official Casino Netscript API. autoDoIt therefore operates the visible blackjack interface:
- save before playing
- play with a controlled wager
- save after a win
- reload the latest winning state after a loss
- open
Statsafter reaching the target
Keep the game in the foreground during this exclusive opening phase and expand
Bitburner's Overview so the save button is available. Set
casinoEnabled: false to disable the workflow.
Since version 2026.08.01.3, blackjack runs in fast mode: DOM state is polled
at short intervals, an unchanged maximum wager is not written again for every
hand, and the more expensive faction/offline-modal scan runs only every 25
hands or at least every two seconds. The safety rules are unchanged: every win
is saved and every loss reloads without saving.
The module is disabled by default through exploitsEnabled: false. Only after
the player deliberately changes it to true will autoDoIt attempt the
following eight entries automatically.
The exploit module automatically attempts eight entries:
- Bypass
- the undocumented Netscript function
- Rainbow
- Development Menu
- Unclickable
- N00dles
- Prototype Tampering
- Time Compression
Prototype Tampering may check for up to 15 minutes and changes only the
formatting of the number 55 while waiting.
-
Reality Alteration: pause
ns.alterReality()in the script debugger and set its localxvariable totruebefore the final check. - True Recursion: travel to New Tokyo, enter the Arcade, and finish the embedded Bitburner Classic cabinet.
-
Edit Save File: export the save, keep an untouched backup, add
"EditSaveFile"to the decoded player'sexploitsarray, and re-import it.
After Stats confirms 11 / 11, the module writes
/data/autoDoIt-source-file--1-complete.txt. The scheduler then removes that
task permanently.
run autoDoIt.js --agree-exploit-risk
Only this argument allows the Desktop version to add the final three save entries. It first saves the game, downloads an untouched timestamped backup, and validates the v3 save structure. Import uses Bitburner's visible two-stage workflow.
Keep the backup until Stats shows 11/11. Unknown save layout, unavailable
compression, missing Desktop bridge, or unexpected import controls cause the
module to stop instead of importing.
Without this argument, autoDoIt never modifies the save.
Darknet can be fully automated or played manually. To disable automatic seeders, password attempts, labyrinths, and STORM_SEED actions, set:
darknetEnabled: falseNormal backdoor tasks remain limited to important faction/progression servers; there is no automatic “backdoor every server” sweep.
Normal augmentations are installed only after enough purchases. Certain Darknet labyrinth rewards require an immediate reset and are installed at once. The scheduler restarts after a real augmentation reset and enters the appropriate opening phase.
w0r1d_d43m0n remains under the progression module's control. This allows
autoDoIt to choose the next BitNode after destruction based on missing
Source-Files and the automation strategy.
© 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