Skip to content

English

ame824 edited this page Aug 1, 2026 · 2 revisions

autoDoIt – English documentation

autoDoIt is designed to guide a Bitburner v3 save from the early game through BitNode progression. It detects the current state, enables only suitable modules, and reports prerequisites that still require player input.

Documentation

  1. Installation – normal and low-RAM download, launch options, and updates
  2. Control Center and RAM – interface, operating phases, RAM goals, and budgets
  3. Modules – all tasks, workers, and special systems
  4. Configuration – switches, budgets, ordering, and language
  5. Manual steps and risks – Source-File 4, Casino, SF‑1, and deliberately gated actions
  6. Troubleshooting – RAM issues, updates, blocked modules, and self-test
  7. BitNode goal matrix – expected behaviour, observable milestones, and warning signals from BN1 to BN15
  8. Architecture and testing – scheduler, modularity, files, and test strategy

Core principles

  • Modules are loaded only when their work is due and enough RAM is available.
  • Missing APIs produce actionable guidance instead of endless error output.
  • Home RAM, cloud servers, and Hacknet grow through controlled budgets.
  • The network is discovered, rooted, and used for hacking workers.
  • Source-Files and fast BitNode completion receive high priority.
  • Routine information stays in the Control Center so the Terminal remains quiet.

Target version

The project follows the stable Bitburner v3 NS interface.

The game and its APIs continue to evolve. After a new Bitburner release, allow the auto-updater to check for changes and run the self-test if anything behaves unexpectedly.

Clone this wiki locally