ohgugl.blogg.se

1. #BITBURNER ANY WAY TO AUTOMATE MANUALLY HACK HOW TO#
2. #BITBURNER ANY WAY TO AUTOMATE MANUALLY HACK CODE#

I probably should, but I'm pretty sure I have more to gain from further refining my hacking strategy. Some scripts are meant to be manually run as needed. 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). It’s plug and play once you have the 3 tiny scripts in your home directory. Guide to Auto Farm for New Players The guide is pretty much in the code section with my attempt at documentation.

#BITBURNER ANY WAY TO AUTOMATE MANUALLY HACK HOW TO#

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. Bitburner How to Run Multiple Scripts Without Writing Scripts Decem0 Guide to Run Multiple Scripts Without Writing Scripts To save myself time between runs, I use the basic beginner while true hack() loop and manually creating it using nano as. Bitburner Basic Auto Hack Script for Beginners Decem12 Basic auto hack script that finds and automates the farming of servers.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. I need direction to plan my scripts for, and so far as I can tell, my main goals might be broken down as follows: 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.