README.md: add clarification and extra information.
[?]
Oct 11, 2020, 12:11 AM
VTCBEUHDJI5KDQNFQ6AF2QXDM7KDEQVBNXJKNY3UQAKQNE7CJV2QCDependencies
- [2]
5TPN2FMTlib_ls.js: minor refactor. rm.js: add. README.md: update. - [3]
2WOLGB42README.md: update. kill.js: fix argument parser. lshw.js: add `-p` option. increase information given. main.js: fix error message. set saner defaults. hacker.js: split some functions into "lib_time.js" and "lib_score.js". ram.js: fix. - [4]
TDRFRQLAREADME.md: fix a formatting typo and some grammatical nitpicks. - [5]
CJBGAILAadd optional `--target` parameter for `main.js`. update `README.md`. - [6]
QU6T4CIVREADME.md: place installation notes nearer to the top. - [7]
6BXWZXOGREADME.md: add some information about scheduling. - [8]
ZRPOW4ERhacker.js, lib_time.js: supress error messages. hacker.js: use `getBitNodeMultipliers`. lib_time.js: use `getStats`. README.md: update. - [9]
FBAPT2WWexecutables: dynamically load help messages. lshw.js, main.js: add options to change score correction method and score factor multipliers. README.md: update. - [10]
HLC2L3NJadd "tor.js" and "programs.js". use `minimist` for "main.js" argument parsing. - [11]
AXGQ7FMLsplit and refactor hacking logic to "hacker.js" and argument parsing and script execution logic to "main.js". update "README.md". - [12]
5DIUM5GJhacknet.js: convert from helper script to stand-alone script. main.js, README.md: update to accommodate "hacknet.js" changes. README.md: add "Troubleshooting" section and alter misleading information about required server for installation. - [13]
Y5OWMCQRall: remove unecessary uses of `exec`. refactor. main.js: add RAM reservation logic. lib_ram.js: renamed to lib_ram_server.js. README.js: update. - [14]
J7PIMHBDhacknet.js: add. main.js, README.md: update. - [15]
BKG7YVUVmain.js, hacker.js, servers.js, ram.js: refactor. - [16]
RWMZ7DVLsplit and refactor various logics. update "README.md". - [17]
V4DMWF25remove redundant preparation steps in "hacker.js". - [18]
JGNALSUQadd "cyclic_weaken.js" feature. hacker.js, main.js, libs: refactor. README.md: update. - [19]
6MBUKAG6remove unneeded functions and comments. update readme. - [20]
JS52JD4Qweaken_manager.js: add. lib_server_used.js: move to lib_ram_script. lib_ps: delete. main.js, hacker.js, lib_ram_script.js: refactor. README.md: update. - [21]
NQ22FUSWadd more options to `main.js`. update `README.md`. - [22]
HHZNTFCTremove `-t` flag for `main.js` which conflicted with the same flag for the `run` command. - [23]
CKC6UBEAREADME.md: update - [24]
2BKHJI2Sinit - [25]
3TYF4BJStarget only hackable servers. replace servers continually. - [26]
QAPXJ43Ahacker.js, weaken_manager.js: use void_copy_script_to from lib_ram_script to copy worker scripts to servers. README.md: update.
Change contents
- replacement in README.md at line 3
Scripts for the game [Bitburner](https://github.com/danielyxie/bitburner).Scripts for the game [Bitburner](https://github.com/danielyxie/bitburner). These may contain spoilers for the game and some probably won't work properly until sufficient in-game progress has been made to unlock some requirements. - replacement in README.md at line 8
Save all the `.js` files in this repository to the root directory of a rooted server (one with at least enough RAM to run "hacker.js", e.g. "foodnstuff") using the same filenames (but not including the directory names) that they currently have in this repository. If in the start of a new game or just after resetting, run `run botnet.js 0.001` to increase the RAM available for the scripts and increase the available hackable servers, then `run kill.js` (to kill any currently running scripts).Save all the `.js` files in this repository to the root directory of a rooted server (one with at least enough RAM to run "hacker.js", e.g. "foodnstuff") using the same filenames (but not including the directory names) that they currently have in this repository.At the start of a new game or just after resetting, run `run botnet.js 0.001` to increase the RAM available for the scripts and increase the available hackable servers, then `run kill.js` (to kill any currently running scripts).---## Syntax and TerminologySome understanding of the syntax and terminology used in this document may be required to be able to properly use the scripts. The following are brief explanations about these.* Flags = Parameters that turn particular features on or off.* Options = Parameters which accept a particular value.* Values delimited by square-brackets (i.e, "[" and "]") = Indicate optional parameters/values.* Values delimited by angle-brackets (i.e., "<" and ">") = Indicate required parameters/values. - replacement in README.md at line 24
Here's an overview of what the executable scripts (located in the "bin" directory of this repository) are supposed to do, as well as usage information and examples for each one:The following section is an overview of what the executable scripts (located in the "bin" directory of this repository) are supposed to do, as well as usage information and examples for each one. - replacement in README.md at line 29
* Run the helper scripts "ram.js"\* (6.6 GB), "servers.js" (8.85 GB), "tor.js"\* (3.8 GB), "programs.js"\* (3.7 GB), "botnet.js" (2.2 GB) and "weaken_manager.js" (4 GB) which should, respectively, attempt to:* Run the helper scripts (located in the "sbin" directory and aren't really supposed to be ran manually) "ram.js"\* (6.6 GB), "servers.js" (8.85 GB), "tor.js"\* (3.8 GB), "programs.js"\* (3.7 GB), "botnet.js" (2.2 GB) and "weaken_manager.js" (4 GB) which should, respectively, attempt to: - replacement in README.md at line 40
* \* = SF-4 Required for these to properly function.* \* = SourceFile-4 required for these to properly function. - replacement in README.md at line 339
* Make sure there is enough RAM (see requirements in the "Overview" section above) on the server that you ran "main.js" from and that there are no scripts running on that server before "hacker.js" has a chance to get spawned into it. Sometimes, "weaken_manager.js" will run "cyclic_weaken.js" on that server so you might need to kill any instances of it on that server before "hacker.js" is spawned.* Make sure there is enough RAM (see requirements in the "Overview" section above) on the server that you ran "main.js" from and that there are no scripts running on that server before "hacker.js" has a chance to get spawned into it. Sometimes, "weaken_manager.js" will run "cyclic_weaken.js" on that server so you might need to kill any instances of the latter on that server before "hacker.js" is spawned.