export const array_get_files_with_string = function (

export const array_get_files_with_string = (

  string_server_source,

  string_server,

) {
  const
    array_files_with_string = [],
    string_type_substring = typeof substring;

) => {
  const string_type_substring = typeof substring;

    case "object":
      const substring_length = substring.length;
      for (
        let integer_index_substring = 0;
        integer_index_substring < substring_length;
        ++integer_index_substring
      ) {
        array_files_with_string.push(
          ns.ls(string_server_source, substring[integer_index_substring])
        );
      }
      break;

      array_files_with_string.push(ns.ls(string_server_source, substring));
      break;

      return ns.ls(string_server, substring);
    case "object":
      return substring.flatMap((string_file) => {
        return array_get_files_with_string(ns, string_server, string_file);
      });

  return array_files_with_string;
};

};

          break;;

          break;

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, run `run botnet.js 0.001` (to increase the RAM available for the scripts) 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. 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).

---
### "rm.js" (3.05 GB)
  * Removes all removable files (which excludes currently running scripts, including this one).
  * Optionally, removes only files whose names match a given regular expression.
  * Optionally, removes only files on servers whose names match a given regular expression.
  * Optionally, removes only files whose names match a given regular expression on servers whose names match a given regular expression.
#### USAGE
  `run rm.js [FLAGS ...] [OPTIONS]`
#### FLAGS
  `-h, --help`
  * Displays a help message then exits.
#### OPTIONS
  `-e, --server <REGEX>`
  * REGEX = Regular expression used for server names.
  `-f, --file <REGEX>`
  * REGEX = Regular expression used for filenames.
#### EXAMPLES
  `run rm.js`
  * Removes all removable files.
  `run rm.js -f txt --file lit`

  * Removes all files with filenames that match the regular expressions "txt" and "lit".
  `run rm.js -e home --server harakiri-sushi`
  * Removes all files from servers whose names match the regular expressions "home" and "harakiri-sushi".
  `run rm.js -f txt --file lit -e home --server harakiri-sushi`
  * Removes all files with filenames that match the regular expressions "txt" and "lit" from servers whose names match the regular expressions "home" and "harakiri-sushi".

  * [See if this discussion about the hacking strategy used answers your questions](https://old.reddit.com/r/Bitburner/comments/g2ry1t/can_someone_explain_traditional_hacking_loop/). If it doesn't, feel free to contact me through one of the channels above.

  * [See if this discussion about the hacking strategy used answers your questions](https://web.archive.org/web/20201010181949/https://old.reddit.com/r/Bitburner/comments/g2ry1t/can_someone_explain_traditional_hacking_loop/). If it doesn't, feel free to contact me through one of the channels above.