Not at all! In fact, this game is made with beginners in mind. Also, you'll want to refer to MDN Web Docs, and other JavaScript tutorials in case you get stuck while programming your scripts.
These are just a part of the filename. There is no explicit command to create them, rather files with the same prepending "directory" string are bundled together.
Short answer: Time-consuming for minimal benefits.
Long answer: Backdooring a server takes a certain amount of time, and the duration is dependent on your hacking level and the given server's at the time of sending backdoor command.
Given the number of servers in the network and how often you have to do so after installing augments, it is ill-advised to perform such potentially lengthy tasks unnecessarily.
It is only possible with an endgame ability, or via exploits.
EHTs (Early Hacking Templates) can somewhat benefit from this at very late stages of the game where the player's hacking level is so high a few threads of ns.hack() can take all money of even strongest servers within the network.
However, targeting multiple servers is not viable for batchers in particular due to the fact such algorithms do not suffer from over-hacking (a loose term that describes a targeted server being drained of all reserved money).
When you run a script, you spawn a "process" that runs your code. With each process, you can specify a number of threads (default to 1).
"Thread" is simply a multiplier applied to the effect of some actions (e.g., hack, grow, weaken). Using more threads multiplies the effect, but it also multiplies the RAM cost of running the script.
No, in fact the game is run in JavaScript which is single-threaded.
No, the project does not take donations.
If you still want to donate, go donate blood to your local blood bank or donate to the Electronic Frontier Foundation or Médecins Sans Frontières
The best way to get help is to join the official discord server. People of all skill levels will be able to give you hints and tips.
Yes, just export the save file from the options menu & import it in the other platform.
You may have created an infinite loop with no sleep. You'll have to restart the game by killing all scripts.
- On Browser: Stick
?noScriptat the end of the URL - On Steam:
- In the menu, "Reloads" -> "Reload & Kill All Scripts".
- If this does not work, when launching the game, use the kill all scripts option.
To maintain compatibility with the web browser version, the save game is not stored as a file on your filesystem. It lives inside the localStorage of the WebKit instance. Export the save (and back it up!) in the option menu.
Due to a limitation with the way Steam tracks the game, if you launch an external link (such as documentation), Steam may keep tracking the game as "Running" even after it is closed. Simply close the web browser to fix this.
Right-click the game in your Steam library, then go into "Manage" -> "Browse Local Files". The game can be launched directly from that location if you're having issues with Steam.
If the game is installed on a network drive, it will fail to start due to a limitation in Chromium.
If you cannot move the game to another drive, you'll have to add --no-sandbox to the launch options. In your Steam Library, right click the game and hit "Properties". You'll see the "launch options" section in the "General" window.
The game is built natively. Do not use Proton unless native does not work.
When launching the game, you will be prompted with three options. If the standard launch does not work, you may attempt the --disable-seccomp-filter-sandbox or --no-sandbox launch options. If this still does not work, the game should be able to start by launching it directly or through the terminal. See "How do I get to the game files?".
Logs (using electron-log)
You may want to access the logs to get information about crashes and such.
- on Linux:
~/.config/bitburner/logs/main.log - on macOS:
~/Library/Logs/bitburner/main.log - on Windows:
%USERPROFILE%\AppData\Roaming\bitburner\logs\main.log
Config (using electron-store)
Configuration files can be found in the application's data directory.
- on Linux:
~/.config/bitburner/config.json - on macOS:
~/Library/Application\ Support/bitburner/config.json - on Windows:
%USERPROFILE%\AppData\Roaming\bitburner\config.json