There are a lot of optimizations that I would make now if I were to write this script - when I started Bitburner, I didn't know anything about Javascript. This is the deployment script that I'm currently running. So no, It's not necessary, nor does it really matter, I just wanted to save time.

Scp works fine for updating the script on the remote hosts, it's just that remoting into each of the hosts to edit the hostname in the script, kill the process and start it again can be a little bit tedious when you have a lot of different spokes you're updating. I made a change to the ns script I use for continuous hacking/growing/weakening, the only purpose of this is to run a quick terminal script that allows me to immediately log into the remote host and edit the ns script as it exists on the remote host. Look at the ns.scp() command (literally, the same as the real-world command, only simpler) to place a local file on the remote host. Likewise, copy/paste into nano on a remote host isn't necessary. Think of it as similar to Cisco Prime or another management interface you hit the button on the management server, it manages the deployment and execution on the remote host. Otherwise, you can do remote execution of local scripts via ns.exec(). Are you trying to backdoor the target server? That's really the only reason to manage a connect script. Originally posted by helix0704:Not sure the purpose behind this.

Bitburner kill not working