I still haven't actually automated purchasing servers. (Though I know if I switched to a more aggressive, RAM hungry, hacking strategy, target selection would be important again.) This makes timing co-ordination way easier, and it seems to be so RAM efficient that, most of the time, I don't have to be too picky about target selection early on.
Bitburner any way to automate manually hack code#
It takes a bit of code to make it work, but the biggest optimization I've made so far is to care as little as possible about where a given task is running: if I need 4 threads-worth of weaken() targeting joe's, it doesn't matter if coming from joe's, csec, or home (well, cores on home might affect things slightly, but I've decided that's a small enough effect to ignore). Some of those scripts are one-offs (like copying relevant scripts to every server you don't need root access on the destination server to scp() files to it!) others launch " daemons", like breakerDaemon.js, which continually checks my available port-opening tools and nuke()s new servers when it can, and hackDaemon.js, my monolithic, central hack-coordinator. My init.js (aliased to simply init) just has an array of objects describing what other scripts to run and what args to pass them. I'm sure I can optimize my priorities a little better to simply go faster, what are your thoughts? What's your order of priorities?
Spread the computing power of the next 20 purchased servers out among the higher class targets sleep profit? Passively do hacking contracts for target faction while buying all remaining port hacks on the darkweb and cracking the rest of the net. Use initial return to fund server purchase script at relevant RAM level, while manually researching 1st port hack to hasten target faction hacking/rep early.įor 1st 5 purchased servers, distribute all 0-port server hack scripts among all purchased servers so they're staggered, reducing downtime for regrowth, eg each server is running multiple scripts targeting each 0-port target instead of all threads draining and then regrowing a single target all at once. Nuke all 0-port servers, run weaken/grow/hack scripts targeting all said servers from upgraded home, use hacked server power to hasten weaken/grow progress on "joesguns" for fast initial return. Run the script from your home server to hack n00dles. ascend.js - (Requires SF4) A nearly-fully-automated way to ascend. This script is far from optimal, but it will help you out a lot the first couple of days. Some scripts are meant to be manually run as needed. Last night I booted it up, set faction hacking contracts to running. I'm assuming you have the 'early-hack-template.script' from the tutorial, but if you don't you can find both the NS1 and NS2 versions of this script here in the documentation. I need direction to plan my scripts for, and so far as I can tell, my main goals might be broken down as follows: Its probably too late to fix this bug anyway, so I wont open an issue now. Even before my 1st Augment restart, I realized I wanted to automate the beginning steps as much as possible, as I will be doing this often, and it covers a lot of ground.
0 kommentar(er)
