What you maybe didn’t hear is that at the same time Putin’s goverment is fighting his other enemy - people of Russia. here is where we keep track of the last run Daemon when we run a new daemon, we kill the old one.You probably know that Putin’s army is currently trying hard to find imaginary nazis in Ukraine and destroy everything it can while at it. arbitrary value added for valuating min security in a growth formula for speed/growth value. some optional values to change the behavior of this method. create an object (array) to hold our servers initialize the current scan length to 0 initialize the scan array with just this host, this provides a starting point and saves a scan() call. presume the host to be the machine this script is running on, should probably be home, but don't let it assume so. When it finds a target inside your capability with more money than your current target, it switches targets by killing your old daemon and running a new one. Some optional variables at the top allow you to run in nuke-only mode or debug mode, if you like, but these aren't currently set up as args you have to change them inside the script before you run it.ĭescription: Assembles a server list and then "works on it", with the end goal being to hack the most valuable server in the game.
Bitburner jo.msg update#
I update the post with fixes constantly and appreciate feedback The daemon does "the work".Īs with all my progression script posts, please let me know if anything borks or doesn't work as advertised. TL DR: start.script assembles all servers, nukes all servers, targets the next most valuable server within your capability with daemon.script. It's been a while since I did one of these posts but here's my new strat for general progression. Mini fix: Scheduler cost in the daemon was set at 2.6GB instead of 2.4, derp. You can uncomment them at your own peril if you have already acquired SourceFile-5 Note: this is a rather expensive function call, adding 4GB to the daemon.script's original 8.25GB costĪdded a tprint to the start script to report that it is switching targets.īitNode multipliers are in the daemon but commented out. The daemon.script now uses the new get-multipliers function instead of expecting you to adjust it by hand. Configure your mults manually to avoid this cost if you can't afford the RAM.Īdded a 0-cycle check to the daemon so it will decrease percentage-to-steal when it is too high for a single run.Īdded skip-logic so that it will recalibrate when the % isn't optimal. The get-player-multipliers function costs 4GB, which is pretty expensive for a single function - it increases the cost of a single daemon by 50%, roughly. Fix this if you use port 1 for something else
You should probably be able to start running these around 256 - 512 GB of RAM, which is easily attainable even with just hacknet nodes.ĭaemon.script wants port 1 to be used for updating percentage-to-steal by hand without changing the script, useful for active daemons that you want to control slightly more real-time. These aren't exceptionally heavy strats, comparatively. Progression Scripts - just means scripts I use to progress.