* Make and execute a schedule containing information about when, where and how many threads (among other information) the "weaken.js", "grow.js" and "hack.js" worker scripts should be executed with.
    * Wait for a duration of time such that jobs in a new schedule will start finishing after the older schedule finishes.

    * Make and execute a schedule containing information about when, where and how many threads (among other information) the "weaken.js", "grow.js" and "hack.js" worker scripts should be executed with. The schedule is generated such that all the jobs will be ran pretty much concurrently, but will sleep for some time such that each one finishes running just after the previous one in the schedule finishes.
    * Wait for a duration of time such that jobs in a new schedule will start finishing just after the older schedule finishes.

  `run main.js -ao --no-botnet --job-cap 4000 -i harakiri-sushi -r 0.7 --steal-cap 0.5 -q normal`

  `run main.js -aof --no-botnet --job-cap 4000 -i harakiri-sushi -r 0.7 --steal-cap 0.5 -q normal`

  * Runs the script with up to 4000 jobs, targetting "harakiri-sushi", only upgrading/replacing servers when at least 0.7 of your network's total RAM is being used, stealing only up to 50% of harakiri-sushi's cash per "hack.js" job that finishes executing, and using the "mean normalised" score correction method, whilst the remaining variables are set to defaults. The "ram.js", "tor.js" and "botnet.js" helper scripts are also prevented from starting.

  * Runs the script with up to 4000 jobs per schedule, targetting "harakiri-sushi", only upgrading/replacing servers when at least 0.7 of your network's total RAM is being used, stealing only up to 50% of harakiri-sushi's cash per "hack.js" job that finishes executing, and using the "mean normalised" score correction method, whilst the remaining variables are set to defaults. The "ram.js", "tor.js" and "botnet.js" helper scripts are also prevented from starting.